You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

Contacts DFF field names are misleading

edited Apr 16, 2020 8:34AM in Human Capital Management 2 comments

Summary

Contacts DFF field names are misleading irrespective of Relationship

Content

hi All,

We have  Upgraded our Instance to 20a and Enabled Responsive UI. From the below navigation we have enabled the Seeded DFF (PER_PERSON_CONTACT_RELATIONSHIP_DDF) provided by Oracle

Me>Personal Info>Family and Emergency Contacts>Create a new Contact

Fields in DFF

1. Name of Spouse's Employer
2. Spouse's Latest Qualification
2. Subject

Can any one let me know what is the the thought process/Reason that oracle has named these fields specifically for Spouse. Even when we change the Relationship (Child,brother) the above dff field remains the same and its misleading.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!