Pay Assignment Utility - HRUTPU

The Human Resources (HR) Pay Assignment Utility (HRUTPU) page is a multi-purpose tool providing support for the mass-creation of pay assignments. Pay Assignment Utility writes PAYA (PAYUTIL added) and PAYU (PAYUTIL updated) to the Action Code field on the Pay Assignments (HRPYPA/HRPYQP) pages. These codes need to exist in HR Non-Entity Specific Codes (HRTBHR) for the Action Code field.

A special common code can be used in conjunction with Pay Assignment Utility options 2, 7, 8, and 9, that will allow the client to clear any combination of Misc, Num, and Special Code fields on the new Pay Assignments created by the Pay Assignment Utility. This functionality was added because many clients have custom FIXALL options that populate some of these fields and that data would not apply to the new Pay Assignments created by the Pay Assignment Utility. If NU Common Codes (NUUPCD), with a Category/Value of PAYU/PAYUCLR is not set up, then Misc, Num, or Special Code fields will not be cleared when the new Pay Assignments are created.

When Copy and Paste functionality is used on this page, the new record (pasted record) will have the Run By and Run Date fields updated to current user and date upon saving.

The NU Common Codes Category/Value of PAYU/MASTER, with a Short Description = DEBUG, can be defined that will cause the resulting tail sheet to show all the common code settings for the Pay Assignment Utility.

List of Common Codes for this Utility:
PAYU/APPRVCD
PAYU/MASTER
PAYU/OPTION1
PAYU/OPTION4
PAYU/OPTION8
PYHR/PAYUCLR
PAYU/SUMFLDS
HRPY/POSACTIV

The utility is divided into sections as listed below:

Option, Roll Type and Test - This section determines the method the Pay Assignment Utility will use to effect pay assignments and whether the utility will update the Pay Assignments pages, or just write a report to the Pay Assignment Utility List (HRUTPL). The utility will run in Browse mode if the Test check box was changed from check marked to blank (e.g., the utility was run in Test mode to test the selection criteria and now the user wants to run the same selection criteria in Real mode).

Selection Criteria - This area provides an array of important fields from Employee Master (HREMEN) and Pay Assignments pages to help select pay assignments to update. The wildcard % is accepted in all selection fields for pattern matching. Placing values in multiple fields has the effect of narrowing the range of pay assignments to be selected. In other words, data values are combined with the “AND” operator, never the “OR” operator. Selections formulated as X and Y and Z tend to become more narrow in scope with each addition.

New Information - This section provides the information necessary to create new pay assignments.

Links: Pay Utility List (HRUTPL) - This companion page stores a report of the pay assignments that were updated or created by the HR Pay Assignments Utility. See example below.

Fields

Option: The Pay Assignments Utility currently offers eight methods, or Options, for effecting changes to pay assignments. Choose from a drop-down list of available Options, documented below.

(Option 1)
Update Pay Assignments with New Salary Schedules: This option is used to force a recalculation of Pay Assignments (the same effect as tabbing through a pay assignment on Pay Assignments pages). This method is commonly used when pay assignments have been created before the underlying Salary Tables have been updated with current salary amounts. By using Option 1, the user can force the updated salary amounts into the pay assignment without having to update individual records manually. However, it is also possible to use Option 1 to make minor data changes to Pay Assignments page records. These changes would include making PCN/Position changes, migration of whole Salary Indexes or portions of Salary Indexes, or processing simple Salary Step Increases. If the Index, Step, or PCN/Position will be changed, NU Common Codes Category/Value of PAYU/OPTION1 must exist. See the Common Code Reference manual for additional information.

(Option 2)
Update Salaries - Insert New Records: This option is used to close out current pay assignments and open new pay assignments in their place. This method is commonly used when a change in salary requires retroactive pay. This method is also used in conjunction with moving continuing contracts between school or fiscal years.

If the utility is to be sensitive to whether a PCN/Position record is Active, then NU Common Codes Category/Value of HRPY/POSACTIV must exist. Nothing needs to be entered anywhere in the common code, it just needs to exist.

