Select language:
Entering content frame!--a11y-->

Function documentation Processing Technical IDoc Errors 

Use

During communication between the external system and the Warehouse Management system (WMS), technical problems can occur in the ALE layer. The following errors can occur:

  • Syntax error in the IDoc
  • Missing partner profile
  • The IDoc was not transferred to a synchronous Remote Function Call on transmission
  • The IDoc was not transferred to the application on receipt

Error During Outbound IDoc Processing

IDoc status 07: Syntax error in IDoc

On sending and receiving IDocs, the system checks the syntax of the individual IDocs. The IDoc definition defines the syntax of the IDoc. The syntax includes:

  • The individual segments of an IDoc type
  • The relationship between the individual segments
  • How many segments can be sent in one IDoc

Normally, incorrect syntax in IDocs only occurs in testing. IDocs with incorrect syntax cannot be repaired. You correct the IDoc structure in the SAP system and send the IDoc again.

Recommendation

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 a one particular partner.

IDoc status 29: Missing or incorrect partner profile

To send an IDoc from the SAP system to the external system, you must define outbound parameters for the message type and all relevant partners.

For more information, see Interfaces ® External Systems ®

Configure Warehouse Management ® Communication R/3 -> External System ® Maintain Partner Profile in the Implementation Guide for Warehouse Management.

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.
  • Resend all existing IDocs, which the system has not yet been able to send.

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.

On subsequent transmission, the incorrect IDoc is flagged with status 31 and copied to a new IDoc, which is enhanced with data from the partner profile and transferred to the asynchronous RFC.

Note

Errors in partner profiles normally only occur in the test run.

IDoc status 30: The IDoc is not transferred to the asynchronous RFC

Although the partner profile is defined and the IDoc has been constructed, the IDoc cannot be transferred to the asynchronous RFC. The IDoc is not sent, and there is no official entry in the RFC valuation (/nSM58) for the relevant subsystem.

You trigger transmission of the IDoc using report RSEOUT00. To start the report manually, choose Tools ® Business Communication ® IDoc Basis ® Test ® Outbound Processing from IDoc (/nWE14), or schedule a regular job in background processing for this report.

Check the outbound processing mode for the IDoc in the partner profile.

  • 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 normally only occur if outbound mode is set to 4.

Error During Outbound IDoc Processing

IDoc status 60: Syntax error in IDoc

On sending and receiving IDocs, the system checks the syntax of the individual IDocs. The IDoc definition defines the syntax of the IDoc. The syntax includes:

  • The individual segments of an IDoc type
  • The relationship between the individual segments
  • How many segments can be sent in one IDoc

Normally, incorrect syntax in IDocs only occurs in testing. IDocs with incorrect syntax cannot be repaired. You correct the IDoc structure in the SAP system and send the IDoc again.

Recommendation

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, particularly for any IDocs that you have created yourself.

IDoc status 63: Missing or incorrect partner profile

To receive an IDoc in the SAP system from the external system, you must define the outbound partner profile for the message type and all relevant partners.

For more information, see Interfaces ® External Systems ®

Configure Warehouse Management ® Communication Ext. System -> R/3 ® Maintain Partner Profile in the Implementation Guide for Warehouse Management.

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.
  • Trigger receipt of all existing IDocs, which the system has not yet been able to process, again.

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 normally only occur in the test run.

IDoc status 64: IDoc is not transferred to the application

Although the partner profile is defined and the IDoc has been received, the IDoc cannot be transferred 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.

Check the processing mode for the IDoc in the partner profile:

  • 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 normally only occur in conjunction with processing mode 3 and output mode 2.

 

 

Leaving content frame