Business Rules Setup - STUPBR
The SubTracker (ST) Business Rules Setup (STUPBR) page allows the user to specify which types of input records should become SubTracker Attendance records and which types should be ignored (some types of records may exist in an external system which are obsolete or superfluous to BusinessPlus, and thus should not result in a timecard record). It also allows the user to specify which BusinessPlus CDH should be used for those records that are to become timecards.
The top section of the page specifies the criteria against which to test an incoming record (incoming records are the records being read from the ST Imported Data (STUPIM) page). Records having values that match the combination of values in a particular record will be processed according to the user specifications at the bottom of that page.
Entity: When the ST Load Flat File (STUTLF) utility was run to load the file from the Substitute Call-In system, an Entity ID was provided. That entity was applied to all of the records that were imported from that particular flat file. If multiple entities exist, be sure that all records in ST Business Rules Setup page are applied to the correct entity.
Timecard Hour Rules
Abs or Sub: Each record that comes in from the ST Imported Data page may have: 1) an Absentee ID AND a Substitute ID, 2) just an Absentee ID, OR 3) just a Substitute ID. Because of this, and because the Absentee portion of a record may be processed differently than the Substitute portion of a record, the process goes through this page once for each portion of the record to find records that match this criteria. This flag identifies which portion of the record should be processed based on this business rule. Valid codes for this field are A for Absentee and S for Substitute.
Input Format: Used to identify which type of imported record should be processed by this business rule.
Valid options are:
1 – Both Absentee ID and Substitute ID
2 – Only Absentee ID
3 – Only Substitute ID
4 – Catch-All – Use if others do not apply
If, on the imported data record being processed, either the Absentee or the Substitute ID contains an ID that is set up as a BLANKME ID in ST Translation Table (STUPTR) page, SubTracker will ignore that portion of the imported data record as if it was empty. For example: If the ST Business Rules Setup page is defined to only create timecard records from those import records that have both an Absentee and Substitute ID present, a 1 would be placed in this Input Record Format field. In this case, if the Absentee ID or the Substitute ID is missing from the imported data record OR if either ID was associated with a BLANKME entry, this entry would NOT be picked up as an applicable rule for that kind of imported data record. The ST Business Rules Setup page could be defined for special entries (possibly with a different CDH number) that are used in the case where a record only has an Absentee ID or a Substitute ID.
Precedence: This is used to determine the order in which the records on this tab are processed. Since SubTracker processes a particular portion of the record (either Absentee or Sub) only once if it matches the criteria, it is important that the more detailed rules (exceptions) are defined with a higher precedence (lower number) than the general, Catch-All rules.
Begin/End Date: On the record coming from the imported data, there is a field that represents the date that the absence took place. The records can be selected by an Absence Date or a range of Absence Dates. Begin Date defaults to 01/01/1901 and End Date defaults to 12/31/2050.
Reason Code: Select the reason code to which this rule applies. Code values are defined in Reason Codes (STUPCD) page.
Imported Account: If the records from the 3 rd Party file had an account number, the account number was written to the Imported Account field on the ST Imported Data (STUPIM) record when the ST Load Flat File utility was run. If the records can be selected based on the account information, enter the account here.
Imported Position: If the records from the 3 rd Party file had position number, the position was written to the Imported Position field on the ST Imported Data (STUPIM) record when the ST Load Flat File utility was run. If the records can be selected based on the position information, enter the position here.
Imported Site: If the records from the 3 rd Party file had a site code, this site code was written to the Imported Site field on the ST Imported Data (STUPIM) record when the ST Load Flat File utility was run. If the records can be selected based on the site information, enter it here.
Miscellaneous 1: There are up to 10 Absentee miscellaneous fields and up to 10 Substitute miscellaneous fields that are loaded into the ST Imported Data (STUPIM) record from the import file. On this page, the MISC1 and/or MISC2 from the STUPIM record can be used as selection criteria. If the portion of the incoming record being processed has an Absentee ID on it, the system will look at the Absentee Misc1 field. If the portion of the incoming record being processed has a Substitute ID on it, then the system will look at the Substitute Misc1 field. Remember, each Imported Data record passes through this business rule twice: once to process the Absentee if an Absentee ID is on the record and once to process the Substitute if a Substitute ID is on the record.
Miscellaneous 2: This field operates in the same fashion as Miscellaneous 1.
Generic Miscellaneous 1 & 2: Generic Miscellaneous fields 1 & 2 work in conjunction with STUPIM Absentee/Substitute Miscellaneous fields 03 through 10. Common codes are used to designate which STUPIM miscellaneous field should be validated against STUPBR Generic Miscellaneous fields. See the ST guide for more information.
Employee Selection Criteria
Emp Master Loc: This selection criterion is NOT compared to information in the ST Imported Data page. If the Absentee or Substitute (determined by which portion of the record the system is processing) is an employee and has a record in the Human Resources (HR) Employee Master (HREMEN) page, then that employee's Location from HR Employee Master will be compared against the value entered here as selection criteria.
Abs Barg Unit/Emp Type: This selection criterion is NOT compared to information in the ST Imported Data page. The Type and Bargaining Unit values entered here are compared against the Absentee record in HR Employee Master.
Sub Barg Unit/Emp Type: This selection criterion is NOT compared to information in the ST Imported Data page. If the Substitute is an employee, the Type and Bargaining Unit values entered here are compared against the Substitute record in HR Employee Master.
Create a Timecard: If the check box is left blank, the ST Make Attendance Records (STUTMA) utility will still create entries in the ST Attendance Records (STUPAT) page for matching records. However, the Timecard Flag on the ST Attendance record will be blank, which means the record will not be used in creating a timecard entry. Valid entries for this field are a check mark for YES and blank for NO.
Select the checkbox Create a Timecard to tell the system that a timecard record should be created from an input record matching the criteria specified in the top section of the page. For all records having Create a Timecard checked, the BusinessPlus CDH to be used must be specified in the Hour for Timecard field. If no entry is found for an incoming record (in other words, no entry exists with criteria on the top half of the page that matches the incoming record), an error message will be generated, and the record rejected. The system goes through the page twice: once for the Substitute and once for the Absentee; this is because the CDH to be used for the Absentee is likely to be different from the CDH to be used for the Substitute.
Hour for Timecard: If Create a Timecard has been selected, this field must be filled with an hour code to be used for the timecard entry. Code values are defined in the Payroll Hour Definition (PYUPHH) page.
Pay Rate/String Component Rules
Besides the funding source, BusinessPlus requires the following pay string items to create a timecard record:
Position
Pay class
Step
These items are derived from a pay assignment already assigned to the Absentee or Substitute. The page tells the system which pay assignment record to use for a particular type of incoming record. In exactly the same way as the other Business Rules tabs, the system will attempt to match incoming records against the criteria specified by the combination of values on the top part of the page.
If the selection is by range of positions (defined by position range begin and position range end), and (optionally) MISC1/2, incoming records with positions that fall within the range specified on a particular record will be processed according to the criteria in the bottom section of the page.
Abs or sub: Each record that comes in from the ST Imported Data page may have: 1) an Absentee ID AND a Substitute ID, 2) just an Absentee ID, OR 3) just a Substitute ID. Because of this, and because the Absentee portion of a record may be processed differently than the Substitute portion of a record, the process goes through this page once for each portion of the record to find records that match this criteria. This flag identifies which portion of the record should be processed based on this business rule. Valid codes for this field are A for Absentee and S for Substitute.
Input Format: Used to identify which type of imported record should be processed by this business rule.
Valid options are:
1 – Both Absentee ID and Substitute ID
2 – Only Absentee ID
3 – Only Substitute ID
4 – Catch-All – Use if others do not apply
If, on the imported data record being processed, either the Absentee or the Substitute ID contains an ID that is set up as a BLANKME ID in ST Translation Table page, SubTracker will ignore that portion of the imported data record as if it was empty. For example: If the ST Business Rules Setup page is defined to only create timecard records from those import records that have both an Absentee and Substitute ID present, a 1 would be placed in this Input Record Format field. In this case, if the Absentee ID or the Substitute ID is missing from the imported data record OR if either ID was associated with a BLANKME entry, this entry would NOT be picked up as an applicable rule for that kind of imported data record. The ST Business Rules Setup page could be defined for special entries (possibly with a different CDH number) that are used in the case where a record only has an Absentee ID or a Substitute ID.
Precedence: This is used to determine the order in which the records on this tab are processed. Since SubTracker processes a particular portion of the record (either Absentee or Sub) only once if it matches the criteria, it is important that the more detailed rules (exceptions) are defined with a higher precedence (lower number) than the general, Catch-All rules.
Pos Range Beg/End: Used to define a range of Imported Positions where this rule would apply. If this rule would apply to all Positions, enter a 0 (zero) in the Begin field, and a Z in the End field.
Miscellaneous 1: There are up to 10 Absentee miscellaneous fields and up to 10 Substitute miscellaneous fields that are loaded into the ST Imported Data (STUPIM) record from the import file. On this page, the MISC1 and/or MISC2 from the STUPIM record can be used as selection criteria. If the portion of the incoming record being processed has an Absentee ID on it, the system will look at the Absentee Misc1 field. If the portion of the incoming record being processed has a Substitute ID on it, then the system will look at the Substitute Misc1 field. Remember, each Imported Data record passes through this business rule twice: once to process the Absentee if an Absentee ID is on the record and once to process the Substitute if a Substitute ID is on the record.
Miscellaneous 2: This field operates in the same fashion as Miscellaneous 1.
Generic Miscellaneous 1 & 2: Generic Miscellaneous fields 1 & 2 work in conjunction with STUPIM Absentee/Substitute Miscellaneous fields 03 through 10. Common codes are used to designate which STUPIM miscellaneous field should be validated against STUPBR Generic Miscellaneous fields. See the ST guide for more information.
Pay Assignment
Abs or Sub: Used to identify whether the Absentee (ABS) or Substitute (SUB) pay assignment is to be used to derive pay rate/string information.
At least ONE of the following fields in this section must be specified.
Pay Class: Used to further identify which pay assignment should be used to derive pay rate/string information. Code values are defined in the Payroll Pay Class (PYUPPY) page.
Position: Used to further identify which pay assignment should be used to derive pay rate/string information. Code values are defined in the HR PCN/Position Code Definitions (HRTBPC) page.
Record Type: Used to further identify which pay assignment should be used to derive pay rate/string information.
Position Ends With: Used to further identify which pay assignment should be used to derive pay rate/string information.
Status: Used to further identify which pay assignment should be used to derive pay rate/string information.
Reason Code: Used to further identify which pay assignment should be used to derive pay rate/string information. Code values are defined in the HR Non-Entity Specific Codes (HRTBHR) page under the Code ID of REASON_CODE.
Department: Used to further identify which pay assignment should be used to derive pay rate/string information. Code values are defined in the HR Entity Specific Codes (HRTBCE) page, Entity Specific tab, under the Code ID of DEPARTMENT_CODE.
Derive Hourly Rate: This option allows the process to derive the hourly rate based on a salary table entry. Valid options are:
HD – Highest Dollars
HS – Highest Step
LD – Lowest Dollars
LS – Lowest Step
Acc Derivation Rules
BusinessPlus requires account information (either GL Key/Obj or FQA) in order to create timecard entries. SubTracker includes several possible scenarios that can be set up to derive this information:
Charge to account imported from the 3 rd - Party software.
Charge to pre-determined account(s) based on reason code and/or other incoming criteria (for example, site or type).
Charge to account(s) already assigned on an Absentee Pay Assignment.
Charge to account(s) already assigned on a Substitute Pay Assignment.
Charge to a hard-coded account.
In exactly the same way as the other Business Rules tabs, the system will attempt to match incoming records against the criteria specified by the combination of values on the top part of the page.
Abs or Sub Rule: Each record that comes in from the ST Imported Data (STUPIM) page may have: 1) an Absentee ID AND a Substitute ID, 2) just an Absentee ID, OR 3) just a Substitute ID. Because of this, and because the Absentee portion of a record may be processed differently than the Substitute portion of a record, the process goes through this page once for each portion of the record to find records that match this criteria. This flag identifies which portion of the record should be processed based on this business rule. Valid codes for this field are A for Absentee and S for Substitute.
Input Format: Used to identify which type of imported record should be processed by this business rule.
Valid options are:
1 – Both Absentee ID and Substitute ID
2 – Only Absentee ID
3 – Only Substitute ID
4 – Catch-All – Use if others do not apply
If, on the imported data record being processed, either the Absentee or the Substitute ID contains an ID that is set up as a BLANKME ID in ST Translation Table page, SubTracker will ignore that portion of the imported data record as if it was empty. For example: If the ST Business Rules Setup page is defined to only create timecard records from those import records that have both an Absentee and Substitute ID present, a 1 would be placed in this Input Record Format field. In this case, if the Absentee ID or the Substitute ID is missing from the imported data record OR if either ID was associated with a BLANKME entry, this entry would NOT be picked up as an applicable rule for that kind of imported data record. The ST Business Rules Setup page could be defined for special entries (possibly with a different CDH number) that are used in the case where a record only has an Absentee ID or a Substitute ID.
Precedence: This is used to determine the order in which the records on this tab are processed. Since SubTracker processes a particular portion of the record (either Absentee or Sub) only once if it matches the criteria, it is important that the more detailed rules (exceptions) are defined with a higher precedence (lower number) than the general, Catch-All rules.
Reason Code: Select the reason code to which this rule applies. Code values are defined in Reason Codes (STUPCD) page.
Imported Site: If the records from the 3 rd Party file had a site code, the site code was written to the Imported Site field on the ST Imported Data (STUPIM) record when the ST Load Flat File utility was run. It the records can be selected based on the site code, enter it here.
Imported Account: If the records from the 3 rd Party file had an account number, the account number was written to the Imported Account field on the ST Imported Data (STUPIM) record when the ST Load Flat File utility was run. If the records can be selected based on the account information, enter the account here.
Hour Derived: Since this tab processes after the Timecard Hour Rules tab, the user has the option to identify the hour as selection criteria. Code values are defined in the Payroll Hour Definition (PYUPHH) page.
Imported Position: If the records from the 3 rd Party file had position number, the position number was written to the Imported Position field on the ST Imported Data (STUPIM) record when the ST Load Flat File utility was run. If the records can be selected based on the position information, enter the position here.
Miscellaneous 1: There are up to 10 Absentee miscellaneous fields and up to 10 Substitute miscellaneous fields that are loaded into the Imported Data (STUPIM) record from the file. On this page, the MISC1 and/or MISC2 from the STUPIM record can be used as selection criteria. If the portion of the incoming record being processed has an Absentee ID on it, then the system will look at the Absentee Misc1 field. If the portion of the incoming record being processed has a Substitute ID on it, then the system will look at the Substitute Misc1 field. Remember, each imported data record passes through this business rule twice: once to process the Absentee if an Absentee ID is on the record and once to process the Substitute if a Substitute ID is on the record.
Miscellaneous 2: This field operates in the same fashion as Miscellaneous 1.
Miscellaneous 3: This field operates in the same fashion as Miscellaneous 1.
Generic Miscellaneous 1 & 2: Generic Miscellaneous fields 1 & 2 work in conjunction with STUPIM Absentee/Substitute Miscellaneous fields 03 through 10. Common codes are used to designate which STUPIM miscellaneous field should be validated against STUPBR Generic Miscellaneous fields. See the ST guide for more information.
Employee Selection Criteria
Emp Barg Unit:
Emp Type:
Section A: Derive Based on Pay Assignment(s)
Use this section if deriving the distribution(s) from existing pay assignments. Section A OR Section B may be filled out. Do not fill out both sections.
Derive Account: If selecting distributions based on a record type, enter ABSxx or SUBxx, depending on which record type is desired.
The rest of the fields in this section allow selection of a GROUP of pay assignments (up to 36 distribution records can be selected) which would correspond with this rule. SubTracker will then spread the value using hours per day as the determining factor.
For example: Assume the selection criteria entered pulls up two pay assignment records. One has 5 hours per day; the second has 8 hours per day. The first would receive 5/12ths of the amount and the second would receive 8/12ths of the amount. The distribution percent is then used to control how much to expense to each distribution line.
Pay Assignment
Record Type: SubTracker will group distributions by the entered Record Type. Code values are restricted to static system codes.
Reason: SubTracker will group distributions by the entered Reason Code. Code values are defined in the HR Non-Entity Specific Codes (HRTBHR) page under the Code ID of REASON_CODE.
Pay Class: SubTracker will group distributions by the entered Pay Class. Code values are defined in the Payroll Pay Class (PYUPPY) page.
Department: SubTracker will group distributions by the entered Department. Code values are defined in the HR Entity Specific Codes (HRTBCE) page, Entity Specific tab, under the Code ID of DEPARTMENT_CODE.
Status: SubTracker will group distributions by the entered Pay Assignment Status.
Position: SubTracker will group distributions by the entered Position.
Pay As Of Date: SubTracker will group distributions by selecting Pay Assignments with Pay dates spanning this date. Defaults to Absence Date.
Calc As Of Date: SubTracker will group distributions by selecting Pay Assignments with Calc dates spanning this date. Defaults to Absence Date.
SECTION B: HARD-CODED DISTRIBUTION(S)
If desired, a specific distribution may be entered to be used with this SubTracker rule. Press the Ctrl+W keyboard combination, or click the Option button at the bottom of the page and select Distribution Worksheet to bring up the data-entry page. Once entered, the Distribution Records Present checkbox will be selected, indicating a hard-coded distribution record is present.
Special Override and Adjustment Rules
The Special Override and Adjustment Rules tab allows the user to specify what special rules (if any) should be applied against incoming records. Some users have special requirements with regard to hours/rate thresholds and overrides. In exactly the same way as the other Business Rules tabs, the system will attempt to match incoming records against the criteria specified by the combination of values on the top part of the page.
Since the page is processed after Timecard rules tab, the system already knows which CDH will be used. This allows the user to specify special processing based on the CDH number and/or MISC code(s). If a match is found, the override hours and/or rate and/or pay specified at the bottom of the page will be used on the ST Attendance record(s) created from the input record being processed.
Abs or Sub Rule: Each record that comes in from the ST Imported Data page may have: 1) an Absentee ID AND a Substitute ID, 2) just an Absentee ID, OR 3) just a Substitute ID. Because of this, and because the Absentee portion of a record may be processed differently than the Substitute portion of a record, the process goes through this page once for each portion of the record to find records that match this criteria. This flag identifies which portion of the record should be processed based on this business rule. Valid codes for this field are A for Absentee and S for Substitute.
Input Format: Used to identify which type of imported record should be processed by this business rule.
Valid options are:
1 – Both Absentee ID and Substitute ID
2 – Only Absentee ID
3 – Only Substitute ID
4 – Catch-All – Use if others do not apply
If, on the imported data record being processed, either the Absentee or the Substitute ID contains an ID that is set up as a BLANKME ID in ST Translation Table page, SubTracker will ignore that portion of the imported data record as if it was empty. For example: If the ST Business Rules Setup page is defined to only create timecard records from those import records that have both an Absentee and Substitute ID present, a 1 would be placed in this Input Record Format field. In this case, if the Absentee ID or the Substitute ID is missing from the imported data record OR if either ID was associated with a BLANKME entry, this entry would NOT be picked up as an applicable rule for that kind of imported data record. The Business Rules Setup page could be defined for special entries (possibly with a different CDH number) that are used in the case where a record only has an Absentee ID or a Substitute ID.
Precedence: This is used to determine the order in which the records on this tab are processed. Since SubTracker processes a particular portion of the record (either Absentee or Sub) only once if it matches the criteria, it is important that the more detailed rules (exceptions) are defined with a higher precedence (lower number) than the general, Catch-All rules.
Reason Code: Select the reason code to which this rule applies. Code values are defined in Reason Codes (STUPCD) page.
Hour Def Misc 1-7: Since this page is processed after Timecard Hour Rules, the system already knows which CDH will be used. This allows the user to specify special processing based on the CDH number and/or MISC code(s) from the definition of that CDH in the Payroll (PY) Hour Definition (PYUPHH) page.
Imported Account: If the records from the 3 rd Party file had an account number, the account number was written to the Imported Account field on the ST Imported Data (STUPIM) record when the ST Load Flat File utility was run. If the records can be selected based on this account information, enter the account here.
Imported Position: If the records from the 3 rd Party file had position number, the position number was written to the Imported Position field on the ST Imported Data (STUPIM) record when the ST Load Flat File utility was run. If to the records can be selected based on the position information, enter the position here.
Imported Site: If the records from the 3 rd Party file had a site code, the site code was written to the Imported Site field on the ST Imported Data (STUPIM) record when the ST Load Flat File utility was run. If to the records can be selected based on the site code, enter it here.
Hrs Range Begin/End: The selection criteria can be set for this entry to apply only to records that have Absentee and/or Substitute Hours in a range that is entered here.
Miscellaneous 1: There are up to 10 Absentee miscellaneous fields and up to 10 Substitute miscellaneous fields that are loaded into the ST Imported Data (STUPIM) record from the import file. On this page, the MISC1 and/or MISC2 from the STUPIM record can be used as selection criteria. If the portion of the incoming record being processed has an Absentee ID on it, then the system will look at the Absentee Misc1 field. If the portion of the incoming record being processed has a Substitute ID on it, then the system will look at the Substitute Misc1 field. Remember, each imported data record passes through this business rule twice: once to process the Absentee if an Absentee ID is on the record and once to process the Substitute if a Substitute ID is on the record.
Miscellaneous 2: This field operates in the same fashion as Miscellaneous 1.
Generic Misc 1 & 2: Generic Miscellaneous fields 1 & 2 work in conjunction with STUPIM Absentee/Substitute Miscellaneous fields 03 through 10. Common codes are used to designate which STUPIM miscellaneous field should be validated against STUPBR Generic Miscellaneous fields. See the ST guide for more information.
Employee Selection Criteria
Employee Master Loc: This field is compared with the Employee Location on the HR Employee Master – not data from the imported record.
Abs Emp Type / Barg Unit: Data entered in these fields is compared with the Type/Location on the HR Employee Master – not data from the imported record.
Sub Emp Type / Barg Unit: Data entered in these fields is compared with the Type/Location on the HR Employee Master – not data from the imported record.
Adjust Operator: Used in conjunction with the Override/Adjust Hours field. If the amount in the Override/Adjust Hours field is greater than zero (0), SubTracker will perform the appropriate calculation based on the selected value in this drop-down.
For example: If the Adjust Hour Operator is + (plus), and Override/Adjust Hours is 1, then SubTracker will ADD 1 to the total hours on the ST Attendance Records (STUPAT) record for records matching this rule.
To remove a previously saved Operator value, use the <none> option to clear out the current selection.
Override/Adjust Hrs: Used in conjunction with the Adjust Hours Operator above.
If Override/Adjust Hours field has an amount larger than zero (0) and the Adjust Hours Operator field is empty, the Total Hours field on the ST Attendance Records (STUPAT) record will be set to the amount in the Override/Adjust Hours field.
Override Rate: Used if the rate for the hour is to be overridden on the Attendance Record.
Override Pay: Used if the total payment is to be overridden on the Attendance Record.