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

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

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
59 26-Nov-2021 10:22 37 KB khiggs to previous
58 26-Nov-2021 10:22 37 KB kparrott to previous | to last
57 26-Nov-2021 10:22 37 KB rforbes to previous | to last
56 26-Nov-2021 10:22 60 KB rforbes to previous | to last
55 26-Nov-2021 10:22 60 KB rforbes to previous | to last
54 26-Nov-2021 10:22 60 KB jmyers to previous | to last
53 26-Nov-2021 10:22 60 KB jmyers to previous | to last
52 26-Nov-2021 10:22 60 KB jmyers to previous | to last
51 26-Nov-2021 10:22 65 KB jmyers to previous | to last
50 26-Nov-2021 10:22 67 KB jmyers to previous | to last
49 26-Nov-2021 10:22 67 KB jmyers to previous | to last
48 26-Nov-2021 10:22 64 KB jmyers to previous | to last
47 26-Nov-2021 10:22 64 KB jmyers to previous | to last
46 26-Nov-2021 10:22 64 KB jmyers to previous | to last
45 26-Nov-2021 10:22 64 KB jmyers to previous | to last
44 26-Nov-2021 10:22 63 KB jmyers to previous | to last
43 26-Nov-2021 10:22 67 KB jmyers to previous | to last
42 26-Nov-2021 10:22 67 KB jmyers to previous | to last
41 26-Nov-2021 10:22 67 KB jmyers to previous | to last

Page References

Incoming links Outgoing links
UPPHF
UPPHF

Version management

Difference between version and

At line 10 changed one line
The following value from X_INTERFACE_TYPE must be used for [IDIF] screen Interface Type field:32 – Pay History Interface
The following value from X_INTERFACE_TYPE must be used for [IDIF] screen Interface Type field:32 – Pay History Interface
At line 13 changed 3 lines
;01 – Pay Headers:Generate interface file with Pay Headers, Pay Amounts and employee basic information.\\This is used when Interface File requires Element amounts without detail information from Pay Lines, performance for this Interface level will be better than ‘02’ level.
;02 – Pay Headers + Pay Lines:Generate interface file with Pay Headers, Pay Lines, Pay Line Details, Pay Amounts and employee basic information.\\This is used when Interface File requires Amounts or Element amounts from Pay Lines level and information such as Cost Center, Work Order etc, performance for this Interface level will be slower than ‘01’ level.
;10 – Journal Entries:Generate interface file with Pay Headers, Journal Entries, Journal Details and employee basic information\\This is used when Interface File requires Journal Entries information, performance for this Interface level will be slower than ‘01’ level
;01 – Pay Headers:Generate interface file with Pay Headers, Pay Amounts and employee basic information.\\This is used when Interface File requires Element amounts without detail information from Pay Lines, performance for this Interface level will be better than ‘02’ level.
;02 – Pay Headers + Pay Lines:Generate interface file with Pay Headers, Pay Lines, Pay Line Details, Pay Amounts and employee basic information.\\This is used when Interface File requires Amounts or Element amounts from Pay Lines level and information such as Cost Center, Work Order etc, performance for this Interface level will be slower than ‘01’ level.
;10 – Journal Entries:Generate interface file with Pay Headers, Journal Entries, Journal Details and employee basic information\\This is used when Interface File requires Journal Entries information, performance for this Interface level will be slower than ‘01’ level
At line 18 changed one line
X_INF_VARIABLE_NAME contains a list of system defined variables that are eligible by Interface type. The following list describes each variable and the usage for Interface Type 32 – Pay History Interface.
X_INF_VARIABLE_NAME contains a list of system defined variables that are eligible by Interface type. The following list describes each variable and the usage for Interface Type 32 – Pay History Interface.
At line 32 changed one line
| 320011 | First Name (32) | From [P2K_HR_IDENTITIES], [first_name|FIRST_NAME]|
| 320011 | First Name | From [P2K_HR_IDENTITIES], [first_name|FIRST_NAME]|
At line 196 changed one line
Interface Type: - must be 32 – Pay History Interface
Interface Type: - must be 32 – Pay History Interface
At line 198 changed one line
Form Type: - please select ‘Not Specified’ from look up list, Form Type is not used for UPPHF
Form Type: - please select ‘Not Specified’ from look up list, Form Type is not used for UPPHF
At line 202 changed one line
Taxation Level: - please select ‘Not Specified’ from look up list, Taxation Level is not used for UPPHF
Taxation Level: - please select ‘Not Specified’ from look up list, Taxation Level is not used for UPPHF
At line 211 changed 3 lines
1 – 29 Header Records
30 – 69 Detail Records
70 – 99 Trailer Records or Update Records
1 – 29 Header Records
30 – 69 Detail Records
70 – 99 Trailer Records or Update Records
At line 220 changed 2 lines
Beginning Position - if File Format = ‘Fixed Format’, the user must specify the Beginning position
Ending Position - if File Format = ‘Fixed Format’, the user must specify the Ending position
Beginning Position - if File Format = ‘Fixed Format’, the user must specify the Beginning position
Ending Position - if File Format = ‘Fixed Format’, the user must specify the Ending position
At line 225 changed one line
Field Type - indicate the result of the Field Variable is a type of ‘Char’, ‘Number’ or ‘Date’
Field Type - indicate the result of the Field Variable is a type of ‘Char’, ‘Number’ or ‘Date’
At line 230 changed 2 lines
- use for Record # with Record Type = ‘Detail Record’ only
- for Record # with Record Type = ‘Detail Level 1’ to ‘Detail Level 5’, it uses the same Sort from Record Type = ‘Detail Record’ so that the Detail Level n records are followed after the ‘Detail Record’
- use for Record # with Record Type = ‘Detail Record’ only
- for Record # with Record Type = ‘Detail Level 1’ to ‘Detail Level 5’, it uses the same Sort from Record Type = ‘Detail Record’ so that the Detail Level n records are followed after the ‘Detail Record’
At line 233 changed 3 lines
- then for the Fld# entry that specify ‘Department’, enter sort sequence: 100
- for the Fld# that specify ‘Employee First Name’, enter sort sequence: 150
- for the Fld# that specify ‘Employee Last Name’, enter sort sequence: 200
- then for the Fld# entry that specify ‘Department’, enter sort sequence: 100
- for the Fld# that specify ‘Employee First Name’, enter sort sequence: 150
- for the Fld# that specify ‘Employee Last Name’, enter sort sequence: 200
At line 240 changed one line
- Sort Sequence is not supported if the IDIF format contains ‘Pay Header Begin’ or ‘Pay Header Summary’ because the Sorting of the Detail Record cannot carry it’s associated Header/Summary Record
- Sort Sequence is not supported if the IDIF format contains ‘Pay Header Begin’ or ‘Pay Header Summary’ because the Sorting of the Detail Record cannot carry it’s associated Header/Summary Record
At line 249 changed 3 lines
1 – 29 Header Records
30 – 69 Detail Records
70 – 99 Trailer Records
1 – 29 Header Records
30 – 69 Detail Records
70 – 99 Trailer Records
At line 254 changed 19 lines
00 – Not Specified - not applicable for this Interface type
01 – Header Record - generate Header records at begin of file
10 – Employer Header - not used for UPPHF
11 – Employer Summary - not used for UPPHF
12 – Employer Header 2 - not used for UPPHF
13 – Employer Summary 2 - not used for UPPHF
14 – Employee Header - not used for UPPHF
15 – Employee Summary - not used for UPPHF
16 – Pay Header Begin - generate records at beginning of each Pay Header
17 – Pay Header Summary - generate records at the end of each Pay Header
20 – Detail Record - generate Pay Header interface records
21 – Detail Level 1 - Detail Level 1 is used for Journal Entries
22 – Detail Level 2 - not used for UPPHF
23 – Detail Level 3 - not used for UPPHF
24 – Detail Level 4 - not used for UPPHF
25 – Detail Level 5 - not used for UPPHF
30 – Detail Summary - not used for UPPHF
80 – Total Record - not used for UPPHF
90 – Trailer Record - generate Trailer records at end of file
00 – Not Specified - not applicable for this Interface type
01 – Header Record - generate Header records at begin of file
10 – Employer Header - not used for UPPHF
11 – Employer Summary - not used for UPPHF
12 – Employer Header 2 - not used for UPPHF
13 – Employer Summary 2 - not used for UPPHF
14 – Employee Header - not used for UPPHF
15 – Employee Summary - not used for UPPHF
16 – Pay Header Begin - generate records at beginning of each Pay Header
17 – Pay Header Summary - generate records at the end of each Pay Header
20 – Detail Record - generate Pay Header interface records
21 – Detail Level 1 - Detail Level 1 is used for Journal Entries
22 – Detail Level 2 - not used for UPPHF
23 – Detail Level 3 - not used for UPPHF
24 – Detail Level 4 - not used for UPPHF
25 – Detail Level 5 - not used for UPPHF
30 – Detail Summary - not used for UPPHF
80 – Total Record - not used for UPPHF
90 – Trailer Record - generate Trailer records at end of file
At line 274 changed one line
91 – Qualify Record - should be used for Record Number 0
91 – Qualify Record - should be used for Record Number 0
At line 277 changed one line
92 – Update Record - should be defined at the end of the IDIF definition
92 – Update Record - should be defined at the end of the IDIF definition
At line 283 changed 7 lines
Constant Value - if Variable Name = ‘Constant Value’, this field specifies the Constant Value to be used
- if Variable Name = ‘User Calc’, this field specifies the User Calc Name
- if Variable Name = ‘UDF (xxx)’, this field specifies the User Defined Field Name
- if Variable Name = ‘Statistics Amt’, this field specifies the Statistics Code
- if Variable Name = ‘Element’, this field specifies the Element Code
- if Variable Name = ‘Total Value’, this field specifies the Rec# and Field # of the Detail Records to be totaled
e.g. Record # 50 Field 70 is to be totaled and Total option = ‘Calculate Total’, then the Trailer record can report the ‘Total Value’, Constant value should be 5070
Constant Value - if Variable Name = ‘Constant Value’, this field specifies the Constant Value to be used
- if Variable Name = ‘User Calc’, this field specifies the User Calc Name
- if Variable Name = ‘UDF (xxx)’, this field specifies the User Defined Field Name
- if Variable Name = ‘Statistics Amt’, this field specifies the Statistics Code
- if Variable Name = ‘Element’, this field specifies the Element Code
- if Variable Name = ‘Total Value’, this field specifies the Rec# and Field # of the Detail Records to be totaled
e.g. Record # 50 Field 70 is to be totaled and Total option = ‘Calculate Total’, then the Trailer record can report the ‘Total Value’, Constant value should be 5070
At line 291 changed one line
Print Zero Rule - applicable to Numeric field only, use for Record Type = ‘Detail Record’
Print Zero Rule - applicable to Numeric field only, use for Record Type = ‘Detail Record’
At line 293 changed one line
- e.g. if the field is from ‘Element Amount’ and the amount is zero, the user may not want to report this amount
- e.g. if the field is from ‘Element Amount’ and the amount is zero, the user may not want to report this amount
At line 295 changed one line
- if all numeric amounts are zero within one Record# and the Print Zero Rule are set to ‘Do not Print zeros’ for each field, then this entry will not be reported on interface file
- if all numeric amounts are zero within one Record# and the Print Zero Rule are set to ‘Do not Print zeros’ for each field, then this entry will not be reported on interface file
At line 297 changed 3 lines
00 – Not Specified
01 – Print Zero Amounts
02 – Don’t Print Zeros
00 – Not Specified
01 – Print Zero Amounts
02 – Don’t Print Zeros
At line 301 changed one line
XML Tag option - applicable to XML file, if Variable Name = ‘XML begin Tag’or ‘XML end Tag’, this field option indicates if the XML Tag should be written
XML Tag option - applicable to XML file, if Variable Name = ‘XML begin Tag’or ‘XML end Tag’, this field option indicates if the XML Tag should be written
At line 303 changed 3 lines
00 – Not Specified
01 – Optional, omit tag if null
02 – Mandatory, always write
00 – Not Specified
01 – Optional, omit tag if null
02 – Mandatory, always write
At line 307 changed one line
Accum Option - applicable to Numeric field only, use for Record Type = ‘Detail Record’
Accum Option - applicable to Numeric field only, use for Record Type = ‘Detail Record’
At line 309 changed 2 lines
- e.g. if the field is a ‘Pay Number’ or ‘Check Number’, then do not accumulate
- if field is ‘Element Value’ or ‘PC Amount’, then you may want to accumulate to avoid writing too much detail per element or per pay component
- e.g. if the field is a ‘Pay Number’ or ‘Check Number’, then do not accumulate
- if field is ‘Element Value’ or ‘PC Amount’, then you may want to accumulate to avoid writing too much detail per element or per pay component
At line 314 changed 2 lines
- e.g. if the field is a ‘FTE’ or ‘Rate of Pay’, then do not totaled
- if field is ‘Statistics Amount’ or ‘User Calc Amount’, then you may want to calculate the total for Trailer record
- e.g. if the field is a ‘FTE’ or ‘Rate of Pay’, then do not totaled
- if field is ‘Statistics Amount’ or ‘User Calc Amount’, then you may want to calculate the total for Trailer record
At line 317 changed 2 lines
00 – Not Specified
01 – Calculate Total
00 – Not Specified
01 – Calculate Total
At line 329 changed one line
- on IDIF Derivation expression, user may decode the Variable Name using the ~ character and return the word ‘BYPASS’ to bypass the Detail record entry that are with certain criteria
- on IDIF Derivation expression, user may decode the Variable Name using the ~ character and return the word ‘BYPASS’ to bypass the Detail record entry that are with certain criteria
At line 331 changed one line
- the ‘BYPASS’ criteria can be set up for Record Type = ‘Qualify record’, ‘Detail record’, and should not be used for Header and Trailer records
- the ‘BYPASS’ criteria can be set up for Record Type = ‘Qualify record’, ‘Detail record’, and should not be used for Header and Trailer records
At line 333 changed one line
- if the return value of any IDIF Record Number/Field Number = ‘BYPASS’, then this Detail record will be bypassed and will not be written to the Interface file
- if the return value of any IDIF Record Number/Field Number = ‘BYPASS’, then this Detail record will be bypassed and will not be written to the Interface file
At line 337 changed one line
- to include only Departments start with ‘P’ on interface file:
- to include only Departments start with ‘P’ on interface file:
At line 340 changed one line
- to include only Departments ends with ‘C’ on interface file:
- to include only Departments ends with ‘C’ on interface file:
At line 343 changed one line
- to bypass Cost Centers that has ‘????’ in second segments:
- to bypass Cost Centers that has ‘????’ in second segments:
At line 351 changed one line
- when UPPHF is run with Interface Level = ‘Pay Headers + Pay Lines’, user may want to BYPASS the current Pay Line and continue to process the next Pay Line
- when UPPHF is run with Interface Level = ‘Pay Headers + Pay Lines’, user may want to BYPASS the current Pay Line and continue to process the next Pay Line
At line 361 changed one line
- when Interface Level = ‘Pay Headers + Pay Lines’, user should use ‘BYPASS-1-PPL’ instead of just ‘BYPASS’ for clarification
- when Interface Level = ‘Pay Headers + Pay Lines’, user should use ‘BYPASS-1-PPL’ instead of just ‘BYPASS’ for clarification
At line 380 changed 4 lines
1) equals to ‘14-OCT-2008’, then return the value of ‘BYPASS’
2) equals to ‘16-OCT-2008’, then return the value of 'GOTO#60#1' - this will GOTO Rec# 60 Field # 1
3) equals to ‘22-OCT-2008’, then return the value of ‘BYPASS-1-PPL’
4) equals to ‘24-OCT-2008’, then return the value of ‘BYPASS-ALL-PPL’
1) equals to ‘14-OCT-2008’, then return the value of ‘BYPASS’
2) equals to ‘16-OCT-2008’, then return the value of 'GOTO#60#1' - this will GOTO Rec# 60 Field # 1
3) equals to ‘22-OCT-2008’, then return the value of ‘BYPASS-1-PPL’
4) equals to ‘24-OCT-2008’, then return the value of ‘BYPASS-ALL-PPL’
At line 404 changed one line
- if an Invalid GOTO is encountered in IDIF definition, the Trial mode parameter is set to ‘Y’ in order to prevent the Updating of the User Defined Fields from the Record Type ’92-Update Record’
- if an Invalid GOTO is encountered in IDIF definition, the Trial mode parameter is set to ‘Y’ in order to prevent the Updating of the User Defined Fields from the Record Type ’92-Update Record’
At line 414 changed one line
- e.g. UEEF IDIF Record# 30 Field # 45, decode Plan_Code, if it equals to ‘HL GROUP LIFE’, GOTO#35#10
- e.g. UEEF IDIF Record# 30 Field # 45, decode Plan_Code, if it equals to ‘HL GROUP LIFE’, GOTO#35#10
At line 433 changed one line
- if Pay Header Group User Defined Field (UDF) ‘PROJECT HOURS BY PERSON’ is ‘Y’, this means the employee is an ‘ADMIN’ employee, then if the Journal Entry is reporting for ‘Hours’, then use the Identities eid.id on the interface file field, otherwise, use the Unit dun.id on the field for all other situation
- if Pay Header Group User Defined Field (UDF) ‘PROJECT HOURS BY PERSON’ is ‘Y’, this means the employee is an ‘ADMIN’ employee, then if the Journal Entry is reporting for ‘Hours’, then use the Identities eid.id on the interface file field, otherwise, use the Unit dun.id on the field for all other situation
At line 435 changed one line
- from above IDIF set up, user should specify the Variable Name using ‘UDF (DGD)’ and enter the UDF name in Constant Value field, then the value of UDF will be returned and represented as ~ in the derivation expression
- from above IDIF set up, user should specify the Variable Name using ‘UDF (DGD)’ and enter the UDF name in Constant Value field, then the value of UDF will be returned and represented as ~ in the derivation expression
At line 442 changed one line
[320803] - Journal Type (DGA), 01 – Financial Journal, 02 – Statistical Journal
[320803] - Journal Type (DGA), 01 – Financial Journal, 02 – Statistical Journal
At line 449 changed one line
- if the value = ‘Y’, then
- if the value = ‘Y’, then
At line 451 changed one line
- if Journal Type = ‘02’ Statistical Journal, then
- if Journal Type = ‘02’ Statistical Journal, then
At line 461 changed one line
- if Pay Header Group User Defined Field (UDF) ‘PROJECT HOURS BY PERSON’ is ‘Y’, this means the employee is an ‘ADMIN’ employee, then use the Pay Period on the interface file field, otherwise use the GL Effective date on the interface file field
- if Pay Header Group User Defined Field (UDF) ‘PROJECT HOURS BY PERSON’ is ‘Y’, this means the employee is an ‘ADMIN’ employee, then use the Pay Period on the interface file field, otherwise use the GL Effective date on the interface file field
At line 463 changed one line
- from above IDIF set up, user should specify the Variable Name using ‘UDF (DGD)’ and enter the UDF name in Constant Value field, then the value of UDF will be returned and represented as ~ in the derivation expression
- from above IDIF set up, user should specify the Variable Name using ‘UDF (DGD)’ and enter the UDF name in Constant Value field, then the value of UDF will be returned and represented as ~ in the derivation expression
At line 475 changed one line
- if the value = ‘Y’, then
- if the value = ‘Y’, then
At line 478 changed one line
- return the value from [320756] GL Effective date with the date format of ‘DD/MM/YYYY’
- return the value from [320756] GL Effective date with the date format of ‘DD/MM/YYYY’
At line 482 changed one line
The user has ability to call some P2K internal functions in the derivation expression under the guidance of HL consultant. The following example is for UPPHF Payroll History Interface, and is used to demonstrate Derivation Expression only. In this example, the Element value of ‘HOURS COMP TIME’ will be returned for Variable Name ‘Pay Header pph_id’.
The user has ability to call some P2K internal functions in the derivation expression under the guidance of HL consultant. The following example is for UPPHF Payroll History Interface, and is used to demonstrate Derivation Expression only. In this example, the Element value of ‘HOURS COMP TIME’ will be returned for Variable Name ‘Pay Header pph_id’.
At line 490 changed one line
The above example can also be achieved by setting up Variable Name = ‘Element pph Value’ with the Element Code specified in the Constant Value field.
The above example can also be achieved by setting up Variable Name = ‘Element pph Value’ with the Element Code specified in the Constant Value field.
At line 503 changed 3 lines
#PPH_ID# - must be capital letters, this #PPH_ID# will be replaced by the current Pay Header’s pph.id
#EEM_ID# - must be capital letters, this #EEM_ID# will be replaced by the current Employment’s eem.id
#EID_ID# - must be capital letters, this #EID_ID# will be replaced by the current Identity’s eid.id
#PPH_ID# - must be capital letters, this #PPH_ID# will be replaced by the current Pay Header’s pph.id
#EEM_ID# - must be capital letters, this #EEM_ID# will be replaced by the current Employment’s eem.id
#EID_ID# - must be capital letters, this #EID_ID# will be replaced by the current Identity’s eid.id
At line 507 changed 2 lines
e.g.. the Element PC value of ‘HOURS O/T’ will be retrieved first and is represented as ~ in derivation expression
- the derivation expression will return the Element value of ‘HOURS COMP TIME’ for #PPH_ID# and add to value of ~
e.g.. the Element PC value of ‘HOURS O/T’ will be retrieved first and is represented as ~ in derivation expression
- the derivation expression will return the Element value of ‘HOURS COMP TIME’ for #PPH_ID# and add to value of ~
At line 515 changed 2 lines
Value of a PC in ‘HOURS O/T’ element * Benefit Element ‘HOURS COMP TIME’
Value of ‘HOURS O/T’ Element
Value of a PC in ‘HOURS O/T’ element * Benefit Element ‘HOURS COMP TIME’
Value of ‘HOURS O/T’ Element
At line 529 changed one line
!!IDIF – Call User Calc
!!IDIF – Call User Calc
At line 534 changed one line
- the user should set up Variable Name = ‘User Calc’, and specify the User Calc name in the Constant Value field
- the user should set up Variable Name = ‘User Calc’, and specify the User Calc name in the Constant Value field
At line 587 changed one line
!!IDIF – Update Record
!!IDIF – Update Record
At line 589 changed one line
!IDIF – Update Record Set Up
!IDIF – Update Record Set Up
At line 592 changed one line
- on IDIF screen, Record Type ’92-Update Record’ should be defined at the end of the IDIF definition
- on IDIF screen, Record Type ’92-Update Record’ should be defined at the end of the IDIF definition
At line 594 changed one line
- the Variable Name should contain the UDF (xxx) that is to be Updated or Inserted, e.g. ‘320629 – UDF (PRN) (32)’
- the Variable Name should contain the UDF (xxx) that is to be Updated or Inserted, e.g. ‘320629 – UDF (PRN) (32)’
At line 603 changed one line
- when UPPHF is run in non-Trial mode, Record Type ’92-Update Record’ will be processed at the appropriate levels to check if the UDF should be updated for the associated Data Base Tables
- when UPPHF is run in non-Trial mode, Record Type ’92-Update Record’ will be processed at the appropriate levels to check if the UDF should be updated for the associated Data Base Tables
At line 608 changed 5 lines
- Rec#500 Field#10 indicates to update ‘UDF (PRN)’, this will be processed at the end of each qualified Pay Run
- Rec#500 Field#20 indicates to update ‘UDF (PPH)’, this will be processed at the end of each qualified Pay Header
- Rec#500 Field#30 indicates to update ‘UDF (PPL)’, this will be processed at the end of each qualified Pay Line
- Rec#500 Field#40 indicates to update ‘UDF (EEM)’, this will be processed at the end of each qualified Pay Header
- Rec#500 Field#50 indicates to update ‘UDF (EASD)’, this will be processed at the end of each qualified Pay Line
- Rec#500 Field#10 indicates to update ‘UDF (PRN)’, this will be processed at the end of each qualified Pay Run
- Rec#500 Field#20 indicates to update ‘UDF (PPH)’, this will be processed at the end of each qualified Pay Header
- Rec#500 Field#30 indicates to update ‘UDF (PPL)’, this will be processed at the end of each qualified Pay Line
- Rec#500 Field#40 indicates to update ‘UDF (EEM)’, this will be processed at the end of each qualified Pay Header
- Rec#500 Field#50 indicates to update ‘UDF (EASD)’, this will be processed at the end of each qualified Pay Line
At line 614 changed one line
- if the UDF is for a Variable Name that can be varied at the Pay Line level, then the UDF will be updated at each Pay Line level, e.g. ‘UDF (DDD)’, each Pay Line may point to a different Department, therefore the UDF may be updated at the Pay Line level for that Department
- if the UDF is for a Variable Name that can be varied at the Pay Line level, then the UDF will be updated at each Pay Line level, e.g. ‘UDF (DDD)’, each Pay Line may point to a different Department, therefore the UDF may be updated at the Pay Line level for that Department
At line 619 changed 12 lines
320606 – UDF (EID) (32)
320607 – UDF (EEM) (32)
320608 – UDF (EPS) (32)
320610 – UDF (EASD) (32)
320621 – UDF (DED) (32)
320623 – UDF (DDD) (32)
320624 – UDF (DLN) (32)
320626 – UDF (DUD) (32)
320628 – UDF (DGD) (32)
320629 – UDF (PRN) (32)
320630 – UDF (PPH) (32)
320631 – UDF (PPL) (32)
320606 – UDF (EID) (32)
320607 – UDF (EEM) (32)
320608 – UDF (EPS) (32)
320610 – UDF (EASD) (32)
320621 – UDF (DED) (32)
320623 – UDF (DDD) (32)
320624 – UDF (DLN) (32)
320626 – UDF (DUD) (32)
320628 – UDF (DGD) (32)
320629 – UDF (PRN) (32)
320630 – UDF (PPH) (32)
320631 – UDF (PPL) (32)
At line 644 changed one line
A pay run's Pay Period End date or Pay Issue date must be on the day of or prior to the user specified ‘As of’ date.
A pay run's Pay Period End date or Pay Issue date must be on the day of or prior to the user specified ‘As of’ date.
At line 781 changed 2 lines
Entity: - mandatory, the user must enter one ‘Entity Code’ to be processed
Payroll: - mandatory, the user must enter one ‘Payroll Code’ to be processed
Entity: - mandatory, the user must enter one ‘Entity Code’ to be processed
Payroll: - mandatory, the user must enter one ‘Payroll Code’ to be processed
At line 784 changed 5 lines
Department: - optional, multiple ‘Department Code’ are allowed to be entered
Org Level Type: - optional, one or multiple ‘Org Level Type’ are allowed to be entered
- user may enter ‘Org Type 02’, ‘Org Type 03’ etc to process applicable level types or
user may enter ‘Org Type 02’ to process only this Level
Org Level: - optional, one or multiple ‘Org Level’ are allowed to be entered within the specified Org Level Types
Department: - optional, multiple ‘Department Code’ are allowed to be entered
Org Level Type: - optional, one or multiple ‘Org Level Type’ are allowed to be entered
- user may enter ‘Org Type 02’, ‘Org Type 03’ etc to process applicable level types or
user may enter ‘Org Type 02’ to process only this Level
Org Level: - optional, one or multiple ‘Org Level’ are allowed to be entered within the specified Org Level Types
At line 790 changed 5 lines
Authorization: - optional, one or multiple ‘Authorization area’ are allowed to be entered
- the authorization area is retrieved from Pay Header or Pay line’s assignment if authorization exists at assignment level, otherwise retrieve from position of the assignment if it exists, otherwise retrieve from department of the assignment
Unit: - optional, multiple ‘Unit Code’ are allowed to be entered
Group: - optional, multiple ‘Group Code’ are allowed to be entered
Cost Center: - optional, multiple ‘Cost Center Code’ are allowed to be entered
Authorization: - optional, one or multiple ‘Authorization area’ are allowed to be entered
- the authorization area is retrieved from Pay Header or Pay line’s assignment if authorization exists at assignment level, otherwise retrieve from position of the assignment if it exists, otherwise retrieve from department of the assignment
Unit: - optional, multiple ‘Unit Code’ are allowed to be entered
Group: - optional, multiple ‘Group Code’ are allowed to be entered
Cost Center: - optional, multiple ‘Cost Center Code’ are allowed to be entered
At line 797 changed one line
Person Code: - the user may enter list of ‘Person Code’
Person Code: - the user may enter list of ‘Person Code’
At line 804 changed one line
- if the From-To Pay Issue Dates are entered, each Pay Header’s Pay Issue Date must be within this date range in order to be processed
- if the From-To Pay Issue Dates are entered, each Pay Header’s Pay Issue Date must be within this date range in order to be processed
At line 806 changed one line
Interface Format Code - select Interface Format Code that is with Interface Type = ’32-Pay History Interface’
Interface Format Code - select Interface Format Code that is with Interface Type = ’32-Pay History Interface’
At line 810 changed 3 lines
01 – Pay Headers
02 – Pay Headers + Pay Lines
10 – Journal Entries
01 – Pay Headers
02 – Pay Headers + Pay Lines
10 – Journal Entries
At line 816 changed one line
- if the word ‘mex’ is specified in the file name, then it will be replaced with the current execution id of UPPHF run
- if the word ‘mex’ is specified in the file name, then it will be replaced with the current execution id of UPPHF run
At line 822 changed 6 lines
A – Append to File
W – Write to File
Exception Level - if Exception Level = ‘0’, only exception messages will be printed
- if Exception Level = ‘1’, one line will be printed per Pay Header with performance time
- if Exception Level = ‘2’, one line will be printed per Pay Header with performance time and one line per Detail Level 1 record
- if Exception Level = ‘8’ or ‘9’, full utility trace, available only if user selects by Person code, otherwise UPPHF will internally reset to Exception level ‘1’ due to volume of trace messages
A – Append to File
W – Write to File
Exception Level - if Exception Level = ‘0’, only exception messages will be printed
- if Exception Level = ‘1’, one line will be printed per Pay Header with performance time
- if Exception Level = ‘2’, one line will be printed per Pay Header with performance time and one line per Detail Level 1 record
- if Exception Level = ‘8’ or ‘9’, full utility trace, available only if user selects by Person code, otherwise UPPHF will internally reset to Exception level ‘1’ due to volume of trace messages
At line 830 changed 2 lines
- the value of ‘Y’ or ‘N’ is always returned in this parameter field
- to run in non-Trial mode (Update mode), the user should define IDIF Record Type ’92-Update Record’ to update UDFs
- the value of ‘Y’ or ‘N’ is always returned in this parameter field
- to run in non-Trial mode (Update mode), the user should define IDIF Record Type ’92-Update Record’ to update UDFs
This page (revision-59) was last changed on 26-Nov-2021 10:22 by khiggsTop