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_PERSON
PER_ALL_PEOPLE_F PER_ALL_PEOPLE_F
PER_PERSON_NAMES_F
PER_NATIONAL_IDENTIFIERS
PER_PEOPLE_LEGISLATIVE_F
PER_ETHNICITIES
Person Type PER_PERSON_TYPES PER_PERSON_TYPES
PER_PERSON_TYPE_USAGES_F 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 PER_CONTACT_RELATIONSHIPS PER_CONTACT_RELATIONSHIPS
Relationship

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
a. Row only created if NID was entered
b. Dated, but not date-effective
3) Legislative Information - Separate table for person’s legislative info. Ex: gender, marital status
a. Row only created if country’s data needs to be entered
b. Date-effective to record historical changes
c. Person can have multiple legislative data rows
d. Concurrent rows with different legislation, but
e. Only one row for a given legislation

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

 Key FlexFields in Fusion and Comparison to EBS
Fusion Application has only two key flex fields compared to six in Oracle EBS.

Key Flexfields in Fusion

- PeopleGroup - hr
- CostAllocation - pay

Key FlexField in EBS

- Personal Analysis
- Grade
- Job
- Position
- People Group
- Cost Allocation

Technically, in fusion all the information is stored in same table. For ex: Job data in Fusion is stored
in per_jobs_f table while in EBS, it is stored in per_jobs_f and per_job_definitions.
 Commonly used database tables in Fusion HR application
Most of the tables in Fusion Applications are inherited from Oracle eBusiness Suite, but there are
additions and modifications in the data model. The tables are more normalized and represents the
information it is storing. Some of the commonly used tables are -

Table Name Alias Suggested Join

PER_ALL_PEOPLE_F
PER_PERSON
PER_NATIONAL_IDENTI
FIERS
PER_ETHNICITIES
PER_PERSON_NAMES_F
PER_PHONES
PER_PEOPLE_LEGISLAT
IVE_F
PER_EMAIL_ADDRESSES
PER_PERSON_ADDR_USA
GES_F
PER_ADDRESSES_F
PER_PERSON_TYPE_USA
GES_M
PER_PERSON_TYPES
FND_LOOKUP_VALUES_
TL
Name
PAPF
PP PAPF.PERSON_ID = PP.PERSON_ID
AND TRUNC(SYSDATE) BETWEEN
PAPF.EFFECTIVE_START_DATE AND
PAPF.EFFECTIVE_END_DATE
NID PAPF.PERSON_ID = NID.PERSON_ID
AND NID.NATIONAL_IDENTIFIER_TYPE = 'SSN'
PE PAPF.PERSON_ID=PE.PERSON_ID
PPNF PAPF.PERSON_ID = PPNF.PERSON_ID
AND UPPER(PPNF.NAME_TYPE)='GLOBAL'
AND TRUNC(SYSDATE) BETWEEN
PPNF.EFFECTIVE_START_DATE AND
PPNF.EFFECTIVE_END_DATE
PPH PAPF.PERSON_ID = PPH.PERSON_ID
PPH.PHONE_TYPE = 'H1'
PPLF PAPF.PERSON_ID = PPLF.PERSON_ID
AND TRUNC(SYSDATE) BETWEEN
PPLF.EFFECTIVE_START_DATE AND
PPLF.EFFECTIVE_END_DATE
PEA PAPF.PERSON_ID = PEA.PERSON_ID
AND PEA.EMAIL_TYPE = 'W1'
AND TRUNC(SYSDATE) BETWEEN
PEA.EFFECTIVE_START_DATE AND
PEA.EFFECTIVE_END_DATE
ADR PAPF.PERSON_ID=ADRU.PERSON_ID
U AND ADRU.ADDRESS_TYPE = 'HOME'
AND TRUNC(SYSDATE) BETWEEN
ADRU.EFFECTIVE_START_DATE AND
ADRU.EFFECTIVE_END_DATE
PA ADRU.ADDRESS_ID = PA.ADDRESS_ID
AND TRUNC(SYSDATE) BETWEEN
PA.EFFECTIVE_START_DATE AND
PA.EFFECTIVE_END_DATE
PPTU PAPF.PERSON_ID = PPTU.PERSON_ID
AND TRUNC(SYSDATE)
BETWEEN PPTU.EFFECTIVE_START_DATE
ANDPPTU.EFFECTIVE_END_DATE
PT AND PUF.PERSON_TYPE_ID = PT.PERSON_TYPE_ID
AND PT.SYSTEM_PERSON_TYPE IN ('CON',’EMP’)
FLVT AND PE.ETHNICITY=FLVT7.LOOKUP_CODE
7 AND FLVT7.LOOKUP_TYPE='PER_ETHNICITY'
 AND FLVT7.LANGUAGE='US'
