What's new in version 2406.5.0.0
Aptean EDI
•
Release Note
•
7/26/2024
•
2 min
Enhancements/Modifications
With this release of the Aptean EDI extension, the system only fills in the ContractNo field in the 855 outbound files if the ReleasePONumber field is present in the 850 inbound file. Previously, the ContractNo field was always filled, but this has been changed because it represents the end customer's PO number, which may not always exist. This update addresses the issue reported in bug ID #215637.
Resolved issues
The following issues have been resolved in this release.
| ID | Description |
|---|---|
| 215637 | The system inherits the ContractNo field value from the inbound message for the ReleasePONumber field value in the outbound file while processing the sales order EDI messages via Aptean EDI 850 port to the following ports: |
| 222016 | The system inherits the Line.EDI Ref. Line No. field value from the Line.Line No. field instead of the inbound 850 file while processing the sales order EDI messages via Aptean EDI 850 port to the following ports: |
| 217314 | The system inherits the Ship-to County field on the sales header field value for the ShiptoState field in the outbound file from the company information instead of from the inbound file. This occurs while processing the sales order EDI messages via Aptean EDI 850 port to the following ports: |