Overview of outbound idocs statuses

The outgoing IDOCs are created when:

the certain events in SAP occur (e.g. the Equipment has been created/changed, the Customer master data has been created/changed, the Activity has been created/changed etc.),
the certain object has been sent explicitly to the Cloud by the Administrator (e.g. the transaction /PACG/ECM_USERMASTER has been used to send the Users master data to the Cloud).

Once the IDOC has been successfully sent to the Cloud, it should have the status 41:

The following Statuses are set during the IDOC lifetime:

Status	Description
01	The IDOC has been created (normally this status is set for a very short time, very soon the next status should be set)
30	The IDOC is ready for dispatching (normally this status is set for a very short time, very soon the next status should be set).
03	The IDOC has been passed to the port. The port in case of FSM Cloud Connector is the Web Service call to the Message Broker. All the IDOCs are configured in the way that they are to be sent immediately. However, the IDOCs are sent to the cloud via the queue (the transaction SMQ1). The queue name for the outgoing IDOCs is /PACG/ECM_STD_OUT. If there are the IDOCs with this status (usually during full synchronization) they are usually waiting in the queue for being sent. So, during the full synchronization (which can take even hours) we can observe the IDOCs with this status As long as the outgoing queue is not blocked and the amount of records in the Queue is changing (increasing in the beginning of the synchronization and decreasing in later stage, when no new IDOCs are create and the existing are sent) it means no malfunction.
29	Error in ALE Service. It means that the IDOC has not been sent. Usually it means that the connection between SAP and the Message Broker is broken.
18	The IDOC has been sent to the Message Broker (the connection between the SAP and the Message Broker is established, the Web Service call was successful). The process of sending the data from the SAP perspective is almost finished (the data has been successfully sent using the Web Service). However out of that Status we cannot claim, whether it is already in the Cloud or not. If the IDOCs have the Status 18 for a very long time it most probably means, that the connection between the Message Broker and the Cloud is broken. In that case you have to monitor the Message Broker.
41	The confirmation from the Cloud has been sent by the Cloud to the Message Broker, the Message Broker has sent this information to the SAP, the Web Service at SAP side has been successfully called, and the function at SAP side has successfully updated the IDOC in question. The process of sending the IDOC has been completed. The IDOCs with the Message Type = /PACG/ECM_RESENDEND and /PACG/ECM_CONFIRM are exception here – they are never confirmed, they never get the status 41 – they will always stay with the Status 18 (it is by design).