UCM Batch Process

This workflow is mainly called by the UCM Batch Manager server component (alias UCMBatchProcess) to process the queued Insert requests. It looks for queued records in the Source Data History table, and then it calls Oracle Customer Hub (UCM) Data Quality Manager to cleanse and match the records. Depending on the match results, it then calls Transaction Manager to execute the insert or update operation, or store the cleansed version for later deduplication processing. This workflow displays each service call as individual workflow steps to allow easier debugging.

You can enable the UCM Batch Process workflow to allow multiple view modes. For example you can use the All View mode which allows you to locate potential records which, though created by different users with different levels of visibility, are still the same record. If you do not specify All View mode, then the most restrictive visibility is applied to the record by default. For information on configuring All View mode, see Siebel System Requirements and Supported Platforms on Oracle Technology Network.