Configuration of HRMS

Oracle HR is a fully integrated Oracle HRMS suite of Applications comprising of HR, Payroll, Self-service, Oracle Time and Labor, i Recruitment etc

This also shares information about employees, jobs, positions, approvals etc across the E-business Suite to support processes.

I have tried to cover as much as possible with screen shots to configure Base HRMS.

Configuration of HRMS

I have tried to cover as much as possible with screen shots to configure Base HRMS.

1. Create HRMS responsibility

1. Create user and attach HRMS responsibility

1. Compile all the Key flexfield - Grade Flexfield/ Group Flexfield/Job Flexfield/Position Flexfield/Cost Allocation Flexfield (to map with GL COA)/ Competence Flexfield

(HRMS KFF – Grade / Job / Position / Competence / Personal Analysis (SIT) / CAGR / Item context / Soft coded)

(Payroll KFF – Cost allocation / People group / Bank details)

1. Create Location – Work structure>Location

1. Go to HRMS responsibility and create Business Group – Location is not mandatory for BG Org Classifications - First complete this setup before selecting HR organization classification

1. Enable HR organization under organization classification – Here attach Reporting Information Additional Organization information – Create 4 segments – Reporting Name/Manager/Start Date/End Date and Work day additional organization information – create 4 segments – Normal Start Time / Normal End Time / Working Hours / Frequency

1. Attach our BG to HR: Business Group and HR: Security profile to our HRMS responsibility

1. Go and create Multi Org architecture in HRMS

1. Attach this MO to all the relevant responsibilities through Sys Admin

1. Create employee and attach in user window

1. All employees created in other BG cant be seen in enter and maintain employee window (business group specific)

1. SIT – Create as many structure (not values) as we need under personal analysis KFF to see this in SIT under other definition

1. Create Special information types (business Group specific) – Other Definition>Special Information Type (Here we can see all the structure as created in 11^th step under personal analysis KFF). Check the other boxes to specify how you plan to use the special information type. This makes it available in the list of values in other windows as follows:

• Job: in the Job Requirements window

• Position: in the Position Requirements window

• Other: in the Special Information window

• OTA: in the Skill Provisions and Search for Event windows in Oracle Training Administration – It is appearing as OTA in apps

The OSHA and ADA check boxes are for US users only.

Create (LOV is available to select – like language , Communication, Certification, medical records, disabilities – click the check box as appropriate)

Define person type – Other definition>Person type (defined in other business group can be seen – this is not BG specific) – Employee/Applicant/Candidate etc.

Define look up code – Application Utilities Lookups

Navigation – Other definition >Application Utilities Lookups

Examples for Lookup codes

Absence Reason

Absence Types

Employment category

Create Job Group - Work Structure > Jobs>Job groups.

Define jobs – available across the BG – defined in other BG can be seen.

While defining jobs attach job group. System will allow to pre date while defining jobs. Only one job group is allowed to use. Even if we create one more job group it can’t be used in position window while attaching jobs against positions.

Define Job path name (BG specific) – Work structure>job>patch name. Define path name like consulting/project manager/program manager (it is only path not actual job or position name). We can optionally define DFF to capture additional information. DFF is per instance for each window. Defined DFF in other BG will available to use.

Define Career path – Work structure>Job>Career path

Select a job from LOV and attach (select from LOV) path name and select the next level and next to next level. We need to define jobs and path name first before this activity

Define position (BG specific) – attach jobs against each position. Position defined in other BG can’t be seen. – Possible segments – position number/position name 2segments.

Select the position type. The choices are:

• Single Incumbent, meaning that only one employee is allowed to hold the position at any time

• Shared, meaning there can be several incumbents, up to the value of the FTE field and headcount field – mention how many people are sharing by mentioning 2/3/4 etc. under hiring information TAB in FTE field

• Pooled (Public Sector only), meaning the position is loosely defined so rules about FTE and hours are not enforced by the system

• None, which you can select if you do not need to record position types

Only corrections are possible in Position window. No updates are possible as we have option in enter and maintain employee window. Back dates are possible in Position window also as Job window where it is possible.

Define position hierarchy – it is BG specific. Defined in other BG can’t be seen. One position primary hierarchy is possible per BG. We need to define employee and attach jobs and position before we define this position hierarchy.

Define Grade – Work structure>Grade>Description. Possible segments – range/level/region 3 segments. It can be different based on the client needs. This is BG specific.

Define Grade Rates – Name the window and select unit from LOV and fix the minimum and maximum rates for all the grades. Work structure>grade>grade rates. This is BG specific.

Define the salary rate for grades. This is BG specific. Define standard hourly rate and monthly rate.

Define pay scale – Work structure>grade>pay scale. This is BG specific.

You define a pay scale, which is a set of progression points for compensation, in the Pay Scale window.

Pay scales are used commonly in government and regulated or unionized enterprises where actual values of pay are defined as a 'pay scale', a 'schedule', or a 'spine'. Characteristics of this functionality are:

• A single scale of points and values is used to establish the actual pay for a grade group.

• Each point in the pay scale has a single value.

• Grades can have a number of distinct steps, with each step given a single point in the pay scale.

• An employee assignment to a grade includes a point, or step value, and the point value determines the actual pay of the employee.

You can have any number of different pay scales in Oracle HRMS. Each scale has its own set of points which may be characters or numbers.

Define scale rate – Work structure>grade>Point values. Attach the pay scale defined above while defining scale rate for each length. This is BG specific. This scale rate is for each hour as defined in pay scale (last step) structure.

Grade steps and points – Work structure>grade>grade steps and points. Link the grade with pay scale. This is BG specific.

Select all the hours from LOV and save. Final result will be as follows:

Assignment rate types> Work structure>Grade>assignment rate types