S_UCM_ADDR_PER.ADDR_ID Column Is Null/Blank When Using [Address Type] Field Or Different Field In The CIFAccount* IO "Account_Business Address" IC User Key (Doc ID 2052728.1)

Last updated on SEPTEMBER 04, 2015

Applies to:

Siebel Universal Customer Master - Version 8.2.2.14 [IP2014] and later
Information in this document applies to any platform.

Symptoms

SIEBEL VERSION:
---------------
Siebel 8.2.2.14 Patch 5 on Linux RHEL 6(84 bit)

ISSUE STATEMENT:
----------------
Customer has a requirement to check Address Type Code (ADDR_TYPE_CD) along with Address line 1 (ADDR) while inserting addresses through UCM batch job. Thus, customer added the Address Type Code field in User Key in CIFAccount* IOs and executed UCM job again. When having this additional user key field, the Account and Address inserted successfully into the Siebel UCM application, but the ADDR_ID column is not getting populated in table S_UCM_ADDR_PER. As a result of ADDR_ID not getting populated, they are not able to retrieve the Primary Address details against Account or Contact if they have multiple addresses.

WHERE IT HAPPENED:
-------------------------------
The issue happens in customer's Development environment.

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

1. Edit the Siebel CIFAccount* IO objects in Siebel Tools, these are objects used by UCM transaction processing.

2. For the CIFAccount* IO objects > expand to the "Account_Business Address" IC > User Key > select the user key > add the [Address Type Code] field to the user key list. Recompile the modified objects into the Siebel srf file, update the SRF file to the Siebel server.

3. Run UCMBatchProcess task to process data from the SDH table, the Account and Address will get inserted. However, the S_UCM_ADDR_PER.ADDR_ID column is null when checking it via the database query.

BEHAVIOR PATTERN:
-------------------------------
The behavior occurs consistently, where in when the Address Type Code is added to the user key, the S_UCM_ADDR_PER.ADDR_ID column is no longer populated.

EXPECTED BEHAVIOR:
-------------------------------
The expected behaviour is that the S_UCM_ADDR_PER.ADDR_ID column gets populated and should not be influenced by changes to the address user key fields.

WHAT IS WORKING:
------------------------------
The S_UCM_ADDR_PER.ADDR_ID column is populated correctly when the Address Type Code field is removed from the User Key.

LOSS OF FUNCTIONALITY / BUSINESS IMPACT:
------------------------------
Since the S_UCM_ADDR_PER.ADDR_ID column is not getting populated, they are not able to retrieve the Primary Address details against Account or Contact if they have multiple addresses.

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