Minimum Version Required: 24.01

Pre-Conditions

The following assumes that a given distributor is ready to begin trading EDI files with a defined trading partner and the distributor does not have an EDI Implementation service request Task ID already assigned.

Steps

How to Create a New EDI Implementation Service Request

1. Go to the Encompass Customer Pourtal

2. Scroll to the bottom of the webpage and click Create a New EDI Implementation service request

3. In the Encompass Customer field, enter the name of your organization (if you already have an existing EDI implementation Task ID, enter that ID in the 'Task ID' field and skip the Encompass Customer field)

4. Fill out the remaining fields and click Submit

5. Upon submission of the form, your EDI Implementation Task ID link will display in the upper-left corner of the screen

If you have issues filling out and submitting the EDI Implementation Service Request form, please submit a Zendesk Ticket.

Fields And Definitions

Task ID: The Encompass Task ID provided to the distributor by Encompass directly

Encompass Customer: The name of the distributor's organization

Trading Partner: The retailer or supplier with whom you are trading files

Trading Partner Primary Contact: The name and email of the designated contact for this EDI implementation

Trading Partner EDI Provider: Who is making this EDI setup request? Is the request direct from a retailer/supplier, or is it an indirect request via AB OrderBud, OpenText GXS (MillerUFF), etc.?

Vendor Numbers: If multiple Vendor Numbers will be used for this setup, specify which Vendor Number is related to which Product Type/Product Group (ALC, NA, Red Bull, etc.)

ECP Customer ISA Qualifier/ID: example: ZZIJOHNDOEDIST; 'ZZ' is the Qualifier and 'JOHNDOEDIST' is the ISA ID

Trading Partner TEST ISA Qualifier/ID: example: ZZ/008965063T is Walgreens' Test ISA Qualifier/ID

Trading Partner PROD IDA Qualifier/ID: example: ZZ/008965063 is Walgreens' Production ISA Qualifier/ID

Functional Typer(s)/Transaction Set: What document types) are being requested? example: 810 (Post-Delivery Invoice), 850 (Purchase Order), 856 (Advance Shipment Notice), etc.

EDI File Spec Sheet(s)/Sample File(s): If any EDI file map specification sheet(s) and/or sample file(s) have been provided by trading partner

Customer Identifier (Chain Store Num, DUNS #, GLN, etc.): What does the trading partner use to identify their individual retail locations? Example: Chain Store Number (used by most retailers), Global Location Number (used primarily by Walmart), and/or DUNS # (used by retailers such as Kroger, Dollar General)

AR Accounts: EDI implementations are managed at the AR Account level. Detail the AR Account(s) specific to this implementation request. EDI best practice strongly suggests a one AR Account to multiple Customers relationship when assigned on the Chain

All or Specific Customer(s): The Cutomer record(s) found on your Customers table in your Encompass system

All or Specific Location(s): The Location record(s) found on you Locations table in you Encompass system

Specific Product Group(s): Is this setup related to Alcohol only, NA only, or Specific Product Group(s) (provide specifics if needed)

Best Practices

Requirements Often Gathered from the Trading Partner or EDI Provider

Trading Partner Primary Contact
Trading Partner EDI Provider
Vendor Numbers
ECP Customer ISA Qualifier/ID
Trading Partner TEST ISA Qualifier/ID
Trading Partner PROD IDA Qualifier/ID
Functional Typer(s)/Transaction Set
EDI File Spec Sheet(s)/Sample File(s)
Customer Identifier (Chain Store Num, DUNS #, GLN, etc.)

Requirements from your Encompass System

AR Accounts
Customers
Locations
Product Groups