Siebel Business Process & Functionality (MOSC)

MOSC Banner

UCM 8.1.1.7 remove suspect status

edited Jan 14, 2016 11:46AM in Siebel Business Process & Functionality (MOSC) 2 commentsAnswered ✓

Hi experts

I'm experiencing the following issue:

Given a Contact record AA exist in OCH, then a new contact AA comes from the external system and as it is matching it is saved as Suspect record in the dedup table and s_party_ucmx table.

When the Data Steward merges the two records with a Survivorship Rule making the new one winning against the existing one, the status of the resulting record still remains Suspect even thought the record is moved to the base table from the dedup table, the oldest is in the history table and everything looks fine in the ui.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

SBL Business Process Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center