Error Analysis Technical Errors in the ALE Service Layer The following errors can occur in the ALE

service layer: Syntax error in the IDoc Missing partner profile IDoc not transferred to the transactional Remote Function Call (tRFC) at transmi ssion IDoc not transferred to the application at receipt Outbound Processing Syntax error in the IDoc: IDoc status 07 On transmitting or receiving IDocs, the syntax of the individual IDoc is checked . When the IDoc is defined, the syntax, which includes the following, is determi ned: The individual IDoc category segments The relationship between the segments How many segments can be transmitted in one IDoc or how often an individual segm ent may occur in one IDoc An IDoc syntax check can be activated in the partner profile for an IDoc categor y and a certain partner. We recommend that you activate this check, particularly for any IDocs that you have created yourself. Otherwise, this error normally on ly occurs in the test run. The incorrect IDocs cannot be repaired so they have t o be transmitted again once the IDoc structure has been corrected in the SAP sys tem. Missing or Incorrect Partner Profile: IDoc status 29 To transmit an IDoc from SAP to the subsystem, you must define the partner profi les outbound processing for the IDoc category (message type) and all relevant par tners. You will find a more detailed description of partner profiles in the onli ne documentation for the Implementation Guidelines (IMG). If the partner (subsys tem) for the IDoc to be transmitted can not be determined, you must proceed as f ollows: Maintain the partner profile All IDocs for transmission have to be set for retransmission. Since this error t riggered a work item for the standard task ALE/EDI: error processing (outbound) and sent it to the relevant users inbox, the incorrect IDoc also has to be set fo r subsequent transmission from the inbox. On subsequent transmission, the incorr ect IDoc is flagged with status 31 and copied to a new one which is enhanced wit h data from the partner profile and transferred to the asynchronous Remote Funct ion Call (aRFC). Errors in partner profiles normally only occur in the test run. IDoc not transferred to asynchronous Remote Function Call (aRFC) on transmission : IDoc status 30 Although the partner profile has been maintained the IDoc is not transferred to the aRFC. In other words, the IDoc is structured but not sent. The corresponding subsystem does not have any open entries in the RFC transaction evaluation (SM5 8). The IDoc is ready for transmission but must be explicitly controlled. This occurs via report RSEOUT00, which can be planned as a periodic job or start Sales and distribution Trans ed directly using the transportation menu Logistics portation External systems Transportation planning ALE monitoring Periodic proces sing Process ALE outbound IDocs Send. Here, the outbound mode for the relevant IDoc should be checked in the partner p rofile. 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 tha t the IDocs should not be directly transmitted in mode 4. Status 30 in the IDoc can normally only occur if outbound mode is set to 4. Inbound Processing Syntax error in the IDoc: 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. We recommend that you activa te this check. Otherwise, this error normally only occurs in the test run. The i ncorrect IDocs cannot be repaired so they have to be transmitted again once the

IDoc structure has been corrected in the sending system. Missing or Incorrect Partner Profile: IDoc status 63 On receipt of an IDoc in SAP, the partner profile inbound processing for IDoc ca tegory (message type) and the transmitting partner must be defined. You will fin d a more detailed description of partner profiles in the online documentation fo r the Implementation Guidelines (IMG). If the partner profile and therefore the inbound method for the recipient IDoc cannot be found, then the application cann ot be activated and the IDoc remains in the system with open status. For this ty pe of error, proceed as follows: Maintain the partner profile All IDocs open for transmission must be set for retransmission. Since this error triggered a work item for the standard task ALE/EDI: error processing (inbound) and sent it to the relevant users inbox, the incorrect IDocs new profile data for the processing application also has to be executed from the inbox. Errors in partner profiles normally only occur in the test run. IDoc not transferred to the application at receipt IDoc status 64 Although the partner profile has been maintained, the received IDoc was not proc essed and flagged as incorrect, which means that the application is not controll ed for processing this IDoc. Although the IDoc is ready for transmission to the application, you need to explicitly set the application for processing the IDoc. This occurs via report RBDAPP01, which can be planned as a periodic job or start ed directly using the transportation menu Logistics Sales and distribution Trans portation External systems Transportation planning ALE monitoring Periodic proces sing Process ALE outbound IDocs Post. As in transmission, you check the processing type in the partner profile. In pro cessing 1, the IDocs are transferred immediately after receipt to the applicatio n for processing. In processing 3 and partially in 2, we recommend that processi ng be explicitly rather than directly controlled. Status 64 in the IDoc can normally only occur in conjunction with processing 3 a nd 2. Logical Errors in the Application The errors described below, which occur in the application, are related to an in bound IDoc in SAP. The IDoc that is to be transferred is structured in the appli cation in such a way that the system will immediately notice any missing or inco rrect Customizing settings in SAP processing (while creating planning requests, for example). During inbound processing of an IDoc in the SAP System, the following errors may occur in the application: Missing or incorrect Customizing settings in the SAP System Missing or incorrect data in the IDoc Error due to blocked objects The incorrect IDoc is flagged with status 51. Missing or incorrect Customizing settings in the SAP System The IDoc that was received cannot be processed because certain IDoc data has 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 make the Customizing settings accordingly for these errors; po sting the incorrect IDoc can be controlled afterwards. Reposting can either take place from the inbox of the person responsible or via report RBDMANIN, which ca n be planned as a periodic job or started via the transportation menu Logistics Sales/distribution Transportation External systems Transportation planning ALE m onitoring Periodic processing Process ALE inbound IDocs Repost. Missing or incorrect data in the IDoc If the data in the received IDoc is incomplete, you must decide whether the inco rrect IDoc should be transmitted again or whether it is possible or appropriate to carry out corrections in the SAP system. You can also make corrections direct ly in the IDoc. It is possible to do this using the IDoc Editor but this should only be used for exceptional cases. Like errors in Customizing settings, the incorrect IDoc can also be posted from the inbox of the user responsible or via report RBDMANIN.

