Technical Errors in the ALE Service Layer (SAP Library - IDoc Interface: EDI Application Scenarios (BC-SRV-EDI))

Technical Errors in the ALE Service Layer

The following errors can occur in the ALE service layer:

IDoc syntax error

Missing partner profile

IDoc was not transferred to aRFC when it was sent

IDoc was not transferred to the application when it was received

Output

IDoc syntax error: IDoc status ‘07’

The syntax of the individual IDocs is checked when these are sent and received. The syntax is defined when the IDoc is defined:

Individual segments of an IDoc type

Relationship between the individual segments

Number of segments that can be sent in an IDoc

The syntax check for the IDoc can be activated in the partner profile for an IDoc type and a specific partner. We recommend that you activate this check in particular for IDocs that you have generated yourself. This error usually only occurs in the test mode. The IDocs in error cannot be repaired and must, therefore, be sent again after the IDoc structure has been corrected in the SAP system.

Missing or incorrect partner profile: IDoc status ‘29’

When an IDoc is sent from the SAP system to the external system, the output of the partner profile for the IDoc type (message type) and all relevant partners must be defined. A detailed description of the partner profiles can be found in the online documentation of the Implementation Guide (IMG). Proceed as follows if it is not possible to determine the partner (external system) for the IDocs to be sent:

The partner profile must be maintained again

All IDocs that are waiting to be sent must be activated so that they can be sent again. Since, in the case of this error, a work item for the standard task ‘ALE/EDI: Error handling (outbound)’ is initiated and placed in the inboxes of the appropriate users, retransmission of the IDoc in error must be activated from the inbox. When the IDoc in error is transmitted again, it is assigned the status ‘31’ and is copied to a new one to which the data from the partner profile is added and which is then transferred to the aRFC.

Errors in the partner profiles usually only occur in the test mode.

The IDoc was not transferred to aRFC when it was sent: IDoc status ‘30’

The IDoc was not transferred to the aRFC although the partner profile has been maintained, i.e. the IDoc was generated but not sent. Furthermore, it is not possible to find an open entry in the RFC transaction evaluation (/nSM58) for the appropriate external system. The IDoc is indeed ready to be sent but transmission of the IDoc must be activated explicitly.

This is carried out by means of the report RSEOUT00 which is scheduled as a periodic job or can be started directly via the WM menu Environment ® External systems ® ALE functions ® Periodic processing ® Process ALE outbound IDocs.

The output mode for the appropriate IDoc should be tested in this case in the partner profile. In output mode ‘2’ the generated IDoc is sent directly, in output mode ‘4’, the IDocs are grouped together and sent in defined packet sizes. Mode ‘4’, therefore, specifies explicitly that the IDocs are not to be sent directly.

Status ‘30’ in the IDoc can usually only occur in conjunction with the output mode ‘4’.

Input

IDoc syntax error: IDoc status ‘60’

As with the output, the syntax check for the IDoc can be activated with the partner profile for an IDoc type and a specific partner. It is advisable to activate this check. This error usually only occurs in the test mode. The IDocs in error cannot be repaired and must, therefore, be sent again after the IDoc structure has been corrected in the transmitting system.

Missing or incorrect partner profile: IDoc status ‘63’

The input of the partner profile for the IDoc type (message type) and the transmitting partner must be defined when an IDoc is received by the SAP system. A detailed description of the partner profiles can be found in the online documentation of the Implementation Guide (IMG). If it is not possible to find the partner profile for the IDocs that have been received and thus the input method, the application for processing the IDoc cannot be activated and the IDoc remains in the system with its status set to open. Proceed as follows if this error occurs:

the partner profile must be maintained again

all open IDocs must be reactivated so that they can be processed. Since, in the case of this error, a work item for the standard task ‘ALE/EDI:Error handling (inbound)’ is initiated and placed in the inboxes of the appropriate users, the application for processing the IDoc in error must be reactivated from the inbox.

Partner profile errors usually only occur in the test mode.

The IDoc was not transferred to the application when it was received: IDoc status ‘64’

The IDoc that was received has not been processed and has not been identified as being in error although the partner profile has been maintained, i.e. the application for processing this IDoc was not activated. The IDoc is indeed ready to be transferred to the application, the application for processing the IDoc must, however, be activated explicitly.

This is carried out by means of the report RBDAPP01 which is scheduled as a periodic job or can be started directly via the WM menu Environment ® External systems ® ALE functions ® Periodic processing ® Process ALE outbound IDocs.

The check carried out on the processing type in the partner profile when the IDoc was sent must also be performed here. In processing mode ‘1’ the IDocs are transferred to the application for processing as soon as they are received. Processing mode ‘3’ and, to a certain extent mode ‘2’, therefore clearly specify that processing is to be activated explicitly and not carried out directly.

Status ‘64’ in the IDoc can usually only occur in conjunction with mode ‘3’ and ‘2’.