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 1 changed 5 lines
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.
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. If the inbound file does not contain a header row, this part of the set up is not required.
Inserts a change in position to the P2K_HR_ASSIGNMENT_DETAILS table.
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. 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.
At line 7 changed 19 lines
!Load Away From Post Exceptions
||Rec\\#||Field\\#||Name||Beg\\Pos||End\\Pos||Field\\Type||Constant\\Value||Add to\\UK set||Derivation\\Expression||Notes
|0 |1| HEADER RECORD*| -1| -1| Char| | | Record Type must be Header Record
|1| 1 |TTX.EAS_ID.EEM_ID.EID_ID.PERSON_CODE| -1| -1| Char| | |
|1| 2| TTX.TIME_EXCEPTION_TYPE| -1| -1| Char| | |
|1| 3| TTX.START_DATE| -1| -1| Char| | {{{TO_CHAR(TO_DATE(RTRIM(~),
'MM/DD/YYYY'),'DDMon-YYYY')}}}|Formats date to match Personality standards
|1| 4| TTX.START_TIME| -1| -1| Char| | {{{concat(substr(~,1,2),substr(~,4,5))]}}}|The time in the file includes the :, the derivation is used to strip out the semi colon
|1| 5| TTX.END_TIME| -1| -1| Char| |{{{concat(substr(~,1,2),substr(~,4,5))}}}|The time in the file includes the :, the derivation is used to strip out the semi colon
|1| 6| TTX.DTC_ID.TIME_CODE| -1| -1| Char| |{{{ P2K_SMGLX('AESOP ABSENCE TRNSLT',UPPER(~))}}}|The derivation translates the value in the file to a time code using a user defined lexicon called AESOP ABSENCE
|1| 7| TTX.TSH_ID.EAS_ID.EEM_ID.TERMINATION_DATE| 0| 0| Char| ' '| |
|1| 8| TTX.EAS_ID.EEM_ID.TERMINATION_DATE| 0| 0| Char| ' '| |
|1 |9| TTX.TSH_ID.EAS_ID.EEM_ID.EID_ID.PERSON_CODE| 0| 0| Char| | {{{(:TTX.EAS_ID.EEM_ID.EID_ID.PERSON_CODE)}}}|This is required for [LMTD] to know which scheduled shift to update.
|1| 10 |TTX.TSH_ID.EAS_ID.PRIME_ASSIGNMENT| 0| 0 |Char| 1| | This is required for [LMTD] to know which scheduled shift to update
|1 |11| TTX.TSH_ID.SHIFT_DATE| 0| 0| Char| | {{{TO_CHAR(TO_DATE(RTRIM((:TTX.START_DATE)),
'MM/DD/YYYY'),'DDMon-YYYY')}}}|Formats date to match Personality standards
|1| 12| TTX.EAS_ID.PRIME_ASSIGNMENT |0| 0| Char| 1 | |Defaults to the prime assignment
|1| 13| TTX.ACT_DIF_POST_UPDATE_BUILD_SCHED| 0| 0| Char| | |Required so that the scheduled day is rebuilt.
|1|14| TTX.ACT_DIF_POST_INSERT_BUILD_SCHED| 0| 0| Char| | |Required so that the scheduled day is rebuilt.
!Load Replacement Exceptions
||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
At line 14 added 6 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.
In this sample, the IEAS will be updated with a new position code as of a specific date.
At line 28 changed 22 lines
!Load Replacement Exceptions
||Rec\\ #||Field\\ #||Name||Beg\\ Pos|| End\\ Pos||Field\\ Type||Constant\\ Value||Derivation\\ Expression||Notes
|0|1|HEADER RECORD*|-1|-1|Char| | | Must have Record Type of Header Record
|1|1|TTX.EAS_ID.EEM_ID.EID_ID.PERSON_CODE|-1|-1|Char| | |
|1| 2| TTX.EAS_ID.ASSIGNMENT_CODE| -1| -1| Char| | {{{P2K_SMGLX('AESOP PAY POSITION TRNSLT',
UPPER(~))}}}|The file includes a field which indicates which assignment to use, the derivation translates this using the specified user defined lexicon.
|1| 3| TTX.TSH_ID.EAS_ID.EEM_ID.EID_ID.PERSON_CODE**| -1| -1| Char| | |The file includes the person code of the employee who is away from post, so the LMTD will use this to locate which scheduled shift to update.
|1 |4| TTX.F_OVERRIDE_ASSIGNMENT| -1| -1| Char| | |The file included an overridden assignment code which is to be ignored. Since the file is character delimited, a foreign field was used to map its position within the file.
|1| 5| TTX.TIME_EXCEPTION_TYPE| -1| -1 |Char| | |
|1| 6| TTX.START_DATE |-1| -1| Char| |{{{TO_CHAR(TO_DATE(RTRIM(~),MM/DD/YYYY'),
'DDMon-YYYY')}}}|Formats date to match Personality standards
|1 |7 |TTX.START_TIME |-1| -1 |Char| | {{{concat(substr(~,1,2),substr(~,4,5))}}}|The time in the file includes the :, the derivation is used to strip out the semi colon
|1| 8| TTX.END_TIME| -1| -1| Char| |{{{ concat(substr(~,1,2),substr(~,4,5))}}}|The time in the file includes the :, the derivation is used to strip out the semi colon
|1 |9| TTX.DTC_ID.TIME_CODE| -1| -1 |Char| |{{{P2K_SMGLX('AESOP PAY TIMECODE TRNSLT',
UPPER(~))}}}|
|1| 10| TTX.TSH_ID.EAS_ID.EEM_ID.TERMINATION_DATE |0 |0| Char| ' '| |
|1| 11| TTX.EAS_ID.EEM_ID.TERMINATION_DATE| 0| 0| Char| ' '| |
|1 |12| TTX.TSH_ID.SHIFT_DATE| 0| 0| Char| |{{{TO_CHAR(TO_DATE(RTRIM((:TTX.START_DATE)),
'MM/DD/YYYY'),'DDMon-YYYY')}}}|Required to help the [LMTD] locate the correct scheduled shift to update. The derivation uses the TTX.START_DATE original value and formats it to match Personality standards.
|1| 13| TTX.TSH_ID.EAS_ID.PRIME_ASSIGNMENT***| 0| 0| Char| 1| | Used to help locate the correct scheduled shift to update.
|1| 14| TTX.ACT_DIF_POST_UPDATE_BUILD_SCHED| 0| 0| Char| | | Required so that the scheduled day is rebuilt.
|1| 15 |TTX.ACT_DIF_POST_INSERT_BUILD_SCHED| 0 |0 |Char| | | Required so that the scheduled day is rebuilt.
\\
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).
At line 51 changed 3 lines
;:*Record 0, Field 1 must have a Record Type of Header Record
;:**Record 1, Field 3 must have the Add to UK Set toggled ON
;:***Record 1, Field 12 must have the Add to UK Set toggled ON
!Load into P2K_HR_ASSIGNMENT_DETAILS
||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).
At line 34 added one line
;:*If the inbound file does not contain a header row, this part of the set up is not required.
This page (revision-21) was last changed on 18-Aug-2023 12:06 by Kevin HiggsTop