Incoming IDOCs

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 51:

The following Statuses are 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: 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.

Message Broker

Besides message monitoring in SAP as described in Data Extractor paragraph above, it is also possible to track the communication on the Message Broker level. Message Broker produces log files that contain runtime information related to the message processing. The messages are generated with the following log levels:

DEBUG – the most verbose level, containing detailed information of message processing, including content and metadata of XML messages being sent between SAP and Cloud
INFO – contains entries for messages transferred, so that it is possible to track message exchange, but no detailed information (i.e. no message content)
WARN – entries generated for non-critical problems
ERROR – entries generated for problems that prevent message exchange (problem to connect to SAP or Cloud, application misconfiguration, etc.)

It is recommended, that the logging is configured at least at a WARN level, so that all unusual situations are visible in the logs. In a starting phase of using FSM Cloud Connector it may be desirable to set logging level to DEBUG, even if causes big files to be generated and brings some performance overhead. The logging parameters (e.g. path to the log files, logging level, etc.) can be set in Message Broker configuration file. By default, logging is set to a DEBUG level and files are generated in c:\tmp\e4c.log\ directory.

User administration

User accounts are synchronized between SAP and Cloud. As such, in order to enable a mobile user, the user's account has to be prepared in SAP first, then synchronized to the Cloud, where a license can be assigned to the user. These steps are described in more details below. It is important to note, that during user synchronization the user's SAP password is not transferred to the cloud.