PYHR - EMPMSLRY

This code is used to configure the EMPMSTR screen to display the pay assignment based on the record type used in the common code. The pay assignment data is displayed on EMPMSTR2 for Classic IFAS and the "Primary" tab for BusinessPLUS 7i. You can set up this common code for each specific ledger - or - you can make the common code apply to all ledgers by using "@@" in the ledger field. If you have this common code set up for both a specific ledger and "@@," the specific ledger will take precedence. If a specific ledger is not found, the "@@" code will be used. If no code is found or if the code 1 value is not a valid RecType, the "PM" RecType will be used. The ledger for each hr_empmstr record is determined by the ledger associated with the Entity ID on the hr_entytble. Put the RecType of the assignment you want to pull from hr_emppay in Code 1.
Code Category: PYHR
Code Value: EMPMSLRY
Short Description: Any description.
Medium Description: Any description.
Long Description: Any description.
Associated Numeric Values
1-5: Reserved for future use.
Associated Codes
1: If no code is found or if the code 1 value is not a valid RecType, the "PM" RecType will be used. The ledger for each hr_empmstr record is determined by the ledger associated with the Entity ID on the hr_entytble. Put the RecType of the assignment you want to pull from hr_emppay in Code 1.
2-5: Reserved for future use.
Associated Descriptions
1-5: Enter any desired description.Common code PYHR/EMPMSLRY can be set to dictate the preference of pay assignment to display. Associated Codes 1 needs to contain the desired Record Type.
Below are the various combinations of common code, and record types and the expected results.
N0 PYHR/EMPMSLRY Common Code
Scenario 1

• 1 current dated PM record
• 1 current OR future dated non-PM record or NO other record

Results in the PM record type displaying in HREMEN, Primary tab
Scenario 2

• 1 current dated non-PM record
• 1 future dated PM record

Results in the PM record type displaying in HREMEN, Primary tab
Scenario 3

• 1 current OR future dated non-PM record
• NO PM current or future

Results in the non-PM record type displaying in HREMEN, Primary tab
Scenario 4

• No PM current or future
• 1 future dated A0 record
• 1 current dated non-PM record

Results in the non-PM record type displaying in HREMEN, Primary tab because it is the current/active pay assignment
PYHR/EMPMSLRY Common Code with A0 in Associated Codes 1
Scenario 1

• 1 current dated PM record
• 1 current dated A0 record

Results in the A0 record type displaying in HREMEN, Primary tab
Scenario 2

• 1 current dated A0 record
• NO PM record at all

Results in the A0 record type displaying in HREMEN, Primary tab
Scenario 3

• 1 future dated B0 record
• NO PM record at all

Results in the B0 record type displaying in HREMEN, Primary tab
Scenario 4

• 1 current dated B0 record
• 1 current dated PM record

Results in the B0 record type displaying in HREMEN, Primary tab – shouldn't the code grab the PM record instead?
Scenario 5

• 1 future dated A0 record
• 1 future dated PM record

Results in the PM record type displaying in HREMEN, Primary tab – shouldn't the code grab the A0 record instead?
Scenario 6

• 1 future dated B0 record
• 1 future dated PM record

Results in the PM record type displaying in HREMEN, Primary tab
Scenario 7

• 1 future dated B0 record
• 1 future dated A0 record

Results in the A0 record type displaying in HREMEN, Primary tab
PYHR/EMPMSLRY Common Code with an invalid Record Type in Associated Codes 1 – for instance, AO where the "O" is the letter "O" not the number "0"
Scenario 1

• 1 current dated PM record
• 1 current dated A0 record

Results in the PM record type displaying in HREMEN, Primary tab because the Associated Codes 1 value is an invalid record type.