261848
261848 - PA-7N6HVR/ Inbound Interface Errors CSV
Copyright OBS Logistics © 2010
The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied
FUNCTIONAL OVERVIEW
Client Requirement
A new report needs to be created from the Interface errors screen capable of showing inbound transmissions with details of failures in each case with a .csv export capability.. In the first instance this is linked to the EFX interface where Trip details are sent from MTS to EFX, and a confirmation Reference is received back into MTS. This will develop in the future to additional transmissions for EFX from MTS Inbound only RIO as requested by OBS
Solution
The source table for EFX inbound information is INT_EFX_TRIP_INBOUND
Two new procedures will be written in the DP_CSV package. One procedure will select the relevant information for the csv extract and the second will write the information to the CSV file. The extract process will be launched from the exports screen by selecting EFX Inbound Errors.
The CSV file will detail the trip information and the cause of the failure, specifically the following information
- INT_RECORD_ID
- LOAD_REF
- EFX_REF
- ACCEPTING_DEPOT
- RECORD_STATUS
- VALIDATION_ERROR
- CREATED_DATE
This will not be created as an Oracle report, only as a CSV export.
The export will list all failures regardless of time period, so records will always appear on the export until they have been successfully processed. There will be no parameters associated with this export. A record will be added to the REP_REPORT table to allow the extract to be launched.
In addition to creating the CSV extract, a new tab will be added to the INTERFACE ERRORS screen which will display inbound EFX errors. The screen will follow the same format as the existing DSG Trip Details TAB which will display the EFX outbound errors and be renamed accordingly.
The tab will display the information available in the INT_EFX_TRIP_INBOUND table which is listed below:
- INT_RECORD_ID
- MSG_TYPE
- LOAD_REF
- EFX_REF
- ACCEPTING_DEPOT
- RECORD_STATUS
- VALIDATION_ERROR ( This will be displayed at the bottom of the screen)
- CREATED_DATE
The value of the new SYSTEM PARAMETER ‘EFX_INCLUDED’ will be used to determine if this TAB is visible to the user. If the parameter is set to N, the new tab will be hidden when the INTERFACE ERRORS screen is opened.
Scope
This change will be applied to system version 10.5.0 on CONTST and once approved CONPRD.
Data
The new extract will be added to the REP_REPORT table to allow the extract to be run from the REPORTS screen. The selection criteria will call the new procedure added to the CSV package for EFX inbound information. CSV.EFX_INBOUND_ERRORS.
No records are required to be added to REP_REPORT_PARAM, as the extract will be run without any parameters settings.
A record will be added to the table ADM_FORM_TAB. This record will ensure that the tab is only visible in the INT ERRORS screen when it has been promoted using the ACCESS CONTROL screen.
FUNCTIONAL DESCRIPTION
A new extract will be available to run from the reports screen. The extract called EFX Inbound Errors will report all FAILURES from EFX. The extract will be created in CSV format in the relevant CSV folder.
The extract will display the following header and data
Header
- Record Status FAILURE
Detail
- INT_RECORD_ID
- LOAD_REF
- EFX_REF
- MSG_TYPE
- ACCEPTING_DEPOT
- VALIDATION_ERROR
- CREATED_DATE
Accepting depot information received from EFX will be decoded to represent and MTS depot, where applicable. If we are unable to decode the accepting depot we will report the efx code plus the text ‘NON-MTS’.
In addition to the new extract a new tab will be added to the INTERFACE ERRORS screen. The tab will report on the information in the INBOUND table from EFX and will include the current functionality on the existing TABS within the screen.
The screen above will also include the field MESSAGE TYPE, before the load Ref. EFX Ref field will be shortened to accommodate the MESSAGE_TYPE field.
REFERENCES
| EST-261848 PA-7N6HVR Inbound Interface Errors CSV |
DOCUMENT HISTORY
| Initial version | ||||
| Reviewed and Issued |
AUTHORISED BY
| Matt Crisford | Development Manager | |
| Peter Greer | TMSCC MTS Product Manager |
