You display XML messages to track inbound and outbound messages in the IDoc adapter. This gives you an overview of which messages were sent or received by the adapter. IDoc tracking (advanced functions) enables you to track IDocs and display them in the remote system.
S_XMB_MONI with ACTVT = 03
S_IDOCMONI with ACTVT = 03
On the XML Messages in IDoc/RFC Adapter screen, you can select and list XML messages using various selection criteria.
The transaction ID is only unique for each sender or receiver.
The following selection criteria are available:
Selection Criterion | Entry |
---|---|
System ID |
Name of port in IDoc adapter |
IDoc number |
Number of the IDoc from the IDoc control record |
IDoc Object |
Name of a customer enhancement or IDoc basic type |
Direction |
Direction of IDoc transfer |
Choose Execute.
The system sorts and lists the XML messages according to the time that they were created. Messages that were received and sent as IDocs are listed together and are identified by the same message ID.
The system also uses the list of messages to summarize the number of messages displayed for each direction. In addition to the specified selection criteria, the system also displays the client .
Monitoring in the Integration Engine displays additional information about the selected message. You can do the following:
More information: Displaying Message Versions
More information: Monitoring XML Messages , Integration Engine
This is only applicable when the message direction is outbound.
Performing IDoc Tracking
Fields for the IDoc number, status, and XI message ID are added to the list.
The message line shows which monitor is displayed.
Outbound:
You can display the IDoc remotely in the IDoc monitor of the SAP system.
More information: IDoc Display
You can display the message remotely in the monitor for processed XML messages.
More information: Monitor for Processed XML Messages
You can display the qRFC outbound queues.
You can display the queue.
Inbound:
Tracking searches for the RFC destination for the sender system for each port. If no RFC destination is found, the partner number and partner type specified in port maintenance are used. This information is used to call the IDoc monitor remotely.
More information: Manage IDoc Metadata Ports