This page (revision-32) was last changed on 26-Nov-2021 10:22 by jescott

This page was created on 26-Nov-2021 10:22 by KateN

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
32 26-Nov-2021 10:22 8 KB jescott to previous
31 26-Nov-2021 10:22 8 KB JMyers to previous | to last
30 26-Nov-2021 10:22 9 KB JMyers to previous | to last
29 26-Nov-2021 10:22 14 KB JAiken to previous | to last
28 26-Nov-2021 10:22 14 KB JAiken to previous | to last
27 26-Nov-2021 10:22 14 KB JMyers to previous | to last
26 26-Nov-2021 10:22 14 KB JMyers to previous | to last
25 26-Nov-2021 10:22 14 KB JMyers to previous | to last
24 26-Nov-2021 10:22 14 KB JMyers to previous | to last
23 26-Nov-2021 10:22 14 KB JMyers to previous | to last TYPE_SEQUENCE ==> PREMIUM_TYPE_SEQUENCE
22 26-Nov-2021 10:22 14 KB JMyers to previous | to last
21 26-Nov-2021 10:22 13 KB JMyers to previous | to last

Page References

Incoming links Outgoing links
ISPM
ISPM

Version management

Difference between version and

At line 8 changed one line
;[Premium|PREMIUM_CODE]:Enter the name of the premium in this field. It is not necessary to build into the name any reference to the unit, it is acceptable (and recommended) to use the same premium codes across multiple units. In this way, a “night shift” premium is always the same code with different rates which are employed based on the union/unit of the employee. Premium_Code is a 16-character alphanumeric mandatory field which you will enter manually.
;[Premium|PREMIUM_CODE]:Enter the name of the premium in this field. It is not necessary to build into the name any reference to the unit, it is acceptable (and recommended) to use the same premium codes across multiple units. In this way, a “night shift” premium is always the same code with different rates which are employed based on the union/unit of the employee.
At line 10 changed one line
;[Unit|UNIT_CODE]:Each premium must be associated with a unit which may be identified in this field. Unit is a mandatory 16-character alphanumeric field which you must complete by selecting a value from the LOV. These values are maintained on the Define Entities ([IDUN]) form.
;[Unit|UNIT_CODE]:Each premium must be associated with a unit which may be identified in this field.
At line 12 changed one line
;[Entity|ENTITY_CODE]:Units are associated with an entity which is identified in this field. This value presented is for information use only and may not be updated by users. Entity is a 16-character alphanumeric information field that defaults from the unit code and may not be updated.
;[Entity|ENTITY_CODE]:Units are associated with an entity which is identified in this field. This value presented is for information use only and may not be updated by users.
At line 14 changed one line
;[Premium Type|PREMIUM_TYPE_CODE]:In this field, you may categorize the premium into one of the premium types created in the [ISPT] form. Premium_Type_Code is a 16-character alphanumeric mandatory field that may be either chosen from the LOV, or manually entered.
;[Premium Type|PREMIUM_TYPE_CODE]:In this field, you may categorize the premium into one of the premium types created in the [ISPT] form.
At line 16 changed 5 lines
;[Type Sequence|TYPE_SEQUENCE]:The sequence field is used by the [UTTG] process to determine an order of priority for premiums. Users may enter a sequence number to define the order of the premium. This sequence will override the sequential order defined before (pay line over assignment over position over job) and is only applicable to the Time Scheduling module.\\This feature works for all premiums of the same type.\\ \\ ''Example:\\Unit - Hourly has two premiums with the Premium Type of TIME; MINREST and TIMEOT\\
*''MINREST pays double-time and TIMEOT pay time-and-a-half.
*''MINREST is added to the Time Entries upon Clock OUT for the MIN HRS BTW SHFT Time Rule.
*''TIMEOT is added to the Time Entries and Pay Transactions during UTTG for the PREM TIME OF DAY Time Rule.
;:Previously this meant that the TIMEOT premium would override the MINREST premium as related to order of processing. By making the ‘Sequence’ of the TIMEOT premium ‘1’ and the ‘Sequence’ of the MINREST premium ‘2’, the MINREST premium will be applied instead of the TIMEOT premium if both are encountered by the UTTG process.''Type_Sequence is a 30-character numeric optional field that may be manually entered.
;[Type Sequence|TYPE_SEQUENCE]:The sequence field is used by the [UTTG] process to determine an order of priority for premiums. Users may enter a sequence number to define the order of the premium. This sequence will override the sequential order defined before (pay line over assignment over position over job) and is only applicable to the Time Scheduling module.\\This feature works for all premiums of the same type.\\ \\ Example:\\Unit - Hourly has two premiums with the Premium Type of TIME; MINREST and TIMEOT\\
*MINREST pays double-time and TIMEOT pay time-and-a-half.
*MINREST is added to the Time Entries upon Clock OUT for the MIN HRS BTW SHFT Time Rule.
*TIMEOT is added to the Time Entries and Pay Transactions during [UTTG] for the PREM TIME OF DAY Time Rule.
;:Previously this meant that the TIMEOT premium would override the MINREST premium as related to order of processing. By making the ‘Sequence’ of the TIMEOT premium ‘1’ and the ‘Sequence’ of the MINREST premium ‘2’, the MINREST premium will be applied instead of the TIMEOT premium if both are encountered by the [UTTG] process.
At line 22 changed one line
;[Description|DESCRIPTION]:This field holds a description of the premium code created. Description is an optional 50-character alphanumeric field that may be manually entered.
;[Description|DESCRIPTION]:This field holds a description of the premium code created.
At line 25 changed one line
;[Premium Rate|PREMIUM_RATE]:This is the rate that will be used when the Premium Calc rule includes “premium rate” in the formula. If the rule indicates premium rate (Prem Rt) then enter the rate as a percentage amount (0.50 for 50%) or a flat amount (100 for a fitness club premium). If the rule indicates a premium percentage (Prem Prc) then enter the percentage as a whole number (25 for 25%). Premium_Rate is a mandatory numeric field that may be entered by users.\\ \\Note that this rate is the default rate, but that it may be overridden, if necessary, for individual jobs, positions, assignments, or transactions (as long as the user has proper security clearance to do so).
;[Premium Rate|PREMIUM_RATE]:This is the rate that will be used when the Premium Calc rule includes “premium rate” in the formula. If the rule indicates premium rate (Prem Rt) then enter the rate as a percentage amount (0.50 for 50%) or a flat amount (100 for a fitness club premium). If the rule indicates a premium percentage (Prem Prc) then enter the percentage as a whole number (25 for 25%).
At line 27 changed one line
;[Rate Basis|RATE_BASIS]:This field defines the time period (hour, day, week, year) used with the premium rate value provided. Rate_Basis is a mandatory fixed lexicon ([X_RATE_BASIS]) that the user may use to look up the value.
;:%%information Note that this rate is the default rate, but that it may be overridden, if necessary, for individual jobs, positions, assignments, or transactions (as long as the user has proper security clearance to do so).%%
At line 29 added 2 lines
;[Rate Basis|RATE_BASIS]:This field defines the time period (hour, day, week, year) used with the premium rate value provided.
At line 52 changed one line
;[Premium Wage Source|PREMIUM_WAGE_SOURCE]:This field allows you to define the source of the premium, either from the pay line or from the highest scale/step rate on the position record. Premium_Wage_Source is an optional fixed lexicon ([X_PREMIUM_WAGE_SOURCE]) that you may use to look up the value.
;[Premium Wage Source|PREMIUM_WAGE_SOURCE]:This field allows you to define the source of the premium, either from the pay line or from the highest scale/step rate on the position record.
At line 54 changed one line
;[Frequency|FREQUENCY]:This field indicates how often, or for what types of pay, the transaction line will be created. [{$applicationname}] uses the term “frequency” to control the timing of payroll deductions, benefits, and earnings. Frequencies are defined during Payroll training and once created may be accessed by the LOV.\\ \\‘Frequency’ is only applicable to the “Prem per Period” and “UPTG Period Premium” calculation method. However, if either of those methods are used, frequency is REQUIRED.\\ \\Frequency is an optional, 16-character alphanumeric field that may be retrieved from the LOV.
;[Frequency|FREQUENCY]:This field indicates how often, or for what types of pay, the transaction line will be created. [{$applicationname}] uses the term “frequency” to control the timing of payroll deductions, benefits, and earnings. Frequencies are defined during Payroll training and once created may be accessed by the LOV.\\ \\‘Frequency’ is only applicable to the “Prem per Period” and “UPTG Period Premium” calculation method. However, if either of those methods are used, frequency is REQUIRED.
At line 72 changed one line
;:Replacement_Option is an optional toggle ([P2K_SA_PREMIUM_DETAILS]) that the user may set on or off.
;[Incl in Highest Rate of Day|HIGHEST_RATE_OF_PAY]:If the toggle is ON it provides the ability to apply the highest rate of pay received on that day worked including premiums. The highest rate on a day of course cannot be determined until all transactions for a pay are available and ‘official’. Because of this, the perfect place to ‘Rate’ [Pay Components|PAY COMPONENTS] with this option, is when the Pay hits the Pay Stage to be audited, so the [UPAUDT] function will be given the responsibility to apply the ‘Highest Rate of the Day’ feature.
At line 74 removed 2 lines
;[Incl in Highest Rate of Day|HIGHEST_RATE_OF_PAY]:If the toggle is ON it provides the ability to apply the highest rate of pay received on that day worked including premiums. The highest rate on a day of course cannot be determined until all transactions for a pay are available and ‘official’. Because of this, the perfect place to ‘Rate’ [Pay Components|PAY COMPONENTS] with this option, is when the Pay hits the Pay Stage to be audited, so the [UPAUDT] function will be given the responsibility to apply the ‘Highest Rate of the Day’ feature.\\Highest_Rate_Of_Pay is an optional toggle ([P2K_SA_PREMIUM_DETAILS]) that the user may set ON or OFF.
\\
At line 93 removed 2 lines
;:PPC_ID_DOLLARS is an optional, 4-character numeric code that may be entered by the user or retrieved from the LOV.
At line 98 changed one line
;[Pay Point Type|PAY_POINT_TYPE]:Choose the point in the payroll cycle when the premium should be processed. Pay Points allow you to control the flow and process steps of the payroll process, and you may in this way ensure that a premium is calculated at the correct point. Pay_Point_Type is an optional, fixed lexicon ([X_PAY_POINT_TYPE]) that may be retrieved from the LOV.
;[Pay Point Type|PAY_POINT_TYPE]:Choose the point in the payroll cycle when the premium should be processed. Pay Points allow you to control the flow and process steps of the payroll process, and you may in this way ensure that a premium is calculated at the correct point.
At line 100 changed one line
;[Pay Point Seq|PAY_POINT_SEQUENCE]: In this field, you may define the sequential order of each step taken within a pay point. Pay_Point_Sequence is an optional, 4-character alphanumeric field that may be manually entered.
;[Pay Point Seq|PAY_POINT_SEQUENCE]: In this field, you may define the sequential order of each step taken within a pay point.
This page (revision-32) was last changed on 26-Nov-2021 10:22 by jescottTop