261354
261354 - MW-7PBH7H II Interface Errors Tab
Copyright OBS Logistics © 2009
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
Functiona Overview
Client Requirement
As part of the EDI development we require in IILV an EDI interface error tab, which will allow users to query inbound and outbound flows
Added by SS 17.02.09: A bookings tab on the interface error form is required to allow users to readily identify failures as well as successful files for the transfer of Tesco information.
As part of the estimate can an additional tab be considered to take into account orders (this may be an option for Iggesund)
Solution
The Interface Errors (INT_ERR) form will be updated to include a new tab called ‘Tesco Bookings’ for inbound messages. There is already a tab present in this form called ‘Bookings’ but this will not be used to display successful/unsuccessful Tesco files as the tables related to this tab do not hold the correct level of information.
Therefore, a new table will be created to hold the corresponding inbound message data that will be displayed on the new ‘Tesco Bookings’ tab. The layout of data on this tab will be similar to the current ‘Bookings’ tab, but will display different fields. This will be detailed more in the Functional Specification. There will also be checks done on the inbound message files that will cause the file to fail if they are not met. E.g. specific fields must be populated, check if file already loaded etc. Again this will be detailed more in the Functional Specification.
Currently there is no tab in the INT_ERR form used to view outbound messages, so there will also be a new tab added to the INT_ERR form required to display details of outbound Tesco messages that are created on status updates and at the end of the day. This new tab will be called ‘Tesco Outbound Msgs’ and will require new tables to hold outbound message data.
Both new tabs will include a few search items that will make it easier for a user to search for specific files. E.g. Sched/Date Range, From Loc etc. Again these search items will be detailed more in the functional specification.
The request to include an additional tab for IIB orders (Iggesund) will not require a new tab. The current ‘Orders’ tab in the INT_ERR form will be used to display these orders. If IIB Inbound Orders are already accepted into MTS then the inbound orders will be input into tables INT_ORDER_HEADER and INT_ORDER_DETAIL, the same as all current inbound orders in other systems. To make these orders available for viewing in the ‘Orders’ tab we will need to set up a specific message type in INT_ORD_MSG_TYPE and a corresponding customer for those orders. This new message type and customer will then be available for selecting from the drop-down list in the ‘Orders’ tab. E.g. Msg Type of IGGESUND_ORDER and Customer IGGESUND if inbound orders for customer Iggesund is required.
Scope
These changes will be applied to system version 10.5 on IIBTST and once approved IIBPRD.
Set-Up
Pre-Requisites
‘260694 MW-7NVJ2A Tesco Booking Inbound Booking Msg’ and ‘261357 MW-7PBH9Q Tesco Outbound Booking Msg’ required for testing purposes
Data
The INT_ERR.fmx form will have 2 new tabs displayed on it called ‘PO Inbound’ and ‘PO Outbound’. These tabs will need setting up in table ADM_FORM_TAB, so that they are available for promoting in the Group Maintenance form
Functional Description
PO Inbound Tab Layout
The layout of the ‘PO Inbound’ tab will be as displayed below. The Inbound Purchase Order Header data will be displayed in the top section of the form along with any header validation errors, with the entire corresponding file Details displayed in the lower section. Note that the lower section has a horizontal scroll bar which can be scrolled across to view all details held in the PO Inbound file. The Special Instructions have their own field as this field can be up to 4000 characters in length so it appropriate to have the field displayed like this to accommodate the possibility of this field holding a lot of data. There is also a section to display validation error for file details.
The header details are displayed by descending created date. E.g. Most recent first. Files in a status of FAILED are displayed by default in this tab, unless the ‘Include Success’ box is checked.
PO Outbound Tab Layout
Below is how the ‘PO Outbound’ tab will look. As the outbound file holds a large amount of data, it isn’t possible to display all outbound file details neatly without having a very long scrollbar. Instead, the details held below are a snippet of the more important items held in the outbound file. E.g. Filename, PO Id, Trip Id, OMS Ref, External Ref. These items are displayed on the main ‘PO Outbound’ tab as they are the more distinguishable items in a file that can be queried using the ‘?...’ and ‘?’ buttons. The outbound file validation is displayed at the bottom
If a user wants to view the entire contents of the outbound file, this can be done using the ‘View’ button.
Clicking the ‘View’ button will display the following pop-up:
This form will display every single detail held in the outbound file. As you can see the layout is divided into different sections for each section displayed in the outbound file – the horizontal scrollbar is shown for those sections that hold a large amount of detail. The non-conformance section has a vertical bar to scroll down if there are more than 2 non-conformances.
The INT_ERR.fmx form will be coded to display Inbound and Outbound file details in the corresponding tabs.
IGGESUND Orders
On the basis that IGGESUND orders are already accepted into MTS, then the inbound details will be held in tables INT_ORDER_HEADER and INT_ORDER_DETAIL, the same as other inbound files. In order for these to be available in the ‘Orders’ tab of the INT_ERR screen, the ‘MSG Type’ drop down list will have to include the IGGESUND order type. This list is populated from table INT_ORD_MSG_TYPE, therefore this table will require updating.
This will now be available for selecting in the drop down list, as shown:
Triggers
4 new tables are required to hold the Purchase Order Inbound and Outbound details. Each table will require a trigger as below.
INT_PO_INBOUND_HEADER trigger to populate created_date and created_by when new records inserted:
References
Not Available
Document History
| Initial version | ||||
| Reviewed and Updated |
Authorised By
| Matt Crisford | Development Manager | |
| Suk Sandhu | TMSCC MTS Product Manager |
