oracle fusion hcm - person model

Fusion Person Model - Technical Details Person Model Fusion person model is designed to separate local attributes from global attributes. In eBusiness Suite, person details – name, national identifier, gender, ethnicity etc. are stored in one table, while in Fusion, it is stored in normalized set of tables. Some of the commonly used tables in Person

Entity EBS Fusion Person Details

PER_ALL_PEOPLE_F

PER_PERSON PER_ALL_PEOPLE_F PER_PERSON_NAMES_F PER_NATIONAL_IDENTIFIERS PER_PEOPLE_LEGISLATIVE_F PER_ETHNICITIES

Person Type PER_PERSON_TYPES PER_PERSON_TYPE_USAGES_F

PER_PERSON_TYPES PER_PERSON_TYPE_USAGES_M

Address PER_ADDRESSES PER_ADDRESSES_F PER_PERSON_ADDR_USAGES_F

Phone PER_PHONES PER_PHONES Email Address Stored in PER_ALL_PEOPLE_F PER_EMAIL_ADDRESSES Contact Relationship PER_CONTACT_RELATIONSHIPS PER_CONTACT_RELATIONSHIPS

Some of the major changes are – 1) Name Format – Name is stored in separate table. A person can have a “Global” name and a “Local” in different

character set. 2) National Identifier – A separate table to store national identifier. A person can have multiple national identifiers. One

for each country or different type within same country • Row only created if NID was entered • Dated, but not date-effective

3) Legislative Information - Separate table for person’s legislative info. Ex: gender, marital status • Row only created if country’s data needs to be entered • Date-effective to record historical changes • Person can have multiple legislative data rows • Concurrent rows with different legislation, but • Only one row for a given legislation

4) Contact Relationships are stored in same way as in EBS.