Capturing the Change

The base product has provided the Audit plug-in spot on the MO to allow for processing to be called by the system upon detecting a change to an MO. The framework calls the algorithm defined on this plug-in spot in the event a change to the MO has been detected. The base product comes with a generic change data capture algorithm F1-GCHG-CDCP that makes use of this plug-in spot to create the sync request BOs. The Sync Request BO MO Option is used to define these sync request BOs. The generic algorithm loops through this list of BOs and instantiates them, if no instances of those BOs yet exist in the initial state. The MO and primary key used for these sync requests will be the MO being modified and its primary key.

Sometimes it is necessary to instantiate a sync request whose MO is different from the MO being modified. As an example, a change to the Person record may need to instantiate an SA sync request. In this case, your implementation will have to create your own Audit algorithm that captures this idiosyncratic logic. For examples on how this is done, please refer to the Oracle Utilities CCB-MDM Integration Implementation Guide.