Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Enterprise Service Automation (ESA) - PSFT (MOSC)

EEX: THE PREFERRED NAME Questions

Apr 16, 2024 5:55PM edited Apr 16, 2024 5:56PM in Enterprise Service Automation (ESA) - PSFT (MOSC) 6 commentsAnswered ✓

QUESTION:
after implementing Bug ID 35704145 and 35613512: EEX: THE PREFERRED NAME, we noticed that:

KNOWN_FIRST_NAME, KNOW, KNOW_MIDDLE_NAME, KNOW_LAST_NAME fields appeared in PERSONAL_DATA, containing FIRST, MIDDLE and LAST_NAME data. Could you let us know how they get populated?
After enabling the HCM IB integration via PERSON_BASIC_SYNC (NAME_DISPLAY) we noticed that:

data get's wiped out from KNOWN_FIRST_NAME, KNOW, KNOW_MIDDLE_NAME, KNOW_LAST_NAME
HCM PERSON_BASIC_SYNC (v3) message does not have KNOWN_FIRST_NAME, KNOW, KNOW_MIDDLE_NAME, KNOW_LAST_NAME fields in it.

Searched all over PeopleBooks and MOS, could not find a single line describing the use of these 3 fields. Our questions:

Tagged:

Preferred Name

1

Howdy, Stranger!

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

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

Category Leaderboard

Top contributors this month