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

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

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
8 26-Nov-2021 10:22 5 KB RForbes to previous
7 26-Nov-2021 10:22 5 KB RForbes to previous | to last
6 26-Nov-2021 10:22 5 KB JMyers to previous | to last
5 26-Nov-2021 10:22 5 KB JMyers to previous | to last
4 26-Nov-2021 10:22 5 KB JMyers to previous | to last
3 26-Nov-2021 10:22 4 KB JMyers to previous | to last
2 26-Nov-2021 10:22 4 KB JMyers to previous | to last
1 26-Nov-2021 10:22 4 KB JMyers to last

Page References

Incoming links Outgoing links
GROUP SOURCE
GROUP SOURCE

Version management

Difference between version and

At line 10 changed one line
Implementing this [Advanced Multiple Assignments] concept in [{$applicationname}] necessitated enhancing the method by which the proper ‘PC Rule’ record is located during Pay Line Generation. The PC Rule is needed for obtaining the correct Pay Component definition.\\ \\
Implementing this [Advanced Multiple Assignments] concept in [{$applicationname}] necessitated enhancing the method by which the proper PC Rule record is located during pay line generation. The PC Rule is needed for obtaining the correct pay component definition.\\ \\
At line 12 changed one line
In addition, the ‘Demographics’ used when determining if a new Pay Header should be created is determined by the new group source rule.
In addition, the demographics used when determining if a new pay header should be created is determined by the new group source rule.
At line 16 changed one line
In the Work Rule definition (IDWR), the new ‘Group Source’ rule has two distinct purposes.
In the Work Rule Definition ([IDWR]) screen, the new Group Source rule has two distinct purposes.
At line 18 changed one line
Firstly, it is used whenever a Pay Header is created, to determine the ‘Demographic’ information that will be stamped on the Pay Header. The Payroll, Unit, Group, Tax Jurisdictions (Home and Work), State/Province (Home and Work), and School District are determined by evaluating the ‘Group Source’ rule. These fields are also used to determine the appropriate payroll history records that will be updated with payroll totals information during the UPCLOZ process. The ‘To Date’ records viewable through the IPVT screen are the records that are used to create state and local W2s.
Firstly, it is used whenever a pay header is created, to determine the demographic information that will be stamped on the pay header. The payroll, unit, group, tax jurisdictions (home and work), state/province (home and work), and school district codes are determined by evaluating the Group Source rule. These fields are also used to determine the appropriate payroll history records that will be updated with payroll totals information during the [UPCLOZ] process. The To Date records viewable through the [IPVT] screen are the records that are used to create state and local W2s.
At line 20 changed one line
Secondly, the group source rule is also used during pay line generation, to obtain an Entity, Unit, and Group. These three values are then used to obtain the correct set of pay component rules from the PC Rule record (IPPC).
Secondly, the Group Source rule is also used during pay line generation, to obtain and entity, unit, and group. These three values are then used to obtain the correct set of pay component rules from the PC Rule record ([IPPC]).
At line 23 changed one line
There are 3 new group source rules.
If the work rule group source field is not populated by the client (i.e. it is Null), or the rule selected is ‘Not Specified’, then [{$applicationname}] will use the Match Assign/Posn rule when locating a PC Rule record. When locating a pay header, [{$applicationname}] will default to 'Prime Assignment'. These choices provide the same behavior as in previous versions.
At line 25 changed one line
If the work rule group source field is not populated by the client (i.e. it is NULL), or the rule selected is ‘Not Specified’, then P2K will use the rule ‘Match Assign/Posn’ when locating a ‘PC Rule’ record. When locating a Pay Header, P2K will default to ‘Prime Assignment. These choices provide the same behavior as in previous versions.
There are three new group source rules, and the following sections provide detailed specifications of the new rules.
At line 27 removed 2 lines
Please refer to sections 4 through 6 for detailed specifications of the new rules.
At line 30 changed one line
This method supports clients that need to bring time transactions in from the Time Entry module, in environments where the Job Code is frequently overridden, causing the unit and group codes (and by inference, the payroll code and tax jurisdictions) to change on a transaction by transaction basis.
This method supports clients that need to bring time transactions in from the Time Entry module in environments where the job code is frequently overridden, causing the unit and group codes (and by inference, the Payroll code and tax jurisdictions) to change on a transaction by transaction basis.
At line 32 changed one line
When creating pay headers and pay lines, the job code from the pay transaction is used to locate a matching assignment, and the group code from that assignment is then used in the header and pc rules logic. If a matching assignment is not found, then group code is instead taken from the first assignment where the unit code matches the unit code associated with the job code on the pay transaction.
When creating pay headers and pay lines, the job code from the pay transaction is used to locate a matching assignment, and the group code from that assignment is then used in the header and PC Rules logic. If a matching assignment is not found, then group code is instead taken from the first assignment where the Unit code matches the unit code associated with the job code on the pay transaction.
At line 37 changed one line
This rule is suitable for all existing clients that do not require the ‘Advanced Multiple Assignments’ functionality, and for all clients whose position or job changes at the pay transaction level are within a single unit and those who operate in a single state and tax jurisdiction.
This rule is suitable for all existing clients that do not require the [Advanced Multiple Assignments] functionality and for all clients whose position or job changes at the pay transaction level are within a single unit and those who operate in a single state and tax jurisdiction.
At line 41 changed one line
This method supports clients that need to bring time transactions in from the Time Entry module, in environments where the Position and Job Codes are frequently overridden, causing the unit and group codes (and by inference, the payroll code and tax jurisdictions) to change on a transaction by transaction basis.
This method supports clients that need to bring time transactions in from the Time Entry module, in environments where the position and job codes are frequently overridden, causing the unit and group codes (and by inference, the payroll code and tax jurisdictions) to change on a transaction by transaction basis.
This page (revision-8) was last changed on 26-Nov-2021 10:22 by RForbesTop