core hr setups

right now at page 1251

Work StructuresKFFs Organization

123456 Competence

pre-requisite for all KFFs attachment to BG:Segments identification EIT vs SIT

KFFs made

Profile options HR : Business Group BG name at responsibility level suggestedHR : User Type HR with payroll userHR : Security Profile BG name at responsibility level suggested

make BG specific responsibilities

Business Group

Job related Job GroupGradePosition related Position HierarchyPeople GroupCost Allocation Location

value sets defined

Security ProfilesSecurity Groups

Organization

define organization quickcodes

EIT vs SIT

define HR organizations

define GRE / Legal EntityHR organization classification and hierarchy

2 screenshotsReturn to Main

Step 1: Identify the kind of organization - Rule based (like govt) / Project Based (consulting / construction etc) / Hybrid

Define Job -->

Return to Main

Localization specific occupational category values through lookup ZA_EMP_EQ_OCCUPATIONAL_CAT. Occupational category value set table validated utilizing that lookup.

Step 2 : Based on 1, the actual Job and position structures would be helpful.. Since we would know for sure which kind of hierarchy we want to lay and where to relate grades

Step 3 : Define Job Groups. All primary jobs should fall under default job group. If HR : Cross Business Group is not set, then the job groups need to be unique only for specific BG.. In other case they need to be unique across implementation

Define job group -->

Job Evaluation -->

Job Requirements

Valid grades

Work Preferences

Step 1: Identify the kind of organization - Rule based (like govt) / Project Based (consulting / construction etc) / Hybrid

Localization specific occupational category values through lookup ZA_EMP_EQ_OCCUPATIONAL_CAT. Occupational

Step 2 : Based on 1, the actual Job and position structures would be helpful.. Since we would know for sure which kind of

Step 3 : Define Job Groups. All primary jobs should fall under default job group. If HR : Cross Business Group is not set, then the job groups need to be unique only for specific BG.. In other case they need to be unique across implementation

Return to Main

Localization specific occupational level values through lookup ZA_EMP_EQ_OCCUPATIONAL_LEV (system lookup). Occupational level value set table validated utilizing that lookup.

Localization specific employment equity function types through lookup ZA_EE_FUNCTION_TYPE (system lookup) which gives list of function types for employment equity in SA. Function type value set table validated utilizing that lookup.

Localization specific occupational level values through lookup ZA_EMP_EQ_OCCUPATIONAL_LEV (system lookup).

Localization specific employment equity function types through lookup ZA_EE_FUNCTION_TYPE (system lookup) which gives list of function types for employment equity in SA. Function type value set table validated utilizing that lookup.

Just for rough idea below structureReturn to Main

Work category includes Administrator, Artisan, Management and ProductionReturn to Main

Location can be Global or Local

Return to Main

It’s a shared field between HRMS, PO and …

Return to Main

EIT SITDFF KFF

LocationOrganizationPositionJobPay ElementsPeopleAssignmentPrevious JobContact InformationRecord information (HR Document Record Infor)

Organization

Click Other buttonClick ZA NQF SETA InformationGive the detail as mentioned in the screen shot.

Attach GRE/Legal Entity to the Organization Classification and save it.Click on Other ButtonGive the detail for ZA Tax Information as mentioned in below screen shot.

Return to Main

Organization hierarchy

Return to Main Link to security groups

Standard Security Model" in Oracle HRMS. In this security model, you will need to create One Responsibility per Security Profile. This is the limitation of this Security Model.

The difference between PER_PEOPLE_F and PER_ALL_PEOPLE_F is that former is a view that filters on Security Profile [on the basis of logged in user/ responsibility ]

Step 1 - Create org or Position hierarchy (on whichever we want

to apply security profile

Step 2. Define a security Profile that is attached to node “XX IT

Technical” of the Hierarchy

Step 4. Run the concurrent program “Security List Maintenance”.

Step 2. Define a security Profile that is attached to node “XX IT

Technical” of the Hierarchy

Step 3. Attach this security profile as a profile option to our responsibility named “XX HRMS

IT Technical Resp”

Link to security groups

Standard Security Model" in Oracle HRMS. In this security model, you will need to create One Responsibility per Security Profile. This is the

The difference between PER_PEOPLE_F and PER_ALL_PEOPLE_F is that former is a view that filters on Security Profile [on the basis of logged

Position Type --> Hiring Status

Hiring info

Return to Main

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

Wrk terms

Reporting to (to make position hierarchy)

Enter the number of Full Time Equivalents to be assigned to this position. If the Position Type is Single Incumbent, FTE must be 1.0 or less.

Valid grades

Enter the number of Full Time Equivalents to be assigned to this position. If the Position Type is Single Incumbent,

Step 1 - For this you can set Profile Option “Enable Security Groups” to Yes.Step 2 - Next, you can assign different Security Profiles to specific users [though for same Responsibility].

Return to Main Link to Sec profile

Step 2 - Next, you can assign different Security Profiles to specific users [though for same Responsibility].