Integration Module XML File Processing

This section deals with the enhancements required to the Zavanti Integration Module (interface and server) in order to maintain and process the Timesheet XML document as described 2.2.2.  by taking the XML data and creating the Unposted Timesheet data within the Job Costing system.

1.     Validating the Timesheet XML Document details

The Timesheet XML document will be rejected from processing if:

•      Document invalid format

•      Invalid Company (COM_CODE), Job (JOB_CODE) , Sub Job (SUB_JOB_CODE) combination has been entered

•      Sub Job (SUB_JOB_CODE) is not blank, when Job Costing defaults ‘USE Sub Jobs’ is NOT enabled for selected company. SUB_JOB_CODE may be blank if this option is enabled

•      Period Number (PERIOD_NO) does not correspond to the Entry Date (ENTRY_DATE), or either field if blank

•      Invalid Engineer code (ENGINEER_CODE) is entered, for the selected Company, or Engineer code is blank

•      Invalid Cost Centre (CLASS_CODE) is entered, for the selected Company, or Cost Centre code is blank

•      Invalid Employee ID code (EMPLOYEE_ID) is entered, for the selected Company (may be left blank)

•      Invalid ‘START_TIME’ and ‘END_TIME’, or end time is less than start time. Start and end times may be blank.

•      Invalid Pay work id (PAY_WORK_ID) has bee entered for the selected company

•      Invalid Pay work id (PAY_RATE_ID) has bee entered for the selected company

•      Invalid Allowance id (ALLOWANCE_ID) has been entered for the selected company

2.     Creating the Unposted Timesheet data

Once all data from the XML document is validated, a new detail row is written to the Unposted Timesheet data table ‘GJC_TCTRANS’. This table described the mapping from the XML table field names to the column names on the database table.

Certain columns will require some additional checking and are not supplied from the XML table data.