An SAP transaction ID is contained within the ALE wrapper business
object. You can use transaction ID support to ensure once-only delivery of
ALE objects.
You can make use of transaction ID support for ALE processing.
The most common reason for using transaction ID support is to ensure once
and only once delivery of data. Install the transaction RAR file (CWYAP_SAPAdapter_Tx.rar)
to use this feature, and import that RAR file into your adapter project before
enterprise service discovery is performed.
Note: The SAP transaction ID property
is always generated by enterprise service discovery; however, it is supported
only for outbound operations when the CWYAP_SAPAdapter_Tx.rar version of the
adapter is used.
The client application must determine how to
store the SAP transaction ID and how to relate the SAP transaction ID to the
data being sent to the adapter. When the events are successful, the client
application should not resubmit the event associated with this TID again to
prevent the processing of duplicate events.
- If the client application does not send an SAP transaction ID with the
business object, the adapter returns one after executing the transaction.
- If the client application has an SAP transaction ID, it needs to populate
the SAP transaction ID property with that value before executing the transaction.
The SAP transaction ID can be used for cross referencing with
a global unique ID that is created for an outbound event. The global unique
ID is something you can create for managing integration scenarios.