EDI Vendor
EDI Vendor Setup
EDI Vendor Setup
This section provides a short overview of the required prequisites for setting up EDI for Vendors.
The Trading partner fields are used to describe how the prequisites setups are allocated to an EDI vendor.
Users can access the form by navigating to EDI > Setup > Trading partners
Vendor Trading Partner Setup - Quick Summary:
| Setup | Short description | Setup path |
|---|---|---|
| Options | ||
| Connection profile | Ability to override the default EDI connection profile on Trading partner level. If blank, default EDI connection will be used. Default EDI connection is determined by: • Outgoing documents: Connection profile setup on EDI > Setup > EDI parameters • Incoming documents: All active connection incoming paths as setup in Connections. |
EDI > Setup > Connection setup |
| Cleanup profile | Ability to override the default Cleanup profile (setup on Shared EDI parameters) on Trading partner level. If blank, default Cleanup profile will be used as setup on EDI > Setup > EDI shared parameters | EDI > Setup > Cleanup profile |
| Order | ||
| Order type | Order type identifiers. Indicates if the order is a purchase order, agreement or release order. | EDI > Vendor setup > Order type group |
| Order purpose | Order purpose identifiers. Indicates if the order is original, confirmation, change or cancellation. | EDI > Vendor setup > Order purpose group |
| Order line change type | Order line change type identifiers. Indicates type of change to the order line, example ‘Add additional item’, ‘Delete items’ or ‘Changes to line items’. | EDI > Vendor setup > Order line change type group |
| Carrier mode | Carrier mode mappings. Ability to send the trading partner’s mapped value per D365 Mode. | EDI > Vendor setup > Carrier mode |
| Charges code | Charges code mappings. Ability to send the trading partner’s mapped value per D365 Charges code. | EDI > Vendor setup > Charges code |
| Payment terms type | Payment terms mappings. Ability to send the trading partner’s mapped value per D365 Terms of payment. | EDI > Vendor setup > Payment terms type group |
| Misc. charge/allowance indicator | Misc. charge/allowance mappings. Indicates if the header charge is an allowance (charge < 0), charge (charge > 0) or no allowance or charge (charge = 0). | EDI > Vendor setup > Misc charge/allowance indicator |
| Misc. method of handling | Misc. method of handling mappings. Indicates if the header charge received on the purchase invoice needs to be added to the D365 invoice. | EDI > Vendor setup > Misc method of handling |
| Acknowledgement | ||
| POA response code group | Status of information used in Purchase order acknowledgement | EDI > Setup > Vendor setup > POA response code group |
| UOM | Unit of measure mappings for in- and outbound documents | EDI > Setup > UOM mapping |
| Outgoing documents | It brings the document template, mappings, settings profile together to enable the document for the trading partner |
|
| EDI Document type | Each applicable outbound document type | EDI > Setup > Document types |
| Template | Document type template | Templates on EDI > Setup > Document types |
| Setting profile | Settings profile | Setting profiles on EDI > Setup > Document types |
| File name setup | Outbound file name | EDI > Setup > Document types |
| Connection profile | Ability to override the default EDI connection profile on document level. If blank, the trading partner’s Connection profile will be used. | EDI > Setup > Connection setup |
| Cleanup profile | Ability to override the default Cleanup profile on document level. If blank, the trading partner’s Cleanup profile will be used. If Trading partner’s Cleanup profile is blank, the default Cleanup profile on EDI shared parameters will be used. | EDI > Setup > Cleanup profile |
| Acknowledgement | An Inbound Functional Acknowledgement is required from the trading partner for the outgoing document. Note: Also required to setup the Functional acknowledgement inbound document under Incoming documents. | Y/N |
| Enabled | Ability to enable/disable document type for Trading partner | Y/N |
| Incoming documents | It brings the document template, mappings, settings profile, validation and filename mask together to enable the document for the trading partner | |
| EDI Document type | Each applicable inbound document type | EDI > Setup > Document types |
| Template | Document type templates defined for the document type | Templates on EDI > Setup > Document types |
| Setting profile | Settings profiles defined for the document type | Setting profiles on EDI > Setup > Document types |
| Validation profile | Validation profiles defined for the document type | EDI > Setup > Document types |
| Search mask | A file mask is used to match files in the document type’s defined directories | |
| Connection profile | Ability to override the default EDI connection profile on document level. If blank, the trading partner’s Connection profile will be used. | EDI > Setup > Document types |
| Cleanup profile | Ability to override the default Cleanup profile on document level. If blank, the trading partner’s Cleanup profile will be used. If Trading partner’s Cleanup profile is blank, the default Cleanup profile on EDI shared parameters will be used. | EDI > Setup > Cleanup profile |
| Acknowledgement | Trading partner requires an Outbound Functional Acknowledgement for the incoming document. Note: Also required to setup the Functional acknowledgement outbound document under Outgoing documents. | Y/N |
| Enabled | Ability to enable/disable document type for Trading partner | Y/N |
Where the System pack and System inner is used to review pack sizes on the Vendor purchase order acknowledgement, the following is required on each item:
See Setup item pack sizes for more details.