MetaPack
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, EDI etc.
This is a generic guide based on the version of the WMS 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.
Process Overview
01. 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.
02. At this point the orders will remain on the WMS EDI inbound transient tables
03. Once a confirmation response is received from MetaPack the order will progress into the WMS and follow existing processes
04. 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
05. Once the data is amended the order will be resent to MetaPack and upon confirmation will progress as point 3
06. Pack confirmation will be amended to send an order update to MetaPack to print the required carrier labels
07. Orders will be manifested on the MetaPack system and upon completion will update the WMS
08. 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
09. 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
Pre-requisites and Setup
Printer Setup (Local PC)
To ensure the carrier labels are printed in the correct orientation and size, a zebra printer must be setup on the local PC.
Select the zebra printer option on your local PC, right click and select Printing Preferences -
Selecting Printer Preferences -
Ensure that values are set as above, with main values being the Paper Format and Size settings.
Order Priority (SOS1600) -
The WMS ‘Order Priority’ data setup must correspond to the same data in the Metapack ‘SERVICE GROUP’ data setup.
Warehouse Maintenance (STKWHSE01A)
A valid Warehouse Id and full address details must be maintained to pass validation on MetaPack. This is to accomodate any returns back to the warehouse.
Warehouse Maintenance, UOM
Requires setting up to ensure the correct unit of measure is sent to MetaPack
Note: Metapack will by default store weights in grams and other dimensions in Metres.
Values required -
- Weight = GRM
- Length = MT
Stock Maintenance (STKSTOC01B)
Gross weight of the product is used to calculate the finished weight of the package, if not populated then the default weight will be passed to MetaPack.
Pallet Maintenance (WHS0045)
The Depth, Width, Max Height and weight of the Pallet/Package Type must be entered to be passed over to MetaPack else the default values will be sent.
Carrier Code Maintenance (WHS0055)
Ensure that carrier codes setup on MetaPack are maintained in the WMS, though not required for Sales Order validation it can be used for reporting and enquiry purposes.
SOAP Setup
Owner Maintenance (STS1000)
External Interfaces Tab -
A new tab 'External Interfaces' will hold a MetaPack indicator which must be set to 'Yes' for the MetaPack functionality to be called.
Simple Object Access Protocol (SOAP) Connection Control Maintenance (XFM1001)
The Metapack SOAP name will need to be set as follows, and the SOAP WSDL will need to be configured to match the correct URL.
SOAP NAME | SOAP WSDL |
---|---|
METAPACK_DEALLOCATE | http://test1.metapack.com/dm/services/AllocationService |
METAPACK_UPDATE | http://test1.metapack.com/dm/services/ConsignmentService |
METAPACK_ALLOCATE | http://test1.metapack.com/dm/services/AllocationService |
METAPACK_CONS_EXIST | http://test1.metapack.com/dm/services/ConsignmentSearchService |
METAPACK_CONS_STATUS | http://test1.metapack.com/dm/services/ConsignmentSearchService |
METAPACK_GET_CONS_REF | http://test1.metapack.com/dm/services/ConsignmentSearchService |
METAPACK_CREATEANDALLOCATE | http://test1.metapack.com/dm/services/AllocationService |
METAPACK_DELETE_CONS | http://test1.metapack.com/dm/services/ConsignmentService |
- CreateandAllocate – This runs the Metapack ‘createAndAllocateConsignmentsWithBookingCode’ message.
- Deallocate – This runs the Metapack ‘Deallocate’ message.
- Update – This runs the Metapack ‘updateConsignments’ message.
- Allocate – This runs either the Metapack ‘AllocateConsignment’ or ‘allocateConsignmentWithBookingCode’ message.
- Cons_Exist, Cons_Status and Get_Cons_Ref – These 3 messages all run the Metapack ‘findConsignmentsByOrderReference’ message.
- Delete_Cons – This runs the ‘deleteConsignment’ message.
Authentication
- “Soap User” / “Soap Password” – This stores the username / password provided to access Metapack.
- “Maximum Batch Size” – This controls the maximum number of records which are sent in any one ‘batch’ of data records.
- “Timeout” – This is the maximum length in time (seconds) before a time-out is generated by the WMS process.
Package Defaults
- “Default Width” / “Depth” / “Weight” and “Height” – these are defaults to be used if none are provided for box size. If no value is provided, the system will default a value of 1.
- Sender Code - Used in MetaPack for reporting purposes, the sender code is the warehouse id as known by MetaPack else the value 'DEFAULT' is entered.
Process
Customer Ref = Order Ref = SOAP Order Number Order Number = SOAP Reference = DM Consignment Number (assigned by metapack when allocated)
Document History
Copyright OBS Logistics © 2008
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