FND_LOOKUP_VALUES_ FLVT AND
TL 8 PPLF.MARITAL_STATUS=FLVT8.LOOKUP_CODE
AND FLVT8.LOOKUP_TYPE='MAR_STATUS'
AND FLVT8.LANGUAGE='US'
PER_ALL_ASSIGNMENTS PAA PAPF.PERSON_ID = PAAM.PERSON_ID
_M M AND PAM.ASSIGNMENT_TYPE IN (‘E’,’C’)
AND TRUNC(SYSDATE) BETWEEN
PAAM.EFFECTIVE_START_DATE AND
PAAM.EFFECTIVE_END_DATE
PER_ASSIGNMENT_STAT PAST PAAM.ASSIGNMENT_STATUS_TYPE_ID=PASTT.ASSI
US_TYPES_TL T GNMENT_STATUS_TYPE_ID
PER_ASSIGN_WORK_ME PAW PAAM.ASSIGNMENT_ID=PAWMF.ASSIGNMENT_ID
ASURES_F MF PAWMF.UNIT='FTE'
PER_ASSIGNMENT_SUPE PASF PASF.MANAGER_ID=PAPF.PERSON_ID
RVISORS_F AND TRUNC(SYSDATE) BETWEEN
PASF.EFFECTIVE_START_DATE AND
PASF.EFFECTIVE_END_DATE
PER_PERIODS_OF_SERVI PPOS PAAM.PERIOD_OF_SERVICE_ID=PPOS.PERIOD_OF_
CE SERVICE_ID
CMP_SALARY CS PAAM.ASSIGNMENT_ID=CS.ASSIGNMENT_ID
CMP_SALARY_BASES CSB CS.SALARY_BASIS_ID=CSB.SALARY_BASIS_ID
HR_LOCATIONS_ALL_F_ HLA PAAM.LOCATION_ID=HLAFV.LOCATION_ID
VL FV AND TRUNC(SYSDATE) BETWEEN
HLAFV.EFFECTIVE_START_DATE AND
HLAFV.EFFECTIVE_END_DATE
PER_DEPARTMENTS PD PAAMV.ORGANIZATION_ID=PD.ORGANIZATION_I
D
AND TRUNC(SYSDATE) BETWEEN
PD.EFFECTIVE_START_DATE AND
PD.EFFECTIVE_END_DATE
PER_JOBS_F_VL HLA PAAM.JOB_ID=PJFV.JOB_ID
FV AND TRUNC(SYSDATE) BETWEEN
HLAFV.EFFECTIVE_START_DATE AND
HLAFV.EFFECTIVE_END_DATE
PER_GRADES_F_TL PGFT PAAMV.GRADE_ID=PGFT.GRADE_ID
AND TRUNC(SYSDATE) BETWEEN
PGFT.EFFECTIVE_START_DATE AND
PGFT.EFFECTIVE_END_DATE
AND PGFT.LANGUAGE(+)='US'
HR_ORGANIZATION_UNI HOU PAAMV.BUSINESS_UNIT_ID =
TS_F_TL _TL HOU_TL.ORGANIZATION_ID
AND HOU_TL.LANGUAGE='US'
AND TRUNC(SYSDATE) BETWEEN
HOU_TL_TL.EFFECTIVE_START_DATE AND
HO.EFFECTIVE_END_DATE
 Fusion Payroll/Compensation - Technical Details
Payroll and Compensation Model

Compensation
Salary details in Fusion are stored in below tables -
EBS Fusion
Salary Details PER_PAY_PROPOSALS CMP_SALARY
CMP_SALARY_COMPONENTS
Salary Basis PER_PAY_BASES CMP_SALARY_BASES

