[{TableOfContents }]

!!GROUP SOURCE

This document describes the functionality of the new ‘Group Source’ rule that has been added to the Work Rule (IDWR) in support of Personality’s ‘Advanced Multiple Assignments’ feature. 
 
The ‘Advanced Multiple Assignments’ feature is not used by clients who simply have employees working with multiple work assignments due to secondary or acting responsibilities, authorization requirements or similar. There is special group source rule logic associated with a null or Not Specified group source rule that ensures existing clients continue to function as previously indicated.  Refer to Work Rule Definition and  Prime Assignment for details of this default processing.
 
The ‘Advanced Multiple Assignments’ feature is only implemented in client environments where there are employees working in multiple assignments across multiple units and groups in different payrolls and tax jurisdictions. 
Implementing this ‘Advanced Multiple Assignments’ concept in P2K 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.

In addition,  the ‘Demographics’ used when determining if a new Pay Header should be created is determined by the new group source rule.

!!Work Rule Definition

In the Work Rule definition (IDWR), the new ‘Group Source’ rule has two distinct purposes. 
 
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.

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).

!!Group Source Rule Options
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 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. 

Please refer to sections 4 through 6 for detailed specifications of the new rules.

!!Job Only
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.

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.

!!Prime Assignment
This is the simplest method of group code derivation. It disregards any position or job code changes found in the pay transaction, and continues to use the group code associated with the employee’s prime assignment. 

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.

!!Matching Assignment / Position

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.

When creating pay headers and pay lines, the position and job code combination from the pay transaction is used to locate a matching assignment.  The pay details will be generated using the group code from this matching assignment.

If the transaction does not have a position code because the job code has been overridden, which causes the position code to be blanked out, then the unit associated with the job code on the transaction is used to locate the first assignment with the same unit, and the group code from the matching assignment will be used to generate pay details.

If a group code is not located at this point, then the group code from the prime assignment is used.