SXMS_REFRESH_ ADAPTER_STATUS: Adapter Status of Messages

Description

Report SXMS_REFRESH_ADAPTER_STATUS refreshes the adapter status of messages that call the IDoc adapter or the ccBPM adapter.

IDoc adapter:

The XI message contains a payload with IDoc XML, which is converted into IDocs and sent by tRFC or qRFC to the recipient. After successful conversion, the XI message is assigned status 3. A tRFC/qRFC function module call of is generated, which transports the IDocs as data to the recipient. The RFC call to the recipient is executed asynchronoulsy decoupled by XI message processing. During this time the XI message is assigned adapter status 1 “not final”, and therefore cannot yet be reorganized. If the RFC call to the recipient is successful, the RFC call is deleted from the RFC database table, but the XI runtime is not notified of this. For this reason, report SXMS_REFRESH_ADAPTER_STATUS must be scheduled. It checks whether the generated RFC calls were processed successfully for all XI messages with outbound IDoc adapters. If this is the case, the adapter status of the XI message is changed from 1 to 6, “final”.

ccBPM adapter:

The XI message contains a payload that is sent to the ccBPM adapter that calls a business workflow, and the XI message is assigned status 3. This workflow is processed asynchronously decoupled. During this time the XI message is assigned adapter status 1 “not final”. Once the workflow has been processed successfully, it is assigned a final status. Report SXMS_REFRESH_ADAPTER_STATUS has to be scheduled to check whether the associated workflow has a final status for all XI messages with outbound ccPBM adapters. If this is case, the adapter status of the XI message is changed from 1 to 6 “final”. This change is a required prerequisite for deleting this XI message later.

Execution

When the report is started, there are two options with which the report can be run:

Timespan “Check messages, that are not older than [min] minutes”. The report checks all XI messages that from the start time are not older than [min] minutes. This can reduce the runtime of the report significantly.
Time points: Check XI messages created in time interval from “start of time calculation” to “current time point”. The report checks all XI messages with a non-final adapter status in the specified time interval. This can result in a long runtime for many messages with a non-final adapter status.

The option “time points” is the default setting.

Comments

We recommend you schedule report SXMS_REFRESH_ADAPTER_STATUS as a background job with the default option “time points”.
It is not possible to refresh only those XI messages with a specific adapter type.
If the adapter status is set to final, and an XI acknowledgment has been requested, it is created at the same time. In this case, the option “time span” is recommended to create acknowledgments promptly.