UCM Type Code for custom child object is not updated from 'Batch' when executing UCM Account Batch Data Management Workflow.

(Doc ID 1069882.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Universal Customer Master - Version 8.0 SIA [20405] and later
Information in this document applies to any platform.
***Checked for relevance on 13-Jun-2013***



Product: Siebel Universal Customer Master
Version: 8.1.1 SIA [21111]
OS platform: Microsoft Windows (32-bit)
DB platform: 2003
Env: dev

Statement of Issue:
The application has been configured to load child objects for the primary SDH object Account. A new account is loaded into S_UCM_ORG_EXT and UCM_TYPE_CD is set to 'Batch'. A new child record is loaded into S_UCM_ORG_CHILD and UCM_TYPE_CD is set to 'Batch'.

A Workflow Process Batch Manager (WPBM) task is started to execute the workflow UCM Account Batch Data Management Workflow to transfer the data from the SDH tables to the UCM base tables. The account and the child record are correctly inserted into the base tables. The account's UCM Type Code (S_UCM_ORG_EXT.UCM_TYPE_CD) is updated to Source-Insert. The problem is that the child's UCM Type Code (S_UCM_ORG_CHILD.UCM_TYPE_CD) is not updated from Batch.

Expected Behavior:
S_UCM_ORG_CHILD.UCM_TYPE_CD is updated from Batch to the appropriate value (Source-Insert, Source-Upsert, Incomplete etc.).

Actual Behavior:
S_UCM_ORG_CHILD.UCM_TYPE_CD is not updated from Batch.

Business Impact:
The UCM_TYPE_CD column in S_UCM_ORG_CHILD would be useful to determine what happened when a child record was processed by the WPBM.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms