This page (revision-79) was last changed on 20-Sep-2023 14:24 by Lilia Urtan

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
79 20-Sep-2023 14:24 81 KB Lilia Urtan to previous
78 05-May-2023 13:45 81 KB Lilia Urtan to previous | to last
77 21-Mar-2023 10:08 80 KB Kevin Higgs to previous | to last
76 26-Nov-2021 10:22 80 KB kparrott to previous | to last
75 26-Nov-2021 10:22 80 KB khiggs to previous | to last
74 26-Nov-2021 10:22 80 KB khiggs to previous | to last
73 26-Nov-2021 10:22 79 KB khiggs to previous | to last
72 26-Nov-2021 10:22 79 KB khiggs to previous | to last
71 26-Nov-2021 10:22 79 KB khiggs to previous | to last
70 26-Nov-2021 10:22 79 KB rmorrell to previous | to last
69 26-Nov-2021 10:22 79 KB rforbes to previous | to last
68 26-Nov-2021 10:22 78 KB jmyers to previous | to last
67 26-Nov-2021 10:22 78 KB jmyers to previous | to last
66 26-Nov-2021 10:22 78 KB jmyers to previous | to last
65 26-Nov-2021 10:22 78 KB jmyers to previous | to last
64 26-Nov-2021 10:22 78 KB jmyers to previous | to last
63 26-Nov-2021 10:22 78 KB jmyers to previous | to last
62 26-Nov-2021 10:22 78 KB jmyers to previous | to last
61 26-Nov-2021 10:22 79 KB jmyers to previous | to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 683 changed one line
!BYPASS capability
!BYPASS Capability
At line 712 added one line
At line 714 added 2 lines
** e.g. UEEF IDIF Record# 30 Field # 45, decode Plan_Code, if it equals to 'HL GROUP LIFE', GOTO#35#10
***this will skip the entire Record# 30 and carry on from Record# 35 Field#10 for the fixed file format
At line 714 changed 2 lines
- e.g. UEEF IDIF Record# 30 Field # 45, decode Plan_Code, if it equals to ‘HL GROUP LIFE’, GOTO#35#10
- this will skip the entire Record# 30 and carry on from Record# 35 Field#10 for the fixed file format
!Multiple Fields Processing
*On IDIF derivation expression, user can specify multiple variable names processing by indicating the lexicon value of the X_INF_VARIABLE_NAME inside the bracket [ ], e.g. [350001]
At line 720 added one line
- lexicon values available from IMLN for X_INF_VARIABLE_NAME are: 32nnnn, 35nnnn
At line 722 added one line
- this provides the full list of INF variables interchangeably for UPPHF, UEEF as long as the Database tables are being loaded according to the Interface Level parameter of the run
At line 724 added one line
- the following example is an excerpt from UPPHF and the same processing logic is applicable to UEEF
At line 727 added 54 lines
Example: Record # 50, Field # 20 Requirement for Employee Row id or Unit id:
- 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
- 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
- in derivation expression, enter:
decode(~,'Y',decode([320803],'02',[320009],[350400]),[350400])
where:
[320803] - Journal Type (DGA), 01 – Financial Journal, 02 – Statistical Journal
[320009] - Identity eid_id
[350400] - Unit dun_id (DUN)
- this derivation expression means:
- decode the value of ~ from UDF
- if the value = ‘Y’, then
- decode the value from [320803] Journal Type
- if Journal Type = ‘02’ Statistical Journal, then
- return [320009] Identify eid.id
- otherwise
- return [350400] Unit dun_id
- otherwise
- return [350400] Unit dun_id
Example: Record # 50, Field # 10 Requirement: Work Date or Pay Period
- 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
- 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
- in derivation expression, enter:
decode(~,'Y',[320102],to_char(to_date([320756]),'DD/MM/YYYY'))
where:
[320102] - Pay Period
[320756] - GL Eff Date (PJD)
- this derivation expression means:
- decode the value of ~ from UDF
- if the value = ‘Y’, then
- return the value from [320102] Pay Period
- otherwise
- return the value from [320756] GL Effective date with the date format of ‘DD/MM/YYYY’