HRMS - Date Track

Date Track is a very important concept in HRMS. Contrary to the other Modules where start dates and end dates stamp the progress of and entity (example Procure to Pay cycle - requisition creation date, order creation date etc), in HRMS the entity person itself is dynamic and is constantly evolving. There is no clear cut flow.

The dimension of time is crucial and based on the date for which we are querying, we would expect a different information for the person. For example, the marital status, age, salary and assignment may be different when querying a person at today's date and at a date 2 years' back.

In HRMS, if there is a change, then a new record is inserted and the previous value end-dated with the date of change. It is therefore crucial to date-track to the appropriate date before making any changes. If I want to change the Position of an employee, then I would date-track to the promotion date before changing the Position.

Making any changes on HRMS brings us to 2 concepts:

1. Correction


2. Update

Oracle will prompt us to decide what we are doing when we are saving after a change.

Correction

In the case of a correction, then the actual value is modified without any change in history. The current record is not end dated. There is no new record inserted.

Update

In the case of update, that means that something has actually changed. The actual value is end dated. A new record is created with the date we have date tracked to. We can view the history. Query of the person with a date anterior to the change will the previous record which was valid for that time Query of the person with a date greater of equal to the date of change brings up the new record.

Note that you can make changes in the past or in the future.

How Date Track Works

[caption id="" align="alignnone" width="708" caption="How Date Track Works"][/caption]

Shameem Bauccha

22 June 2009

HRMS - Enter and Maintain People Form

Oracle HRMS offers the ‘People Form’ as the main point of data entry. A thorough understanding of the ‘People Form’ is a good starting point for those new to Oracle HRMS.

Note that you can use the ‘Enter and Maintain’ form to create and maintain the following person types:

1. Employee


2. Applicant


3. Contingent Worker

HRMS Super User --> People --> Enter and Maintain

[caption id="" align="alignnone" width="752" caption="Enter and Maintain People Form"][/caption]

The form consists of 3 sections: the main page, the tabs and buttons.

Main Page

• Name Section

Here you input the name of the employee/applicant.

• Action

Action allows you to create a person (whether it is an employee, an applicant or a contingent worker).

• Person Types

Based on the action you have taken, the person type appears here. In case you have customized the person types, your customized person type will appear instead.

(See ‘Person Types’ --> Document to follow)

• Identification

This section stores 2 identifications. The first column is for the company identification number of the person (employee number, for example.). The ‘National Identifier’ can be any identifier used ay national legal like National Identity Card Number or Social Security Number.

The employee number can be automatically generated, manually input or generated based on a custom function according to your setup.

• Effective Dates

This refers to the effective date of the creation of the record. In case of an employee it will refer to the hiring date. In case of an applicant it will be the date the applicant was received. In the case of a contingent worker it will be the date as from which the billable time for the person begins.

It is crucial to first date-track to the appropriate date before actually begin to create a record on Oracle HR.

• Descriptive Flexfield

This descriptive flexfield allows you to extend the Main Page.

Tab Pages

• Personal

At this level you put further personal information like date of birth, nationality and marital status. Note that although date of birth is not a mandatory field, it is required if you want to register the person on Oracle Payroll. All the lookups like ‘Nationality’, ‘Marital Status’ can be customized (with seeded values enabled/disabled and new values added) to meet client requirements.

• Office Details

[caption id="" align="alignnone" width="727" caption="Office Details"][/caption]

• Applicant

[caption id="" align="alignnone" width="721" caption="Applicant"][/caption]



You can hold the application of a candidate.

• Further Name

[caption id="" align="alignnone" width="723" caption="Further Name"][/caption]

• Other

Push buttons

• Address

This button opens a pop-up window where you can choose your address style and input your address accordingly.

Note that you can define your own address styles.

(See ‘Address Styles’ --> Document to follow)

• Picture:

This button opens a web page where you can attach a photo of the person.

• Assignment:

This button opens the ‘Assignment’ form. This will be taken in more details in a post to follow soon.

(See ‘Assignment’ --> Document to follow)

• Special Info

Special info is a Key Flexfield that you can define and enable (Personal Analysis Key Flexfield). You can use Special Info to record any structure that is not directly available on the standard ‘Enter and Maintain’ People Form and not directly extensible through the DFFs available on the screens.

This will be taken up in subsequent posts.

(See ‘Define Special Info’ --> Document to follow)

• Others:

This button brings a list of values that link to additional forms and refer to additional functions that you can record for a person, for example ‘Medical Information’, ‘Phone Numbers’ etc.

(See ‘HR Functions - Others’ for the list of functions available--> Document to follow)

Shameem Bauccha

22 June 2009

Click here to download the document.

