Data setup and configuration for Versatile DEX processing with MiniMate application
Versatile DEX App Setup
Please refer to Prism Support for Versatile DEX User Manual to set up Veratile DEX App.
ServQuest DEX Setup
DEX requires a couple credential values / information from both the vendor (sender / supplier) and retailer (receiver / retailer) for validation.
[VENDOR – provided by your company]
DUNS
COMM_ID
LOCATION
[RETAILER – obtained from each retail chain]
DUNS (CUST_DUNS)
LOCATION (CUST_LOCATION)
UCS VERSION (DEX_VERSION)
Address Maintenance – Customer DEX information
- Cust Duns - Every vendor (and retailer) must have their own unique DUNS number – assigned by the DUNS & Bradstreet organization.
- Comm ID - The communications ID (Comm ID) is sometimes calculated by using the company’s 10 digit phone number.
- Location (Store Code) - A Location value is used primarily to describe where the invoice items Are related to (meats / dairy / beverages), but if the retail chain does not care, the vendor could just send 000001 (for example).
Inventory Maintenance - DEX UOM
MiniMate Config
MiniMate Configuration for DEX should match these settings:
DEX_COMM_ID
- The communications ID (Comm ID) is sometimes calculated by using the company’s 10 digit phone number.
DEX_DUNS
- Every vendor (and retailer) must have their own unique DUNS number – assigned by the DUNS & Bradstreet organization. If they are not aware of their DUNS number, they should contact the DUNS & Bradstreet organization.
DEX_LOCATION
- A LOCATION value is used primarily to describe where the invoice items Are related to (meats / dairy / beverages), but if the retail chain does not care, the vendor could just send 000001 (for example).
DEX_VERSION
- DEX versions are either 4010 or 5010 – if you do not specify either, VersatileDEX will default to 4010.
DEX_ITEMS_ALWAYS_EA or DEX_ITEMS_ALWAYS_CA
- Must have all relevant DEX items listed, separated by commas, depending on DEX UOM