Functional Area: Organizational Management / Maintain Organizational Plan Data (Menu-Guided)
Purpose
Use this procedure to maintain data for organizational management objects. This includes organizational units, jobs and positions. Using this transaction will provide a consolidated method for maintaining organizational management objects.
Trigger
Perform this procedure when the completed, approved request has been received by Human Resources.
Prerequisites
- All required approvals within the requesting organizational unit (for example, departments, and colleges) must be obtained prior to Human Resources completing maintenance to OM objects.
- This includes approvals required to maintain organizational units, jobs, and positions.
Use the following menu path to begin this transaction:
- SelectHuman ResourcesOrganizational ManagementExpert ModeGeneral to go to theMaintain Objectscreen.
PP01
Business Process Information
- PP01 gives the end-user the ability to maintain infotypes related to OM objects. This includes Organizational Units, Jobs and Positions maintenance. In order for Human Resources to be able to maintain OM objects, a request must be initiated by the requesting department. The maintenance action will need to be initiated by the department through use of the online form and forwarded to HR for completion in UC Flex.
- The department must obtain ALL required approvals prior to forwarding to HR for completion.
- PP01 should be used in addition to and to accompany PQ03, PQ10, and PQ13 as well as PO03, PO10, and P013. This will ensure complete processing of all infotypes that are required for maintenance to objects within the organizational plan. Since the user is able to select the object they want to maintain, PP01 is an easier transaction to navigate as opposed to the complex screens in PPOME.
- The R/O/C column in the field description tables below defines whether the field is required (R), optional (O), or conditional (C).
- On certain screens you may have to scroll to view some data entry fields.
Work Instruction
Functional Area: Organizational Management / Maintain Organizational Plan Data (Menu-Guided)
Procedure
1. / Perform one of the following:
If You Are / Then / Go To
In transaction PPOME
It is recommended that you maintain organizational units in PP01. / - - / Step 2
At the SAP Easy Access screen / Start the transaction using the menu path or transaction code / Step 4
Organization and Staffing Change
2. / Double-click on Search term under Organizational unit located in the Find by section to find the appropriate organizational unit.
3. / Select Goto Detail object Enhanced object description.
Maintain object
4. / Perform one of the following:
If You Want To / Then / Go To
Maintain an organizational unit / - - / Step 5
Display an infotype for the organizational unit / 1. Click to the left of the appropriate Infotype Name.
2. Click . / Step 12
Maintain a job / - - / Step 15
Maintain a position / - - / Step 21
Exit this transaction / - - / Step 28
/ If you entered the transaction using the menu path or transaction code, only the Plan version and From and to date fields will be populated. All other fields will be blank.
/ Infotypes created for the organization unit have a displayed to the right of the Infotype Name field.
Maintain object
5. / As required, complete/review the following fields:
Field / R/O/C / Description
Plan version / Required / Contains a one or two alphanumeric key that differentiates between scenarios in an organizational plan
Example:
Current plan
Object type / Required / Determines type of object to process; For example, organizational units, jobs, and positions
Example:
Organizational unit
Object ID / Required / Object number
Example:
(00000009) Compensation
6. / Click to the left of the appropriate Infotype Name.
7. / Click .
/ When you enter the Object ID , the system will automatically populate the Object abbr. field after you validate the data.
8. / Click .
Create Description
9. / As required, complete/review the following fields:
Field / R/O/C / Description
Validity / Required / Defines the first and last valid date of a particular SAP record
Example:
01/01/2006
The Validity start date will default to the current day. The start date and end date can be changed if necessary.
to / Required / End value when specifying a range of values, dates and/or times
Example:
12/31/9999
Subtype / Required / A reason or description used in conjunction with an infotype
Example:
General description
Description / Required / Text to identify and characterize an object or activity
Example:
Free text regarding general notes about the organizational unit.
10. / Click .
Maintain object (2)
11. / Return to Step 4.
/ The system displays the message, “Record created”.
Display Object
12. / Review the displayed information.
/ The screens will vary based on the infotype selected.
13. / Click .
14. / Return to Step 4.
15. / As required, complete/review the following fields:
Field / R/O/C / Description
Plan version / Required / Contains a one or two alphanumeric key that differientiates between scenarios in an organizational plan
Example:
Current Plan
Object type / Required / Determines type of object to process; For example, organizational units, jobs, and positions
Example:
Job
Object ID / Required / Object number
Example:
00000076
16. / Click to the left of the appropriate Infotype Name.
17. / Click .
Create Description (2)
18. / As required, complete/review the following fields:
Field / R/O/C / Description
Validity / Required / Defines the first and last valid date of a particular SAP record
Example:
01/01/2006
to / Required / End value when specifying a range of values, dates and/or times
Example:
12/31/9999
Subtype / Required / A reason or description used in conjunction with an infotype
Example:
General description
Description / Required / Text to identify and characterize an object or activity
Example:
Free text regarding general notes about the position.
/ For this example, you will add a description to the job.
19. / Click .
Maintain object (4)
20. / Return to Step 4.
/ Infotypes created for the position have a displayed to the right of the Infotype Name field.
/ The system displays the message, “Record created.”
21. / As required, complete/review the following fields:
Field / R/O/C / Description
Plan version / Required / Contains a one or two alphanumeric key that differientiates between scenarios in an organizational plan
Example:
Current plan
Object type / Required / Determines type of object to process; For example, organizational units, jobs, and positions
Example:
Position
Object ID / Required / Object number
Example:
00000010 (Human Resources Director, Compensation)
22. / Click to the left of the appropriate Infotype Name.
23. / Click .
Create Vacancy
24. / As required, complete/review the following fields:
Field / R/O/C / Description
Validity / Required / Defines the first and last valid date of a particular SAP record
Example:
01/20/2006
To (field located to the right of the Validity field) / Required / End value when specifying a range of values, dates and/or times
Example:
12/31/9999
25. / Perform one of the following:
If / Then
The position has not been filled / Select to the left of Open.
UC Flex will automatically select Open when you create a new position.
The position has been filled / Select to the left of Vacancy filled.
26. / Click .
Maintain object (5)
27. / Perform one of the following:
If You Want To / Go To
Maintain additional organizational plan data / Step 4
Exit this transaction / Step 28
/ The system displays the message, “Record created.”
28. / Click until you return to the SAP Easy Access screen.
29. / You have completed this transaction.
8/22/2017
Ver: / 10_OM_PP01_Main Org Plan Data_OM1_0.udc
© University of Cincinnati / 1/15
Work Instruction
Functional Area: Organizational Management / Maintain Organizational Plan Data (Menu-Guided)
Result
You have maintained organizational units, jobs, and positions.
Comments
None
8/22/2017
Ver: / 10_OM_PP01_Main Org Plan Data_OM1_0.udc
© University of Cincinnati / 1/15