Configuring the Blue Yonder Dispatcher WMS Integration

Review the following after Dispatcher WMS has been installed:

Dispatcher WMS configurable parameter settings

Workflow	Function	Function type	Description
General	Validate order types	Global	Must be enabled because Metapack services are validated against the order types set in the Metapack DM Configuration screen.
	Web access to Metapack DM configuration maintenance	Group
	Web access to Metapack DM configuration query	Group
	Allow update of Metapack daemon flags	Group	Determines which fields can be updated in an order header when updating orders manually.
Pre-carrier selection	Metapack - Only place mixable SKUs on the same pallet	Global	This works with the new Metapack Pallet Mixing option on the SKU Maintenance screen. If enabled, the page must be configured and the necessary information set in each of the fields to enable Dispatcher WMS to communicate effectively with the SOAP Shipping API. (The Metapack Platform can be configured by site, client, and order.) If disabled, SKUs with the option disabled cannot be mixed and will each be assigned to a different pallet identifier.
Pre-carrier selection	Web access to Metapack rectify carrier screen	Group	Needed for gaining access to the relevant screen.
Parcel packing	Metapack - Append parcels to consignment at packing	Global	This option allows the number of parcels in the consignment to be changed without having to deallocate and then reallocate the consignment in the Metapack Platform. Appending parcels to a consignment will not cause a change of carrier.
	Metapack - Further automate parcel packing	Global	Requires “Append parcels to consignment at packing”. If enabled, speeds up the parcel packing process as follows:You will be able to pack parts of an order without having to return to the packing tab. The consignment close tab will be skipped with pallet identifiers generated automatically. If an order is destined for a ship dock without an in-stage set, it will be automatically marshalled there.
	Metapack - Print Labels using parcel rapid print	Global	Upon successful carrier allocation, a number of labels will be generated by the Metapack Platform by invoking their rapid print functionality of Delivery Manager. If the version of Dispatcher WMS being used is pre-2011.1, to bypass the initial authentication within Delivery Manager, each workstation user must have a Metapack Web GUI session open in the background. If no browser screen is open while using the rapid print functionality, users will be prompted to log into Metapack. If enabled, allows the printing of labels per parcel rather than per order. This is particularly useful when appending parcels to an order. If disabled, the Metapack Platform regards the labels for an order as already printed.
	Web Repacking - Display special order handling instructions	Global	Must be enabled if special instructions linked to SKUs, orders, and so on must be displayed when repacking into parcels. If enabled, special instructions linked to SKUs, orders, and so on are displayed when repacking into parcels. If disabled, special instructions linked to SKUs, orders, and so on are not displayed when repacking into parcels.
	Metapack Administration - Allow printing of Metapack documents	Group	Needed for printing various documents for partially or fully packed orders.
	Metapack Administration - Allow printing of delivery note	Group	Needed for printing various documents for partially or fully packed orders.
	Metapack Administration - Allow printing of parcel label	Group	Needed for printing various documents for partially or fully packed orders.
	Web access to Metapack reprint label screen	Group	Needed for gaining access to the relevant screen.
	Web Access to parcel packing	Group	Needed for gaining access to the relevant screen.
	Web Repacking - Print delivery note	Group	If enabled, activate the Print on the Weight and Label tab (Operations > Order > Parcel Packing).
	Web Repacking - Print shipping label	Group	If enabled, activate the Print on the Weigh and Label tab (Operations > Order > Parcel Packing).
	Parcel Packing - Allow add button/drag and drop functionality	Group	If enabled, allow users to highlight inventory and drag it to the selected section instead of using Add. If disabled, universal product codes (UPCs) must be scanned to add them to a parcel.
	Parcel Packing - Check maximum weight for container type	Group	If enabled: If the calculated weight of the inventory being packed exceeds the maximum net weight set on the Pallet Type record, the warning message “Container weight exceeded” is displayed. If no maximum weight is set for the parcel type, the weight check will not be enforced even if this option is enabled.
	Parcel Packing - Prevent exceeding maximum weight for container type	Group	If enabled: If the calculated weight of the inventory being packed exceeds the maximum net weight set on the Pallet Type record, you must either choose a different parcel type or unpack one or more parcel items. If no maximum weight is set on the parcel type, the weight check will not be enforced even if this option is enabled.
	Parcel Packing - Prevent mixing of carrier within a pallet	Group	If enabled, you will not be able to pack orders with different carrier identifiers set on the order header (line).
	Parcel Packing - Prevent mixing of carrier/service level within a pallet	Group	If enabled, you will not be able to pack orders with different carrier identifiers and service levels set on the order header.
	Parcel Packing - Prevent mixing of consignment within a pallet	Group	If enabled, you will not be able to pack orders with different consignment set on the order header.
	Parcel Packing - Print special instructions report from pop-up screen	Group	This controls whether a special instructions report is generated automatically when the special instructions dialog is displayed. If enabled: A pop-up will be displayed prompting you to print a report. Only SKUs with special instructions codes, with the “use with reports” option enabled, and linked will be printed.
	Parcel Packing - Only display tasks for container	Group	If enabled, when you are packing by container rather than by order, prevents all the tasks for an order being displayed on the packing panel of the parcel packing screen.
	Parcel Packing - Skip Start tab if not all previously searched items are repacked	Group	If enabled, skip the Start tab on the parcel packing screen if the previously searched items are not repacked.
	Parcel Packing - Packing by Piece	Group	If enabled and the Parcel Packing - Packing by Piece check box is selected for a SKU (Settings 4 tab on the SKU page), Dispatcher WMS forces warehouse operators to scan piece by piece to confirm a SKU until all items are packed.
	Parcel Packing - Packing by Piece, Quantity Override	Group	If enabled and a warehouse operator partly packs the pieces of a SKU from the Parcel Packing page, Dispatcher WMS prompts the operator to pack multiple pieces based on the value set in the Qty Override field on the Parcel Packing page.
	Parcel Packing - Blind Scanning	Group	If enabled, warehouse operators will not be able to view the number of items that need to be packed.
	Parcel Packing - Print Delivery Note for last packed carton	Group	If enabled, warehouse operators can print the delivery note (shipping document) from the Parcel Packing page only after all of the product items of an order are packed.
	Parcel - Electronic signature capture for packed dimension update	Group	If enabled, a pop-up will be displayed requiring a supervisor user name and password to be entered before you can complete the parcel packing process.
