270880
DHL MTS
Purchase Order Version Ctrl
FUNCTIONAL SPECIFICATION - 10.5
13/11/2009 - 1.0
Reference: FS 270880 MW-7X2DUS
Client Requirement
Within the purchase order screen for Tesco - we need to apply a version control to show updates and status changes - since the po is really a SKU level, we need to group these together.
We are currently using the file reference as the version number - NYK max out at 9999 - we are currently in the 7000. When a po is sent to Tesco there needs to be a uniformed version number across all sku's - this also needs to take into consideration if 1 sku is not actioned, this must also be updated. This also needs to continue when the order is on a trip - maybe using trip status action.
Solution
It is important to clarify that currently in MTS there is an ‘inbound’ version number which is added to the SCH_PURCHASE_ORDER record on receipt of a new inbound PO EDI file and updated on receipt of an existing PO file by way of update. This new version number is specifically related to the outbound PO file and is independent not connected to the inbound version number in any way.
The new ‘outbound’ version number is intended to indicate the latest outbound file version that has been sent for a particular Purchase Order. The file naming and sequence of the outbound PO file will remain unchanged.
A new field will be added to the table SCH_PURCHASE_ORDER. This field will store the new ‘outbound’ version number. The new ‘outbound’ version number will provision for at least 4 digits ‘9999’
When an action is performed on a particular Purchase Order AND only when an outbound message is triggered, the ‘outbound’ version number for that PO will be incremented by 1. A check will then be made on the PO Number and all other SCH_PURCHASE_ORDER records that belong to that same PO Number will also be updated to the same version number
The version number will be incremented for all PO’s for that specific PO Number whenever an event occurs that triggers an outbound PO EDI message. A change will be required to INT_XML to update the version numbers when required.
A new field will be added to the outbound XML file which will contain the PO version number. This will require an update to the XSD which forms the formal format and content of the XML PO Outbound file. This new format will need to be co-ordinated with ESI and require corresponding mapping changes.
This new version number will be displayed on the Purchase Order screen (PURCH_ORD) for reference. Suggestion would be on the ‘Edit Purchase Order’ sub-screen as viewed from the main Purchase Order Screen when double clicking a Purchase Order or clicking the ‘Edit’ button.
NB: Additional 0.75 days added to Implementation time required due to new requirement of setting existing PO’s version numbers as per Mark Wilson’s Email:
We do not want the option to amend this version ourselves, all current orders when we implement this will need to have a version number against this new format, so yes when a new provisional order comes in, it is to be default to 1, so when this is sent for the first time then it would be version 2 being sent.
Due to a issue with Tesco, they have been taking in version 2 for all our orders from the start, so if we set as a one off when we go live that all po's that are not Provisional have a version of 2 then when we send the next message they go out as version 3, this would be an natural increment to the latest version of 2 that is against all orders.
Scope
This change will be applied to system version 10.5
Set-up
Pre-requisites
Menu-Structure
Data
Functional Description
A new field will be added to the table SCH_PURCHASE_ORDER. This field will be used to store the outbound version number against each PO.
PO_OUTBOUND_VERSION number(5);
Certain actions against a PO will trigger an XML message to be sent. When one of these actions takes place the PO Number version will be incremented by 1 for the particular PO being actioned.
A check will then take place to find all other PO’s that contain the PO Number being actioned. The Po version number of these PO’s will then be updated to match. This will keep the version number of PO’s in line.
The actions that will increment the version number are
Status change to PO
When the trip moves to Accepted status.
When the POC is set for an order and the trip is at status EN-ROUTE
When the POD is set for an order and the trip is at status COMPLETED
If one of these actions takes place the version number for the PO number will be increased. For the trip messages all PO’s on the trip that match the necessary criteria to be included in the file will be updated with the next version number in the sequence for that PO.
The version number will be included in the Outbound XML file. This will require a change to the interface package INT_XML, and also a column will need to be added to the table INT_PO_OUTBOUND_FILE to store the version number for sending.
A new field will be added to the Purchase Orders screen to display the version.
Table Updates Required
New column PO_OUTBOUND_VERSION NUMBER(5) added to
SCH_PURCHASE_ORDER,
INT_PO_OUTBOUND_FILE
Document History
| Initial version | ||||
| Reviewed and Issued | ||||
AUTHORISED BY
| Matt Crisford | Development Manager | |
| Peter Greer | TMSCC MTS Product Manager |
