Parent-Child Relationship For SDH Tables S_UCM_CONTACT And S_UCM_CON_CHILD Not Working
Last updated on AUGUST 15, 2016
Applies to:Siebel Universal Customer Master - Version 18.104.22.168  and later
Information in this document applies to any platform.
On : 22.214.171.124  version, Universal Customer Master
Parent-Child relationship for SDH Tables S_UCM_CONTACT and S_UCM_CON_CHILD not working
Customer sends inbound request to Siebel UCM OM component to create contact records into Siebel UCM. When Siebel UCM creates the contact record, it will save the inbound request message into the Siebel S_UCM_CONTACT table as the historical record. According to the Siebel application's schema for UCM Contact, it has:
Foreign Key Table: S_UCM_CONTACT ; to the ROW_ID column
Thus, it would be S_UCM_CON_CHILD.PAR_ROW_ID = S_UCM_CONTACT.ROW_ID
However, when Siebel UCM creates the data, it is not associating the S_UCM_CON_CHILD.PAR_ROW_ID = S_UCM_CONTACT.ROW_ID. Instead, it is setting S_UCM_CON_CHILD.PAR_ROW_ID to the base table S_CONTACT.ROW_ID column instead.
Parent-Child relationship for SDH Tables S_UCM_CONTACT and S_UCM_CON_CHILD should work
The issue can be reproduced at will with the following steps:
1. Set up UCM application.
2. Enable the UCM workflow processes and the PersonService web service.
3. Generate the WSDL file for the PersonService web service.
4. Load the PersonService WSDL file into SOAPUI.
5. Trigger the proper request
The issue has the following business impact:
Due to the incorrect value being populated into the field/column, it impacts the customer's Table Space reclaim activity where they are Purging data from these tables but need to avoid orphan records and parent-child relationship integrity.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms