This page (revision-21) was last changed on 18-Aug-2023 12:06 by Kevin Higgs

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

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
21 18-Aug-2023 12:06 7 KB Kevin Higgs to previous

Page References

Incoming links Outgoing links
LMTD LOADING DATE EFFECTIVE SPLITS
LMTD LOADING DATE EFFECTIVE SPLITS

Version management

Difference between version and

At line 7 changed 4 lines
!Header Row
The first line of these interfaces will make the assumption that the file will contain a header row identifying the column names. As the position of the data in the file will be established in the IDIF interface, the header row will not be required. Establishing a header row in the interface will instruct the interface to skip the first row of data found on the file.
!Load Replacement Exceptions
!!Header Row
The first line of these interfaces will make the assumption that the file will contain a header row identifying the column names.
\\
\\
!Header Row Set Up
At line 14 added 3 lines
\\
!!Sample # 1
!Insert a change in position to the P2K_HR_ASSIGNMENT_DETAILS table with an effective date.
At line 18 added 17 lines
In this sample, the IEAS will be updated with a new position code as of a specific date. All the data being updated will be coming from the file. All position defaulting logic will be applied as part of this load (Updating the position code may impact the EASD.JOB_CODE, EASD.UNIT_CODE, EASD.WAGE_RATE, etc).
\\
!Sample #1 - File format
PERSON_CODE,ASSIGNMENT_CODE,EFFECTIVE,CHANGE_CODE,POSITION_ID\\
3001,00,02/22/2021,POSITION_CHANGE,10789\\
3002,00,02/22/2021,POSITION_CHANGE,10985\\
3400,00,02/22/2021,POSITION_CHANGE,11700\\
3904,00,02/22/2021,POSITION_CHANGE,10001\\
\\
!Sample #1 - IDIF Set Up
|0|1|HEADER RECORD*|-1|-1|Char|Header| | | | Must have Record Type of Header Record
|1|1|EASD.EAS_ID.EEM_ID.EID_ID.PERSON_CODE|-1|-1|Char| | Y| | | Person Code using in the IEID to identify the employee
|1|2|EASD.EAS_ID.ASSIGNMENT_CODE|-1|-1|Char| | Y | | | Assignment must match the code for the employee on IEAS
|1|3|EASD.EFFECTIVE|-1|-1|Char| | Y | |{{{TO_CHAR(TO_DATE(RTRIM((~)),
'MM/DD/YYYY'),'DD-Mon-YYYY')}}} | Formats date to match Personality standards. This deriviation is only required if the inbound date format does not match DD-MON-YYYY
|1|4|EASD.DCR_ID.CHANGE_CODE|-1|-1|Char| | | | | Optional Field - Change code as seen on IDCR
|1|5|EASD.DPS_ID|-1|-1|Char| | | | | Must be in the form of the ID of the P2K_CM_POSITIONS code (Positions may have more than 1 matching POSITION_CODE. So ID must be used).
At line 15 changed 3 lines
*If the inbound file does not contain a header row, this part of the set up is not required.
!!Insert a change in position to the P2K_HR_ASSIGNMENT_DETAILS table with an effective date.
\\
At line 19 changed one line
In this sample, the IEAS will be updated with a new position code as of a specific date.
!IDIF Set Up
||Rec\\ #||Field\\ #||Name||Beg\\ Pos|| End\\ Pos||Field\\ Type||Record\\ Type||Add to\\UK Set||Constant\\ Value||Derivation\\ Expression||Notes
|0|1|HEADER RECORD*|-1|-1|Char|Header| | | | Must have Record Type of Header Record
|1|1|EASD.EAS_ID.EEM_ID.EID_ID.PERSON_CODE|-1|-1|Char| | Y| | | Person Code using in the IEID to identify the employee
|1|2|EASD.EAS_ID.ASSIGNMENT_CODE|-1|-1|Char| | Y | | | Assignment must match the code for the employee on IEAS
|1|3|EASD.EFFECTIVE|-1|-1|Char| | Y | |{{{TO_CHAR(TO_DATE(RTRIM((~)),
'MM/DD/YYYY'),'DD-Mon-YYYY')}}} | Formats date to match Personality standards. This deriviation is only required if the inbound date format does not match DD-MON-YYYY
|1|4|EASD.DCR_ID.CHANGE_CODE|-1|-1|Char| | | | | Optional Field - Change code as seen on IDCR
|1|5|EASD.DPS_ID|-1|-1|Char| | | | | Must be in the form of the ID of the P2K_CM_POSITIONS code (Positions may have more than 1 matching POSITION_CODE. So ID must be used).
!!Insert a wage rate change to the P2K_HR_ASSIGNMENT_DETAILS table with an effective date.
In this sample, the IEAS will be updated with a new wage rate as of a specific date.
At line 22 changed one line
All position defaulting logic will be applied as part of this load (Updating the position code may impact the EASD.JOB_CODE, EASD.UNIT_CODE, EASD.WAGE_RATE, etc).
There will be no change made to any other field other than the CHANGE_CODE,EFFECTIVE and WAGE_RATE on P2K_HR_ASSIGNMENT_DETAILS.
At line 24 changed one line
!Load into P2K_HR_ASSIGNMENT_DETAILS
!IDIF Set Up
At line 66 added 4 lines
This page (revision-21) was last changed on 18-Aug-2023 12:06 by Kevin HiggsTop