Error due to blocked objects There are often problems in SAP processing with blocking individual objects. Mul tiple attempts (by different users) to access the same SAP object, processing wi ll be terminated, with an error note for the blocked object. This error is treat ed like all other errors in IDoc processing. The user does not have to do anythi ng to solve it, since reprocessing at a later point will solve the problem autom atically. This means that using background processing (periodic job) in the RBDM ANIN report can be used for reposting the IDoc. The error status parameter in th is report uses the error message ID to limit 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 use r responsible. Work items are used for certain important error notes that are ei ther transmitted directly from the subsystem or structured in IDoc processing in ternally 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 transferr ed to SAP by IDoc SYSTAT01. Unlike errors, work items for notes must be completed rather than processed from the inbox. More information about Inbound statuses 64 -> 62 : There is no way to distinguish automatic call from manual call (BD20, RBDAPP01) Though an IDoc may contain partner profile errors, we may force inbound processi ng (status becomes 62), but then an error will happen again RSEINB00 program to process IDocs from a file BD20 transaction (RBDAPP01 program) to process IDocs in status 64. If you want f uture IDocs to be processed immediately, change partner profile customizing (WE2 0). RBDINPUT program: status 51: BD73 / RBDMANIN status 56, 61, 63, 65: BD84 / RBDAGAI2 status 60: RBDSYNEI status 62: IDocs remaining in status 62 is abnormal. Use program RBDCHST A ([Note 92552 - IDocs-Status 62 cannot be processed||http://service.sap.com/sap /support/notes/92552]), so that to change their status back to 64 and process th em again status 64, 66: BD20 / RBDAPP01 status 68: WPIE / RBDAGAIE More information about Outbound statuses RBDOUTPU program: status 02, 04, 05, 25, 29: BD83 / RBDAGAIN status 26: RBDSYNEO status 30: WE14 / RSEOUT00 status 32: WPIE / RBDAGAIE -> 03 : IDocs are sent to the tRFC queue. 03 -> 12 : use BD75 transaction (RBDMOIND program). Answer from Rainer Hbenthal i n SDN forum: "Idocs with with status 03 are transferred to the tRFC queue. This does not mean that they are sent out, they may stuck up on that queue (e.g. rece iver system is down) in that queue. BD75 checks if it can find the idoc in that queue. If so, it is not beeing send and status remains on 03. If it is not on th e t-rfc queue, the systems considers that this icon is sent and change the statu s to 12. You can check the tRfc queue with SM58 and initiate resending by right click cho osing execute LUW. in BD75 you can check "unsent idocs" and you will get a similar list." Note 189887 - ALE: Help report to search for IDocs sent twice: program ZDUPLICAT EIDOC Miscellaneous

RC1_IDOC_SET_STATUS program to change IDoc status. Exists since 6.10 Monitor for Inbound and Outbound: BD87 / RBDMON00 to restart erroneous IDocs Archiving: RSEXARCA archives IDocs. They must be in an archivable status (not possi ble to archive IDocs in status 30 or 64, ie waiting to be processed). RSEXARCL to reload IDocs from archive to the database. Status will be ei ther 35 (outbound) or 71 (inbound). WE47 to change STACUST table; see [Note 26564 - IDoc: Can status values be defined?||http://service.sap.com/sap/support/notes/26564] RSECSTAT include contains constants for status RC1_IDOC_SET_STATUS