MetaPack: Difference between revisions
Lwinchester (talk | contribs) No edit summary |
Lwinchester (talk | contribs) |
||
Line 12: | Line 12: | ||
Process | =='''Process'''== | ||
1. Orders will be sent via an external sales ordering system via the standard EDI process and upload into the WMS with a new additional step to interface to MetaPack. | |||
2. At this point the orders will remain on the WMS EDI inbound transient tables | |||
3. Once a confirmation response is received from MetaPack the order will progress into the WMS and follow existing processes | |||
4. If an exception occurs then an alert will be generated to update Vision and the existing EDI validation screens will be used to amend the data | |||
5. Once the data is amended the order will be resent to MetaPack and upon confirmation will progress as point 3 | |||
6. Pack confirmation will be amended to send an order update to MetaPack to print the required carrier labels | |||
7. Orders will be manifested on the MetaPack system and upon completion will update the WMS | |||
8. A new process will be developed to run on a timed basis to place a call on MetaPack to confirm the status of an order, if the order is at the correct status the process will despatch confirm the order to allow EDI processing | |||
9. A new WMS screen will be developed to view the MetaPack audit log? | |||
10. A new screen will be developed in Vision to view the MetaPack exceptions | |||
11. The new audit log file will be added to the Oracle Data Extract suite for reporting | |||
Upload of orders from external Sales Ordering System, orders are initially loaded onto the transient table for the first validation checks by the WMS. | Upload of orders from external Sales Ordering System, orders are initially loaded onto the transient table for the first validation checks by the WMS. |
Revision as of 12:05, 18 July 2011
IN Progress
INTRODUCTION
This document describes the required screens to be used in setting up the information concerned with the Owners of stock in the warehouse. Other guides describe the set up of company, user, warehouse, stock etc.
This is a generic guide based on the version of the SCE system at the time of writing.
It can also be used by clients to specify their specific data values to aid initial system set up as well as for future reference.
Note that fields marked ‘**’ are mandatory and are needed to ensure correct set up of the system.
Process
1. Orders will be sent via an external sales ordering system via the standard EDI process and upload into the WMS with a new additional step to interface to MetaPack. 2. At this point the orders will remain on the WMS EDI inbound transient tables 3. Once a confirmation response is received from MetaPack the order will progress into the WMS and follow existing processes 4. If an exception occurs then an alert will be generated to update Vision and the existing EDI validation screens will be used to amend the data 5. Once the data is amended the order will be resent to MetaPack and upon confirmation will progress as point 3 6. Pack confirmation will be amended to send an order update to MetaPack to print the required carrier labels 7. Orders will be manifested on the MetaPack system and upon completion will update the WMS 8. A new process will be developed to run on a timed basis to place a call on MetaPack to confirm the status of an order, if the order is at the correct status the process will despatch confirm the order to allow EDI processing 9. A new WMS screen will be developed to view the MetaPack audit log? 10. A new screen will be developed in Vision to view the MetaPack exceptions 11. The new audit log file will be added to the Oracle Data Extract suite for reporting
Upload of orders from external Sales Ordering System, orders are initially loaded onto the transient table for the first validation checks by the WMS.
Upon successful validation, the messages are fed to metapack and validated on their system (i.e. correct postcode /date/time etc)
Upon successful validation on Metapack the orders are then released in to the order well ready for allocation, if the orders fail validation on Metapack then an error message is displayed in the EDI sales order validation screen MetaPack tab.
Orders are then processed through to and including packing, at which point there will be an option to manifest the order on the MetaPack system which will have assigned a carrier dependent on the service indicator for the order, a label will be produced and a message sent to the WMS that when processed will despatch the order from the system.
Pre-requisites
Warehouse UOM requires setting up to ensure the correct unit of measure is sent to MetaPack
<piccy UOM>
Setup
Customer Ref =
Order Ref = SOAP Order Number
Order Number =
SOAP Reference = DM Consignment Number (assigned by metapack when allocated)