If the common code exists, when option 2 is run, if the HR PCN/Position Code Definitions (HRTBPC) page Position Active is anything but null, blank or A, the process will not complete and an error will display in the Pay Utility List page.

The error message is as follows, with the difference always being the Position and PCN numbers: Position 100130 is not active for PCN: 100130 in PCN Table.

(Option 3)
Close Pay Assignments: This option closes the Pay and Calc end dates to those entered on the Pay Assignments Utility for all records that match the selection criteria.

(Option 4)
Assign Template Pay Assignment to Sel. Criteria: This option is based on creating new pay assignments for entire groups based on a predefined template. On many occasions, employees are assigned supplemental stipends that are identical. With this method, the user may define the stipend for one employee and then use that record as the template for all other selected employees. Keep in mind that this method is only useful when everything except the Employee ID and Record Type is identical between two employee pay assignments.

Template: Valid for Option 4 only. Enter the Unique ID of a template record from any of the Pay Assignment pages. When running Option 4, this should be the only field filled out in the New Information section.

To retrieve the Unique ID from the Pay Assignment screen simply click and drag the cursor over the no-entry Unique ID field, right click and copy the data. Then go to this screen and paste the data into the Template field.

Once the data exists in this field and selection criteria exist above, run the Pay Assignment Utility.

The NU Common Codes Category/Value of PAYU/OPTION4 can be used to control the record type assigned to the new pay assignment records. The common code can be used to indicate the existing template record type should be used and if a duplicate record type is encountered, should it be incremented or should the software display an error for that record.

(Option 5)
Adjust Overridden Pay Assignments: This option is the only option that uses the Increase on Fields, Increase in Override Assgns, and Percent/Amount fields in the New Information portion of the screen.

Users are accustomed to running Pay Assignment Utility with current records in the Selection Criteria area, but for Option #5, the user is likely to be choosing future records in the Selection Criteria area. This option should only be used on existing records in the HR Pay Assignments page.

Normally users would run Option #2 first, to create new records, and then use Option #5 to update those records.

To use this option, records in HR Pay Assignments must have the Override Salary flag set to Y (Yes).

(Option 7)
Apply Step Increase Using Experience Data (WA custom): This option is similar to Option 2 in that it closes out the existing pay assignment and opens a new one. Except that in Option 7, the Pay Assignment Utility additionally reads the HR Education and Skills (HREMES) records to determine the sum of experience in order to create a new vertical Salary Step Placement on the Salary Schedule. This method is also used when moving continuing contracts forward into new school or fiscal years.

(Option 8)
Change Course/Grade Using Education Info/Course Units Data (WA): This option is similar to Option 2 in that it closes out the existing pay assignment and opens a new one. Except that in Option 8 the Pay Assignment Utility additionally reads the records on the General tab of Education and Skills to locate a Degree and then reads the records on the Course Units tab to determine the sum of post-degree educational Course Units in order to create a new horizontal Salary Grade Placement on the Salary Schedule. This method is also used when moving continuing contracts forward into new school or fiscal years.

(Option 9)
Run Option 7 and Option 8 Consecutively: This option combines Options 7 and 8 in order to create a one-stop solution to salary placement for continuing contracts carried between school or fiscal years.

Roll Type: This is an optional field used in conjunction with the new Effective Paid Dates (described below) to determine how to treat Paid Dates on the Pay Assignments for Options 2, 7, 8, and 9 only. Two valid codes can be entered into this field: F= Fiscal Year Roll; M= Mid-Period change.

Run Option Guidelines

If Roll Type field is left empty and the Paid Date range on the Pay Assignment Utility is left empty, the Paid Dates on the Pay Assignments records will be empty. Upon pressing enter to run the Pay Assignment Utility, the system will inform the user of this and ask if they wish to continue. If an N is entered, the Pay Assignment Utility will be aborted. If a Y is entered, the Pay Assignment Utility will create Pay Assignments records with empty Paid Effective Dates.
If Roll Type contains an F, and the new Paid Effective Dates range on the Pay Assignment Utility is left empty, the new records in the Pay Assignments will have empty Paid Dates (e.g. the Paid Dates will not roll forward to the new fiscal year).
If Roll Type contains an M, and the new Paid Date range on the Pay Assignment Utility is left empty, the system will open a window to tell the user that any Pay Assignments records that have Paid Dates on them will be skipped and ask if they want to continue. If they answer N, then the Pay Assignment Utility run will be aborted, nothing will be done to Pay Assignments records, and the insert into the Pay Assignment Utility page will be rejected. If they answer Y, then the Pay Assignment Utility will only process Pay Assignments records that have Paid Dates that are empty.
If Roll Type contains an F, and the new Paid Date range on the Pay Assignment Utility is filled, then the Paid Dates on the Pay Assignments records will be treated like pay and calc dates. The current Pay Assignments will be turned off as of the new Paid Begin Date minus 1 day and the new Pay Assignments will be created with the new Paid Begin and new Paid End Dates entered on the Pay Assignment Utility.
If Roll Type contains an M, and the New Paid Date range on the Pay Assignment Utility is filled, then the Paid Dates on Pay Assignments will be treated like pay and calc dates. The current Pay Assignments will be turned off as of the new Paid Begin Date minus 1 day and the new Pay Assignments page records will be created with the new Paid Begin Date and new Paid End Date entered on the Pay Assignment Utility.

Test: Check the field to run in Report Only mode. Uncheck the field to update the Pay Assignments pages.

Each time the Pay Assignment Utility is run, all the parameters supplied on the page are saved to the database. It is possible to create and run a Pay Assignment Utility procedure from Collect Mode if Test is check marked. If the user achieves the desired results from the trial run of the Pay Assignment Utility, then the user can browse that same record in the Pay Assignment Utility, changing the Test field from check marked to blank and then press Enter to save. This method will run the exact same procedure, except that it will update the Pay Assignments pages.

Selection Criteria

Entity: If the user has been set up correctly, the Entity Code will default appropriately. Otherwise, enter the correct Entity. The field defaults to the entity associated with the logged in user on HRRQUS, if a record exists. Code values are defined in the HR Entity Codes (HRRQEN) page.

Employee ID: Input a valid Employee ID (from Pay Assignments) in the field to select a single employee or an array of employees matching a pattern.

Type: Input a valid Employee Type (from Employee Master) in the field to select a single type or an array of types matching a pattern.

Status: Input a valid Employee Payroll Status (from Employee Master) in the field to select a single employee status or an array of statuses matching a pattern.

PCN: Input a valid PCN (from Pay Assignments) in the field to select a single PCN or an array of PCNs matching a pattern.

Position: Input a valid Position (from Pay Assignments) in the field to select a single Position or an array of Positions matching a pattern.

Fiscal Year: Input a valid Fiscal Year (from Pay Assignments) in the field to select records having a certain Fiscal Year or an array of records matching a Fiscal Year pattern.

Action: Select a valid Action Code (from Employee Master) in the field to select records having a certain code.

Record Type: Input a valid Record Type (from Pay Assignments) in the field to select records having a certain Record Type or an array of records matching a Record Type pattern.

Pay Class: Input a valid Pay Class (from Pay Assignments) in the field to select records having a certain Pay Class or an array of records matching a Pay Class pattern.

Calendar: Input a valid Pay Calendar (from Pay Assignments) in the field to select records having a certain Calendar or an array of records matching a Calendar pattern.

Special Function: Input a valid Special Function (from Pay Assignments) in the field to select records having a certain Special Function or an array of records matching a Special Function pattern.

Reason: Input a valid Reason Code (from Pay Assignments) in the field to select records having a certain Reason Code or an array of records matching a Reason Code pattern.

Assignment Status: Input a valid Assignment Status (from Pay Assignments) in the field to select records having a certain Assignment Status or an array of records matching an Assignment Status pattern.

Bargain Unit: Input a valid Bargain Unit (from Pay Assignments) in the field to select all records having that Bargain Unit or an array of Bargain Units matching a pattern.

Department: Input a valid Department (from Pay Assignments) in the field to select a single Department or an array of Departments matching a pattern.

Salary Index: Input a valid Salary Index (From Pay Assignments) in the field to select records having a certain index or an array of Salary Indexes matching a pattern. Salary Index values are expressed as Schedule/Range/Step or Bargaining Unit/Schedule/Range/Step. Any portion of an index that the user would prefer to leave as a variable can be expressed as %, which is the wildcard pattern matching character.

Example 1	The user wants to select all records that share Salary Schedule ACME. All ranges and steps of the ACME schedule are to be included, thus the input value is ACME//. Since no specific pattern matching needs to occur at the range or step level, the simple addition of the / (forward slash) character that delimits the range, or the / (forward slash) character that delimits the step are sufficient to say: Select all of these. The example would have the effect of choosing all pay assignments on any range or step that share a common Schedule, ACME.
Example 1a	The user wants to select all records that share Salary Schedule ACME and have a Salary Step that is like 05. The input value is ACME//05%. The value of ACME is supplied, while the // (two forward slashes) denotes that any range value may be present. The value of 05% denotes a search for any value that begins in 05 and ends with any variable string following.
Example 2	The user wants to select all records that share a common Salary Range MA+45, regardless of schedule or step values. The input value in this case would be /MA+45/. Since no specific pattern matching needs to occur at the schedule or step level, the simple addition of the / (forward slash) character that delimits the beginning of a range, or the / (forward slash) character which delimits the end of the range are sufficient to say: Select all of these. This would have the effect of choosing all pay assignments on any schedule or step, as long as the range was MA+45.
Example 2a	The user wants to select all records that share a common Salary Range MA+45, but only when paired with salary schedules beginning with A. The input value in this case would be A%/ MA+45/. The value of A% is supplied, meaning any schedule beginning in A, while the /MA+45/ supplies a literal value of Range. The exclusion of any step value denotes that the schedule/range selection will be made regardless of step.
Example 3	The user wants to select all records that share a common Salary Step 05, regardless of schedule or range values. The input value in this case would be //05. Since no specific pattern matching needs to occur at the schedule or range level, the simple addition of the / (forward slash) character that delimits the beginning of a range, or the / (forward slash) character which delimits the beginning of a step are sufficient to say: Select all of these. This would have the effect of choosing all pay assignments on any schedule or range, as long as the step was 05.
Example 3a	The user wants to select all records that share a common Salary Step that is like 05, but only when that step is paired with the ACME schedule and ranges like MA. The input value in this case would be ACME/MA%/05%. The value of ACME is supplied, while the /MA%/ denotes that only ranges beginning in MA will be selected. The value of 05% denotes a search for values that begin with 05 and end with any variable string that follows.

Pay Effective Begin Date: Input a valid begin date (from Pay Assignments) in the field to select all records having that same begin date. Pattern matching does not function in Date fields.

Pay Effective End Date: Input a valid end date (from Pay Assignments) in the field to select all records having that same end date. Pattern matching does not function in Date fields. If left blank, then the existing end dates on the selected pay assignments will be used.

As of Date: Input a valid date (from Pay Assignments) in the field to select all records having a Pay Effective Begin Date less than or equal to and a Pay Effective End Date greater than or equal to the as of date. In other words, select all records active as of the date provided.

Calc Effective Begin Date: Input a valid begin date (from Pay Assignments) in the field to select all records having that same begin date. Pattern matching does not function in Date fields.

Calc Effective End Date: Input a valid end date (from Pay Assignments) in the field to select all records having that same end date. Pattern matching does not function in Date fields. If left blank, the existing end dates on the selected pay assignments will be used.

As of Date: Input a valid date (from Pay Assignments) in the field to select all records having a Calc Effective Begin Date less than or equal to and a Calc Effective End Date greater than or equal to the as of date. In other words, select all records active as of the date provided.

Contract Effective Begin Date: Input a valid begin date (from Pay Assignments) in the field to select all records having that same date. Pattern matching does not function in Date fields.

Contract Effective End Date: Input a valid end date (from Pay Assignments) in the field to select all records having that same date. Pattern matching does not function in Date fields.

As of Date: Input a valid date (from Pay Assignments) in the field to select all records having a Contract Effective Begin Date less than or equal to and a Contract Effective End Date greater than or equal to the as of date. In other words, select all records active as of the date provided.

PCN Effective Begin Date: Input a valid begin date (from Pay Assignments) in the field to select all records having that same date. Pattern matching does not function in Date fields.

PCN Effective End Date: Input a valid end date (from Pay Assignments) in the field to select all records having that same date. Pattern matching does not function in Date fields.

As of Date: Input a valid date (from Pay Assignments) in the field to select all records having a PCN Effective Begin Date less than or equal to and a PCN Effective End Date greater than or equal to the as of date. In other words, select all records active as of the date provided.

HR Select Sequence #: Select a valid HR Select Sequence # (from Pay Assignments) in the field to select all records having that sequence #.

Custom SQL: Input custom selection criteria. Any column from the Employee Master and Pay Assignments pages may be referenced. If the column name appears on both the Pay Assignments and the Employee Master, then a table qualifier of A for Pay Assignments and B for Employee Master must be included.

Example 1

To use hr_emppay.ID, enter A.ID, to use hr_empmstr.DEPARTMENT, enter B.DEPARTMENT.

Example 2

The SQL terms in and not in provide the means necessary to provide Pay Assignments Utility with multiple values for a single data field. The terms in and not in allow the user to supply a list of values delimited by commas and enclosed in parentheses to select a list of values to include (IN) or exclude (NOT IN). So, to enter several Pay Classes to be selected for update the user would type PAYCLASS in (“100”,”200”,”302”,”499”,”500”). To exclude those same classes from a different Pay Assignments Utility run, the user would type PAYCLASS not in (“100”,”200”,”302”,”499”,”500”).

New Information

Pay Effective Begin Date: Input the Pay Begin Date for the new pay assignments. Either this field or the Selection Pay Begin field must be entered. In other words, the user must either fix the Pay Begin Date here, or input a literal pay date in the selection criteria so that only assignments starting on a single date are selected, and consequently created.
If the new Pay Begin and End Dates and the new Calc Begin and End Dates are left blank, then each record that matches the selection criteria will be rolled forward using the dates that exist on the Position Default (HRRQPD) page for the position.

This functionality is for creating pay assignments for a new fiscal year. Thus, the code is not going to close any records that overlap. It will simply give an error message.
The new Fiscal Year field on the Pay Assignments Utility will have to be entered for this option, otherwise an error message will be displayed, and the utility will terminate. The new fiscal year and existing Pay Assignments position will be used as selection criteria for selecting a record from Position Default for each processed pay assignment. The processed pay assignments will have their pay and calc dates replaced with what is on Position Default. The Pay Assignments will then have to be calculated, including calculating actual days and actual periods.

Pay Effective End Date: Input the Pay End Date for the new pay assignments. If left blank, the existing pay assignment Pay End Date will be used.

Calc Effective Begin Date: Input the Calc Begin date for the new pay assignments. If this date is left blank, then the Pay Begin date on the new assignment(s) will be used for the new assignments.
If the new Pay Begin and End dates and the new Calc Begin and End dates are left blank, then each record that matches the selection criteria will be rolled forward using the dates that exist on HR Position Default (HRRQPD) page for the position.

This functionality is for creating pay assignments for a new fiscal year. Thus, the code is not going to close any records that overlap. It will simply give an error message.
The new Fiscal Year field on HR Pay Assignments Utility will have to be entered for this option, otherwise an error message will be displayed, and the utility will terminate. The new fiscal year and existing Pay Assignments position will be used as selection criteria for selecting a record from Position Default for each processed pay assignment. The processed pay assignments will have their pay and calc dates replaced with what is on Position Default. The pay assignments will then have to be calculated, including calculating actual days and actual periods.

Calc Effective End Date: Input the Calc End date for the new pay assignments. If this date is left blank, then the Calc End date on the current assignment(s) will be used for the new assignments.

Paid Effective Begin and End Dates: If these dates are entered in conjunction with a Roll Type code, then the Pay Assignments Paid Dates will be closed out on the old Pay Assignments record and will be used as is on the newly created Pay Assignments record. See the description of Roll Type field for details. If you enter one new Paid Date, you must enter both new Paid Dates.

