How To Configure UCM Survivorship Engine To Compare Base Table Attribute Modification Timestamp (S_UCM_ORG_ATGP.LAST_MOD_DT) To A Custom SDH Datetime Column? (Doc ID 1551564.1)

Last updated on JULY 13, 2017

Applies to:

Siebel Universal Customer Master - Version 8.1.1.8 SIA [23012] and later
Information in this document applies to any platform.

Symptoms

When a UCM Batch Process is used to create a new record the value inserted in column S_UCM_ORG_ATGP.LAST_MOD_DT by default is the current timestamp i.e. the timestamp the record was processed and not the value from SDH table.

The value from S_UCM_ORG_ATGP.LAST_MOD_DT is used by survivorship engine to verify if record needs to be updated or not when the comparison rule is defined as Recent or History.

If Recent rule is defined and same record has different versions in SDH table when the records are processed it won't update the record in base table for the fields defined in survivorship once the value created in S_UCM_ORG_ATGP. LAST_MOD_DT has a greater value compared to the value from SDH table (in thi case S_UCM_ORG_EXT).

E.g.

1 - Create a survivorship rule based on Recent for field Alias for example.

2 - Create two new records in S_UCM_ORG_EXT table with different values in LAST_UPD and ALIAS columns (default column used to compare dates).

3 - Process the first record (with lower LAST_UPD) value and observe the value of S_UCM_ORG_ATGP.LAST_MOD_DT that is set to current timestamp if the record is created.

4 - Process the second record and see that Alias value is not updated even that record was inserted later in SDH table.

 

Cause

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