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

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
6 26-Nov-2021 10:22 3 KB JMyers to previous
5 26-Nov-2021 10:22 3 KB JEscott to previous | to last
4 26-Nov-2021 10:22 3 KB JEscott to previous | to last
3 26-Nov-2021 10:22 3 KB RForbes to previous | to last
2 26-Nov-2021 10:22 3 KB JEscott to previous | to last
1 26-Nov-2021 10:22 3 KB JEscott to last

Page References

Incoming links Outgoing links
LMTD LOADING TRANSACTIONS TO IPTL
LMTD LOADING TRANSACTIONS TO IPTL

Version management

Difference between version and

At line 5 changed one line
|1| 2| PLPL.START_DATE| 12| 19| Char| |{{{TO_CHAR(TO_DATE(RTRIM(~),'MMDDYYYY'),'DD-Mon-YYYY')}}}|This will format the incoming date to the Personality standard.
|1| 2| PLPL.START_DATE| 12| 19| Char| |{{{TO_CHAR(TO_DATE(RTRIM(~),'MMDDYYYY'),'DD-Mon-YYYY')}}}|This will format the incoming date to the eP standard.
At line 12 changed one line
:PLPL.TIME_CODE))}}}|The value provided is the client's Labor Code. The system will first check if the Work In Process value is a 1 or 2, if it is then it will use OTR1 or OTR2 time code accordingly. If the WIP value is neither a 1 or 2, then the value provided will be translated to an Personality time code by comparing the provided value with the displayed value in the client's user defined PL_TIME_CD_KEYED lexicon. The file format is a fixed format.
:PLPL.TIME_CODE))}}}|The value provided is the client's Labor Code. The system will first check if the Work In Process value is a 1 or 2, if it is then it will use OTR1 or OTR2 time code accordingly. If the WIP value is neither a 1 or 2, then the value provided will be translated to an eP time code by comparing the provided value with the displayed value in the client's user defined PL_TIME_CD_KEYED lexicon. The file format is a fixed format.
At line 19 changed 2 lines
|1| 12| PLPL.DESTINATION_TYPE |-1| -1| Char |01| | Hard codes the Destination to be [IPTR]
|1| 13| PLPL.UPTL_STATUS| -1| -1| Char|00| |Hard codes the [UPTL] Status to be 'To Be Loaded'
|1| 12| PLPL.DESTINATION_TYPE |-1| -1| Char |01| | Hard codes the Destination to be IPTR
|1| 13| PLPL.UPTL_STATUS| -1| -1| Char|00| |Hard codes the UPTL Status to be 'To Be Loaded'
At line 22 changed one line
|1| 15| PLPL.BATCH_CODE| -1| -1| Char| RAIL| |This will hard code the Batch Code field in [IPTL] with RAIL.
|1| 15| PLPL.BATCH_CODE| -1| -1| Char| RAIL| |This will hard code the Batch Code field in IPTL with RAIL.
At line 32 changed one line
END}}}|This derivation is used to determine if the record qualifies for this type of load. It checks to see if the first 2 characters of the value in the time code field are VA, if they are then the record does not qualify and thus will be bypassed. This is used to Bypass vacation type components which will be loaded directly into [IAAL] via a different interface. The RECORD TYPE must be QUALIFY RECORD.
END}}}|This derivation is used to determine if the record qualifies for this type of load. It checks to see if the first 2 characters of the value in the time code field are VA, if they are then the record does not qualify and thus will be bypassed. This is used to Bypass vacation type components which will be loaded directly into IAAL via a different interface. The RECORD TYPE must be QUALIFY RECORD.
At line 35 removed 5 lines
----
![Notes|Edit:Internal.LMTD+LOADING+TRANSACTIONS+TO+IPTL]
[{InsertPage page='Internal.LMTD+LOADING+TRANSACTIONS+TO+IPTL' default='Click to create a new notes page'}]
This page (revision-6) was last changed on 26-Nov-2021 10:22 by JMyersTop