Minimum Version Required: 25.01
Pre-Conditions
Distributors setting up these data feeds must:
Carry products that are manufactured by MolsonCoors
Have a login to the MolsonCoors Drive system
Steps
Work with OpenText to begin sending files
1. Confirm the following information:
Which Locations should be receiving these files?
Which files would each Location like to receive? (Most distributors utilize both Drive Shipment and Drive ASN.)
2. Send an email to [email protected] with the following request:
{Distributor name} ({distributor number}) would like to begin receiving {Drive ASN, Drive Shipment, and/or Drive Order} files to their Encompass site. Their expected go-live date is {Go-live date}. Additionally, what is the ‘Receiver Routing Number’? (formerly known as Legacy MillerCoors Dist Num)
Set up the ECP site to ingest these files
1. Set up the Mailbox in the distributor site with the same field values as below. The mailbox name is important, and should be ‘MB{Receiver Routing Number}’
2. Set up one ExchangeConfiguration per Location and file type.
a. For Drive ASNs, set the Mailbox, SenderID, and ReceiverID
b. For Drive Shipments and Drive Orders
i. Create another Mailbox with the Drive_Inbound API Command. The Mailbox name should be the same as the Drive SuppliersReports.DistributorNumber. Make one of these for each Location. NOTE: This mailbox may already be created if Drive Supplier Reporting is already set up.
ii. Add Exchange Configuration(s) as well. These records should not have the new mailbox assigned to them. Only the ExchangeMap needs to be set on these. Use the MolsonCoors Drive Inbound Shipments Exchange Map for Drive Shipments and MolsonCoors Drive Inbound Orders for Drive Orders
3. Add corresponding ExchangeConfigurationsLocation record(s).
4. Ensure that a SuppliersReports record is set up with ReportType=Drive
Fields And Definitions
MolsonCoors Drive has the capability to send 3 different files to Encompass. These files are used to automatically create future Purchases and Shipments in the distributor’s ECP site.
File Types:
Drive Order - Rough estimates of upcoming shipments used. Does not contain pallet-level data, and does not completely align with the ECP table structure. Most distributors do not utilize this file, as it typically tends to just muddy up the shipments and purchases tables with inaccurate data that does not get automatically updated.
Drive Shipment - More official Drive Order. Basically what MolsonCoors thinks they will likely deliver.
Drive ASN - Sent after the shipment is loaded and is in transit. Contains pallet-level data used for scanning in these shipments when received.
Other terms:
OpenText: A file trading partner. MolsonCoors uses OpenText as the “middleman” to facilitate these file transfers.
Receiver Routing Number: Formerly known as the Legacy MillerCoors distributor number. This is one of the identifiers that MC uses to identify a warehouse.
Best Practices
Ensure that all MolsonCoors products have accurate OSKUs (Products.SupplierProductNum). These values can be pulled from the global product catalog by using the ‘Product Manager’ tool.
Do not set up Drive Order files. These files will clutter up your Purchases table and Shipments table with data that does not automatically get updated or cleaned up.