Oracle Apps - R12 - Core HR Lookups

There are a list of Lookups that are available in core HR and that you can extend for your own purpose.

See below the list of lookups and their purpose:

LOOK UP CODE	DESCRIPTION
TITLE	Represents TITLE in People Screen.
SEX	Represents Gender in People Screen.
PERSON_TYPE	Represents Person Types in People Screen.
ORG_TYPE	Represents the Organization Type.
MAR_STATUS	Represents Marital Status in People Screen.
NATIONALITY	Represents Nationality in People Screen.
REGISTERED_DISABLED	Represents Registered Disabled in People Screen.
ADDRESS_TYPE	Represents Address Type in People Screen.
ABSENCE_CATEGORY	Represents Absence Category in Absence Screen.
ABSENCE_REASON	Represents Absence Reason in Absence Screen.
APL_ASSIGN_REASON	Represents Assignment Change Reason in Application Screen.
APL_INTERVIEW_TYPE	Represents Interview Type in Interview Screen.
EMP_EVENT_TYPE	Represents Type in Bookings Screen.
PER_CM_MTHD	Represents Delivery Methods in Communication Delivery Methods Screen.
PROFICIENCY_SOURCE	Represents Source of Proficiency Rating in Competence Profile Screen.
CERTIFICATION_METHOD	Represents Source of Certification Method in Competence Profile Screen.
CONTACT	Represents Relationship Type in Contact Screen.
CONTRACT_TYPE	Represents Contract Type in Contract Screen.
CONTRACT_STATUS	Represents Contract Status in Contract Screen.
CONTRACT_STATUS_REASON	Represents Contract Status Reason in Contract Screen.
DOCUMENT_STATUS	Represents Document Status in Contract Screen.
CONTRACT_START_REASON	Represents Contract Start Reason in Contract Screen.
CONTRACT_END_REASON	Represents Contract End Reason in Contract Screen.
DISABILITY_CATEGORY	Represents Disability Category in Disability Screen.
DISABILITY_REASON	Represents Disability Reason in Disability Screen.
TERM_APL_REASON	Represents Reason for Ending an Application in End Application Screen.
LEAV_REAS	Represents Leaving Reason in End Employment Screen.
CONSULTATION_TYPE	Represents Consultation Type in Medical Assessment Screen.
CONSULTATION_RESULT	Represents Consultation Result in Medical Assessment Screen.
PHONE_TYPE	Represents Phone Type in Phones Screen.
PER_SUBJECT_STATUSES	Represents Status of Qualification in Qualifications Screen.
PER_SUBJECT	Represents Subject in Qualification Screen.
PER_WORK_HOURS	Represents Work Hours in Work Preferences Screen.
PER_WORK_SCHEDULE	Represents Work Schedule in Work Preferences Screen.
PER_FTE_CAPACITY	Represents FTE Capacity in Work Preferences Screen.
VACANCY_CATEGORY	Represents Vacancy Category in Requisition and Vacancy Screen.
VACANCY_STATUS	Represents Vacancy Status in Requisition and Vacancy Screen.
REC_TYPE	Represents Source Type for Recruitment Activity in Requisition and Vacancy Screen.
FREQUENCY	Represents Frequency for Review Salary, Review Performance, and Working Hours in Assignment Screen.
QUALIFYING UNITS	Represents Units for Probation Period and Notice Period in Assignment Screen.
PQP_EMPLOYER_TYPE	Represents Employer Type in Employment History Screen.
PQP_EMPLOYER_SUBTYPE	Represents Employer Sub Type in Employment History Screen.
DOCUMENT_CATEGORY	Represents Document Category in Documents of Record Screen.

Oracle Apps - R12 - High Level Setup for Core HR

Basic Administration Checklist

Define the following Key Flexfields

1. Job (Human Resources)


2. Position (Human Resources)


3. Grade (Human Resources)


4. Competence (Human Resources)


5. People Group (Payroll)


6. Cost Allocation (Payroll)

Define Descriptive Flexfields where required:

1. Additional Job Details (Human Resources)


2. Additional Position Details (Human Resources)


3. Additional Organization Unit Details (Human Resources)

Complete the following Work Structures Checklist:

1. Define Locations


2. Define Business Group


3. Define Other Organizations


4. Define Organization Hierarchies

Define Roles

1. Define Jobs


2. Define Positions


3. Define Grades


4. Define Position Hierarchies

Person Types and Assignment Statuses

1. Define Person types


2. Define Assignment Statuses for Employees

Profile Options & Lookups

1. Set Profile Options


2. Configure Lookups if required

Localization

1. Run International HRMS setup (if required)

Shameem Bauccha

18 June 2009