10.0.31.20230505
This document describes the features that are either new or changed in the release version 10.0.31.20230505.
Release 10.0.31.20230505
Build 10.0.31.202305054
Release date: 25 May 2023
Bug fixes
Vendor module
| Number |
Name |
Description |
| 14407 |
Purchase invoice |
Where the purchase invoice contained a zero unit price, the purchase order line’s unit price was used in calculation the invoice’s line amount. This has now been fixed to use staging values. |
Build 10.0.29.202305053
Release date: 5 May 2023
New features
Core module - Applies to all modules
| Number |
Functionality |
Reason |
| 12869 |
Azure connection |
New field Folder name for Azure connections adds the ability to set an azure folder for incoming and outgoing paths. Test path connection excludes folder names. |
| 13014 |
Text template |
Additional Row delimiter option Tilde {~} |
| 12403 |
Export batch job |
Where there is no data to export, change export batch’s log from error to info log |
| 13519 |
Picking list |
New option Restrict EDI picking route generation to allowed document types on EDI parameters • 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. |
| N/A |
License manager |
License manager version 10.8.32.10171 Enhanced Licensing capabilities to assist with licensing support and scaling. Note: Required to upgrade all installed DXC products to at least the following versions: • EDI 10.0.29.202305053 • Finance utilities 10.0.29.202305051 • SmartSend 10.0.29.202304142 • Core extensions 10.0.29.202304142 • DocuSign 10.0.29.202304211 • Item creation 10.0.29.202304211 • PLM 10.0.29.202304211 • Forex 10.0.29.202305101  |
Customer module
| Number |
Functionality |
Reason |
| 12615 |
Sales invoice |
Additional Sales order header fields added to Sales invoice line fields: • Sales responsible • Sales taker |
| 12647 |
New entity ‘EDI sales order entity’ |
New entity EDI sales order entity (SAB_EDISalesTable) provides users the ability to populate this table for sales order orders not created via EDI. This is useful for cutover sales orders where a customer is not set to receive EDI ASN or Sales invoice for non-EDI Sales orders. |
| 13782 |
SAB_EDISalesUseCustomerPrice |
Changed SAB_EDISalesUseCustomerPrice from Private to Public |
| 13698 |
EDI Sales order processing - Pending POA |
Ability to select multiple Pending POA records and click Send to EDI on the EDI Sales order processing workspace |
Vendor module
| Number |
Functionality |
Reason |
| 12897 |
Vendor purchase order acknowledgement (POA) |
When Line item - added is used to create a new line on the D365 Purchase order (PO), the PO line’s Site and Warehouse will be set by POA staging line if these fields are provided, else set by the Site and Warehouse on the PO header. |
| 13075 |
Vendor purchase order acknowledgement (POA) |
Where a Vendor purchase order acknowledgement staging record has errored because of Error tolerance validation, button Override error validation can be used to override and process to target. The button is available on: • EDI > Vendor workspaces > EDI purchase order processing. Select the Validation tab and select POA Errors under Processing or the tile under Summary. • EDI > Documents > Vendor documents > Vendor purchase order acknowledgement. Button is enabled when status is not completed or canceled. |
| 12898 |
Vendor advanced shipping notice (ASN) |
Use the purchase order line’s location when creating the Arrival journal. Previously used the default location. |
| 13649 |
Purchase invoice |
Related to 10372, Product receipt quantity to match logic has been updated to include invoice quantity of zero. |
3PL module
| Number |
Functionality |
Reason |
| 12403 |
Product master |
New document Product master in 3PL module. Can be used to provide information about new products and changes to existing products that apply to the warehouse. Products can be manually flagged and/or use periodic job to flag as applicable to the warehouse. Setup and Processing. |
Bug fixes
Core module
| Number |
Name |
Description |
| 10532 |
Inbound files Outbound files |
When file was processed by batch Log didn’t show the log message. |
| 12628 |
Trading partner documents |
EDI > Inquiries and reports > Trading partner documents. Form couldn’t open if environment contains a large number of trading partners (example 3000 EDI trading partners). |
| 12715 |
Document type - XML and JSON templates |
Removed automatic upper case applied to mapping name. For example renaming CurrencyCode to Currencycode, used to automatically revert to CurrencyCode and processing would fail if the incoming document field was called Currencycode. |
| 13854 |
FTP and SFTP Connection types |
When new was selected on Incoming paths, the first Outgoing path document’s Type was changed from Outbound to Inbound |
Customer module
| Number |
Name |
Description |
| 14057 |
Sales order |
Fix to query on Trading partners link on Sales order (EDI tab on ActionPane). |
| 13654 |
Sales invoice |
Revert changes from 11723. Caused Batch invoicing not creating Sales invoice EDI staging records. |
Vendor module
| Number |
Name |
Description |
| 12747 |
Vendor purchase order acknowledgement (POA) |
When the Vendor purchase order acknowledgement is processed from import to staging, and there are two vendors with the same GLN (two different legal entities), it would pick up the first Vendor GLN’s Company to create the staging record. And then tries to find the purchase order in the incorrect company when processing to target. |
3PL module
| Number |
Name |
Description |
| 14108 |
Transfer order - History |
EDI History was limited to Transfer orders where the To (receiving) warehouse was setup for EDI. Now includes From (shipping) warehouse that are setup for EDI. |