An interface format similar to the example below is needed for the LPTS to load time sheets with Start and End times.
If the time code is not supplied, the DFLT TIME CODE from the time rule tab in IDWR is used.
The line 'PTSE.ACT_DIF_PRE_INSERT_CREATE_TS' will cause the LPTS to create a new time sheet if necessary. If this is missing the LPTS will not create new time sheets and if a matching time sheet cannot be found the record will be skipped.
Additionally clients can define overriding fields such as assignment, position, job or department. Another option available is to increase the end time with 15 minutes. This can be done by specifying PTSE.F_BANK_TIME in IDIF. If the value is '1', an additional 15 minutes will be added to the 'End_Time' on the line. If the value is '0', additional time will not be added.
| Rec # | Field # | Name | Beg Pos | End Pos | Field Type |
|---|---|---|---|---|---|
| 1 | 1 | PTSE.EAS_ID.EEM_ID.EID_ID.PERSON_CODE | -1 | -1 | CHAR |
| 1 | 2 | PTSE.EAS_ID.ASSIGNMENT_CODE | -1 | -1 | CHAR |
| 1 | 3 | PTSE.ENTRY_DATE | -1 | -1 | CHAR |
| 1 | 4 | PTSE.START_TIME | -1 | -1 | CHAR |
| 1 | 5 | PTSE.END_TIME | -1 | -1 | CHAR |
| 1 | 6 | PTSE.DTC_ID.TIME_CODE | -1 | -1 | CHAR |
| 1 | 7 | PTSE.DCC_ID.COST_CENTER_CODE | -1 | -1 | CHAR |
| 1 | 8 | PTSE.DDP_ID.DEPARTMENT_CODE | -1 | -1 | CHAR |
| 1 | 9 | PTSE.DJB_ID.JOB_CODE | -1 | -1 | CHAR |
| 1 | 10 | PTSE.ACT_DIF_PRE_INSERT_CREATE_TS | -1 | -1 | CHAR |
| 1 | 11 | PTSE.EAS_ID.EEM_ID.DEN_ID.ENTITY_CODE | -1 | -1 | CHAR |
| 1 | 12 | PTSE.TIME_SHEET_ENTRY_SOURCE | -1 | -1 | CHAR |
There is special logic within LPTS which sets the Job ID to the assignment's Job ID after it has set the assignment ID or entry date. Therefore, if the Job Code is being overridden in the file make sure the Job Code is placed in a higher Field # sequence than the Assignment Code and Entry Date so that the LPTS does not override the Job with the Assignment's Job.
