Processing Logical IDoc Errors in
EWM 
Use
If you receive an IDoc from the non-SAP system in the SAP system, the following errors can occur in Extended Warehouse Management (EWM):
● Missing or incorrect Customizing settings in EWM
● Missing or incorrect data in the IDoc
● Error Due to Blocked Objects
Logical IDoc errors do not occur in IDoc outbound from the SAP system, because EWM responds to missing or incorrect Customizing settings beforehand.
The system flags the incorrect IDocs with status 51.
Missing or Incorrect Customizing Settings
Cause
The SAP system cannot further process the received IDoc in the following circumstances:
● You have not defined certain data for the IDoc in the SAP system.
Along with the IDoc, you transmit a stock movement with a warehouse process type from the non-SAP system, which is unknown in the SAP system.
● The received IDoc data does not match the Customizing settings in the SAP system.
The stock movement reported by the external system is defined for immediate confirmation. However, the warehouse process type in EWM does not permit immediate confirmation for this stock movement.
Procedure
...
1. You correct the relevant Customizing settings.
2. You subsequently post the incorrect IDoc
Either from the inbox of the assigned user
Or via report RBDMANIN, which you schedule periodically in background processing.
Missing or Incorrect IDoc Data
If the data in the received IDoc is not complete, you decide whether the system should resend the incorrect IDoc, or whether a correction in the SAP system is useful and possible.
● You make the corrections to the IDoc using the IDoc editor.
Only correct the IDoc using the IDoc editor in exceptional cases.
● You can subsequently post IDocs of the type WMIVID01 on reporting physical inventory data and correct the data in the relevant transaction.
Procedure
You subsequently post the incorrect IDoc
● Either from the inbox of the assigned user
● Or via report RBDMANIN, which you schedule periodically in background processing.
Error Due to Blocked Objects
If blocking problems occur in the SAP system, IDoc processing leads to an error.
If there are concurrent attempts (by different users) to access the same SAP object, the system terminates processing, with an error note for the blocked object.
Procedure
You do not need to intervene manually. Schedule report RBDMANIN for periodical background processing.
You can use the Error Status parameter in the report to specify that the system automatically reposts IDocs with the error message describing a lock error.
Important Error Notes in Inbox
For the errors listed above, the
system creates a workflow work item in the inbox of the person responsible.
For more information, see 
Rule Resolution in
Exception Handling.
Workflow work items are also suitable for important notes
● Which the external system sends to the SAP system
● Which occur during IDoc processing in EWM.
These workflow work items
● Inform the user about a problem or a conflict situation
● Send on important messages from the external system to the SAP system.
The external system transmits the messages via message type WMINFO.
If the system can no longer confirm a warehouse task or handling unit because the confirmation has already been made, the non-SAP system triggers an internal message. Ensure that the system stores this information, since the confirmation can only be made by the non-SAP system.