1. Metapack
  2. Shipping
  3. Integrations
  4. Integrating with Manhattan EPI

Configuring WMOS for use with Delivery Manager

Setting up the required EPI parameters

In Manhattan's WMOS, you need to configure the following EPI parameters with the values listed in the following tables:

Table 10. All Parameters

Category

Parameter

Value

EPI

EPI Provider Name

METAPACK

EPI

EPI Provider URL

Your Metapack Delivery Manager URL, e.g. https://dm-delta.metapack.com/ if you are using the test environment.

EPI

Maximum number of retries for EPI Server calls

3

EPI

Maximum wait time (milliseconds) to get response from EPI Server

10000

EPI

Save Failed Parcel Messages Only

No

Now go to the parameters for each warehouse in turn:

Warehouse_Parameters.png

Set the following:

Table 11. Warehouse Parameters

Category

Parameter

Value

EPI

Enable External Parcel Integration

Yes

EPI

Maximum number of threads for EPI Process

10

EPI

Print EOD Documents on End of Day process

No

EPI

EPI Profile

manhepidelta

Note

This is the username that will be used in messages to Metapack

EPI

EPI Ship Failure Message Format

Plain Text

EPI

EPI Print oLPN Barcode with Shipping Label

EPI Shipping Label with oLPN barcode (1 Label)

Setting up the required EPI records

in Manhattan's WMOS, you need to set up the following EPI records:

Note

At least one Carrier, one Service Level, and one corresponding Ship Via, must be configured.

Carriers
Carrier_Records.png

The mandatory fields that need to be set up for each Carrier record (not all shown in the above screenshot), are as follows:

  • Carrier Code

  • Carrier Name

  • Carrier Company Name

  • Parcel Carrier Type (set this to 'External' as it is an EPI Carrier)

  • EPI Carrier Code (set this to the Metapack Delivery Manager Carrier Code).

  • Supports EOD Process? (set this to 'Yes' if you are going to be creating manifests in Metapack Delivery Manager).

  • Supports HOLD Process? (set this to 'Yes' if you are going to using Ship and Hold).

  • Carrier Address

  • Enabled

  • Business Unit

  • Mark For Deletion (set this to 'No').

  • Carrier – Mode

  • Carrier - Service Level. This is updated after the list of Service Levels have been created, as shown here:

    Carrier_Details.png
Service Levels
Service_Levels.png

The mandatory fields that need to be set up for each Service Level record (not all shown in the above screenshot), are as follows:

Ship Vias
Ship_Via.png

The mandatory fields that need to be set up for each Ship Via record are as follows:

  • Ship Via Name

  • Ship Via Description

  • Carrier

  • Mode

  • Service Level

  • Business Unit

Setting up the required EPI system codes

In Manhattan's WMOS, verify that Manhattan Support have set up the codes described below. You can contact them here.

EPI Service Groups

When selected in WMOS, the chosen group represents the Carrier 'Service Group' in Metapack Delivery Manager) that is to be used for rate shopping (if required).

Note

WMOS does not define, but only maintains, the list of rate shop groups to be used by Metapack.

The actual definition of the rate shop group, including the carrier services associated with the group, needs to be set up and maintained in Metapack Delivery Manager - refer to Creating your Carrier 'Service Groups'.

An EPI Service Group is maintained through system code S D29 in WMOS, and an entry for this system code is added by entering the following:

  • CODE ID (to be mapped to the name of the rate shop Carrier 'Service Group' in Metapack Delivery Manager).

  • CODE ID Description

  • CODE ID Short Description

For example:

Rate_Shop_Group.png
Remaining Codes

The remaining codes that need to be set up are as follows:

  • Order Notes. These are used to bridge the key Metapack information such as the carrier service code and the carrier 'service group' for every order. The three fields that are populated in Order Notes are: Notes, Note Type and Note Code. The Notes store the carrier service code and carrier 'service group' values in B/MBC. Additional codes B/348 and B/349 are used to store the value variations (in Note Type and Note Code, respectively).

  • B/MET. This Warehouse-level system code needs to be added with a value of "MetaPack Configuration". Miscellaneous flags bytes 1-100 need to be defined as “Parameter Value”.

  • B/LBL. This Warehouse-level system code needs to be added with a value of "Shipping Label Properties", with a maximum code length of 10 and bytes 1-100 defined as "Parameter Value".

  • B/MBC. This Enterprise-Level system code needs to be added as "MetaPack Booking Code", with a maximum code length of 3. Each code ID then needs to be added to B/MBC, e.g.

    Booking_Codes_Manhattan.png

    The following parameters then need to be added to B/MBC:

    Booking_Codes_Manhattan_2_.png

  • B/PDF. This Warehouse-level system code needs to be added with a value of "Customs Documents Properties", with a maximum code length of 10 and bytes 1-100 defined as "Parameter Value". The code_ids need to be configured as follows:

    Customs_Docs.png

  • B/140. This is a "Miscellaneous Instruction Type" for which Code_Ids can be added as in the following example:

    Miscellaneous_Codes.png

    Important

    These Code_Ids (including the one for harmonisedProductCode that is not shown above) can be used to pass on item-specific information to MetapackDelivery Manager as part of the Product and Dangerous Goods arrays. Each instruction can be added through Items UI. These product-level items are particularly important post-Brexit.

  • S/708 Purge Types. Code ID 903 needs to be added with a value of "EPI_MANIFESTS". This is so that manifested records are purged from the EPI_CONSIGNMENTS table. Refer also to Purge System Tables.

  • Message Master. This is required in order to generate any end of day system errors.

  • Nextup Counter. Counter “EPI End of Day ID” needs to be added, and configured so that the real manifest IDs returned from Metapack do not clash with the values generated by the counter.

  • Purge System Tables. An entry needs to be added to these tables for the purging of EPI_CONSIGNMENTS.

    Note

    The purge also needs to be included in the schedule to meet Metapack's requirements.

    The purge does not support the archiving of purged data.