|
There is a need to create a new job that does not have a salary range but does have a series of specific salary values (for example, a training program) - table 510 entry.
Business Process Procedure Overview |
The process of creating a job occurs at the direction of the Office of State Personnel through authority granted by the State Personnel Commission. OSP develops jobs to provide common treatment in the selection, compensation and other employment processes for State government entities subject to the State Personnel Act. A job is a generalized description of duties and responsibilities sufficiently similar in duty assignment to justify that common treatment. OSP must provide the following: name, abbreviation, job family, job branch, EEO code, State SOC code, retirement code, effective date and FLSA status. T 510 Graded and Flat Rate 01/02 - Graded and Trainee 01/03 - Graded and Apprenticeship 03/03 - Flat Rate and Judicial 03/13 - Flat Rate and NCSM For the combinations above, the expected results are: 1. Class range is populated from either the planned compensation of the position or from the job, if there is no planned compensation record for the position. 2. The class range is populated from the actual level stored on the position or the job. 3. Since there are no salary ranges in table 510, the class range on IT9025 has the same value in both the "min" and the "max" fields. 4. The first field in the class range field is open for editing allowing the user to change the entry but the value in the maximum value field is locked for editing. 5. Salary grade equivalent and competency level field are grayed out.
|
Tips and Tricks
· This BPP will be used to create jobs that derive their salary date from Table 510. They are jobs that have no salary ranges but one value in one salary table per pay scale. This table is not used for rated jobs.
· All jobs must be assigned a retirement code, State SOC code, EEO category, effective date, job branch and job family.
· The internal number range for a job is 31000000 through 31999999, and each job number is automatically created by the system.
The external number range for a job is 30000000 through 30999999, and was used for conversion data.
· Other than this number range, there is no logic attached to the job ID.
Procedure:
SAP Easy Access
|
1. Update the following required and optional fields:
Field Name |
Description |
R/O/C |
Values |
White alphanumeric box in upper left corner used to input transaction codes |
R |
Enter value in Command. Example: PQ03 |
Actions for Job
|
3. Update the following required and optional fields:
Field Name |
Description |
R/O/C |
Values |
One-digit code representing the status of an Infotype. |
R |
Enter value in Infotype status. Example: 1 | |
A one to four character code that represents an action. An action is a series of procedures that must be completed in order to achieve a specific objective. |
R |
Enter value in Action. Example: 60 |
Information: The possible actions include:
· 10 = Create Organizational Unit
· 30 = Create Position
· 35 = Create Vacancy Posting
· 36 = Maintain Vacancy Posting
· 60 = Create Job
When you are on the Create Job transaction [PQ03], the only option available will be 60 for creating a job.
4. Update the following required and optional fields:
Field Name |
Description |
R/O/C |
Values |
The date identifying the start of a validty period |
R |
Enter value in Validity. Example: 06/01/2007 |
Information: Typically the beginning date of the job will be the first day of the month, as approved by OSP and/or the State Personnel Commission.
Create Object
|
6. Update the following required and optional fields:
Field Name |
Description |
R/O/C |
Values |
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: MATHPROF | |
Short description of the object to be created. |
R |
Enter value in Object name. Example: Math Professor |
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.
Essential relationship Relationships
|
8. Update the following required and optional fields:
Field Name |
Description |
R/O/C |
Values |
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: 80000024 |
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.
Information: Clicking Enter will validate the ID entered. You may change this ID if it is incorrect, and ensure that the data is correct before saving.
Essential relationship Relationships
|
Create Description
|
11. Select 9105 Job Specification in the Subtype dropdown.
12. Update the following required and optional fields:
Field Name |
Description |
R/O/C |
Values |
Brief text description of the object in focus. |
R |
Enter value in Description field. Example: info as appropriate |
Information: Enter job information in this text field as appropriate. You may copy text from another location and paste it in this text field. There are no limitations of this text field.
Create Planned Compensation
|
Information: For jobs using the 510 table, the Pay Scale tab will be used to enter pay scale information. The screen will default to the Pay Grade tab, the user must click on the Pay Scale tab here.
Create Planned Compensation
|
15. Update the following required and optional fields:
Field Name |
Description |
R/O/C |
Values |
Pay scale type |
R |
Enter value in P.scale type. Example: 03 |
Information: The possible options for the P.scale type (pay scale type) field include:
· 01 = Graded
· 02 = Banded
· 03 = Flat Rate
· 04 = T-Grade
· 05 = X-Grade
16. Update the following required and optional fields:
Field Name |
Description |
R/O/C |
Values |
Distinguishes the salary structure. Some examples include: · 09 Flat Rate Judicial · 14 Flat Rate Judicial Hourly |
R |
Enter value in PS Area. Example: 13 |
Information: The possible options for the PS Area (pay scale area) field include:
· 01 = Annual salaries
· 02 = Trainee
· 03 = Apprenticeship
· 04 = Physician
· 05 = Pilot Bands
· 06 = Career Banding
· 07 = Skill Based Pay
· 08 = Education
· 09 = Judicial
· 10 = Lottery
· 11 = Hourly
· 12 = SMR - Delimited
· 13 = Faculty NCSM
· 14 = Flat Rate
· 15 = X-Grade
17. Update the following required and optional fields:
Field Name |
Description |
R/O/C |
Values |
This is the Employee Subgroup for Capacity field which set at configuration and is always "3". |
R |
Enter value in ESG for CAP. Example: 3 |
Information: The ESG for CAP (employee subgroup for CAP) will always be [3].
18. Update the following required and optional fields:
Field Name |
Description |
R/O/C |
Values |
Defines the code for the salary range within the pay grade. Each level has a minimum and a maximum amount. |
R |
Enter value in Pay Scale Group. Example: F000 |
Information: Choose the appropriate Pay Scale Group from the match-code search drop down.
Information: Planned compensation is found on all jobs except banded jobs. Planned compensation for banded jobs is found on the position in order to provide the appropriate range for that specific position (usually contributing, journey or advanced).
Information: For Jobs from Table 510 given below are the possible combination of Pay Grade type and area. Pick the combination based on the type of job that needs to be created.
Pay Grade Type Pay Grade Area
Graded (01) Trainee (2)
Graded (01 Apprenticeship (03)
Flat Rate (03) Judicial (09)
Flat Rate (03) NCSM (13)
Change View "Infotype 1610: US Job Attributes": Details
|
Field Name |
Description |
R/O/C |
Values |
Equal Employment Opportunity category. |
R |
Enter value in EEO category. Example: 02 |
Information: The AAP category, OCC Category, and FLSA Indicator fields are not used. Only enter data on the EEO category field within the Equal Opportunity Employment section.
Change View "Infotype 1610: US Job Attributes": Details
|
Critical: Must process ZOMJOB after you create a job in order to update the OM ZOMJOB table (entering the SOC Code and Retirement Code). See BPP for ZOMJOB. If additional information is necessary, refer to the configuration/user guide for OM Z Tables.
Critical: For all banded jobs and flat rate jobs from table 710, and graded jobs from table 510 skip the planned compensation infotype during the action. The 8 digit ID of the job needs to be entered in the pay grade field in the salary tables T710 and T510. Users must send communication to Shared Services to request entering the job ID into the salary tables.
Actions for Job
|
button.
button.
button.
button.
button.
button.
tab button.
button.
button.
button.
button.
button.
button.