Create the table, structures, and triggers that collects entity changes and passes
them to the Syclo Framework.
- Create a transparent table ZEPM_BUSINESSPARTNERS_EX in the data
dictionary with the following fields and include structures:
- Include field MANDT, and data element
- Include Syclo standard structures
- Set structure /SYCLO/CORE_EXCHANGE_KEY_STR as a key.
- Find the appropriate trigger location by analyzing the data object update
The trigger location is code that runs whenever a business partner record is
updated. Within this code, execute an Exchange Framework Implementation (EFI) to
collect changes and pass them to the Syclo Exchange Framework. There are multiple
ways you can identify and implement trigger locations: user exit, Business Add-Ins
(BAdI), explicit or implicit enhancement framework implementation, business
transaction events, or gateway service operations for create, update, and delete.
Given the key role of EFI to construct the data-pair list of before and after images
of the SAP data object being changed, the EFI trigger spot determines the extent and
scope of change detection.
- Create the EFI Advanced Business Application Programming (ABAP) include file, using
transaction SE38; name the file
The include file contains the programming logic for before and after image
construction. For this example, determine the business partner details before and
after the update. You need not track all field changes—this is controlled by the EFI
implementation. If required, you can extend change tracking to related tables, such
as sales orders.
- Use transaction SE24 to create a subclass of the
CL_CORE_EX_HANDLER_BASE base class; name the subclass