Manifesting	Metapack - Flag parcels for manifesting when they are shipped	Global	If enabled, a request is made to add certain information (Metapack consignment identifier, and so on) to the shipping manifest.
Manifesting	Metapack - Delete order container records after manifesting	Global	If enabled, an order container record is deleted when the order is manifested. If disabled, an order container record is deleted when shipping manifest records are purged.

Dispatcher WMS data setup

Data requirement	Menu option	Description
Address maintenance	Data > General > Setup > Site > Address (tab)	The From Site (from where stock is being dispatched) on the order header must have a corresponding Address ID set up in Address Maintenance page. Otherwise, Dispatcher WMS will not communicate effectively with the Metapack Platform. The address details must also be entered. Otherwise, the Metapack daemon (`metapackdae`) will respond with error messages and an order will have its status changed to Hold.
Order header maintenance	Data > Order > Order Header	To support this integration, fields have been added to the Order Header Maintenance screen, which is updated automatically during the Metapack pre-carrier selection and labelling process. For each order header, ensure that the Metapack Carrier Pre-Selection check box is selected.
Order type maintenance	Data > Order > Order Type	To create an order type: In the Type field, enter a service group defined in your Metapack shipper account. Select the Metapack check box to make the order type available for processing by the Metapack platform. Select the Metapack Carrier Pre-selection check box to make the order type available for pre-carrier selection. Click Add. Note The Metapack Channel ID check box is no longer used.
Site maintenance - Parcel Packing	Data > General > Setup > Site > Parcel Packing (tab)	These options limit the parcel numbers created during parcel packing to a purely numeric value when packed in a specific site. There will be no prefix or suffix applied. The number of digits padded to will be controlled by a system profile entry.
SKU maintenance - Metapack option	Data > SKU > SKU	Select the Metapack Pallet Mixing check box if you want to use the configurable parameter Metapack - Only place mixable SKUs on the same pallet for pre-carrier selection.
Metapack HTTP TIMEOUT	System Profile > ROOT > SYSTEM > WAREHOUSE > METAPACK	Set the HTTP-TIMEOUT parameter to prevent transfer timeouts in the Metapack interface.
Metapack Delivery Manager configuration	Operations > Metapack Control > Metapack DM Configuration	The page must be configured and the necessary information set in each of the fields to enable Dispatcher WMS to communicate effectively with the SOAP Shipping API. The Metapack Platform can be configured by site, client, and order. Configure the following settings: Site ID: The site to which the configuration will be applied. Client ID: Metapack warehouse identifier. Order Type: Metapack Service Group code set up in both Order Type Maintenance and the Metapack Platform. Metapack URL: The URL for Metapack instance, which is specific to your user account. Metapack Username or Metapack Password: The user name and password used to log into Delivery Manager. Priority: The priority by which the specified order types should be processed at the pre-carrier selection. Height Conv Factor, Width Conv Factor, Depth Conv Factor, or Weight Conv Factor: Conversion factors. Max Batched: The maximum number or orders to batch during the pre-carrier selection process. Blue Yonder recommends setting the value of this parameter to 30 or less to prevent any performance problems when parsing returned messages.

Metapack daemon setup

The Metapack daemon needs to be run for both pre-carrier selection and manifesting.

Specifically, the daemon must be run twice for each order:

After an order has been created or interfaced, the daemon must be run before it can be allocated.
After the order has been shipped, the daemon should be run again to ensure that manifests can be produced.

To run the daemon, enter the following command:

metapackdae [options]

Command line options are as follows.

Command line option	Description
`[-C client]`	Client for which to process records.
`[-d]`	Debug features on (no updates made to database).
`[-T level]`	Oracle trace level (1, 4, 8, 12).
`[-t type]`	Order type to process.
`[-L level]`	Package logging level (1 to 5).
`[-1]`	Search once, check then exit.
`[-S site]`	Site in which to process records.
`[-s secs]`	Sleep time between checks (default: 60 seconds).

Dispatcher WMS-Metapack field mappings

Parameter	Metapack Platform field	Comments
Consignments	`alreadyPalletisedGoodsFlag`	Always `false`.
	`bookingCode`
	`calculateTaxAndDuty`
	`cardNumber`
	`carrierCode`
	`carrierConsignmentCode`
	`carrierName`
	`carrierServiceCode`
	`carrierServiceName`
	`cartonNumber`
	`consignmentCode`	`Order_Header.Mpack_Consignment`
	`consignmentlevelDetailsFlag`	Always `false`.
	`consignmentValue`	`Order_Header.Order_Value`, default as `0.0` if not set.
	`consignmentValueCurrencyCode`
	`consignmentWeight`	`Order_Header.Expected_Weight`, default as `1.0` if not set; multiplied by conversion factor if set.
	`custom1`	`Order_Header.User_Def_Type_1`, `null` if not set.
	`custom2`	`Order_Header.User_Def_Type_2`, `null` if not set.
	`custom3`	`Order_Header.User_Def_Type_3`, `null` if not set.
	`custom4`	`Order_Header.User_Def_Type_`4, `null` if not set.
	`custom5`	`Order_Header.User_Def_Type_5`, `null` if not set.
	`custom6`	`Order_Header.User_Def_Type_6`, `null` if not set.
	`custom7`	`Order_Header.User_Def_Type_7`, `null` if not set.
	`custom8`	`Order_Header.User_Def_Type_8`, `null` if not set.
	`custom9`
	`custom10`
	`cutOffDate`
	`deliveryPrice`
	`despatchDate`
	`earliestDeliveryDate`
	`fragileGoodsFlag`	Always `false`.
	`guaranteedDeliveryDate`
	`hazardousGoodsFlag`	`true` for hazardous goods, else `false` - from SKU table. Note This integration does not support hazardous goods.
	`liquidGoodsFlag`	Always `false`.
	`maxDimension`
	`moreThanOneMetreGoodsFlag`	Always `false`.
	`moreThanTwentyFiveKgGoodsFlag`	Always `false`.
	`orderNumber`	`Order Header.Order _ID`
	`parcelCount`	Default value is `1` for pre-carrier selection becase final number is not clear at that stage.
	`parcels` [Array] `code` `dutyPaid` `number` `parcelDepth` `parcelHeight` `parcelValue` `parcelWeight` `parcelWidth`	Pre-carrier selection will be `null` but will be the `Order_Container.Container_ID` at parcel packing. Always default as `0.0`. Pre-carrier selection will be `null` but will be the `Order_Container.Carrier_Consignment_Num` at parcel packing. Pre-carrier selection will be `1.0` but will be the `Order_Container.Container_Depth` at parcel packing (derived from pallet type) multiplied by conversion factor if set. Pre-carrier selection will be `1.0` but will be the `Order_Container.Container_Height` at parcel packing (derived from pallet type) multiplied by conversion factor if set. Pre-carrier selection will be `1.0` but will be the `Order_Container.Container_Weight` at parcel packing (derived from pallet type) multiplied by conversion factor if set. Pre-carrier selection will be `1.0` but will be the `Order Container.Container_ Width` at parcel packing (derived from pallet type) multiplied by conversion factor if set.
	`products` [Array] `countryOfOrigin` `fabricContent` `harmonisedProductCode` `productCode` `productDescription` `productQuantity` `productTypeDescription` `totalProductValue` `unitProductWeight`	`SKU.CE_COO` if set, otherwise `Site.Country`. `SKU.Harmonised_Product_Code Order Line.SKU_ID` `SKU.Description` `Qty` being repacked `Order Line.Product_Price` `Qty` being repacked, default as `1.0` if not set. `SKU.Each_Weight`, default as `1.0` if not set; multiplied by conversion factor if set. `productTypeDescription` is set to the Carrier Product if it has been set on the SKU.
	`pickTicketNumber`
	`pickupPoint`
	`podRequired`
	`properties` [Array] `propertyName` `propertyValue`
	`recipientAddress` [Array] `countryCode` `line1` `line2` `line3` `line4` `postCode` `type`	`Order_Header.Country` (Metapack Platform uses ISO 3166) `Order_Header.Address1` `Order_Header.Address2` `Order_Header.Town` `Order_Header.County` `Order_Header.Post_Code`
	`recipientCode`
	`recipientContactPhone`	`Order_Header.Contact_Phone`
	`recipientEmail`	`Order_Header.Contact_Email`
	`recipientMobilePhone`	`Order_Header.Contact_Mobile`
	`recipientName`	`Order_Header.Contact`
	`recipientNotificationType`
	`recipientPhone`
	`recipientVatNumber`
	`senderAddress` [Array] `countryCode` `line1` `line2` `line3` `line4` `postCode` `type`	(Site) Address for the site needs to be setup as a valid address record. (Site) `Address.Country` (Metapack Platform uses ISO 3166). (Site) `Address.Address_1` (Site) `Address.Address_2` (Site) `Address.Town` (Site) `Address.Country` (Site) `Address.Post_Code`
	`senderCode`	`Order_Header.From_Site_ID` (must set up on Metapack Platform).
	`senderContactPhone`	(Site) `Address.Contact_Phone`
	`senderEmail`	(Site) `Address.Contact_Email`
	`senderMobilePhone`	(Site) `Address.Contact_Mobile`
	`senderName`	(Site) `Address.Name`
	`senderNotificationType`
	`senderPhone`
	`senderVatNumber`	(Site) `Address.VAT_Number`
	`shippingAccount`
	`shipmentTypeCode`	Always default to `MERCHANDISE`
	`signatoryOnCustoms`	(Site) `Address.Name`
	`speciallnstructions1`	`Order_Header.lnstructions`
	`speciallnstructions2`
	`status`
	`termsOfTradeCode`	Either `DDU` or `DDP` from `Order Header.TOD` (`DDU` by default).
	`transactionType`	Always default to `delivery`.
	`twoManLiftFlag`	`true` if any SKUs on parcel are flagged as two-man lift, else `false`.

Dispatcher WMS configurable parameter settings

Dispatcher WMS data setup

Note

Metapack daemon setup

Dispatcher WMS-Metapack field mappings

Note