Developing business objects using dynamic transaction

The Dynamic Transaction function module is a mapping tool and dynamic code generator. It uses SAP's Call Transaction API to get data into an SAP application. Also, it stores static definitions of Batch Data Communication (BDC) sessions by object/verb combinations. Before the BDC data is passed to a Call Transaction, the business object attribute values are mapped into the BDC session. At the completion of the call transaction, the resulting key value is set in the appropriate value of the business object, and all messages from the call transaction are logged.

Note:
If the Call Transaction fails, the connector does not store a BDC session in SAP for reprocessing. Obsolete versions of the connector agent did store a BDC session; however, using the stored session led to inconsistencies in cross-referencing and request processing.

The Dynamic Transaction function module builds a BDC session to do a call transaction by combining the BDC defined in the Dynamic Transaction table, YXR_CHANGE, and the values from the incoming business object. When the Dynamic Transaction function module is called, the following steps are performed:

  1. All entries are retrieved from YXR_CHANGE, where:

    object name = objectName and verb = objectVerb

  2. Field input values are mapped from the business object into the BDC session based on the attribute name.
  3. BDC sessions are processed using Call Transaction.
  4. Key values are captured, Call Transaction messages are logged, and the key is set in the business object.
Note:
Before you can generate a business object definition, you must create a WebSphere business object using the IBM WebSphere InterChange Server Connector Tools Window (YXR1).

Copyright IBM Corp. 1997, 2003