All synchronous adapter notifications (the RFC listener notification, ALE listener notification, and the routing notification) support the forward Confirm event feature. This is a useful feature in scenarios where a transactional request is received by Adapter for SAP and then forwarded to an SAP system via tRFC, and where the client wants to achieve transactional behavior from end to end.

If the Forward Confirm event flag is activated, Adapter for SAP tries to forward the Confirm TID event, which is triggered by the tRFC protocol, to the same destination where the document went. What happens then depends on the transport used.

Transports that have an SAP system or other Integration Servers as the destination confirm the TID on the destination system. This may become important in those cases where the final receiver of the message is another SAP system. For each tRFC it receives, an SAP system keeps an entry in a check table (ARFCRSTATE) to protect against duplicate processing of the same document. Only after the sender has indicated via Confirm TID that this document will never again be posted, the receiving system can safely remove this entry from its check table.

Up to version 4.6, Adapter for SAP would not forward this Confirm TID event, so the check table in the receiving SAP system would keep growing. This feature enables a clean-up of this check table in scenarios like:

if the external client uses the service pub.sap.client:confirmTID.

The following two simplified dynamic model diagrams show how Adapter for SAP handles requests differently depending on the setting of the $action parameter. They show a combined view of three possible scenarios: