Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

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.

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.

  • No labels