EDI Core
EDI Core - Setup EDI parameters
EDI Core - Setup EDI parameters
The EDI parameters page is used to define settings that apply across the EDI module. These settings affect number sequences, and other behaviour. The setup on this page is set per legal entity and can be modified by users who have the appropriate security permissions.
To open the EDI parameters page, go to EDI > Setup > EDI parameters. Then set the fields as described in the following subsections.
After each deployment, users should select the Refresh module button on the General tab of EDI parameters page.
This option will refresh the modules artefacts and ensure the module is up to date.
The parameters control the operation for the module per legal entity. The EDI parameter’s Date format will be used to default Text document type’s Date formats. XML and JSON uses standard ISO formats, but can be overridden on a document level.
Leave XML and JSON as Standard date format to utilities the standard formats. If they are setup as Custom, the custom date and time format must be specified.
The following table describes the fields that are available on the General tab of the EDI parameters page.
| Field | Description |
|---|---|
| Document Types | |
| File Attachment Document Type | Specify the Document management type used to store EDI files that are sent and received for review. Ensure file types/extensions that will be received from Trading partners, are included in File types at Organization administration > Document management > Document management parameters. |
| Connection | |
| Connection profile | Specify the default Connection profile to be used when sending Outbound documents. This default can be overridden on Trading partner or Trading partner’s document level. |
| Date | |
| Date and time format | Standard – Enables standard date/time formats. Enables the following fields: - Standard date and time format - Standard time format - Culture Custom – Provides ability to specify a custom date/time format. Enables the following fields - Custom date and time format - Custom time format |
| Standard date and time format | Enabled when Date and time format is set to Standard. Options |
| Standard time format | Select between Short time or Long time |
| Culture | Enabled when Date and time format is set to Standard - Custom – Enables the Custom date and Custom time format fields - Invariant – Culture insensitive, associated with English language but not with any country/region - Standard – Enables Standard language field, to select applicable std language |
| Standard language | Enabled when Culture is set to Standard. Select applicable standard language |
| Custom date format | Enabled when Culture is set to Custom |
| Format | Select the default date format to be used for all text templates |
| Day | Select the default format used for day for all text templates |
| Month | Select the default format used for month for all text templates |
| Year | Select the default format used for year for all text templates |
| Separator | Select the default date separator used for all text templates |
| Custom time format | Enabled when Culture is set to Custom |
| Format | Select the default time format to be used for all text templates |
| Separator | Select the default time separator used for all text templates |
| Custom date and time format | Enabled when Date and time format is set to Custom |
| Custom date and time format | Enter custom date and time format |
| Formatted date and time example | Displays example date and time for Custom date and time format (in UTC timezone) |
| Custom time format | Enter custom time format |
| Formatted time example | Displays example time for Custom time format (in UTC timezone) |
| Sales orders | |
| Restrict EDI picking route generation to allowed document types | • No (default) - Record created in table SAB_EDIWMSPICKINGROUTEEXT each time a picking list is posted. • Yes - Record will only be created in table SAB_EDIWMSPICKINGROUTEEXT for customers with Customer advanced shipping notice and Warehouses with Picking list documents enabled. |
| Allow historic PO types | Customer order types: Confirmation, Cancel and Change have been moved to Order purpose. This field provides Backwards compatibility to still show these deprecated options under order types |
| Saved views | |
| Apply standard view | Applicable when feature Saved views performance enhancement is enabled, and user navigates from a Staging form to Inbound files using the Inbound files button. Inbound file’s Default view is applied and could result in applicable inbound file not displaying. When setting new EDI parameters field Apply standard view to: • Yes: the standard view will be applied • No: the default view will be applied |
Use the Number sequences tab on the EDI parameters page to assign number sequence codes to the different number sequences that the EDI module uses. The following table describes the purpose of each of those number sequences. For more information about number sequences, see Number sequences overview and its related topics.
Note: Number sequences displayed is dependent on enabled licensed modules.
| Reference | Description |
|---|---|
| EDI number | Unique identifier for EDI staging record. This stores the data in D365 in an intermediary/staging tables before creating the target record. |
| Group control number | Unique identifier assigned to field Group control number on outbound staging records. The Inbound functional acknowledgement needs to refer to the outbound document’s Group control number in order to reconcile against the correct outbound record and update the Received status to Yes. |
| ASN number | Unique identifier assigned to ASN number on Consignment notes when creating a Customer Advanced Shipping Notice (ASN) record. Customer license only |
| Reconciliation Id | Unique identifier assigned to Inventory reconciliation’s Reconciliation Id when creating a 3PL Reconciliation. 3PL license only |
| Consignment note number | Unique identifier assigned to Consignment note number when using Customer advanced shipping notice Document setting Auto assign consignment note number set to Yes and the Sales order’s Shipping carrier isn’t set to automatically create Consignment notes. Customer license only |
The Hold codes tab is only available for Customer license. Assign the Hold codes to be used when creating the Sales order when processing Customer purchase order records.
If required, create new Hold codes via Sales and marketing > Setup > Sales orders > Order hold codes.
Order hold codes used for EDI, should have the following fields set to No:
The following table describes the fields that are available on the Hold codes tab of the EDI parameters page.
Ensure different hold codes are assigned for each.
| Field | Description |
|---|---|
| POC pending hold code | Specify the hold code to be used for sales orders that require a Purchase order confirmation (POC). When Customer purchase order acknowledgement document setting PO confirmation required is set to Yes, the Sales order will be created with this Hold code. |
| POA pending hold code | Specify the hold code to be used for orders that require a POA must be sent. When Customer purchase order acknowledgement document setting Lock order is set to Yes, the Sales order will be created with this Hold code. |
| Validation error hold code | Specify the hold code to be used for validation errors. When the Customer purchase order violates Error type validations, the sales order will be created with this Hold code. |