Below are sample interfaces that show how to insert effective date records on to date effective tables.
All samples show the required fields only to insert a new record. Additional fields to be updated may be added to these interfaces provided they are found on the subject table being updated.
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#
| 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 | off | Must have Record Type of Header Record |
Sample # 1#
Insert a change in position to the P2K_HR_ASSIGNMENT_DETAILS table with an effective date.#
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_ID3001,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). |
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). |
Sample #2#
Insert a wage rate change to the P2K_CM_POSITION_DETAILS table with an effective date.#
In this sample, the IDPS will be updated with a new wage rate, rate basis and a change reason as of a specific date.
In this sample, the inbound file will only contain the POSITION_CODE, WAGE_RATE and RATE_BASIS. All the other fields to be updated will come as constants in the interface.
Sample #2 - File format#
ABC01,53.10,07 ABC02,26.50,07 ABC03,35.67,07 MGRABC, 90000,01Sample #2 - 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). |
IEAS - EASD.EAS_ID.EEM_ID.EID_ID.PERSON_CODE, EASD.EAS_ID.ASSIGNMENT_CODE, EASD.EFFECTIVE IDPS - DPD.DPS_ID_CHILD_OF.POSITION_CODE DPD.DPS_ID_CHILD_OF.DEN_ID.ENTITY_CODE DPD.EFFECTIVE, IDJB - DJD.DJB_ID.JOB_CODE DJD.DJB_ID.DUN_ID.UNIT_CODE DJD.EFFECTIVE IDDP - IDUN - IDGR - IDWR -
- *If the inbound file does not contain a header row, this part of the set up is not required.
Notes #
Click to create a new notes pageScreen captures are meant to be indicative of the concept being presented and may not reflect the current screen design.
If you have any comments or questions please email the Wiki Editor
All content © High Line Corporation