There is a need to create a new non-banded job that has a salary range (to include minimum, maximum and reference salaries) - table 710.
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. To create a new position, transaction PQ03 is used. Required infotypes for the job object will need to be created with the required validity dates. Once the job is created, the requesting party is notified with the job number and description. For Graded Judicial there is only one level with a grade - GR. For Flat Rate Judicial there is only one level with a grade - FR. Outlined below are the list of combinations and their expected outcomes in IT9025 based on the planned compensation stored either on the position or on the related job. T710 - Graded/Flat Rate/T Grade and X Grade 01/01 - Graded and Annual salaries 01/04 - Graded and Physician 01/08 - Graded and Education 01/09 - Graded and Judicial 01/11 - Graded and Hourly 03/09 - Flat Rate and Judicial 03/14 - Flat Rate and Flat Rate 04/01 - T Grade and Annual Salaries 05/05 - X Grade and X Grade For the combinations above, the expected results are: 1. Class range is populated from either the planned compensation of a position or from the planned compensation of the job (if the position does not have a planned compensation record). 2. The class range populated would be from the level encompassing the whole range irrespective of the level stored on the position or the job. For example, if the job and position have the same pay grade but the position has a different level than the level that encompasses the whole range, the range populated on IT9025 will still be the level that encompasses the whole range. If the position has a different grade than that of the job and the level stored on the position does not encompass the whole range, then the range on IT9025 will still be populated from the level tied to the pay grade of the position that encompasses the whole range. For example, GR for Graded and T Grade, FR for Flat Rate, and XG for X Grade. 3. Class range is grayed out for editing. 4. Salary grade equivalent and competency level fields are grayed out. T 710 - Banded 02/05 - Banded and Pilot Bands 02/07 - Banding and Skill Based Pay 02/10 - Banding and Lottery 02/06 - Banding and Career Banded For the combinations above, the expected results are: 1. Class range is populated from either the planned compensation of the position or from the planned compensation of the job, if the position does not have a planned compensation record. 2. The class range populated would be from the level encompassing the whole range irrespective of the level stored on the position. For example, if the job and position have the same pay grade but the position has a different level than the level that encompasses the whole range, the range populated on IT9025 will still be the level that encompasses the whole range. If the position has a different grade than that of the job and the level stored on the position does not encompass the whole range, then the range on IT9025 will still be populated from the level tied to the pay grade of the position that encompasses the whole rage. For example, 02/05 = Level PB, 02/07 = Level 00, 02/10 = Level 00, or 02/06 = Level CB. 3. Class range is open for editing. 4. Salary grade equivalent field is open for editing. 5. Competency level field is grayed out for all banded positions except for the Banded/Career Banding combination. For this combination, pick from levels A, J, or C for the competency level.
|
Tips and Tricks
· Non-Banded Jobs include: Graded, Flat Rate, T Grade, and X Grade Jobs (Explained further on).
· All jobs must be assigned a retirement code, State SEC 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 the number range, there is 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 | |
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.
4. Update the following required and optional fields:
Field Name |
Description |
R/O/C |
Values |
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 |
· 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.
Actions for Job
|
Create Object
|
7. 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: AstroRscher | |
Short description of the object to be created. |
R |
Enter value in Object name. Example: Astronomy Researcher 1 |
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
|
9. 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: 80000066 |
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: Click Enter to validate the object ID entered. Make sure the object ID is correct before saving.
Essential relationship Relationships
|
Create Description
|
12. Select 9105 Job Specification in the Subtype dropdown.
13. 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. Example: the appropriate description |
Information: Enter job specific text in the text field. 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
|
15. Select 10 USA in the Ctry Grouping dropdown.
16. Update the following required and optional fields:
Field Name |
Description |
R/O/C |
Values |
Type of pay grade. Distinguishes between the different types of pay grade structures, such as · 01 Graded · 02 Banded · 03 Flat rate · 04 T-Grade · 05 X-Grade This field is populated from the Planned Compensation infotype for the Job |
R |
Enter value in Pay grade type. Example: 01 | |
Distinguishes the salary structure. Some examples include: · 09 Flat Rate Judicial · 14 Flat Rate Judicial Hourly |
R |
Enter value in Pay grade area. Example: 01 | |
Stores the minimum of pay range. This field is populated by the Planned Compensation infotype record for the Job |
R |
Enter value in Pay grade. Example: GR72 |
Information: For Non Banded Jobs, given below, are the possible combinations 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 Pay Grade Level
· Graded (01) Annual Salaries (01) GR
· Graded (01) Physician (04) GR
· Graded (01) Education (08) GR
· Graded (01) Judicial (09) GR
· Graded (01) Hourly (11) GR
· Flat Rate (03) Judicial (09) FR
· Flat Rate (03) Flat Rate (14) FR
· T-Grade (04) Annual Salaries (01) GR
· X-Grade (05) X-Grade (15) XG
For all Non-Banded Jobs the level that stores the complete range should be picked by work at the field inside by Grade Area on the top.
Information: If the Planned Compensation on the position is needed then one can be created above the level. For a job (01) Graded / 01 Annual Salary - GR 50. Position Level could be Q1 / Q2 / Q3 or Q4.
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 (contributing, journey or advanced).
Information: For Graded Judicial there is only one level with a grade - GR.
For Flat Rate Judicial there is only one level with a grade - FR
Information: Clicking Enter will validate the data and populate the rest of the fields on this screen.
Create Planned Compensation
|
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: AAP category, OCC category, and FLSA Indicator are not used on this screen. Only enter the EEO category under the Equal Opportunity Employment section.
Change View "Infotype 1610: US Job Attributes": Details
|
Change View "Infotype 1610: US Job Attributes": Overview
|
Actions for Job
|
Critical: Must Process ZOMJOB after you create a job in order to update the OM ZOMJOB table. See BPP for ZOMJOB.
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.