TID Management for SAP Outbound

The SAP Suite adapter for JCo 3.x manages transactional integrity for SAP outbound to confirm that an IDoc packet has been successfully processed once. The SAP system assigns a transaction ID (TID) for every IDoc packet. The SAP Suite adapter for JCo 3.x stores the TID in the Sterling B2B Integrator database in the SAP_TID table.

Each row in the following table represents a separate IDoc packet and contains the following rows:

Table 1. Transactional Integrity Parameters
Row Description
DATE_TIME Date and time at which the TID table was updated.
TID (PK) SAP transaction ID.
STATE
  • CREATED – Received the TID from SAP
  • EXECUTED – Received the IDoc message with the TID and committed the transaction
  • ROLLEDBACK – Rolled back the IDoc packet from further processing
  • CONFIRMED – IDoc message has been queued for processing and the transaction has been committed
WFID ID of the business process that has been started for processing the IDoc packet.
INSTANCE_NAME (PK) Name of the service configuration of the SAP Suite adapter for JCo 3.x that received the IDoc packet.
It is important that entries in the TID table can only be modified by the service configuration of the SAP Suite adapter for JCo 3.x that created the entry. This includes the following guidelines:
  • Multiple RFC servers connected to the same Program ID can share the same TID management.
  • RFC servers from different configurations of the SAP Suite adapter for JCo 3.x (and different Program IDs) cannot share the same TID management.