/
Inbound idocs statuses

Inbound idocs statuses

Owned by proaxia
Last updated: Apr 02, 2025
3 min read

The incoming IDOCs are created when the objects are to be created/updated at SAP side (triggered by the Cloud). Once the incoming IDOC has been successfully processed, it should have the Status 53.

 

If automatic processing is disabled, IDOCS are kept in status 64 and can be processed manually in BD87. If inbound message is processed successfully, the IDOC status is 53, in case of error it is 51. Failed IDOC can be and usually should be reprocessed.

image-20250402-080437.png


Detailed overview of the statuses set during the lifetime of the IDOC:

Status

Description

60

IDOC has been created (normally this status is set for a very short time, very soon the next status should be set)

64

IDOC ready to be transferred to the application (normally this status is set for a very short time, very soon the next status should be set)

62

IDOC passed to the application (normally this status is set for a very short time, very soon the next status should be set)

53

The IDOC has been properly processed. To see more details, you should double click at the status 53 and choose “Application Log”. You will find this log also if you call the transaction SLG1 directly, but if you follow this procedure you are directed immediately to the right log. By analyzing this log, you can find out, which document has been created at SAP side (e.g. the Activity Number for the incoming Activities). Be aware, that all objects in SAP are created/updated by the same communication user (configured in the Message Broker) – you are not able to distinguish which person has created the object (in contradiction to the documents created by the users using SAP GUI).

51

The IDOC has not been properly processed. To see more details, you should double click the status 51. The following screen should appear. Choose "Application Log":


The log is presented:


By analyzing the log, you can decide what was the reason of the failure and eventually reprocess the IDOC with the standard transaction BD87.

56 and 68

If the FSM Cloud Connector transporter does not receive confirmation for a message after a certain amount of time (around 15 minutes), the transporter resends the same message. Such timeout should not happen if connection and traffic is well optimized. Duplicated messages will be identified and receive status 56. Sincestatus:(S4)PACG 200 SP6 they’re then automatically set to status 68.

 

Related content

If you'd like to help us improve the documentation, please provide your feedback using the communication channels listed /wiki/spaces/PFCC/pages/1561427969. Learn about support possibilities here.