Scribd
Upload
2K views

Oracle Fusion HCM - Person Model

Fusion person model separates and normalizes person data across multiple tables for improved data management. It stores names in a separate table to allow for multiple name formats per person. National identifiers are also separated out to support multiple identifiers per person by country or type. Legislative details like gender are separated into their own table to track historical changes over time. Contact relationships remain structured similarly to the previous EBS system.

Uploaded by

khiljis
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
2K views

Oracle Fusion HCM - Person Model

Fusion person model separates and normalizes person data across multiple tables for improved data management. It stores names in a separate table to allow for multiple name formats per person. National identifiers are also separated out to support multiple identifiers per person by country or type. Legislative details like gender are separated into their own table to track historical changes over time. Contact relationships remain structured similarly to the previous EBS system.

Uploaded by

khiljis
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

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
Person Details

EBS

Person Type
Address

PER_PERSON_TYPES
PER_PERSON_TYPE_USAGES_F
PER_ADDRESSES

Phone
Email Address
Contact Relationship

PER_PHONES
Stored in PER_ALL_PEOPLE_F
PER_CONTACT_RELATIONSHIPS

PER_ALL_PEOPLE_F

Fusion
PER_PERSON
PER_ALL_PEOPLE_F
PER_PERSON_NAMES_F
PER_NATIONAL_IDENTIFIERS
PER_PEOPLE_LEGISLATIVE_F
PER_ETHNICITIES
PER_PERSON_TYPES
PER_PERSON_TYPE_USAGES_M
PER_ADDRESSES_F
PER_PERSON_ADDR_USAGES_F
PER_PHONES
PER_EMAIL_ADDRESSES
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 persons legislative info. Ex: gender, marital status
Row only created if countrys 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.

You might also like