Siebel Business Process & Functionality (MOSC)

MOSC Banner

Preferred Language Code (S_CONTACT.PREF_LANG_ID)

in Siebel Business Process & Functionality (MOSC)

In UCM we load data both through batch and through real-time web services. In both cases, the value provided is the 3-digit language code (e.g. "ENU", "FRA", "ITA", etc). This is per the OOTB configuration mention in the previous post. For batch, the S_UCM_CONTACT.PREF_LANG_ID is populated via the UCMContactSourceDataAndHistory->Contact->Preferred Language Code field. This then populates the S_CONTACT.PREF_LANG_ID via the CIFContactInsert->Contact->Preferred Language Code field. For real-time, the S_CONTACT.PREF_LANG_ID is populated via the SwiPersonIO->Contact->Preferred Language Code.

Given the way the join is configured/defined, when it (the join) is resolved no language record is found because it expects a ROW_ID to be provided. My question is whether or not anything will break by changing the OOTB join specification to use the following:

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