Technical errors on the ALE Service Layer

The following errors can occur in the ALE service layer:

Outbound

IDoc Syntax Error: IDoc Status ‘07’

On transmitting or receiving IDocs the syntax of the individual IDoc is checked. The syntax is determined when the IDoc is defined, including:

An IDoc syntax check can be activated in the partner profile for an IDoc category and a certain partner and we recommend that you do so, particularly for any IDocs that you have created yourself. Otherwise this error normally only occurs in the test run. The incorrect IDocs cannot be repaired so they have to be transmitted again once the IDoc structure has been corrected in the SAP system.

Missing or Incorrect Partner Profile: IDoc Status ‘29’

To transmit an IDoc from SAP to the subsystem you must define the partner profile’s outbound processing for the IDoc category (message type) and all relevant partners. You will find a more exact description of partner profiles in the online documentation for the Implementation Guidelines (IMG). If the partner (subsystem) for the IDoc to be transmitted can not be determined, you must follow this procedure:

Errors in partner profiles normally occur in the test run.

IDoc is not transferred to aRFC on transmission : IDoc Status ‘30’

Although the partner profile has been maintained the IDoc is not transferred to the aRFC, i.e. the IDoc is structured but not sent. The relevant subsystem does not have any open entries in the RFC transaction evaluation (SM58). Although the IDoc is ready for transmission it has to be explicitly controlled.

This takes place via report RSEOUT00, which can be planned as a periodic job or started directly using the transportation menu  Logistics Sales and distribution Transportation External systems Transportation planning ALE monitoring Period.worken IDoc, ALE outbound Send .

Here the outbound mode for the relevant IDoc should be checked in the partner profile. In outbound mode ‘2’ the created IDoc is transmitted directly, in ‘4’ the IDocs are collected together and sent in defined package sizes. We recommend that the IDocs are not directly transmitted for mode ‘4’.

Status ‘30’ in the IDoc can normally only occur if outbound mode is set to ‘4’.

Inbound Processing

IDoc Syntax Error: IDoc Status ‘60’

As in outbound processing an IDoc syntax check can be activated in the partner profile for an IDoc category and a certain partner and we recommend that you do so, particularly for any IDocs that you have created yourself. Otherwise this error normally only occurs in the test run. The incorrect IDocs cannot be repaired so they have to be transmitted again once the IDoc structure has been corrected in the SAP system.

Missing or Incorrect Partner Profile: IDoc Status ‘63’

On receipt of an IDoc in SAP the partner profile inbound processing for IDoc category (message type) and the transmitting partner must be defined. You can read a more detailed description of partner profiles in the online documentation for implementation guidelines (IMG). If the partner profile and therefore the inbound method for the recipient IDoc cannot be found, then the application cannot be activated and the IDoc remains in the system with open status. In this situation follow this process:

Errors in partner profiles normally occur in the test run.

IDoc is not transferred to application on receipt: IDoc Status ‘64’

Although the partner profile has been maintained, the received IDoc is not processed and flagged as incorrect, i.e. the application is not controlled for processing this IDoc. Although the IDoc is ready for transmission to the application, you must set the application for processing the IDoc explicitly.

This takes place using report RBDAPP01, planned as a periodical job or can be started directly using the transportation menu  Logistics Sales/distribution Transportation External systems Transportation planning ALE monitoring Period.work IDoc, ALE outbound Send .

As in transmission you check the processing type in the partner profile. In processing ‘1’ the IDocs are transferred immediately after receipt to the application for processing. In processing ‘3’ and partly in ‘2’ we recommend that processing is not controlled directly but explicitly.

Status ‘64’ in IDoc normally only occurs in conjunction with processing ‘3’ and ‘2’.

Logical Errors in the Application

The errors described below, which occur in the application, are related to an inbound IDoc in SAP. For message the IDoc to be transferred is structured in the application, so that any missing or incorrect Customizing settings will be noticed directly in SAP processing, e.g. while creating planning requests.

During inbound processing of an IDoc in the SAP system the following errors could occur in the application:

The incorrect IDoc is flagged with status ‘51’ .

Missing or Incorrect Customizing Settings in the SAP System

The received IDoc cannot be processed because certain IDoc data have not been maintained in the system. For example a shipment category is transferred from a shipment registered in the subsystem that has not been defined in the SAP system. You must implement the Customizing settings accordingly for these errors; posting the incorrect IDoc can be controlled afterwards. Posting can either take place from the inbox of the person responsible or via report RBDMANIN, which can be planned as a periodic job or started via the transportation menu  Logistics Sales/distribution Transportation External systems Transportation planning ALE monitoring Period.work IDoc, ALE outbound Resend .

Missing or Incorrect Data in the IDoc

If the data in the received IDoc are incomplete, you must decide whether the incorrect IDoc should be transmitted again or whether it is possible or appropriate to carry out corrections in the SAP system. You can also correct the IDoc directly. It is possible to do this using the IDoc Editor but this should only be used for exceptional cases.

Similarly to errors in Customizing settings the incorrect IDoc can also be posted from the inbox of the user responsible or via report RBDMANIN.

Errors through Locked Objects

There are often problems in SAP processing with blocking individual objects. More than one access to an SAP object will cause processing to terminate, with an error note for the blocked object. This error is treated like all other errors in IDoc processing. The user does not have to do anything to solve it as repeated processing at a later point will solve the problem automatically. This means that using background processing (periodic job) from report RBDMANIN can be used for posting the IDoc. The parameter ‘error status’ in this report uses the error message ID to delimit posting for certain errors; in this case only for each error message related to a blocking error.

Important Error Notes in Inbox

For each error described a work item is created and put in the inbox of the user responsible. Work items are used for certain important error notes that are either transmitted directly from the subsystem or structured in IDoc processing in the application. Work items are not to be used for re-starting IDoc processing from the inbox but to inform the user of a conflict or to forward an important message from the subsystem to the SAP system. The message is transferred to SAP by IDoc SYSTAT01.

Unlike errors, the work item for notes is not processed from the inbox but completed.