Create Job Branch

Trigger:

A new Job Branch is required.

 

Business Process Procedure Overview

 

This process is rare and occurs as a result of reviewing/reorganizing existing jobs or creating a new series of jobs that does not relate to existing job branches.  New job branches are also required if a new job family is created because roles can only relate to job branches.  The system is not configured for jobs to relate directly to job families.  The Office of State Personnel, through authority granted by the State Personnel Commission, is responsible for the establishment and maintenance of job branches.

 

 

 

 

 

 

Tips and Tricks

 

· Be sure to enter the effective date of the job branch rather than the date it is physically being created in the system.

· Before entering the name and abbreviation, review the new name and abbreviation for consistency with existing names and abbreviations.  Also determine if the names and abbreviations follow the current naming convention for upper/lower case and frequently used abbreviations.

· The internal number range for a job branch is 81000000 through 81999999, and each job number is automatically created by the system.

The external number range for a job branch is 80000000 through 80999999, and was used for conversion data.

· All abbreviations and titles will be entered using upper and lower case, as in [Upper And Lower Case].

 

 

Access Transaction:

 

Via Menu Path

SAP menu >> Human Resources >> Organizational Management >> Expert Mode >> PP01 - General

Via Transaction Code

PP01

 

 

 

Procedure:

 

SAP Easy Access

1. Update the following required and optional fields:

Field Name

Description

R/O/C

Values

Command

White alphanumeric box in upper left corner used to input transaction codes

R

Enter value in Command.

Example: PP01

2. Click Enter button.

Maintain object

3. Select 30 in the list box.

4. Update the following required and optional fields:

Field Name

Description

R/O/C

Values

From

Effective date of the personnel action

R

Enter value in From.

Example: 06/01/2007

Information:  This is the effective date of the job branch.

5. Click Object button.

6. Click Create infotype (F5) button.

Create Object

7. Update the following required and optional fields:

Field Name

Description

R/O/C

Values

Object abbr.

An abbreviation of up to 12 characters. The abbreviation identifies a specific object (such as an Organizational Unit)

R

Enter value in Object abbr..

Example: EnvInspectr

Object name

Short description of the object to be created.

R

Enter value in Object name.

Example: Environmental Inspections

Information:  Before entering the name and abbreviation, review the new name and abbreviation for consistency with existing names and abbreviations.  Also determine if the names and abbreviations follow the current naming convention for upper/lower case and frequently used abbreviations.

All abbreviations and titles will be entered using upper and lower case, as in [Upper And Lower Case].

8. Click Save (Ctrl+S) button.

Essential relationship Relationships

9. Update the following required and optional fields:

Field Name

Description

R/O/C

Values

ID of related object

Contains an 8-digit number that represents an object. This field identifies the second object involved in a relationship.

R

Enter value in ID of related object.

Example: 91000001

Information:  All relationships require the knowledge of the ID of related object that the current object is being related to.  These object ID's may be found using the match-code search, or may be included in the information provided by OSP.  If the object ID is entered and the user then clicks the Enter key, the corresponding name of the object will populate on the screen for verification.  The user may change this ID if it is incorrect, and should ensure the data is correct before saving.

Information:  The following relationships pertain to the organizational structure:

· An organizational unit is a parent, and can have children organizational units.

· A position is attached to an organizational unit.

· A job family is above a job branch, which is above a job.

· A job belongs to a job branch, which belongs to a job family.

· When creating a job, the job family and job branch must already exist to tie the relationship to.  This relationship data will be provided by OSP.

· A position is assigned to, or described by, a job, but is not attached to a job.

10. Click Enter button.

Information:  Validate that the appropriate relationship has been chosen before continuing.

11. Click Save (Ctrl+S) button.

Maintain object

12. Click Back (F3) button.

13. The system task is complete.