During communication between the non-SAP system and Extended Warehouse Management (EWM), errors can occur in the ALE layer. The following errors can occur:
● Syntax error in the IDoc
● Missing partner profile
● The system did not transmit the IDoc to an asynchronous Remote Function Call at sending
● The system did not transmit the IDoc to an application at receipt
On sending and receiving IDocs, the system checks the syntax of the individual IDocs. The IDoc definition specifies the syntax of the IDoc. This syntax can include:
● The individual segments of an IDoc type
● The relationship between the individual segments
● How many segments you can send in an IDoc
Incorrect syntax in IDocs often occurs during tests only. IDocs with incorrect syntax cannot be repaired. You correct the IDoc structure in the SAP system and send the IDoc again.
We recommend only switching on the syntax check during testing of IDocs created yourself. You activate the syntax check via the partner profile for one IDoc type and one particular partner. To do this, on the SAP Easy Access screen, choose Tools ® ALE ® ALE Administration ® Runtime Settings ® Partner Agreement.
When you send IDocs from the SAP system to the non-SAP system, you must have defined the outbound section of the partner agreement for the message type and all relevant partners. To do this, on the SAP Easy Access screen, choose Tools ® ALE ® ALE Administration ® Runtime Settings ® Partner Agreement.
If the system cannot find the partner (that is, the connected partner system) for sending the IDocs, proceed as follows:
● Define the missing partner profile.
● You retrigger sending of all pending IDocs that you could not send before.
For this error, the system triggers a workflow work item for the standard task Output: Error processing with IDoc and sends a message to the inbox of the corresponding user.
You trigger subsequent sending of the IDocs that contained errors from the inbox.
During this subsequent sending, the system flags the incorrect IDoc with the status 31, and copies the IDoc into a new IDoc, to which the system adds the data from the partner agreement and transmits to the asynchronous RFC.
Errors in partner profiles only occur in the test run.
Although you have defined the partner agreement and the system has constructed the IDoc, the system cannot transmit the IDoc to the asynchronous RFC. The system cannot send the IDoc. and there is no official entry in the RFC valuation (/nSM58) for the relevant subsystem.
You trigger transmission of the IDoc using report RSEOUT00. Choose Tools ® Business Communication ® IDoc Basis ® Test ® Outbound from IDoc, to manually start the report, or schedule a regular background job for the report.
● Outbound processing mode 2: The system sends the IDoc immediately
● Outbound processing mode 4: The system collects IDocs that have been created and sends them in packets of a predefined size.
IDocs are not intended to be sent directly.
Status 30 in the IDoc can only occur if outbound mode is set to 4.
On sending and receiving IDocs, the system checks the syntax of the individual IDocs. The IDoc definition specifies the syntax of the IDoc. This syntax can include:
● The individual segments of an IDoc type
● The relationship between the individual segments
● How many segments you can send in an IDoc
Incorrect syntax in IDocs only occurs during tests. IDocs with incorrect syntax cannot be repaired. You correct the IDoc structure in the SAP system and send the IDoc again.
You activate the syntax check via the partner profile for one IDoc type and one particular partner. We recommend that you activate the syntax check for all IDocs you create yourself.
When you send IDocs in the SAP system from the non-SAP system, you must have defined the inbound section of the partner agreement for the message type and all relevant partners. To do this, on the SAP Easy Access screen, choose Tools ® ALE ® ALE Administration ® Runtime Settings ® Partner Agreement.
If the system cannot find the partner (that is, the connected partner system) for receiving the IDocs, proceed as follows:
● Define the missing partner profile.
● You retrigger receiving of all pending IDocs that you could not process before.
For this error, the system triggers a workflow work item for the standard task Input: Error processing with IDoc and sends a message to the inbox of the corresponding user.
From the inbox, you trigger the subsequent transmission of the IDocs which contained errors.
Errors in partner profiles only occur in the test run.
Although you have defined the partner agreement and the system has constructed the IDoc, the system cannot transmit the IDoc to the application.
You trigger transmission of the IDoc using report RBDAPP01. To do this, plan a regular job in background processing for this report.
● Processing mode 1: The system transmits the IDoc immediately after receipt in the application
● Output mode 3: The system collects received IDocs.
IDocs are not intended to be transmitted directly to the application.
Status 64 in the IDoc can only occur in conjunction with processing mode 3 and output mode 2.