EDI Customer
EDI Customer Setup on Trading partners
EDI Customer Setup on Trading partners
This section provides a short overview of the required prequisites for setting up EDI for Customers.
The Trading partner fields are used to describe how the prequisites setups are allocated to an EDI customer.
Users can access the form by navigating to EDI > Setup > Trading partners
Customer 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 |
| Customer EDI order types | Order type identifiers. Determines if the Customer purchase order record will create a Sales order, Agreement, or Release order | EDI > Customer setup > Customer EDI order type group |
| Order purpose | Order purpose identifiers. Determines if the order is original, confirmation, change or cancellation | EDI > Customer setup > Order purpose group |
| Order line change type group | Order line change type identifiers. Determines the update tolerance for each EDI order change type | EDI > Customer setup > Order line change type group |
| POA response code group | Status of information used in Purchase order acknowledgement | EDI > Customer setup > POA response code group |
| No backorders | Identify if the trading partner accepts backorders. | Y/N |
| 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 |
During the sales process for EDI orders, there are times when a sales order must be placed on hold. When a sales order is placed on hold, an order hold code is assigned to the sales order to indicate the reason for the hold.
The following Customer setup is required on EDI parameters.
Users can access the form by navigating to tab Hold codes on EDI > Setup > EDI parameters.
| Setup | Short description | Setup path |
|---|---|---|
| Validation error hold code | Specify the hold code to be used for validation errors | Sales and marketing > Setup > Sales orders > Order hold codes |
| POA pending hold code | Specify the hold code to be used for orders that require a POA must be sent | Sales and marketing > Setup > Sales orders > Order hold codes |
| POC pending hold code | Specify the hold code to be used for orders that require a PO confirmation (POC) must be received | Sales and marketing > Setup > Sales orders > Order hold codes |
Where the System pack and System inner is used to confirm pack sizes on the Customer purchase order acknowledgement, the following is required on each item:
See Setup item pack sizes for more details.
Where advanced shipping notice (ASN) will be sent to EDI customers it is required to assign ASN line configuration on the ‘Ship from’ warehouses. Determines what information will be used when creating the ASN: