EDI Customer
EDI Customer Setup - Document type Setting profiles - Customer purchase order
EDI Customer Setup - Document type Setting profiles - Customer purchase order
Users can access the form by navigating to EDI > Setup > Document types.
| Field | Description | Options/Example |
|---|---|---|
| Purchase order | ||
| Item ID Source | Determine the method of item identification used by this customer when ordering products. Where the External item number, GTIN or Barcode is unique per Variant, EDI will create the sales order against the correct variant, i.e. the customer doesn’t have to supply variant details in inbound document. | • Our Item number - this is the item ID on the items form • External item number - this is the item Id on the customer external item form • GTIN - this is the GTIN assigned to an item • Barcode - This is the Barcode assigned to an item. |
| Blank unit | Populate D365 sales order line’s Unit with one of these options when the staging line’s Unit is blank | • Sales unit - Populate with item’s sales unit • Sales trade agreement unit - Populate with applicable sales trade agreement unit. Where the Item id source is set to Barcode or GTIN, the Unit from Barcode and GTIN will be used. Where the Item id source is Our item number or External item number and no applicable sales trade agreement is found, the product’s Sales unit will be used. • Inventory unit - Populate with item’s inventory unit • Error - Errors the complete staging record |
| Price includes tax | Specify if the price (line amount &/or unit price) received from the Customer includes tax | Yes/No |
| Use Customer Price | Select this flag to use the customer’s price on the sales order | • Yes: If there is a variance between the trade agreement /list price stored in D365 and the Customers price received in the purchase order, the purchase order will be used if within the variance range. • No: System price will be used when creating the sales order. |
| Price variance type | Select if Maximum negative price variance and Maximum positive price variance is based on Amount or Percentage. For example 1 could be $1 or 1% variance compared to system unit price. | • Amount • Percentage |
| Maximum negative price variance | Where Use Customer Price is set to Yes: Specify the maximum negative price variance that can occur without warning. |
It is recommended that these settings are set to at least 0.01 if the ‘Price include tax is ticked’ to avoid any rounding differences between the two solutions being flagged. |
| Maximum positive price variance | Where Use Customer Price is set to Yes: Specify the maximum positive price variance that can occur without warning |
It is recommended that these settings are set to at least 0.01 if the ‘include tax flag is ticked’ to avoid any rounding differences between the two solutions being flagged. |
| Create release order without blanket order | The action taken when a release order is received without a blanket order | • No - do not allow the release order • Yes - allow the release order • Warning - allow the release order with a warning message |
| Duplicate tolerance | If a Customer purchase order (Customer requisition) is received more than once, D365 needs to determine what to do with the duplicate/s | • Error - Duplicate purchase orders not allowed and the staging record will error and not create an additional D365 sales order. • Accept - Duplicate purchase orders are allowed. Duplicate purchase orders will create a new D365 sales order. • Accept on flagged orders - Duplicate purchase orders are only allowed if existing sales order is flagged to allow duplicates. On the original sales order header set on the EDI FastTab set Bypass duplicate check to Yes. Staging records with a duplicate Customer requisition where the sales order’s Bypass duplicate check is set to No will error. |
| Update confirmed ship date | Similar to Simulate delivery dates, updates the Confirmed ship date and Confirmed receipt date on the sales order header, which are also used in the Customer purchase order acknowledgement. Confirmed dates are only updated when Delivery date control is not set to None. | Yes/No |
| Sales origin | If the target Sales order’s Sales origin should be set to a specific value, select here. If field Sales origin is received in the import file, the staging value will be used to set the target Sales order’s Sales origin. | EDI |
| Suppress add new address | Not applicable to staging records that have Store code populated, only applicable where the staging header’s address fields are used to create the new sales order. When the staging header’s address can’t be found against the customer and Suppress add new address is set to Yes, a new address will not automatically be added to the customer and used on the sales order - the staging record will error instead. | Yes/No |
| Skip error lines | Ability to set if lines with below errors should be skip when processing the record. The sales order will still be created, without these error line(s). The error lines will still be included in the outbound Customer purchase order acknowledgement with POA code mapping for ‘Line item - error’. Supported error scenarios: • Item not found • Item stopped for sales orders • Sell by date in the past |
|
| Purchase agreement | ||
| Agreement classification | Select the agreement classification used when blanket orders are created | |
| Strip field delimiter | Specify the delimiter used to identify a release order Some of the trading partners use a slightly different PO number on the Blanket order compared with the Release order. An example of a Blanket order PO number is 0005055365-0000, they will then send four releases with the number 0005055365-0010, 0005055365-0020, 0005055365-0030 and 0005055365-0040. In the template the strip field delimiter would be set to “-“, it should then find the applicable sales agreement by using the number before the delimiter. | |
| Supplementary items | ||
| Add mandatory supplementary items | Option to automatically add mandatory supplementary items upon sales order creation | Yes/No |
| Add optional free of charge supplementary items | Enabled when Add mandatory supplementary items is set to Yes. Option to automatically add optional free of charge supplementary items | Yes/No |
| Add optional charged supplementary items | Enabled when Add mandatory supplementary items is set to Yes. Option to automatically add optional charged supplementary items | Yes/No |
| Retail | ||
| Channel | Option to set the channel when creating retail sales order. | Drop-down options from Name as setup in Retail and commerce > Channels > Stores > All stores |
| Automatic complete retail order | Option to automatically Complete the Sales order and process payment for retail orders where the customer’s Allow on account is set to Yes. Utilizes Payment method as set below. If payment can’t be completed the sales order is put on hold. | Yes/No |
| Payment method | Option to set the Retail payment method for processing Payment. If Payment method is blank, the first Payment method for the Channel where Default function is Customer is utilized. | Drop-down options from Retail and commerce > Channel setup > Payment methods. Filtered to Default function = Customer (only Customer supported) |
The Setting profile can be assigned on the Incoming documents FastTab to document type Customer purchase order for the Customer Trading partner at EDI > Setup > Trading partners.