Setup Position Budgeting - PBSTRQ

The Position Budgeting (PB) Setup (PBSTRQ) page consists of the following tabs, for the input information that governs the import process.

Create model definition.
Set up global data.
Data import selection criteria.
Record type import selection.

Model: Enter a model name. The model name uniquely identifies records that belong to a model.

Description: Enter a description for the model. The description will be displayed on all pages that have the Model field.

Create Model Definition Tab

The Create Model Definition tab is used to create a model definition. The page can also activate several special functions in the import and calculation program.

Comments: Information about the model can be entered in the Comments fields. This is very helpful when needing to see what modifications were done to data within a model.

Entity: Indicates the entity for which the model is created. If a site has multiple entities, then a model for each entity will have to be created. Code values are defined in the HR Entity Codes (HRRQEN) page.

Data Import Begin/End Dates: Enter a data import begin and end date. When creating a future budget these dates usually represent the dates of the current fiscal year. Remember that the PB system is designed to project a future budget based on current information.

Calc Method: The Calc Method field is only used if a client has paid for customization to the calculation program. If such an entered customization has been made, then the client ID would be into the Calc Method field. Otherwise, it will be left blank.

Debug: This field controls the amount of debug information displayed in tail sheets. To show extensive debug set the code to Y.

Override Calculation Begin Date: Normally, the Data Import Dates are used as the model calculation dates. If though, the cost for a specific date range is needed, then override calculations begin date may be entered. If entered, this date must be greater than the Data Import Begin Date. If this field is left blank, then the Data Import Begin Date will be used as the calculations begin date.

Override Calculation End Date: Normally, the Data Import Dates are used as the model calculation dates. If though, the cost for a specific date range is needed, then an override calculation end date may be entered. If entered, this date must be less than the Data Import End Date. If this field is left blank, then the Data Import End Date will be used as the calculation end date.

Years of Service Date: This date is used to calculate years of service for the following Employee Master Dates: Original Hire, Hire, Leave, Separation, District Seniority, POS/PCN Seniority, and Longevity. These years of service are written to the Employee Information page and may be referenced by the PB utilities and Import Support Information page.

Ledger: Select the general ledger code to associate with the model. Code values are defined in the GL General Information (GLUPGN) page.

Re-Import: This field is used to perform a special import after a normal import has been performed. When this field is selected then only the employees that meet the model selection criteria will be deleted and re-imported. For example, if the selection criteria on Data Import Selection Tab were changed to only import a specific bargaining unit, then only those employees assigned to that bargaining unit will be deleted and re-imported.

Misc Field 1 - 8: The eight Misc fields may be used to store any 10-character (max) client desired misc codes. The Misc fields also have predefined codes that activate special functionality in the import and calculation programs.

The codes and a description of the functionality that the codes activate are:

FTE=APU1 — This code is used to set the PCN FTE equal to APU1 when importing records from Employee Pay Assignments to the PB Benefit Information page. Since the HR Quick Pay Assignments (HRPYQP) page does not have APU values, the FTE is still used for HRPYQP records.
FTE=APU2 — This code is used to set the PCN FTE equal to APU2 when importing records from Employee Pay Assignments to the PB Benefit Information page. Since HRPYQP does not have APU values, the FTE is still used for HRPYQP records. Do not enter both FTE=APU1 and FTE=APU2 into the Misc fields. If this is done, then the FTE=APU2 code will be used.
USEINDEX — If the salary index is to be imported for overridden HR pay assignments, use this option. Normally, the salary index is not imported for HR pay assignments with the salary override field set to Y or for HR pay assignments attached to salary indexes that are a Min/Max type. Salary indexes are not imported for these pay assignments because the amounts have been manually entered. Thus, the amounts do not necessarily correspond to the amount on the salary table. Since PB calculates salaries based on the salary index, this would cause inaccuracies when calculating these pay assignments. The actual annual amount is imported in place of the salary index.
REORDERSAL — This code is used to re-order a salary table so that each step on the salary table is the next logical step when performing step increases (if not already set up that way). If this code is used, then the Misc field at the end of each salary index on the PB Salary Table Information page, that is to be re-ordered, must contain a new step. All salary indexes that were marked for re-order will be changed on the PB Salary Table Information and the PB Pay Assignments pages.
NOTABLELCK — This code will prevent the PB system from locking tables in exclusive mode. Normally, when importing data, calculating a model, or while running a utility, the PB system locks tables in exclusive mode. The advantage to this is that while a table is locked exclusively, no other process may update the data in that table. This ensures the integrity of the data. The disadvantage is that no other process may update the table while it is locked. Thus, if a model is being imported and another model is having a utility run on it, then locking errors can occur. The client needs to decide whether absolute data integrity or allowing users the ability to update tables simultaneously is more important.
BENERATFTE — This code applies to the Calc Pay Assignment Ratio FTEs/Hrs utility (PBUTCR). It will cause the calculated value from the Sum of all Pay Assignment FTEs field to be written to the Misc 4 field on the PBUPEM, Benefits page. The value may then be used, via an SQL statement in PBTBPU, to prorate a benefit amount/percent value. Example SQL: Update pcbencod set amount = amount * misc4 where cdh = 1654.
BENERATHRS — This code applies to the Calc Pay Assignment Ratio FTEs/Hrs utility (PBUTCR). It will cause the calculated value from the Pay Assignment Hours Sum field to be written to the Misc 3 field on the PBUPEM, Benefits page. The value may then be used, via an SQL statement in PBTBPU, to prorate a benefit amount/percent value. Example SQL: Update pcbencod set amount = amount * misc3 where cdh = 1654.
FLAT*RT% — This code will make the system multiply the value in the Flat Salary field by the value in the RT% field. Normally, this only happens for the amounts that are tied to salary indexes.
PRORTESAL$ — This code will make the system multiply the value in the Flat Salary field by the calculated date ratio for a pay assignment. Normally, this does not happen.
WA — Only clients in the state of Washington use this code. It causes the import program to import retirement information from RETIREWA instead of RETIRECA.

Information on Last Processing of Import/Calculation/Batch Creation

Import ID: This field is system derived and displays the ID of the user that performed the most recent data import into the model. If the When field, following the Last Import ID field, is blank, then the Last Import ID field will contain the ID of the user that created the Create Model Definition entry.

When: This field is system generated and denotes the last time that data was imported into the model.

Calc ID: This field is system generated and displays the ID of the user that last calculated the model.

When: This field is system generated and denotes the last time that the model was calculated.

Batch ID: Display only field.

When: Display only field.

Interface: Display only field.

Batch: Display only field.

Setup Global Data Tab

The Setup Global Data tab contains default information used by the import and calculation programs.

System Setup Tab

O/T Object Code: Enter a default overtime object code. This object code will be used if an org key and amount/percent is entered on the PB Overtime Information (PBSTMA) page without entering an object code or CDH#.

Period Type: A default period type. This value is used by the calculation program to determine a number of periods for any entry on the PB Employee Information page with an AXP of P or on the PB Benefit Information page, that is attached to a salary index with an AXP of P and with a P in the Period Tp field on the PB Benefit Information page.

Hours/Year: If a record on the PB Benefit Information page has 0 <zero> Days or 0 Hours and is attached to a salary index with an AXP of H (these pay assignments are calculated using: rate * days * hours), then this value will be used as a default number of annual hours when calculating the pay assignment. A warning message will be displayed indicating this value is being used. If this field is blank, then 2080 will be used as the default annual hrs.

Hours/Day: When entering a record on the PB Vacant Positions page, this value will auto-fill the Hours field after the cursor leaves the Model field.

Days/Year: When entering a record on the PB Vacant Positions page, this value will auto-fill the Days field after tabbing from the Model field. Also, if a PB Benefit Information page record has 0 Days and is tied to a daily amount salary table, this value will be used as a default amount of annual days. If left blank, then 260 will be used.

Use Fully Qualified Accounts: If this field is checked, fully qualified accounts are set up in the GL and it activates the fully qualified code in PB.

Default/Actual Info: This field lets the user choose whether to use actual or default hours per day and days per year information from HR Employee Pay Assignments. This is only used when an employee's pay assignment is attached to a salary table that is expressed in hourly amounts. The hourly amount from the salary table is multiplied by the hours per day and then that figure is multiplied by the days per year to determine an annual salary for the employee. If budgeting is determined based on default information then choose D, otherwise choose A to budget by actual amounts from Employee Pay Assignments. If D is chosen, then for HR Quick Pay Assignments records (these records do not have default days/hours information) the days/hours info from the HR PCN/Position Code Definitions (HRTBPC) page will be used. The default is A if this field is left blank. Code values are defined in static codes.

Bargaining Unit from: This field lets the user control from where the bargaining unit on PB pay assignments will be imported. If E (Employee Master) is chosen, then if an employee has multiple pay assignments (e.g., PM, R0, S0, etc.), all of them will be populated with the employee's bargaining unit from Employee Master. IF P (Employee Pay Assignments) is chosen, then the bargaining unit on each pay assignment will be imported into PB. The default is E if this field is left blank. Code values are defined in static codes.

Pay/Calc for Salary: Enter a P if pay dates are used or a C if calc dates are to be used in PB for salary table lookups. Code values are defined in static codes.

Limits Tab

FICA CDH: Enter the CDH associated with FICA (if it has not been auto filled). The FICA, Medicare, SDI, and SUI CDHs should auto-fill after the cursor leaves the Model field in ADD mode. The CDHs are selected from the PY database using Miscellaneous Code 1 as selection criteria. FICA, for example, will have a code of FICA in Miscellaneous Code 1.

FICA Rate: Enter the rate (percent) associated with FICA. Be sure to enter the rate as a whole number (e.g. 5% would be entered as 5.00000, not 0.05000).

FICA Limit: Enter the FICA limit. The limit represents the annual dollars that will be paid on behalf of an employee. It is not the limit on applicable wages.

Medi CDH: Enter the CDH associated with Medicare (if it has not been auto filled). The FICA, Medicare, SDI, and SUI CDHs should auto-fill after the cursor leaves the Model field in ADD mode. The CDHs are selected from the PY database using Miscellaneous Code 1 as selection criteria. Medicare, for example, will have a code of MEDI in Miscellaneous Code 1.

Medi Rate: Enter the rate (percent) associated with Medicare. Be sure to enter the rate as a whole number (e.g. 5% would be entered as 5.00000, not 0.05000).

Medi Limit: Enter the Medicare limit. The limit represents the annual dollars that will be paid on behalf of an employee. It is not the limit on applicable wages.

SDI CDH: Enter the CDH associated with SDI (if it has not been auto filled). The FICA, Medicare, SDI, and SUI CDHs should auto-fill after the cursor leaves the Model field in ADD mode. The CDHs are selected from the PY database using Miscellaneous Code 1 as selection criteria. SDI, for example, will have a code of SDI in Miscellaneous Code 1.

SDI Rate: If SDI is a contribution, then enter the rate (percent) associated with SDI. Be sure to enter the rate as a whole number (e.g. 5% would be entered as 5.00000, not 0.05000).

SDI Limit: Enter the SDI limit. The limit represents the annual dollars that will be paid on behalf of an employee. It is not the limit on applicable wages.

SUI CDH: Enter the CDH associated with SUI (if it has not been auto filled). The FICA, Medicare, SDI, and SUI CDHs should auto-fill after the cursor leaves the Model field in ADD mode. The CDHs are selected from the PY database using Miscellaneous Code 1 as selection criteria. SUI, for example, will have a code of SUI in Miscellaneous Code 1.

SUI Rate: If SUI is a contribution, then enter the rate (percent) associated with SUI. Be sure to enter the rate as a whole number (e.g. 5% would be entered as 5.00000, not 0.05000).

SUI Limit: Enter the SUI limit. The limit represents the annual dollars that will be paid on behalf of an employee. It is not the limit on applicable wages.

Salary Increment Setup

Increment Date 1 & 2 Cluster, Attribute, + Days, OR Salary Increment Date: These fields are related to step increases for pay assignments and control how two effective date fields will be populated. If step increases are based on an employee's hire date or anniversary date (or another date that is stored on one of the clusters in the pick list) then the cluster and attribute of the date field may be entered in the Cluster and Attribute fields. For example, if step increases are effective on an employee's hire date, which resides on Employee Master, then the Cluster field would contain Employee Master and the Attribute field would contain HDT (the column name for hire date).

