This is version 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 . It is not the current version, and thus it cannot be edited.

Back to current versionRestore this version

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.

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

• 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.

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).

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).

*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 page