UCM Contact HE Constituent Address Type Is Not Being Set Using The UCM_HE_ADDR_TYPE LOV Type Value

(Doc ID 2325400.1)

Last updated on NOVEMBER 06, 2017

Applies to:

Siebel Data Quality - Version 16.5 [IP2016] and later
Information in this document applies to any platform.

Symptoms

PRODUCT VERSIONS:
------------------------------
SIEBEL VERSION: Siebel 16.5
SIEBEL APP O/S: Linux x86

ISSUE STATEMENT:
----------------------------

EIM was used to load Contact and its address information in the UCM SDH table, S_UCM_CONTACT for the contact and S_UCM_ADDR_PER for the contact address. When the UCMBatchProcess runs and executes, it inserts a new contact record with the data from the S_UCM_CONTACT table, but it is not inserting any new address for the contact, it is not retrieving any address information from the UCM S_UCM_ADDR_PER record for the contact.

STEPS TO REPRODUCE:
---------------------------------
The behaviour occurs as follows:

1. Use EIM to load a record into the S_UCM_CONTACT for the contact and S_UCM_ADDR_PER for the contact address.

2. Run UCMBatchProcess task on the contact SDH record in the above S_UCM_CONTACT table.

3. The contact record is inserted but it has no address information.

EXPECTED BEHAVIOR:
-------------------------------
The expected behaviour is that the contact is inserted and the address is also inserted and associated to the contact.

WHAT IS NOT WORKING/ACTUAL RESULTS:
-------------------------------------
The actual result is that UCM does not find any address for the contact from the S_UCM_ADDR_PER table and thus no address was inserted.

LOSS OF FUNCTIONALITY / BUSINESS IMPACT:
--------------------------------------------
Due to this, the address information is not being processed as expected/desired.

Changes

 

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