Payroll
After hiring an employee, Work Relationship and Payroll Relationship is created with the start date
as the Hire Date. This is different from the eBusiness suite where payroll is linked with assignment.
In Fusion HR, a person can have multiple payroll relationship with different Payroll.
EBS Fusion
Employee PAY_ALL_PAYROLLS_F PAY_ALL_PAYROLLS_F
Payroll PAY_REL_GROUPS_DN
Details PAY_ASSIGNED_PAYROLLS_DN
Payment PAY_PAYMENT_TYPES PAY_PAYMENT_TYPES
Types
Organizatio PAY_ORG_PAYMENT_METHODS_F PAY_ORG_PAY_METHODS_F
n Payment PAY_ORG_PAY_METHOD_USAGES_
Method F
Personal PAY_PERSONAL_PAYMENT_METHODS PAY_PERSON_PAY_METHODS_F
Payment _F
Methods
People PAY_PEOPLE_GROUPS PAY_PEOPLE_GROUPS
Group
Element PAY_ELEMENT_TYPES_F PAY_ELEMENT_TYPES_F
Types
Element PAY_ELEMENT_INPUT_VALUES_F PAY_ELEMENT_INPUT_VALUES_F
Input
Values
Element PAY_ELEMENT_LINKS_F PAY_ELEMENT_LINKS_F
Links
Element PAY_ELEMENT_ENTRY_VALUES_F PAY_ELEMENT_ENTRY_VALUES_F
Entry
Element PAY_ELEMENT_ENTRIES_F PAY_ELEMENT_ENTRIES_F
Entry
Values
 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_PERSON
PER_ALL_PEOPLE_F PER_ALL_PEOPLE_F
PER_PERSON_NAMES_F
PER_NATIONAL_IDENTIFIERS
PER_PEOPLE_LEGISLATIVE_F
PER_ETHNICITIES
Person Type PER_PERSON_TYPES PER_PERSON_TYPES
PER_PERSON_TYPE_USAGES_F 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 PER_CONTACT_RELATIONSHIPS PER_CONTACT_RELATIONSHIPS
Relationship

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
a. Row only created if NID was entered
b. Dated, but not date-effective
3) Legislative Information - Separate table for person’s legislative info. Ex: gender, marital status
a. Row only created if country’s data needs to be entered
b. Date-effective to record historical changes
c. Person can have multiple legislative data rows
d. Concurrent rows with different legislation, but
e. Only one row for a given legislation

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

 Fusion HCM Application - Person Number generation

Person Number Generation

In Fusion, person number (i.e. Employee Number) generation is done using database sequence
“PER_NUM_1_DYD”. The number generation can be configured from user interface -

To set the person number generate, navigate to Setup and Maintenance -> Manage Enterprise
HCM Information -> Search for your enterprise

There are four available options –

o Automatic Prior to submission - Generate upfront in which case they will see person number in the
UI, but might get gap

o Automatic upon final save - Generate at the end once the hire is approved, in which case they will not
see person number in the UI, but would avoid gaps

o Formula

o Manual

By default the person number generation is Automatic.

Automatic Person Number Generation

Person number is generated automatically when generation method is set to –

 Automatic Prior to submission

 Automatic upon final save

 Formula
 Few things to note when using above “Automatic” person number generation

1. User can’t modify Person Number from the user interface.

2. While using File Based Loader –

a. If the person number is left blank then the person number is generated automatically and assigned.

b. If the “Person Number” attribute is populated in the data file, value given in the file is used for person
number even though the Person Number Generation Method is set to Automatic.

Note: SR should be logged with Oracle to reset the “person number” to highest person number used in the
data file. In release 7 onward, this can controlled using attribute “Initial Person Number” available in the
Enterprise HCM Information.

Manual Person Number Generation

1. User is forced to enter a person number in the User Interface.

2. When using FBL to convert employees, the user is forced to enter the person number in the data files.

Person Number generation while initial data migration using File Based
Loader (FBL)

If the requirement is to convert existing person numbers, but then wants to make the person
number as automatic then –

 Set the Person number generation method to automatic.

 Set the attribute “Initial Person Number” available in the Enterprise HCM Information to “max”
existing employee number (this is available release 7 onward). In release 5, you need to log SR with
Oracle to reset the person number.
 Convert the employees, by passing the legacy person numbers in the data files

Some important Oracle notes –

 Set The Employee Number/Person Number To Certain Value (Doc ID 1500596.1)

 Fusion Global HR: How to Have Person/Assignment Number Generated to Own Corporate
Requirements (Doc ID 1502884.1)