TRG HRGOM
TRG HRGOM
TRG HRGOM
Revised: 2/6/2018
Introductions
Slide 2
House Rules
Please:
• Silence phones
• Refrain from email and internet use
• Leave the room tidy and ready for the next class
• Participate – This is your class!
Slide 3
What Class Is and What Class Is Not
To give you the basic knowledge and skills Designed for your specific division or
you need to perform your tasks in KHRIS agency procedures and policies
as well as to perform any related business
processes
To demonstrate how you can further Inclusive of all of the scenarios you
develop your skills, by using the classroom encounter in your current job role
materials and the end-user training
materials website to continue your KHRIS
education after training is completed
Designed with the primary goal of making Designed to cover agency-specific tasks
you effective on the tasks you will use done in KHRIS very sporadically, such as
most frequently in the system quarterly or annually
Slide 4
Instruction Method
Slide 5
KHRIS Terminology Review
What is SAP?
Slide 7
Master Data
Employee/Position Address
Slide 8
Infotypes
Infotypes (ITs) group data together according to related subject
matter.
Slide 9
Transactions
Transactions are used to display data in different formats in
KHRIS.
3
There are three methods to access
2
transactions.
• Method #1, Menu Path – By using a menu path,
we can access transactions by clicking the
arrows, or nodes, next to the folders to reveal 1
the actual transaction steps for processing.
This is known as a tree structure.
• Method #2, Transaction Code – We can enter
a transaction code in the Command field, but
we have to know the transaction code we want
to access
• Method #3, Favorites – We can create a
Favorites list of commonly used transactions
Slide 10
Security Roles
Slide 11
Dates
Slide 12
Validity Periods
Validity periods are the start and end dates that define the life
span of the record.
Start Date
End Date
Start Date
End Date
Slide 13
Questions and Answers
Slide 14
Organizational Management
Course Map
Lesson 1: OM Overview
Lesson 3: Jobs
Lesson 4: Positions
Lesson 5: Reporting
Wrap-up
Slide 16
Course Objectives
Slide 17
Organizational Management Overview
Lesson 1
Course Map
Lesson 1 OM Overview
Lesson 3: Jobs
Lesson 4: Positions
Lesson 5: Reporting
Wrap-up
Slide 19
Lesson 1 Objectives
Slide 20
Key Terms
Slide 21
Integration
Slide 22
What is Organizational Management?
Slide 23
What is Organizational Management?
Slide 24
Uses for Organizational Management
Organizational management (OM) is the component of KHRIS that maintains the
organizational structure in the system.
• It provides a clear picture of the organization at any point in time
• Past
• Present
• Future
• It provides access to the reporting structure in real time
• Relationships stored in KHRIS:
• Allow structural authorization, or what information we can view (security)
• Create hierarchy
• Link jobs to positions
• Link positions to employees
• Link positions to positions
• Link positions to organizational units
• Link positions to cost centers
• Link objects to qualifications
Slide 25
OM Components
Slide 26
Enterprise Structure
The enterprise structure defines the legal structure of the state.
• Company code – COMK for the Commonwealth; creates a link
between the information in human resources and accounting
• Personnel area – tied directly to the company code and is used in
Payroll to identify the branch of government for whom the employee
works
• Personnel subarea – assigned at the position and defines the payroll
rules for the employee
• Cost center – ties the HR structure to the finance structure
Slide 27
Personnel Structure
The personnel structure describes an Employee
employee’s position in the Commonwealth. Group 18A
Slide 28
Organizational Structure
The organizational plan defines the hierarchical relationship
between OM objects, including org units, positions and jobs.
Slide 29
Organizational Information
Enterprise structure
Personnel structure
Organizational structure
Slide 30
OM Objects
Slide 31
Organizational Units
Slide 32
Jobs
A job is the foundation from which positions are created.
Jobs:
• Describe the general classification of functions and duties that are
identical across the Commonwealth
Slide 33
Position
A position is a detailed representation of a job and is held by an
individual. A number of positions can be based on the same job.
A position:
• Belongs to an org unit
• Reports to another position
• May be vacant or filled
• Represents a set of tasks performed by a person
• As a rule, represents one employee
• May be classified as a chief position
• Can be a line supervisor of another position
• Is represented in KHRIS by Object Type S and a 30 million number
(i.e. 30003424)
• We can access positions using transaction code PO13D
Slide 34
Holder
The Holder represents an employee and is the central object in
the Personnel Administration module. A Holder refers to the
physical person who fills a given position.
A Holder:
• Is assigned to a position
• Inherits the attributes of all related OM objects (org/job/position)
• Is represented in KHRIS by Object Type P and a six digit
personnel number (PERNR)
• We can access employees through Personnel Administration
transaction PA20.
Slide 35
Qualifications
Qualifications:
• Are maintained by the
Personnel Cabinet
• Are represented in
KHRIS by Object Type Q
and a 50 million number
(i.e. 50000265)
• Stored against a position,
org, or job
• Used for reporting
purposes only
Slide 36
Relationships
Org management uses relationships to link positions, persons, org units, jobs,
cost centers, and qualifications.
• OM is based on the concept that each element in an organization represents a
stand-alone object with individual characteristics
• These objects are created and maintained separately, then linked together
through relationships
• Relationships are displayed in IT 1001
• Agencies are responsible for maintaining the following relationships stored on a
position:
• A002 – Reports to
• B002 – Is Line Supervisor of
• A012 – Manages (Chief)
– Upon establishment of the position or a request to the OM Branch
Slide 37
Inheritance
Slide 38
Knowledge Check
Slide 39
Display the Org Structure
Slide 40
PPOSE Welcome Screen
A welcome message displays the first time we access PPOSE.
Slide 41
PPOSE Graphical View
1
Search 3
Display
Name of the
Org Unit
Position &
holder
2 4
Selection Details
Slide 42
Customize the PPOSE View
Collapse
Slide 43
Exercise 1.1: Display Organizational Structure
Observe as the instructor demonstrates the steps. You will
then have the opportunity to complete the exercise on your
own.
Purpose:
This exercise will provide you with the information needed to display an
organizational unit, the staffing, and how it fits within the organization.
Slide 44
Knowledge Check
A. Holds
B. Belongs to
C. Inherits
D. Describes
E. Defines
Slide 45
Organizational Units
Lesson 2
Course Map
Lesson 1: OM Overview
Lesson 3: Jobs
Lesson 4: Positions
Lesson 5: Reporting
Wrap-up
Slide 47
Lesson 2 Objectives
Slide 48
Organizational Units
Section
Unit
Slide 49
Reorganizations
Reorganizations
Changes in the organization of the executive branch may be necessary to
achieve economic objectives, improve efficiency, and/or increase
oversight in certain areas. These changes can include the establishment,
alteration, or abolishment of an organizational unit or administrative body
and may include the transfer of functions, duties, responsibilities,
personnel, funds, equipment, facilities, and records from one
organizational unit or administrative body to another.
The legal framework for reorganizations is found in KRS 12.027 and KRS
12.028.
Slide 50
Reorganizations
There are two types of reorganization:
Executive Orders
• Affect top organizational levels which is approved and signed by the Governor or
relevant Constitutional Officer.
Cabinet
Departments
Offices
Divisions
Administrative Orders
• Affect lower organizational levels which is approved by the Cabinet Secretary or
Constitutional Officer.
Branches
Sections
Units
Slide 51
Display Org Units
Org unit infotypes can be displayed using transaction
code PO10D.
Slide 52
Exercise 2.1 : Display Org Units
Observe as the instructor demonstrates the steps. You will
then have the opportunity to complete the exercise on your
own.
Transaction: PO10D
Purpose:
Slide 53
Knowledge Check
Slide 54
Jobs
Lesson 3
Course Map
Lesson 1: OM Overview
Lesson 3: Jobs
Lesson 4: Positions
Lesson 5: Reporting
Wrap up
Slide 56
Lesson 3 Objectives
Slide 57
Jobs
Jobs are the general classification of functions and duties that are
identical across the Commonwealth (Administrative Specialist I,
for example).
Slide 58
Jobs
Job infotypes that can be
displayed using transaction code
PO03D.
Infotypes stored against a job are:
• IT 1000 Object
• IT 1001 Relationships
• IT 1005 Planned Comp
• IT 1610 US Job Attributes
• IT 9103 KY Job Spec
• IT 9105 Special Entrance Rate
Slide 59
Exercise 3:1 : Display Job Infotypes
Observe as the instructor demonstrates the steps. You will
then have the opportunity to complete the exercise on your
own.
Transaction: PO03D
Purpose:
Slide 60
Knowledge Check
Slide 61
Positions
Lesson 4
Course Map
Lesson 1: OM Overview
Lesson 3: Jobs
Lesson 4: Positions
Lesson 5: Reporting
Wrap-up
Slide 63
Lesson 4 Objectives
Slide 64
Positions
Positions are directly related to, and inherit their tasks and
characteristics from, a job.
• Positions may be filled or vacant
• A position must always be related to the following through
Relationships:
• Another position through the relationship “reports to”
• An organizational unit through the relationship “belongs to”
• A job through the relationship “is described by”
• Other relationships include:
• A011 Cost Center (Establish position form)
• A012 Manages (Chief) (Establish position or email to the OM Branch)
• B002 Line Supervisor
Slide 65
Positions (Continued)
There can only be one position per Org unit designated as Chief,
although there can be multiple line supervisors. The chief relationship
must be identified when establishing the position and/or through an
e-mail to the OM Branch.
Agencies are responsible for maintaining the following relationships:
• A002 Reports To
• A012 Manages (email to OM Branch)
• B002 Line Supervisor
Slide 66
Display Position Infotypes
Position infotypes can be displayed using transaction code PO13D.
Infotypes that can be stored against a
position are:
• IT 1000 Object
• IT 1001 Relationship
• IT 1002 Description
• IT 1005 Planned Comp
• IT 1007 Vacancy
• IT 1008 Account Assignment
• IT 1013 Emp Group/SubGrp
• IT 1018 Cost Distribution
• IT 1028 Address
Before processing an Appointment an
• IT 9101 Additional Position Info Agency should use transaction PO13D to
• IT 9102 KY Position Des ensure the position is set up correctly.
This will eliminate PA/Payroll errors.
Slide 67
Exercise 4.1: Display Position Infotypes
Observe as the instructor demonstrates the steps. You will
then have the opportunity to complete the exercise on your
own.
Transaction: PO13D
Purpose:
Slide 68
Position Forms
Agencies use Human Capital Management Processes and
Forms (HCMPF) to initiate the processes to create or maintain
positions. The following forms will be discussed in this lesson:
• Establish Position
• Establish Position with Position Description
• Reclassification No Position Description Required
• Reclassification with Position Description
• Reallocation No Position Description Required
• Reallocation with Position Description
• Work County Change
• Update Position Description
Slide 69
KHRIS Self-Service Center
The HCMPF forms are accessed through the KHRIS Self-
Service Center.
• Web-based portal (khris.ky.gov)
• Access based on security role
• Our user ID is our
alphanumeric
employee ID
(ABC1234)
• For security reasons,
the portal will time
out after 15 minutes
of inactivity
Slide 70
User Security Agreement
Employees will be required to read and sign a User Security
Agreement annually so that an updated form is on record.
Slide 71
Accessing Forms in Self-Service Center
Slide 72
HR Generalist Tab
HR Generalist
KHRIS Processes
Slide 73
Selecting Process to Complete
We will use the “Start Organizational Process” link to access
and initiate the forms.
Slide 74
Establish Position with Position Description Form
The infotypes updated using
this form include:
• IT 1000 Object
• IT 1001 Relationships
• IT 1002 Description
• IT 1005 Planned Comp
• IT 1007 Vacancy
• IT 1008 Acct Assignment
• IT 1013 Emp Grp/SubGrp
• IT 1018 Cost Distribution
• IT 1028 Address
• IT 9101 Adl Position Info
• IT 9102 KY Position Des
Slide 75
Establish Position Without Position Description Form
Slide 76
Exercise 4.2: Establish Position with Position Description
Purpose:
You will complete the form needed to create a new position including a
description.
Slide 77
Reclassification with Position Description Form
The infotypes updated using this
form include:
Org Management:
• IT 1000 Object
• IT 1001 Relationship
• IT 1002 Description
• IT 1005 Planned Comp
• IT 1028 Address
• IT 9102 KY Position Des NOTE: When processing
reclassifications requiring a change in
Personnel Administration:
the FLSA status of the position, the
• IT 0000 Actions Human Resource Administrators
must communicate with the
• IT 0001 Org Assignment (Job Personnel Cabinet to ensure the
Data) information is updated accordingly.
• IT 0008 Basic Pay
Slide 78
Reclassification Without Position Description Form
Slide 79
Reclassification
Reclassification
Slide 80
Exercise 4.3: Reclassification with Position Description Form
Purpose:
You will reclassify a position with a position description.
Slide 81
Reallocation with Description Change Form
The infotypes updated using
this form include:
Org Management:
• IT 1000 Object
• IT 1001 Relationship
• IT 1002 Description
• IT 1005 Planned Comp
• IT 1028 Address
• IT 9102 KY Position Des
Personnel Administration:
• IT 0000 Actions
• IT 0001 Org Assignment (Job
Data)
• IT 0008 Basic Pay
Slide 82
Reallocation Without Position Description Form
The infotypes updated using
this form include:
Org Management:
• IT 1000 Object
• IT 1001 Relationship
• IT 1002 Description
• IT 1005 Planned Comp
• IT 1028 Address
Personnel Administration:
• IT 0000 Actions
• IT 0001 Org Assignment (Job
Data)
• IT 0008 Basic Pay
Slide 83
Reallocation
Reallocation
Slide 84
Work County Change Form
Slide 85
Update Position Description Form
1. What is a Reclassification?
2. What is a Reallocation?
Slide 87
Org Management Forms Approval Process
Slide 88
KHRIS Workflow
KHRIS is configured to automatically route workflow items to the
appropriate approver or approvers.
Records waiting for approval are accessed through the portal in the
approver’s Universal Worklist (UWL).
Slide 89
KHRIS Workflow (Continued)
• Each agency identifies its approvers in a pre-determined order
• Each level may have only one approver or multiple approvers
• When more than one person sits at an approval level, once one person
picks up the action it will be removed from the other users’ worklists
• An action automatically moves to the next agency approver if not
approved at any level, other than the Final Agency Approver, within three
business days
• The form will not leave the agency until it has been approved by the
Final Agency Approver
• HR staff who are both initiator and approver must go into their worklists
and approve actions at each level to keep it moving through workflow
• The originator of the form will be notified by email:
• Upon decision by the Agency Final Approver
• Upon decision by the Personnel Cabinet
Slide 90
KHRIS Workflow (Continued)
Through the KHRIS Portal an Agency can withdraw or see where a
form is in workflow using the reference number.
Slide 91
Exercise 4.4: Search/Withdraw an Action in Workflow
Purpose:
Slide 92
Knowledge Check
Slide 93
Maintain Position
Agencies maintain the following infotypes using transaction
code PO13 Maintain Position.
• IT 1001 Relationships
• A002 Reports to
• B002 Line Supervisor
• IT 1018 Cost Distribution
• Assign Additional Cost Centers
• Identify WBS Element or Order Number
• Identify Functional Areas
• IT 1028 Address
• Work Address
• IT 9101 Adl Position Info
• Working Title (Unclassified Only)
Slide 94
Exercise 4.5: Maintain Position
Observe as the instructor demonstrates the steps. You will
then have the opportunity to complete the exercise on your
own.
Transaction: PO13
Purpose:
Perform this procedure when a request has been received to make a
change to infotype data stored for a position.
Slide 95
Delimit
Slide 96
Exercise 4.6: Delimit Position(s)
Observe as the instructor demonstrates the steps. You will
then have the opportunity to complete the exercise on your
own.
Transaction: ZOME012
Purpose:
You need to put an end to a position(s).
Slide 97
Integration Aha
Enterprise structure
Personnel structure
Organizational structure
Slide 98
Knowledge Check
Slide 99
Reporting
Lesson 5
Course Map
Lesson 1: OM Overview
Lesson 3: Jobs
Lesson 4: Positions
Lesson 5: Reporting
Wrap-up
Slide 101
Lesson 5
Slide 102
Reporting in KHRIS
https://hr.personnel.ky.gov/Pages/Reports-OM.aspx
Slide 103
Reports
Allow you to view information in a logical format.
• Data is reported in an
easy-to-read line-item
table that can be
customized
• You can sort and filter the
results
• Most reports can be
exported to Excel
Slide 104
Exercise 5.1: Navigate a Report
Follow along as your instructor leads you through the steps:
Transaction: ZPAR004_POSITION
Purpose:
The instructor will guide you through the basic steps to complete the
navigation of a report. (Master position listing)
Slide 105
Knowledge Check
Slide 106
Wrap-up
KHRIS Jeopardy
The
What is
foundation from
indicated with a What is KHRIS?
which positions
10 million #
are created
What transaction
Data grouped
Represents code will display
together on a
a specific task org structures,
screen into areas
performed by org unit, position
with similar
a person holder
content
Slide 108
Course Review
Participants should now be able to:
• Define Organizational Management
• Describe the org management structure
• Explain relationships and inheritance to org management objects
• Identify object infotypes
• Display organizational structure, jobs, and positions
• Print a Job Specification
• Print a Position Description
• Maintain positions
• Identify Human Capital Management Process forms
• Describe the workflow approval process
• Navigate reports
Slide 109
Need Assistance
Slide 111
Evaluation
Slide 112