This is a basic layout of what may be used to load into IPSN.
| Record # | Field # | Name | Beg Pos | End Pos |
|---|---|---|---|---|
| 1 | 1 | PSL.EAS_ID.ASSIGNMENT_CODE | -1 | -1 |
| 1 | 2 | PSL.EAS_ID.EEM_ID.EID_ID.PERSON_CODE | -1 | -1 |
| 1 | 3 | PSL.EEM_ID.EID_ID.PERSON_CODE | -1 | -1 |
| 1 | 4 | PSL.PFQ_ID.FREQUENCY_CODE | -1 | -1 |
| 1 | 5 | PSL.PPC_ID.PC_CODE | -1 | -1 |
| 1 | 6 | PSL.TIME_ENTERED | -1 | -1 |
| 1 | 7 | PSL.START_DATE | -1 | -1 |
| 1 | 8 | PSL.END_DATE | -1 | -1 |
| 1 | 9 | PSL.TIME_BASIS | -1 | -1 |
| 1 | 10 | PSL.SUNDRY_LINE_TYPE | -1 | -1 |
| 1 | 11 | PSLD.PPC_ID.PC_CODE | -1 | -1 |
| 1 | 12 | PSLD.AMOUNT | -1 | -1 |
| 1 | 13 | PSLD.AMOUNT_OVERRIDE | -1 | -1 |
| 1 | 14 | PSLD.DESCRIPTION | -1 | -1 |
| 1 | 15 | PSLD.PC_DETAIL_TYPE | -1 | -1 |
| 1 | 16 | PSLD.PC_ACTION | -1 | -1 |
Any time loading into a table that has EAS_ID as a column the interface format should also be defined with fields that include EAS.EEM_ID and EAS.ASSIGNMENT_CODE so that the LTMD can focus to the correct record in the database. In the above example, we are providing PSL.EAS_ID.ASSIGNMENT_CODE, PSL.EAS_ID.EEM_ID.EID_ID.PERSON_CODE, PSL.EEM_ID.EID_ID.PERSON_CODE. The reason for this is so that the LMTD can focus to the correct EAS_ID in the sundry table based on the EAS_EEM_ID and EAS_ASSIGNMENT_CODE.
