Page Comparison

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:

The following screen should appear. Choose "Application Log":

The log is presented:

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. Since