Contract Effective Begin and End Dates: Enter the Contract Begin Date and End Date for the new pay assignments. If the dates are left blank, then the Contract Begin and End Date on the current assignment(s) will be used for the new assignments.

PCN Effective Begin and End Dates: Enter the PCN Begin Date and End Date for the new pay assignments. If the dates are left blank, then the PCN Begin and End Date on the current assignment(s) will be used for the new assignments.

Fiscal year: Input the Fiscal Year for the new pay assignments. If this field is left blank, then the Fiscal Year from the current assignment(s) will be used for the new assignments.

Action: Select a new Action Code to uniquely identify the new assignments.

As of Date: Input a valid date in this field to select all records having a begin date less than or equal to, and an end date greater than or equal to the as of date. In other words, select all records active as of the date provided. This code is only valid for options 2 and 3.

Reason: Select a new Reason Code to uniquely identify the new assignments.

Assignment Status: Select a new Assignment Status to uniquely identify the new assignments.

Calendar: Select a new Employee Calendar to be used for the pay assignment.

Approval: Select an approval code to indicate whether the record is ready to send, or has been sent, to payroll. If the record is to be sent to payroll, it must indicate SEND.

Range Increase: Ranges to increase to.

Contract Sequence #: Select 1 to increment the contract sequence number. Select 2 to reset the contract sequence number to 01.

Override Salary: This field allows the user to override the current value of the Override salary field. Enter Y or leave blank to prevent the HR Pay Assignment Utility from forcing a recalculation of Salary for the new assignment. Enter N to reset the override value and allow the Pay Assignment Utility to force a recalculation of salary for the new assignment.

Override Hours/Days: This field allows the user to override the current value of the Override Days/Hours field. Enter Y or leave blank to prevent the Pay Assignment Utility from forcing a recalculation of Days and Hours for the new assignment. Enter N to reset the override value and allow the Pay Assignment Utility to force a recalculation of Days and Hours for the new assignment.

Steps to Increase: Input the number of Salary Steps to increase the new assignment. This is a simple step increase, meaning that if the number 1 is expressed in the field, the Pay Assignments utility will simply locate the next sequential step on the Salary Definitions (HRTBSL) record and change the Salary Index to reflect that step. If there are no more steps available to use, a message will display on the record in the Pay Assignment Utility List (HRUTPL) page. If Common Code PAYU/MASTER, Associated Codes #5 contains BLOCK, no processing of the record will occur and the HRUTPL record will have the Error checkbox selected, with a message about the maximum step being realized. If the common code is not set to block, processing will occur up to the maximum step and the HRUTPL record will display a warning/informational message.

To cause a decrease/reversal of steps, the NU Common Codes Category/Value of PAYU/MASTER must have CUSTOM_STEPS entered into Associated Codes 1 and the Salary Definitions record must have RVSI in the Misc 1 field at the bottom of the page. A positive number is still entered into the Steps to Increase field but is interpreted by the software to be negative.

Retro Type: Input a Retroactive Type.

Retro Begin: Enter the date in the past at which point the Retroactive Pay process will begin calculating.

Payout Type: Enter L to instruct the Retroactive Pay process to pay a lump sum payment of retro dollars. Enter S to instruct the Retroactive Pay process to spread payment of retro dollars across the remaining periods to be paid on the contract.

PCN: Select a new Position Control Number if the user desires to migrate the new pay assignment to a new PCN number at the time the assignment is created. If a new PCN is specified, a new Position must be specified as well.
The utility does not check position control when changing a PCN/Position. If a PCN/Position is to be changed, then the following selection criteria fields must be entered:
Entity
PCN
Position
At least one of the following dates:
Pay Begin
Pay End
Pay As of
Calc Begin
Calc End
Calc As of

Position: Select a new Position if the user desires to migrate the new pay assignment to a new Position at the time the assignment is created. If a new Position is specified, a new PCN must be specified as well.