When the data is imported into the model, the year of the employee's hire date is converted into a year that falls within the model begin and end dates and will be written to one of the Salary Increase Date fields on the pay assignment page. If step increases are based on an entered date (hire date, anniversary date, etc.) plus a number of days (e.g., 30, 60, 90) then this number may be entered into the + Days field. If step increases are based on a predefined date, such as the beginning of the fiscal year, then this date may be entered into one of the Salary Increment Date fields. This date is not modified, so it should fall within the dates of the model. The + Days field may also be used with the Salary Increment Date fields. The system will not allow a salary increment cluster/attribute and a salary increment date to be entered.

Days: This field represents the number of days to add to the Salary Increment Date.

Data Import Selection Criteria

Data Selection Criteria

The Data Import Selection Criteria tabs enable very detailed, client-specific selection criteria to be entered, which will control what data is imported into each model. It can also be used to globally disable the importing of Benefits (HRTBBE/HRPYBE), Miscellaneous Contributions (HRPYPR), Taxes (HRPYPR), Additional Pay (HRPYPA). Retirement (varies by state), or Tax Sheltered Annuities (HRPYPR).

Global Tab

The check boxes below are used to indicate all of the data from the associated pages is to be imported into the model. If only certain data is to be imported, then the fields on the Compensation and Other tabs may be used. The fields, together, control what data, either globally and/or by page, is imported into PB.

Benefits: If the model is to include the cost of benefits, then check the Benefits field. If this field is unchecked, then no benefits from Benefit Information will be imported into the model.

Miscellaneous Contributions: If the model is to include the cost of miscellaneous contributions, then check the Miscellaneous Contributions field. If this field is unchecked, then no contributions from Miscellaneous Contribution assignments will be imported into the model.

Taxes: If the model is to include the cost of tax contributions, then check the Taxes field. If this field is unchecked, then no contributions from tax assignments will be imported into the model.

Additional Contributions: If the model is to include the cost of additional contributions then check the Additional Contributions field. If this field is unchecked, then no contributions from Additional Contributions will be imported into the model.

Retirement: If the model is to include the cost of retirement contributions, then check the Retirement field. If this field is unchecked, then no contributions from Retirement will be imported into the model.

Tax Sheltered Annuities (TSA): If the model is to include the cost of TSA contributions, then check this field. If this field is unchecked, then no TSA contributions from TSA will be imported into the model.

Custom Where Clause Setup For Data Import - Global: Enter the global selection criteria. The Global selection criteria entry creates a list of employee IDs that are allowed to have data imported into the model. Each of the other selection criteria fields (Pay, Benefits, Miscellaneous Contributions, Taxes, Additional Contributions, Retirement, Salary Table, and TSA's) may further limit the records that are imported for those employees, but they cannot cause data to be imported for employees that are not included in the global list. If the Global line is entered as BARGUNIT = CLER or BARGUNIT = MGMT, then only employee's whose bargaining unit, on the hr_empmstr table, equals CLER or MGMT will be imported.

Compensation Tab

Pay: Enter any pay assignment specific selection criteria.

Benefits: Enter any benefit specific selection criteria.

Misc Contributions: Enter any miscellaneous contribution specific selection criteria.

Addl Contributions: Enter any additional contribution specific selection criteria.

Other Tab

Taxes: Enter any tax specific selection criteria.

Retirement: Enter any retirement specific selection criteria.

Salary Table: Enter any salary table specific selection criteria.

TSA's: Enter any TSA specific selection criteria.

Misc Field Selects

The Misc Field selects Tab controls how miscellaneous fields and effective date fields on the PB Benefit Information and PB Pay Assignment pages are populated. These miscellaneous fields are used as custom selection criteria when running utilities. The effective date fields are used as new begin dates when running utilities.

Pay/Employee Master

Pay Assignment Information (Employee Master Only) Misc Field 0-9: Select a column from the supplied list. The data from that column will be imported into the corresponding miscellaneous field on the PB Pay Assignment page.

Pay/Custom Setup

Fields set up on the Pay and Benefits Custom Setup tabs take precedence over the Employee Master tabs.

Screen 0-9: Select a screen name from the supplied list. The screen is used as selection criteria for the column list. (Screen = Cluster)

Column 0-9: Select a column from the supplied list. The data in the column will be imported into the corresponding miscellaneous field on the PB Benefit Information page. (Column = Attribute)

Type: This non-enterable field displays the column type (e.g., CH – Char, YN – Yes/No, etc.).

Position Begin: This field is only enterable for columns with a Type of CH. It indicates the begin position of the data stored in the column to be imported. Example: If the Begin field contains 3, then the data imported into PB will not include the first 2 characters.

Position End: This field is only enterable for columns with a Type of CH. It indicates the end position of the data stored in the column to be imported. Example: If the End field contains 5, then the data imported into PB will not include data after position 5.

Benefits/Employee Master

Employee Benefits Information (Employee Master Only) PCBENCOD 0-4: Select a column from the supplied list. The data from that column will be imported into the corresponding miscellaneous field on the PB Employee Information page.

Benefits/Custom Setup

Fields set up on the Pay and Benefits Custom Setup tabs take precedence over the Employee Master tabs.

Cluster 0-4: Select a screen name from the supplied list. The screen is used as selection criteria for the column list. (Screen = Cluster)

Attribute 0-4: Select a column from the supplied list. The data in the column will be imported into the corresponding miscellaneous field on the PB Employee Information page. (Column = Attribute)

Type: This non-enterable field displays the column type (e.g. CH – Char, YN – Yes/No, etc.).

Begin: This field is only enterable for columns with a Type of CH. It indicates the begin position of the data stored in the column to be imported. Example: If the Begin field contains 3, then the data imported into PB will not include the first 2 characters.

End: This field is only enterable for columns with a Type of CH. It indicates the end position of the data stored in the column to be imported. Example: If the End field contains 5, then the data imported into PB will not include data after position 5.

Dates Tab

Pay 1: Enter an attribute, from the supplied list, that will be imported into the Date 1 field on the PB Benefit Information page. The year of the date stored in HR will be modified to fall within the date range of the model. Thus, if HDT (hire date) was entered and the hire date was 04/03/1989 and the model dates were 07/01/2001 - 06/30/2002, then the date written to the Date 1 field would be 04/31/2002. This date can then be used as selection criteria when running utilities.

Pay 2: Enter an attribute, from the supplied list, that will be imported into the Date 2 field on the PB Benefit Information page. The year of the date stored in HR will be modified to fall within the date range of the model. Thus, if HDT (hire date) was entered and the hire date was 04/03/1989 and the model dates were 07/01/2001 - 06/30/2002, then the date written to the Date 2 field would be 04/31/2002. This date can then be used as selection criteria when running utilities.

Bene 3: Enter an attribute, from the supplied list, that will be imported into the Date 3 field on the PB Employee Information page. The year of the date stored in HR will be modified to fall within the date range of the model. Thus, if LONGEVITY (longevity date) was entered and the longevity date was 04/03/1989 and the model dates were 07/01/2001 - 06/30/2002, then the date written to the Date 3 field would be 04/31/2002. This date can then be used as selection criteria or as an effective date when running utilities.

Bene 4: Enter an attribute, from the supplied list, that will be imported into the Date 4 field on the PB Employee Information page. The year of the date stored in HR will be modified to fall within the date range of the model. Thus, if LONGEVITY (longevity date) was entered and the longevity date was 04/03/1989 and the model dates were 07/01/2001 - 06/30/2002, then the date written to the Date 4 field would be 04/31/2002. This date can then be used as selection criteria or as an effective date when running utilities.

Add (1-4): These fields represent the number of days to add to the imported date.

Record Type Import Selection

The Record Type Import Selection page controls what pay assignment record types will be imported into each model. If all pay assignment record types are to be imported into a model, then select Import All Record Types and refresh the page or reselect your results to see all applicable record types. If only selected record types are to be imported, then they may be entered manually.

Import All Record Types?: If all assigned record types on Employee Pay Assignments are to be imported into the model, then check this field.

Record Types: Enter/view the pay assignment record types that will be imported into the model.