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 added 7 lines
!!!LMTD LOADING DATE EFFECTIVE SPLITS
\\
The LMTD process can be used to insert date effective records onto date sensitive child tables.\\
\\
An IDIF interface will need to be established. The interface must use the [Interface type|INTERFACE_TYPE] of 'EFFECTIVE SPLIT'. If the interface uses any other type the values will not load correctly.\\
\\
At line 10 added one line
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.\\
At line 4 changed one line
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.
!!DISABLE TRIGGERS
If doing a __mass upload__ of data to a table containing workflow triggers, it is highly recommended to disable those triggers prior to performing the load. \\
At line 15 added 3 lines
1) Prior to load - __ALTER TRIGGER P2K_XXXX_BIUD DISABLE;__\\
2) Complete the load\\
3) After the load - __ALTER TRIGGER P2K_XXXX_BIUD ENABLE;__\\
At line 10 removed one line
\\
At line 17 changed one line
\\
At line 32 added one line
\\
At line 40 added 2 lines
\\
||Rec\\ #||Field\\ #||Name||Beg\\ Pos|| End\\ Pos||Field\\ Type||Record\\ Type||Add to\\UK Set||Constant\\ Value||Derivation\\ Expression||Notes
At line 35 removed one line
At line 37 removed one line
At line 47 changed one line
\\
At line 49 changed 2 lines
!!Insert a wage rate change to the P2K_CM_POSITION_DETAILS table with an effective date.
!Insert a wage rate change to the P2K_CM_POSITION_DETAILS table with an effective date.
\\
At line 65 added 2 lines
The inbound file will only contain the [position code|IDPS], wage rate and a [rate basis|X_RATE_BASIS]. All the other fields to be updated will come as constants in the interface.
The rate basis will need to be translated to match the values found on the [X_RATE_BASIS] lexicon on [IMLN].
At line 54 changed 2 lines
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.
;:Note the the start and end position in the IDIF are set to 0 where columns are not found on the file.
\\
At line 57 changed 5 lines
ABC01,53.10,07
ABC02,26.50,07
ABC03,35.67,07
MGRABC, 90000,01
ABC01,53.10,HR\\
ABC02,26.50,HR\\
ABC03,35.67,HR\\
MGRABC,90000,YR
\\
At line 65 changed 6 lines
|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).
|1|1|DPD.DPS_ID_CHILD_OF.POSITION_CODE|-1|-1|Char| | Y| | | Position code as seen on IDPS
|1|2|DPD.WAGE_RATE|-1|-1|Char| | | | | Wage Rate to be updated
|1|3|DPD.RATE_BASIS|-1|-1|Char| | | |DECODE(~,'HR','07','01') | Changes the value in the file into the saved value of the lexicon HR = 07, YR = 01
|1|4|DPD.DCR_ID.CHANGE_CODE|0|0|Char| | | COLA INCREASE | | Optional Field - Change code as seen on IDCR
|1|5|DPD.EFFECTIVE|0|0|Char| | Y | 01-MAR-2021 | | Must be in the form DD-MON-YYYY
|1|6|DPD.DPS_ID_CHILD_OF.DEN_ID.ENTITY_CODE|0|0|Char| | Y |ABC123| | Entity Code as seen on IDEN
At line 72 removed 17 lines
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 -
At line 88 added 21 lines
!!Minimum set up requirements for effective date split screens
\\
The following chart shows the minimum set up required in an IDIF record to insert a new date effective record.\\
Once the fields found in the "Required" column have been defined, any value found in on the "Subject Table" can be updated. Please use the [Maintain Column Details|IMCD] form in the application for a listing of columns available to update based on you subject table.\\
\\
;:NOTE: this process will allow the update of [User Defined Columns|USER DEFINED COLUMN|USER DEFINED COLUMN (UDC)], but will not be able to update [User Defined Fields|USER DEFINED FIELD].
\\
\\
||Subject Table||Alias||Sample Screen||Required**||
|P2K_HR_ASSIGNMENT_DETAILS|EASD|IEAS|EASD.EAS_ID.EEM_ID.EID_ID.PERSON_CODE,\\EASD.EAS_ID.ASSIGNMENT_CODE,\\EASD.EFFECTIVE
|P2K_HR_PERSONALS|EPS|IEPI|EPS.EID_ID.PERSON_CODE,\\EPS.EFFECTIVE
|P2K_CM_POSITION_DETAILS|DPD|IDPS|DPD.DPS_ID_CHILD_OF.POSITION_CODE,\\DPD.DPS_ID_CHILD_OF.DEN_ID.ENTITY_CODE,\\DPD.EFFECTIVE
|P2K_CM_JOB_DETAILS|DJD|IDJB|DJD.DJB_ID.JOB_CODE,\\DJD.DJB_ID.DUN_ID.UNIT_CODE,\\DJD.DJB_ID.DUN_ID.DEN_ID.ENTITY_CODE,\\DJD.EFFECTIVE|
|P2K_CM_DEPARTMENT_DETAILS|DPD|IDDP|DDD.DDP_ID.DEPARTMENT_CODE,\\DDD.DDP_ID.DEN_ID_LEGAL.DEN_ID.ENTITY_CODE,\\DDD.EFFECTIVE
|P2K_CM_UNIT_DETAILS|DUD|IDUN|DUD.DUN_ID.UNIT_CODE,\\DUD.DUN_ID.DEN_ID.ENTITY_CODE,\\DUD.EFFECTIVE
|P2K_CM_GROUP_DETAILS|DGD|IDGR|DGD.DGR_ID.GROUP_CODE,\\DGD.DGR_ID.DUN_ID.UNIT_CODE,\\DGD.EFFECTIVE
|P2K_CM_WORK_RULES|DRWD|IDWR|DWRD.DWR_ID.WORK_RULE_CODE,\\DWRD.DWR_ID.DEN_ID.ENTITY_CODE,\\DWRD.EFFECTIVE
|P2K_SA_SALARY_RANGE_DETAILS|SSRD|ISSR|SSRD.SSR_ID.RANGE_CODE,\\SSRD.SSR_ID.DEN_ID.ENTITY_CODE,\\SSRD.EFFECTIVE
|P2K_SA_WAGE_STEP_DETAILS|SWSD|ISWS|SWSD.SWSS_ID.SWS_ID.SCALE_CODE,\\SWSD.SWSS_ID.SWS_ID.DUN_ID.UNIT_CODE,\\SWSD.SWSS_ID.SWS_ID.DUN_ID.DEN_ID.ENTITY_CODE,\\SWSD.SWSS_ID.STEP_CODE,\\SWSD.SWSS_ID.STEP_SEQUENCE,\\SWSD.EFFECTIVE
;:**The ADD TO UK SET toggle must be enabled for all of these fields. This toggle must be disabled for any other field added to the interface not listed in the chart.
This page (revision-21) was last changed on 18-Aug-2023 12:06 by Kevin HiggsTop