Template: Valid for Option 4 only. Enter the Unique ID of a template record from any of the Pay Assignment screens (HRPYPA/HRPYQP). When running Option 4, this should be the only field filled out in the New Information section.
To retrieve the Unique ID from the Pay Assignment screen simply click and drag the cursor over the no-entry Unique ID field, right click and copy the data. Then go to this screen and paste the data into the Template field.
Once the data exists in this field and selection criteria exist above, run the Pay Assignment Utility (HRUTPU).

Salary Index: Input a whole or portion of a new Salary Index. If only part of a new salary index is entered, then a slash ( / ) will indicate the start of a new part of the salary index.

Example 1:	Change from an existing Schedule to Schedule MGMT, while keeping the same grade and step. Thus, the new salary index would be entered as MGMT. Only the first part of the salary index is to be changed, thus no slashes are needed.
Example 2:	Change from an existing range to Range 002, while keeping the same Schedule and Step. Thus, the new salary index would be entered as /002. Only the second part of the salary index is to be changed, thus one slash is entered.
Example 3:	Same as above, but for a salary index that begins with Bargain Unit (Salary Index Code Use = 02 on Salary Schedule Codes (HRTBSC). Thus, the new salary index would be entered as //002. Only the third part of the salary index is to be changed, thus two slashes are entered. This is also applicable for multiple part changes, such as, a new salary index entered as /002/01. The range and step will be replaced on the processed records. To replace the schedule and step, the new salary index would be entered as MGMT//05. When migrating indexes from more than one Salary Schedule, all of the Salary Schedules attached to the selected records must have the same entry in the Salary Index Code Use field on Salary Schedule Codes. If all of the records do not have the same value in this field, then the utility is to display an error message and terminate without making any changes. Each newly created salary index must have a valid entry on Salary Definitions (HRTBSL) for the Entity and appropriate date range (e.g., Pay or Calculation dates, determined by a flag on HR System Set Up (HRRQSS, Addl Pay Info tab). If a matching entry is not found on Salary Definitions, then skip the pay assignment and write an error message to the Pay Assignment Utility List.

Change on Field: Select the field on Pay Assignment Pages to which to apply the adjustment. After the specified field amount has been adjusted, the code that is triggered when entering a value in the Re-Calc Code field will fire to calculate the other actual amount fields.

Change in Override Assgns: Input the adjustment amount. This can be a flat dollar or percent amount. If a percent is entered, then it must be >= -100 and <= 100.

Percent/Amount: This field indicates if the value in the Amount field is a flat dollar or percent amount.

Run Information

Run By: System derived. The User ID of the user who ran a particular procedure.

Run Date: System derived. The date and time the utility was run.

Additional Specifications

Specifications for Option 7

Change/Update the Salary Step placement for an employee based on information stored in the Education and Skills (HREMES, Experience tab) page.

Sum all records on the Education and Skills, Experience tab, with an Action Code not equal to UTIL and a Total Add Code equal to CERT (formula described below).
Sum all records on the Education and Skills, Experience tab, with an action code equal to UTIL, a Total Add Code equal to CERT, and having the same Fiscal Year (this is entered in MISCCODE1). A unique sum will be calculated for each fiscal year on the Education and Skills for entries with the Action Code equal to UTIL and the Misc. Code 1 field equal to a non-null, non-blank, fiscal year value. If any of these sums are greater than 1, then set them to 1.

Example:

The employee has the following entries:
· 1996-97 Sums to 0.75
· 1997-98 Sums to 1.2 (is re-set to 1)
· 1998-99 Sums to 0.5
· 1999-00 Sums to .9
Then the sum for step B would be (0.75 + 1.00 + 0.50 + 0.90) = 2.70.

Totaling will follow a client specific formula for how to add up the various fields on the Education and Skills, Experience tab. The common code PAYU/SUMFLDS will control what fields are summed.
The result of Step 1 is added to the result of Step 2, the overall number is rounded to the next whole number.

Example:
Step 1 total = 6.75
Step 2 total = 10.50
Overall total = 7.25
Rounded = 17 years of experience
The rounded value, in this case 17, represents the new step on the salary table for the employee's new pay assignment.

If the new step is more than one step above the old step, or if the new step is below the current step, then write a record to HR Pay Assignment Utility List with an appropriate error message.
If the new step does not exist on the salary table, then choose the highest step that is less than the calculated step.

Example:
Look for Step 17, if 17 is not found search for Step 16, if 16 is not found, then step 15, etc. This will continue until HR Pay Assignments Utility arrives back at the original step. The message written to the HR Pay Assignment Utility List should not be Successful, but should be Could not locate step 17, using step 16.

Specifications for Option 8
Create Salary Placement for a New Contract According to Education and Experience. Change/Update the Salary Grade placement for an employee based on information stored in the HR Education and Skills (Course Units and General tabs) page.
Data on the Education and Skills will identify what type of advanced degree the teacher holds.
The steps used in evaluating the Education and Skills page information are listed below:

Record all degrees based on their rank, as established by the HR Entity Specific Misc HR Codes, Course Grade Codes (HRTBCE) page.
Select competing degrees (two Bachelors for same employee) by earliest Issue Date.
Record the Issue Date of the selected Bachelor degree. This is interpreted as follows:
- A Doctoral degree represents the terminus of the grade scale. A PHD cancels the need to accumulate credits. A Master's degree is treated as higher than a Bachelor degree, used when evaluating the Education and Skills (Course Units tab) information.
Record the Issue Date of the Master's Degree, if applicable. Special note should be made if the MA degree is the only record present.
HR Education and Skills (Course Units tab) data tells how many continuing education credits the employee has earned. The page is used to sum all Post-MA, Post-BA, and Grandfather Credits. It is interpreted as follows:

All entries marked P for pending (this will be stored in Misc. Code 4) will only be included if the run-time question Include Pending CRSEUNIT Entries? is affirmative.
The Accepted 1 field will always be used for accumulation (never use the Accepted 2 field).
Sum all records with an Applied Date before January 1, 1992. These are considered Grandfather Credits. If sum of Grandfather Credits is greater than or equal to 135, then select the Salary Grade from the HR Entity Specific Misc HR Codes, Course Grade Codes tab, that has the Grandfather Field set to G. If Grandfather sum is >= 135, no other processing is performed.
If an employee has an MA and a BA, then accumulate Post-MA and Post-BA credits. Post BA credits are defined as: All records with an Applied Date greater than or equal to the Applied Date on the BA record and less than the Applied Date on the MA record.
If an employee only has an MA, then accumulate post MA credits only. Post MA credits are defined as: All records with an Applied Date greater than or equal to the Applied Date on the MA record.
If the employee has a BA and an MA, then calculate their credits as follows: Post-MA credits + Post-BA credits - 45. If this formula returns a value that is less than 0, the value is set to 0. Round the sum to the nearest whole number.

Pair the highest-ranking degree with the sum of course units and select the appropriate matching record from the HR Entity Specific Misc HR Codes (HRTBCE), Course Grade Codes.
Replace the Grade (Range) portion of Salary Index on the Pay Assignments with the Grade from HR Entity Specific Misc HR Codes (HRTBCE), Course Grade Codes. Create the new salary index using the salary grade and verify that it is valid. If it is invalid, then write an error message to the HR Pay Assignment Utility List and skip the record, else proceed with the normal HR Pay Assignment Utility functionality.

Example:
A certified employee who last year held a Bachelor Degree with 35 Credits, but recently (during the summer) earned a Master's degree, would have his/her pay assignments active from September 1, closed out. In addition, new pay assignments would be created that would show the employee advancing to the Masters plus Zero Credits Salary Grade.
By default, the Pay Assignment Utility only processes Pay Assignments records with an approval code of SEND. The NU Common Codes Category/Value of PAYU/APPRVCD may be set up to cause the Pay Assignment Utility to process up to five additional approval codes.

Tools for Pay Assignment Utility

Show Selection Criteria

This tool is available under the Tools section of the Option Bar under Tools for Pay Assignment Utility page. The tool is used to show the selection criteria (i.e., the generated SQL). The tool is active only in Add mode and requires that all the mandatory fields be selected.

Links

Clicking on link opens the Pay Assignment Utility List (HRUTPL) page.