Previous EDI Notes
Vision EDI
This page only contains the historical release notes
The documents list details of bug fixes, improvements and new features that have been implemented in order to enhance the way that Vision EDI works.
Where a new feature has been added, you will be able to link directly to the user manual page giving details of how the new feature works and what it does.
You will also be able to view the details of changes which are due to take place in future releases of Vision EDI.
| Version | 3.7.4 |
|---|---|
| Release Date | 12/07/2019 |
| Other Application Requirements | VW v5.1.7+ |
| Warnings or Notices | Incompatible with VW v5.2.0+ |
| UID | Summary | Issue Type | Affects Version/s | Component/s | Description | Linked to | Configuration changes | License required |
|---|---|---|---|---|---|---|---|---|
| VEDI-768 | VCIS Order Import - UB Transport | Issue | 3.7.3 | General | The UB Transport info saved against VCIS order is not being populated in the EDI SO XML file and therefore not making it into the VW order. | VCIS-1128, VW-3370 | No | No |
| VEDI-771 | Orders - PODLineNumber | Bug | 3.7.3 | Files outgoing | When sending an order from VC,EDI,VCIS, it is not populating the PODLineNumber against the order line. | No | No | |
| VEDI-781 | Validation Failures - Delete SO line | Bug | 3.7.3 | Files incoming | Error produced when user attempts to delete a SO line in Validation Failures. | VSUP-10600 | No | No |
| VEDI-747 | Orders - Site code lookup | Bug | 3.7.2 | Files incoming | When a sales order is submitted without the HO section, and therefore no site code, the site code is looked up. This is not ignoring archived customers. | VSUP-9760 | No | No |
| Version | 3.7.3 |
|---|---|
| Release Date | 07/06/2019 |
| Other Application Requirements | VW v5.1.5+ |
| Warnings or Notices | None |
| UID | Summary | Issue Type | Affects Version/s | Component/s | Description | Linked to | Configuration changes | License required |
|---|---|---|---|---|---|---|---|---|
| VEDI-762 | API - new services | Improvement | 3.7.2 | API | Preliminary work for the following outbound reports to be fully available in the API in the next EDI version released: - Goods Received - Order Picking Confirmation - Stock Snapshot By Rotation - Stock Snapshot By Product | No | No | |
| VEDI-760 | Order - disappearing | Bug | 3.7.0 | Files incoming | After accepting an order from the 'Validation Failures' screen, the following error is sometimes seen in the log: Error processing an item from the Validation Failed Queue, Unable to add item to the Failed Validation Queue. The order then gets sent to the 'Failed Messages' (not 'Validation Failures') queue waiting to be manually reposted. Changes made to help prevent this from occurring in the first place, and also changes to fix the problem preventing users from reposting these failed messaged from the EDI app. | VSUP-10030 | No | No |
| VEDI-757 | Ordering - 'Excise No' Field length inconsistency | Bug | 3.7.2 | General | The Excise no on an order allows 50 characters, however, when this is being sent over to VB the destination field allows 16 only for both EMCS processing and Bond Doc generation. Changes to ensure this field follows the standard automatic truncation process as the other fields. | VW-4055 | No | No |
| VEDI-756 | Orders - C426No field | Issue | 3.7.3 | Files incoming | VEDI is not populating the C426No field in VW for D type orders. | No | No | |
| VEDI-753 | Schedule reports - site code validation | Issue | 3.7.3 | General | Site code validation message and validator are not displayed correctly. | No | No | |
| VEDI-745 | VCIS Orders - DP Account Ref | Issue | 3.7.2 | Files incoming | DP Account Ref is not mandatory for VCIS Orders is causing validation failures, the field will be filled with NA if it's not populated. | VSUP-9721 | No | No |
| VEDI-743 | New Orders Entered & Held Orders - Duplicates | Bug | 3.7.2 | Files outgoing | Orders duplicated on New Orders Entered and Held Orders Details report when the deferment account has multiple owners. | VSUP-9707 | No | No |
| VEDI-741 | Outgoing Files - SSCCs duplicating in outgoing file | Bug | 3.7.2 | Files outgoing | SSCCs are duplicating for each line in the Orders Processed XML file. | VSUP-9685 | No | No |
| VEDI-734 | Outbound files - XML whitespace (UI changes) | Design Change | 3.7.1 | Application / UI | Following on from the changes made in VEDI-732, the UI will now be updated to allow users to configure the XML condensing option. | VEDI-732 | No | No |
| VEDI-733 | Transfer collection - unable to load PO | Design Change | 3.7.0 | General | Changes required for VW-4279. | VW-4279 | No | No |
| VEDI-726 | Order picking confirmation - link to VB | Bug | 3.7.0 | General | Customers were receiving an email when the order picking confirmation was generated: "Whilst Vision EDI was generating the Orders Picking Confirmation report for customer: XYZ, movements which were expected in Vision Bond were not available, as such these movements have not been included in the sent report". The customer does not have Vision Bond so this message should never be generated. | VSUP-9068 | No | No |
| VEDI-725 | Purchase Order - Validation Failure Issues | Issue | 3.7.0 | Files incoming | On some PO when amending the supplier information the information is not being saved correctly after updating and is causing the failures to not clear. | No | No | |
| VEDI-720 | Non Latin Characters | New Feature | 3.7.0 | General | Changes linked to VW-4182 to ensure VEDI can send and receive non latin characters. | VW-4182 | No | No |
| VEDI-718 | Excise and VAT Summary - None-Due VAT | Bug | 3.7.0 | Files outgoing | On the Excise and VAT summary, None-Due VAT is not being shown correctly, it is showing as having Deferred VAT due incorrectly. | VSUP-8657 | No | No |
| VEDI-716 | API - Customer delivery status | Improvement | 3.7.0 | API | Delivery status is output in some API services, this is currently the internal status but an alternative customer status was added which can be used instead. | No | No | |
| VEDI-682 | Sales order - deferment number for non bonded customers | Issue | 3.6.4 | Files incoming | Orders are failing for non bonded customers as the system is insisting on a deferment number to be entered, yet deferment numbers cannot be set up for these customers in VW. | No | No | |
| VEDI-575 | Incoming Permission > Security changes | Issue | 3.5.0 | Files incoming | In the Incoming Permission screens > Stock Movement types are not being checked. | No | No |
| Version | 3.7.2 |
|---|---|
| Release Date | 04/04/2019 |
| Other Application Requirements | Requires Crystal reports redistributable v13.0.24+ + see previous version(s) notes |
| Warnings or Notices | None |
| UID | Summary | Issue Type | Affects Version/s | Component/s | Description | Linked to | Configuration changes | License required |
|---|---|---|---|---|---|---|---|---|
| VEDI-738 | Order Picked Confirmation - Picks from multiple locations | Issue | 3.7.0 | Files outgoing | When a rotation is picked from multiple locations, the Order Picked Confirmation is outputting a record for each location which invisible to the user, it should be grouping them together. | No | No | |
| VEDI-554 | CIS to EDI: Collection date | Issue | 3.4.1 | Files incoming | In VCIS-916 we fixed the issue whereby the CollectionDate was not saving by adding a new field, here we'll update the service to use the new field. | VCIS-916 | No | No |
| VEDI-737 | Stock Snapshot - Missing Product Single Size | Bug | 3.7.0 | Files outgoing | Stock Snapshot by Product Enhanced shows zero in the Product Single Size field. | VSUP-9633 | No | No |
| VEDI-735 | Transaction audit - not generating | Bug | 3.7.1 | Files outgoing | The transaction audit report is not generating on the schedule and reporting an error in the log. | No | No | |
| VEDI-714 | POD Extract - CSV (Order Ref and Doc Ref) | Bug | 3.6.2 | Files outgoing | For deliveries retrieved from VD, the Order Reference and Document Reference field data is swapped around. | VSUP-8567 | No | No |
| Version | 3.7.1 |
|---|---|
| Release Date | 28/03/2019 |
| Other Application Requirements | See previous version(s) |
| Warnings or Notices | None |
| UID | Summary | Issue Type | Affects Version/s | Component/s | Description | Linked to | Configuration changes | License required |
|---|---|---|---|---|---|---|---|---|
| VEDI-732 | Outbound files - XML whitespace | Design Change | 3.7.0 | Files outgoing | Changes made in VEDI-707 caused an issue on some systems processing the "leaner" outbound files. With this change, the compression will be configurable at "report schedule" level - in the back end only - the UI changes will come later. - By default, new report schedules will be setup to condense the XML. - Existing report schedules will be setup to not condense with the option of changing them to enable it if their system supports it. | VEDI-707, VSUP-9589 | No | No |
| Version | 3.7.0 |
|---|---|
| Release Date | 05/12/2018 |
| Other Application Requirements | Vision Warehousing v5.1.2+ Vision Distribution v2.1.4+ |
| Warnings or Notices | None |
| UID | Summary | Issue Type | Affects Version/s | Component/s | Description | Linked to | Configuration changes | License required |
|---|---|---|---|---|---|---|---|---|
| VEDI-691 | Goods received Confirmation PDF | Report | 3.6.3 | Files outgoing | Modify the Goods received Confirmation PDF Add Duty Stamped Y/N field. | RFC-462 | No | No |
| VEDI-692 | EDI XML combined stock report | New Feature | 3.6.3 | Files outgoing | New xml EDI stock report that combines the stock at product level across all sites for the same customer number and also includes stock in transit between sites. The data provided should show the product code, description, single size, SPC, CPC, and allow the customer to see by product the quantity in cases plus singles, split between frozen and unfrozen, DP and UB and also include details of allocated and on order quantities (if possible). Whether the stock gives a total across all sites including in transit or is broken down by site is flexible. Whichever is simplest to design. For stock in transit, if the stock is broken down by site then it should treated as at the destination site Details published on the wiki but shared selectively with users requiring this: https://visionsoftware.atlassian.net/wiki/spaces/VEDI/pages/318930945/8.+Multi+Site+-+Product+Stock | RFC-452 | Yes | Yes |
| VEDI-677 | API - Internal Orders Information | New Feature | 3.6.0 | API | Internal use API which will provide details of Orders Requested can be either - All orders currently outstanding - Specific Orders Those outstanding would be defined as Delivery Outstanding or Warehose outstanding. | RFC-393 | Yes | Yes |
| VEDI-707 | Outbound files - XML whitespace | Issue | 3.7.0 | Files outgoing | The XML outputs can be too big too email in some cases, a large portion of this is unnecessary whitespace (aesthetic spaces and carriage returns to read the XML easier). These will now be removed as these are unnecessary to programmatically read and process the files. | No | No | |
| VEDI-700 | Delivery status API - Redeliveries | Issue | 3.6.4 | API | When a delivery fails and is being redelivered, the delivery status returned by the API does not make sense to the customer. | VC-1619, VDIST-988 | No | No |
| VEDI-696 | Incoming sales order - history - failure to save | Issue | 3.6.3 | Files incoming | When an order attempts to save into VW, and it fails for an unknown reason, a notification is sent and the order moves to the validation failures screen, however no entry is logged into the history to say it failed. | No | No | |
| VEDI-695 | Inbound file notification - failing orders | Issue | 3.6.3 | Files incoming | The system is handling some notifications incorrectly, some (relating to internal issues such as deadlocks, timeouts, etc) are being sent to customers which should not be. | No | No |
| Version | 3.6.4 |
|---|---|
| Release Date | 17/10/2018 |
| Other Application Requirements | Vision Warehousing v5.1.0+ Vision Bond v4.2.0+ |
| Warnings or Notices | None |
| UID | Summary | Issue Type | Affects Version/s | Component/s | Description | Linked to | Configuration changes | License required |
|---|---|---|---|---|---|---|---|---|
| VEDI-689 | POD API - POD unavailable | Bug | 3.6.3 | API | When the POD is unavailable the API incorrectly returns: "Delivery found and images successfully prepared" | No | No | |
| VEDI-673 | API - OrderStatusByDocRef - Invalid parameters | Issue | 3.6.0 | API | The service is always returning "Invalid parameters specified for the requested API" even when the correct parameters are specified by the calling application. | No | No | |
| VEDI-686 | VCIS order import - intermittently emailing support team | Bug | 3.6.2 | Files incoming | The service which imports orders from VCIS into VEDI is intermittently emailing the support team reporting a functional issue which does not affect the order. | VSUP-7662 | No | No |
| VEDI-680 | Incoming pre advice - pickup address | Bug | 3.6.3 | Files incoming | When there are some address lines populated and others not for a pickup request, the blank lines are being populated from the customer / site's address, making the complete address invalid. | VSUP-7301 | No | No |
| VEDI-678 | Incoming orders - Splitting / missing lines | Bug | 3.6.2 | Files incoming | Sometimes lines were going missing when an order was split on submission or re-submission. | VSUP-7402, VSUP-7163 | No | No |
| VEDI-666 | Incoming orders - connection to Vision Distribution | Bug | 3.6.0 | Files incoming | If the customer does not have Vision Distribution, Vision EDI fails importing order records. | No | No | |
| VEDI-515 | Incoming orders - Mandatory fields | Issue | 3.4.0 | Files incoming | Some fields are 'mandatory' on the EDI specification but EDI has no validation to ensure these are populated. | No | No | |
| VEDI-699 | Stock frozen audit - ordering the output | Design Change | 3.6.3 | Files outgoing | The output must be in chronological order. | No | No | |
| VEDI-698 | POC extract - resending the same records | Bug | 3.6.3 | Files outgoing | The POC extract is sending the same records repeatedly each time the report is run. | VCC-584 | No | No |
| VEDI-693 | Transport management report - not generating | Bug | 3.6.2 | Files outgoing | When the Monthly Transport Management reports are scheduled to generate they were not running correctly. The EDI service was producing an error visible in the log table. | VSUP-7652 | No | No |
| VEDI-671 | Excise and VAT summary - zero value CCT | Issue | 3.6.1 | Files outgoing | If a customs duty transaction has been calculated with a 0 CCT amount then it is not showing on the Excise and VAT summary. | VB-830 | No | No |
| VEDI-688 | Incoming orders - changes for VW v5.1.0 | Issue | 3.6.3 | General | The stock availability checks for ordering and picking has changed in VW-3393 and requires changes to dependencies in Vision EDI. | No | No | |
| VEDI-668 | Inwards approval - file receipt email | Bug | 3.6.2 | General | The system is allowing standard users to create inwards approval entries and this has resulted in duplicated entries which has caused issues when sending the file receipt email as there's conflicting information held in the system for the same customer code. Changes made to no longer allow users to create new inwards approval entries, these will be created by Ontech following successful EDI integration testing for the customer. | VSUP-6631 | No | No |
| Version | 3.6.3 |
|---|---|
| Release Date | 01/06/2018 |
| Other Application Requirements | Vision Warehousing v5.0.13 Vision CIS v3.6.0 |
| Warnings or Notices |
Bug Fix - Type M orders were not saving correctly.
| Version | 3.6.2 |
|---|---|
| Release Date | 31/05/2018 |
| Other Application Requirements | Vision Warehousing v5.0.13 Vision CIS v3.6.0 |
| Warnings or Notices | also contains some notes from 3.6.1 which was not a pulic release |
| UID | Summary | Issue Type | Affects Version/s | Description | Config Required | License Required |
|---|---|---|---|---|---|---|
| VEDI-665 | Pre advice collection address overridden | Bug | 3.6.0 | When the PA file contains 'SupplierCode' and the supplier address information, VEDI is overwriting the user submitted address information with the supplier details held in VW. This causes a problem because in VW the supplier codes stored are not unique to the customer, as such the supplier information submitted by the user is lost, and this subsequently arrives in Vision with an incorrect collection address. | No | No |
| VEDI-661 | Stock Snapshot by Product | Bug | 3.5.9 | The Stock Snapshot by Product report includes any line marked as cancelled or deleted in its Allocated Stock calculation on the CSV and XML versions of the Report. | No | No |
| VEDI-647 | Incoming order - No quantity on lines | Bug | 3.5.9 | Various issues when sending an order with 0 quantity. | No | No |
| VEDI-664 | PO Submission Failed during validation | Bug | the field hectolitres per annum was removed from supplier which was causing an error | No | No | |
| VEDI-657 | Order Pick Confirmation | Bug | SSCC duplication | No | No | |
| VEDI-653 | POC not generating | Bug | No | No | ||
| VEDI-652 | Sales Order - Rotation No error | Bug | When an invalid rotation was being used, we received an error | No | No | |
| VEDI-650 | Excise and VAT - Summary email | Bug | The figures within the body of the email were not calculating correctly. | No | No | |
| VEDI-646 | Report : Stock Snapshot by Product | Bug | Deleted order lines were showing as allocated | No | No | |
| VEDI-631 | Timeout Errors - Notifications | Bug | Reclassified this as internal so that customers were not being told of time outs | No | No | |
| VEDI-667 | Transfer Order - No Reserve Customer | Change | 3.6.2 | When sending A Transfer Order - it is failing in EDI due to Receiving reserve customer code but the customer that we are transferring to has no reserves. | No | No |
| VEDI-655 | Upgrade EDI with VW 5.0.13 modification | Change | 3.6.1 | VW-3462 and VW-2644 changes require an EDI upgrade with latest onion dlls. | No | No |
| VEDI-607 | Incoming order - ConsigneeCountry | Change | 1.0.7 | The consignee country is provided in the file but not filled in VW. | No | No |
| VEDI-663 | GDPR changes | Improvement | 3.6.1 | GDPR changes necessary for VW v5.0.13. | No | No |
| VEDI-669 | Goods Received file | Issue | 3.6.2 | Goods Received File not populating the SDPRef | No | No |
Version 3.6.0 (13/04/2018)
The application was made compatible with secure mail server communications for the likes of office 365
Version 3.5.9 (14/03/2018)
| UID | Summary | Issue Type | Affects Version/s | Description | Links |
|---|---|---|---|---|---|
| VEDI-643 | Report: Excise and Vat Summary email body coming through blank | Bug | 3.5.8 | If a customer is missing either Customs Duty or Excise Duty from their Excise and VAT summary then the email sent out does not have any body text. | VSUP-5762 |
| VEDI-642 | Collection confirmation report - CSV | Bug | 3.5.8 | This report is being shown as CSV available but only XML is available. | |
| VEDI-637 | Order screen - override charge band | Bug | 3.5.6 | The override charge band is not flowing through to VD because of an issue in the way VW saves this field. | VW-3690 |
| VEDI-626 | Incoming order - no lines with a quantity saved to VW | Bug | 3.5.5 | If an order file is received with a line with 0 quantity this is getting saved into VW and put on hold with reason 'DeliveryDatesUnavailableFromVD', these orders crash the order screen but should not have been accepted in in the first place. | VSUP-5583, VCC-378, VSUP-5413 |
| VEDI-619 | Incoming order - Export not put on hold | Bug | 3.5.5 | Export Orders not getting put on hold even when details are some UB info details are missing. | VSUP-5454 |
| VEDI-634 | SSCC - Order Pick Confirmation XML | Issue | 3.5.6 | The SSCC is 18 characters long and the output maximum in this field is 256 this allows only 14 pallets to be scanned. Whilst this was designed for one pallet one rotation thus one SSCC it is now being used for multiple. The XML output needs to indent the SSCC segment within the LD and then repeat this element for the number of SSCC that there are for the detail line Also within this XML output add into HD segment - Customer DP Refernence LD segment - SO Line Notes | VF-424 |
Version 3.5.8 (08/03/2018)
| UID | Summary | Issue Type | Affects Version/s | Description | Links |
|---|---|---|---|---|---|
| VEDI-641 | Order - Held unnecessarily | Bug | 3.5.7 | An order was put on hold unnecessarily and users could not take it off hold. | VW-3741 |
Version 3.5.7 (06/03/2018)
Requires VW v5.0.10+
| UID | Summary | Issue Type | Affects Version/s | Description | Links |
| VEDI-640 | Incoming orders - Validation Failure NHibernate errors | Bug | 3.5.6 | Some incoming orders are failing validation with an NHibernate error. | |
| VEDI-638 | Sales Order -> Manufacturing -> Transport Defaults | Issue | 3.5.6 | When entering a manufacturing order, certain fields used to be get defaulted (the Vehicle registration being one of them); this is no longer happening. | VW-3626, VSUP-5372 |
| VEDI-636 | Ordering - Delivery charge customer | Bug | 3.5.6 | The 'Delivery Charge Customer' & Site Code are not being set from the Customer Maintenance > Vision e-POD > Transport Master Account field like they were before. It should be set automatically for Vision EDI & Vision Warehousing orders. | VW-3691 |
| VEDI-635 | Order - Delivery Issue and Confirmation fields are not set on Order / Delivery | Bug | 3.5.6 | The EPOD notification fields (e.g.Send Delivery Confirmation, Delivery Issue Email, etc...) on an Order / Delivery are not being checked even though these fields are set for the Customer in VW. | VW-3693, VSUP-5268, VSUP-5614 |
| VEDI-633 | Delivery time window validation | Issue | 3.5.6 | Modifications to the delivery time window validation to make the existing validations less strict. | VCIS-965 |
| VEDI-632 | Sales Orders: Delivery Information not being saved correctly. | Bug | 3.5.6 | When an order has come through EDI and goes straight through to the Pick Well without being saved at any point some of the Delivery Information is not being populated correctly. | VW-3666, VSUP-5665 |
| VEDI-629 | Incoming order - Nhibernate.StaleObjectException error | Bug | 3.5.5 | Orders are intermittently falling into Validation Failures with the error below: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect) Once 'accepted' again they usually go through fine. |
Version 3.5.6 (26/02/2018)
| UID | Summary | Issue Type | Affects Version/s | Description | Links |
|---|---|---|---|---|---|
| VEDI-625 | Report: Collection confirmation not generating | Bug | 3.5.5 | The collection confirmation report is failing to generate for some customers but not others. | VSUP-5787, VSUP-5525 |
| VEDI-623 | Sales Order: IsChargeable column not being set correctly | Bug | 3.5.5 | Orders from EDI and VCIS are not setting the IsChargeable flag correctly which can result in orders being missed for Goods Out charges. | VSUP-5510 |
| VEDI-622 | Increase the column length of Doc Ref field in the SO validation failure screen. | Improvement | 3.5.5 | Can't see the doc ref fully in the validation failure screen for the SO. | |
| VEDI-621 | Incoming order - Rotation number formats | Bug | 3.5.5 | Some customers have data imported from legacy systems where the rotation number may not be /D or /0, if they don't fit this then EDI is rejecting them even though the rotation number does exist in the system. | |
| VEDI-616 | Excise & VAT Summary - Customs duty value incorrect | Bug | 3.5.5 | The customs duty value output on the Excise & VAT Summary is showing the total for each day against each transaction, not the individual transaction value. | |
| VEDI-614 | Excise & VAT Summary - Customs duty not output in the totals section | Bug | 3.5.5 | Customs duty is not being output in the second section of the document where the totals are shown beneath each order. | |
| VEDI-613 | Excise & VAT Summary - Customs duty repeating day after day | Bug | 3.5.5 | Day after day the same customs duty records are being output. | |
| VEDI-612 | Excise & VAT Summary - Merging records | Bug | 3.5.5 | If there are two records which appear identical, the system is merging them and only showing 1. | |
| VEDI-611 | Rotation Stock Report: Calculating Case Quantites incorrectly | Bug | 3.5.4 | The Rotation Stock report is calculating quantities incorrectly in some scenarios | VSUP-5663, VSUP-5375, VSUP-5179, VSUP-5214 |
| VEDI-608 | Incoming order - transfer of UB stock to DP customer | Bug | 1.0.7 | 1) The order went to validation failures but didn't explain why in the reasons at the top 2) After accepting it (after making no changes) the order disappeared and errors were logged. | VW-3560 |
| VEDI-599 | Excise & VAT Summary PDF - Values incorrect | Bug | 3.5.2 | Page 2 is correct as per the W5D - but the total amount on the rest of the pages are completely incorrect. | VSUP-5446 |
Version 3.5.5 (07/02/2018)
Version 3.5.4 (03/02/2018)
| UID | Summary | Issue Type | Affects Version/s | Fix Version/s | Description |
|---|---|---|---|---|---|
| VEDI-605 | Incoming orders - rotation line number ignored | Bug | 3.4.3 | 3.5.4 | The rotation line number on incoming order files is ignored by EDI so VW is picking different stocks to those requested by the customer. |
| VEDI-604 | Incoming orders - default site code & pay customs duty | Improvement | 3.5.3 | 3.5.4 | Site code to be defaulted if it's not sent on the incoming file, the system will default this if the customer code exists in only one site. Also pay customs duty will be ticked unless the customer specifically sends this in as false. |
| VEDI-601 | Orders - Status set incorrectly in VW | Bug | 3.5.3 | 3.5.4 | Orders in VW which have passed validation and are not on hold which are not showing in the picking screen. |
3.5.3 (01/02/2018)
| UID | Summary | Issue Type | Affects Version/s | Fix Version/s | Description | Links |
|---|---|---|---|---|---|---|
| VEDI-600 | SO - CustomerPORef | Bug | 3.5.2 | 3.5.3 | The CustomerPORef is not being saved to VW from the XML files. | |
| VEDI-599 | Excise & VAT Summary PDF - Values incorrect | Bug | 3.5.2 | 3.5.3, 3.5.6 | Page 2 is correct as per the W5D - but the total amount on the rest of the pages are completely incorrect. | VSUP-5446 |
Version 3.5.2 (31/01/2018)
| UID | Summary | Issue Type | Affects Version/s | Fix Version/s | Description | Links |
|---|---|---|---|---|---|---|
| VEDI-598 | Sales order - failed repost procedure | Change | 3.5.1 | 3.5.2 | Created a procedure to allow us to put a failed order from the tblTempSalesOrderRepost table back into Validation Failures to be manually reposted. | |
| VEDI-597 | Sales order - Pick instructions field | Bug | 3.5.1 | 3.5.2 | The pick instructions field is not being saved to VW. | |
| VEDI-596 | Order Pick Confirmation - CSV duplicating lines (PDF does not) | Bug | 3.3.4 | 3.5.2 | The CSV version of this file is duplicating lines of certain orders, whereas the PDF is not. | VSUP-4973 |
| VEDI-595 | SO - Time windows | Bug | 3.5.1 | 3.5.2 | If a SO is saved in VCIS with only one time window, it's being sent to EDI like the following example: 08:00 - 12:00 00:00 - 00:00 The 00:00 - 00:00 then causes EDI to fail validation, this second part should be omitted. |
Version 3.5.1 (23/01/2018)
| UID | Summary | Issue Type | Affects Version/s | Fix Version/s | Description |
|---|---|---|---|---|---|
| VEDI-593 | SO - Delivery Instructions | Bug | 3.5.0 | 3.5.1 | Delivery instructions are not copying over to VW from the EDI file. |
| VEDI-592 | SO - Transporter name | Bug | 3.5.0 | 3.5.1 | Transporter name appears to be mandatory for type P orders. |
| VEDI-591 | Outwards report PDFs failing | Bug | 3.5.0 | 3.5.1 | The reports do not seem to be included in the installer for the service and this is causing the problem. |
| VEDI-584 | Schedule reports | Issue | 3.5.0 | 3.5.1 | When selecting 'Realtime' the 'Select File Type' group box is pushed down and looks wrong on the screen. The 'Override Email Address' will be changed to always be visible but greyed out unless 'Realtime' is selected. |
| VEDI-578 | Schedule > Period Description > Duplicating Values | Bug | 3.5.0 | 3.5.1 | When editing an existing report schedule the Period Description drop down shows certain values multiple times. |
Version 3.5 (25/01/2018)
| Issue key | Summary | Type | Affects Version/s | Description | Linked to | Configiration Required | License Required |
|---|---|---|---|---|---|---|---|
| VEDI-420 | Excise & VAT Summary | Report | 3.4.0 | VB-152 introduced much faster methods for retrieving this information VEDI will be updated to use these newer faster methods. | VB-152 | No | No |
| VEDI-361 | Order Transaction Audit - Enhancement | Report | 3.4.0 | Add the following fields to the report Supplier code Supplier name | No | No | |
| VEDI-457 | EDI - Collection Confirmations | New Feature | NEW | Confirmation of Collections from Warehouse. The ability to generate a file on collection of goods from warehouse This core new functionality is part of VW v5 and already in Flex. There was no extract for this as part of the scope of the original project. See wiki - POC XML | RFC-194 | No | Yes |
| VEDI-421 | Incoming SO XML - Ability to supply an order by reserve code & product | New Feature | NEW | Modification to EDI File Received Add the ability to specify at order header level the reserve customer the stock must come from which runs a pre processing process in EDI which sets the rotation numbers for the lines (if enabled for the customer in EDI). | RFC-92 | No | Yes |
| VEDI-405 | EDI API - Status of Orders | New Feature | NEW | API Implementation - New Module This will allow a customer to query the status of an order by submitting the DOC_REF of the order. It will return the warehouse status of the order and the distribution status of the order. The purpose of this is to - Know the order is on the WMSsystem [Existing – New Orders] - Order has been picked / Order available for distribution manifesting (same time point) - Order pick confirmation [Existing – Order Pick Confirmation] - Order manifest finalised (confirming the delivery date from the system) [Existing – VD ePOD Summary] - ETA Information [Existing – VD ePOD Confirmation] - Revised ETA Information - POD Information [Existing – POD XML] Existing EDI XML Items are already in the plan to be placed on the API | RFC-7 | No | Yes |
| VEDI-589 | SO - Errors after import and acceptance | Issue | 3.5.0 | Only with some orders when they first appeared in Validation Failures (after reading in the order file), it showed with a "System.NullReferenceException" error, later after accepting in Validation Failures it came back with a "System.Data.SqlClient.SqlException (0x80131904): Incorrect syntax near 'S'" error. | No | No | |
| VEDI-588 | Manufacturing order - UB info prefill | Issue | 3.5.0 | Manufacturing orders are not prefilling all info in the UB Info tab. | No | No | |
| VEDI-587 | Orders disappear after passing validation | Issue | 3.5.0 | We've seen orders which have disappeared after passing validation. The order is received and processed and 'ValidationPassed' is shown in the history. Then in the log, errors are shown. The order is nowhere to be seen in VW nor in VEDI validation failures. | No | No | |
| VEDI-583 | SO - Transporter name | Issue | 3.5.0 | Transporter name should not be mandatory for UB orders this validation will be removed so the VW users can enter the transport code to pre-populate everything. | No | No | |
| VEDI-582 | Underbond Collection orders from VC | Issue | 3.5.0 | Underbond Collection orders sent from Vision Commerce are not being processed. | No | No | |
| VEDI-581 | Incorrect validation on the Sales Price | Issue | 3.4.2 | VW is only accepting Sales Prices which are whole numbers; it should allow decimals. | No | No | |
| VEDI-580 | The DespatchURL is not being copied | Issue | 3.5.0 | When a carrier label is generated from VC, the label is given as a URL. This URL must be copied over to VW to allow the carrier labels to be printed out. | No | No | |
| VEDI-579 | Excise and VAT Summary Report | Issue | 3.5.0 | The Excise and VAT Summary Report is failing to generate when it has been scheduled, however it runs ok when the report is done Real time. | No | No | |
| VEDI-572 | Validation Failure >Customer and rotation | Issue | 3.4.2 | If receiving an Invalid Customer and rotation Number combination failure, the validation failures window no longer indicates which rotation number/order line the error relates to. | No | No | |
| VEDI-568 | Validation Failure > DateTime Error | Issue | 3.5.0 | If an order fails in EDI when trying to re-submit the older will fail with a message about not being able to store a date of 2013-01-16. | No | No | |
| VEDI-573 | Validation failures for orders - available rotations | Improvement | 3.4.2 | Display a button in the order lines section of the validation failures screen which when clicked will connect to VW and show the rotations with stock available for the product code requested. | No | No | |
| VEDI-570 | VCIS to EDI Import Service - Stopping | Improvement | 3.4.1 | The service is designed to stop when an error occurs and the support team would like to stop this. | No | No | |
| VEDI-566 | Background changes for SO save diagnosis | Improvement | 3.5.0 | Background changes have been made to simplify the diagnosis of issues when saving sales orders. | No | No | |
| VEDI-565 | SO - Deferment number when unknown | Improvement | 3.4.2 | When customers do not store the deferment number, some of them send through the customer code in the deferment fields. This was an unwritten rule in the pre VW v5 version and was never an official feature, as such it was removed during the VW v5 rewrite. It will now be put back in as an official change. | No | No | |
| VEDI-553 | Message failure email wording | Improvement | 3.4.1 | Changes will be made to the wording of the email generated when a message fails processing to make it simpler for users to understand what they need to do. | No | No | |
| VEDI-535 | Schedule reports - usability | Improvement | 3.4.0 | The controls will be made wider to fit in the available options, and the drop down menus will be put into alphabetical order. | No | No | |
| VEDI-527 | SO - Transfers (receiving reserve customer) | Improvement | 3.4.0 | Type T orders where Delivery Address3 is empty this should not be a validation failure but should go into VW to be updated manually. | VEDI-465 | No | No |
| VEDI-520 | Outbound files - dependencies on Vision databases | Improvement | 3.3.3.1 | Some reports, for example the "Orders Picking Confirmation" are dependant not only on the Vision Warehousing database but also Vision Distribution & Vision Bond, yet not all customers have these systems. Similar work was done on the inbound files in VEDI-426, now we need to do the same work for the outbound files for all report types. | No | No | |
| VEDI-465 | Notifications | Improvement | 3.4.0 | When a customer is not setup for inbound files, the file is still accepted and could process but the failed message is going to the generic email address, this needs to be improved. There needs to be separation for incoming message types - SO standard - SO Web - PA standard - PA web - PA Vision to Vision (Intra Vision PO) - PC Standard - PC Web Where it is a web order then any error should be coming to the support desk to be reviewed because we write the system there should not be any errors on these orders. | YES | No | |
| VEDI-411 | EDI "Pickup" Pre-Advices | Improvement | Addition of an improvement for the EDI Pre-Advices XML message which will allow additional information to be sent with a pre-advice and applies when the pre-advice has had a request to pick up the goods to return them to the warehouse. The current message does not allow this information to be sent, changes will add the following fields. - Pickup Time Window (Save against the pickup created) - Header Notes (Delivery Instructions field) - Associated Doc_Ref number (To be displayed on the pickup note, no screens, it's there to save them manually putting "Deliver with xxxxx") - Item Notes - PDNotes - (Display on pickup note) - Item Marker - PDMarker - (which will be used to ensure the pre-advice created does not populate the product codes but only the descriptions, this is to ensure that in cases where there is a potential that the items picked up are not be the same as what is expected. | VW-2447 | No | No | |
| VEDI-406 | EDI - New DO Segment | Improvement | In VEDI-364 a new segment was added in the xml order "Delivery Options", this is solely for the transport system and receive the fields shown on the wiki https://visionsoftware.atlassian.net/wiki/display/VEDI/Sales+Order+-+XML+Format Here we will map the Delivery Service Level to a potential Delivery Charge (optional) or a uplift % on the existing costs. Only accept Delivery Service Levels if they exist, if they do not then they are to be removed. e.g. HOM (HOME) would come into here and use the HOME charge band 24 would come in and use standard charging SAT would come in and use standard charging with an uplift of say 50% AM would come in and use standard charging with an uplift of say 20% In addition the service level could over ride the default pick calculation - e.g. 48 means delivery within 2 working days of the current date, 24 means delivery next working day, SD means Same Day Delivery, SAT would force delivery on a Saturday even if the delivery day is non standard. We have to be able to derive from this code - Pick date - Specific Delivery date - Charge band - Uplift of charge | RFC-15 | No | No | |
| VEDI-422 | Incoming SO XML - AWRS Registration Number | HMRC | 3.5.0 | Due to some recent HMRC events, it will become a requirement for the warehouse to record the AWRS number and ensure it is applicable for trade orders, as such we need to add this into the HO section of the Sales Order EDI. | No | No | |
| VEDI-577 | Management Transport > Report schedule | Bug | 3.3.3 | The Management Transport report is failing to generate when it has been scheduled, however it runs ok when the report is manually scheduled. | VSUP-4618 | No | No |
| VEDI-576 | Security - user / customer code checking | Bug | 3.4.2 | All services must be checking that the authenticated user has access to the data of the customer requested. | No | No | |
| VEDI-571 | Order Type T > Validation failure for Transport Name | Bug | 3.4.2 | When sending over a Sales order Type T, it is failing on the Transport Name | No | No | |
| VEDI-550 | SO XML - DO segment failure | Bug | 3.4.1 | SO XML files are failing submission where only some ordersin a single file contain a <DO> segment. Currently some customers are working around this by inserting a blank DO segment against all orders. Within the file. | VC-1413 | No | No |
Version 3.4.2 (08/11/2017)
| UID | Summary | Issue Type | Affects Version/s | Description |
|---|---|---|---|---|
| VEDI-543 | CIS Transfer Order Error in EDI | Issue | 3.4.1 | Receiving an error when sending a CIS Transfer Order across. |
| VEDI-519 | Manufacturing order from EDI | Issue | 3.4.0 | Manufacturing order passed validation in EDI however not populating into VW. |
| VEDI-547 | Order > Customer Batch Number | Issue | 3.4.0 | In certain scenarios the customer batch number is mandatory when saving, these need to be removed so customer batch number will never be mandatory for EDI unless specifically needed- raised form VW-3234 |
| VEDI-542 | SO with Booking/CollectionDate | Issue | 3.4.1 | Unable to send an XML file over to EDI with the Booked/Collection Date receiving Failure. |
| VEDI-551 | VC Order with BOM Products | Issue | 3.4.0 | VC Order with Mixed Products/Normal Products Failure Receiving a failure when sending a VC order through with Mixed Products/Normal Products |
| VEDI-549 | VCIS/EDI Sales Order > PayCustomsDuty | Issue | 3.4.1 | The Pay Customs Duty box has been un-ticked when the order has been pulled into VW. |
| VEDI-439 | VW v5 - Order & EMCS status changes | Improvement | VW-1330 - change in the sales order status. | |
| VEDI-546 | Excise And VAT Summary-Error | Bug | 3.4.0 | Excise And VAT Summary-String or binary data would be truncated The below error occurs in EDI while testing VB-728 String or binary data would be truncated. at Vision.BusinessServices.ReportsBUS.GetDutyAndVATExtractDetails(String customerCode) at VisionEDIService.OutwardsQueueMonitor.GetReportDetails(OutwardsQueueItem outwardsQueueItem) |
| VEDI-556 | SO - Blank time and rotation elements | Bug | 3.4.0 | An EDI file with the following blank XML elements is causing an issue as we are expecting the empty field indicator to be shown, when this is not the case we have an error, so we need to accomodate sending en empty field. <EarliestTime></EarliestTime> <LatestTime></LatestTime> Causes the following error message: System.FormatException: String was not recognized as a valid DateTime. at System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles styles) at System.Convert.ToDateTime(String value, IFormatProvider provider) at System.String.System.IConvertible.ToDateTime(IFormatProvider provider) at System.Convert.ToDateTime(Object value) at Vision.Infrastructure.VEDIManager.ConvertToEDIOrder(DataSet dsSalesOrder) at Vision.Infrastructure.Data.Services.OrderPreprocessingService.ConvertDataSetToEDIOrder(DataSet dsEDISalesOrder) at Vision.Infrastructure.OrderService.SaveEDIOrder(DataSet dsEDIOrders, Int32 userId) at VisionEDIService.SalesOrderManager.SendSalesOrderForSaving(DataSet dsSalesOrders, Validate& valid) at VisionEDIService.SalesOrderManager.AwaitingSOValidationQueuePeekCompleted(Object sender, PeekCompletedEventArgs e) Also a blank XML element for rotation number <RotationNo></RotationNo> causes the following error message: 'Invalid rotation number' |
| VEDI-557 | SO Transfers - data missing | Bug | 3.4.1 | SO Transfers - data missing when posted to VW Product Setup & Receiving Lines tabs on VW are missing data when sending transfers through VEDI. |
| VEDI-555 | Stock Snapshot - negative singles | Bug | 3.4.1 | Stock Snapshot shows negative singles when frozen stock is greater If the amount of frozen stock is greater than the amount of unfrozen stock the Snapshot by Rotation report is showing negative singles. |
| VEDI-541 | Transaction Audit | Bug | 3.4.0 | This element output is incorrectly formatted <PlanDate>Sep 20 201</PlanDate> |
Version 3.4.0 (20/09/2017)
This release will only work with Vision Warehousing v5 or later.
| Issue UID | Summary | Issue Type | Description | Linked to |
|---|---|---|---|---|
| VEDI529 | Fusion without duty payment | Issue | Errors received when processing fusion files. | |
| VEDI512 | Deferment Issues - non bonded use | Issue | Deferment information validation failure for orders involving non-bonded customers | |
| VEDI508 | SO - Delivery Times should not be Mandatory | Issue | Merge VEDI-506 changes into the this release Earliest/Latest times should not be mandatory on the EDI SO files. | |
| VEDI473 | VW v5 - Ordering - "CollectionDeliveryArea" (Collection Groups) | Improvement | In VW v5 the CollectionDeliveryArea is being removed and replaced with Collection Groups, this is part of VW-2847. To finish off the work, it's necessary to make some changes to the VEDI process. To prevent this causing issues with customers already using this field in the SO EDI files, we will keep the field for EDI but it will be used slightly differently. If the value exists as a VW Collection Group then it will be used and the order will be saved as a collection, otherwise it's a delivery and it will be used in Distribution for setting the delivery area and / or charge band as it does currently. | |
| VEDI439 | VW v5 - Order & EMCS status changes | Improvement | VW-1330 - change in the sales order status. | VW-2895 |
| VEDI423 | VW v5 - Changes required to EDI | Improvement | VW-2895 | |
| VEDI537 | Transaction audit - Movement quantities | Bug | Within the STMV > MoveOut and STMV > MoveIn sections, the wrong quantities are displayed. Here we're showing the order / pre advice quantities but it should be the actual moved quantities otherwise we have a problem looking at 'Increase in production' movements and their subsequent despatches as it shows the original pre advice quantities. | |
| VEDI523 | Transaction Audit - Losses | Bug | The 'MoveOut' segment is empty for LS movements, not even the quantity is displayed. | |
| VEDI503 | Stock Snapshot By Product: Quantity wrong when picked from multiple locations | Bug | If a product has been allocated to a sales order but a rotation has not been specified and the quantity on the order is greater than a single stock record the Stock Snapshot by Product report is showing an incorrect amount of singles. | VSUP-2499 |
| VEDI501 | Pre-Advices: Being picked up twice in EDI and being processed twice | Bug | Customer has noticed that some files coming in for GoodsInwards are being duplicated this includes: Normal Pre-Advices - this is resulting in 2x Pre-Advice in VW Pickup from customer requests - being picked up twice by EDI, this is resulting in 2x Pre-Advice in VW and 2x Pickup from Customer deliveries in VD being created. | VSUP-3013 |
| VEDI500 | VCIS > EDI Service - Constraint error causing service to stop | Bug | The VCIS > EDI service was stopping every now and then due a constraint violation and had to be restarted. | VSTASK-599 |
| VEDI498 | Stock Snapshot Rotation Enhanced: Columns displaying incorrectly | Bug | On the Stock Snapshot Enhanced By Rotation the PresentTotalSinglesUnderbond and the PresentTotalSinglesDutyPaid fields are not calculating correctly. Also on the CSV the date received column is titled as 'Column1' | VSUP-2849 |
| VEDI497 | CIS to EDI Service: Order collection date | Bug | When keying an order on VCIS and choosing 'Collection From Warehouse' sites asks for a collection date/time. When the order comes over into VW however it will not have the collection time. | VSUP-2373 |
Version 3.3.2 (12/07/2017)
A bug fix release to fix a bug when using "COLL"
Version 3.3.1 (06/07/2017)
| Issue key | Summary | Issue Type | Affects Version/s | Description | Linked | Config needed | Licensed Module |
|---|---|---|---|---|---|---|---|
| VEDI-491 | Stock snapshot by product enhanced | Bug | 3.3.0 | A stock snapshot enhanced file was produced with 1033 present cases but TotalSUB and TotalSDP were 0, this shouldn't ever happen. Present Stock + Frozen stock make up these total columns, in addition we will split these out into: TotalSUBAV Total in Singles Underbond Available TotalSDPAV Total in Singles Duty Paid Available TotalSUBFZ Total in Singles Underbond Frozen TotalSDPFZ Total in Singles Duty Paid Frozen | No | No | |
| VEDI-490 | Inwards file stuck | Bug | 3.3.0 | Some files are getting stuck in the inwards folder for an unknown reason. | No | No | |
| VEDI-489 | Fusion Order: Source Customer validation | Bug | 3.2.0 | Issue was noticed with first fusion order after 3.2.0 upgrade where the validation on the source customer was not being made correctly. Customer existed in VW but was still giving error. | No | No | |
| VEDI-488 | Sales orders - Error while monitoring the low validation priority queue | Bug | 3.3.0 | While trying to monitoring the low priority queue in the VEDI service, an error is being logged. | No | No | |
Version 3.3.0 (26/06/2017)
This is an interim release to provide some customers with additional functionality.
| UID | Summary | Issue Type | Affects Version/s | Affects Version/s | Description | Linked | Config Needed | Licensed Module |
|---|---|---|---|---|---|---|---|---|
| VEDI456 | EDI - Orders Received | New Feature | New XML Output Format Added See wiki for Orders Received XML | RFC-193 | No | YES | ||
| VEDI455 | EDI - Transaction Audit | New Feature | New XML Transaction Audit format added new Transaction Audit XML format as defined on the wiki | RFC-190 | No | YES | ||
| VEDI447 | SO processing - Multi-threading | New Feature | A multi-threading technique is introduced in this version to speed up the processing of sales orders, and back end changes for VEDI-424 have also been made allowing us to prioritise sales orders for individual customers based on cut off times (front end & file receipt email changes will be done in a later version) | No | No | |||
| VEDI472 | Goods received - LD - PackType | Issue | The 'PackType' within LD section should read EMCS codes | No | No | |||
| VEDI444 | Pre-Advice - Country Code | Issue | CWC on EDI Pre-advice import is not populating with Supplier default Country Code. | No | No | |||
| VEDI458 | EDI - Stock Frozen Audit | Improvement | Additional fieldsadded to the output See wiki for new fields. | RFC-192 | No | No | ||
| VEDI454 | XML - Goods Received | Improvement | Enhancement to XML HD Segment add the following elements - Supplier Account Code <SAC> - Supplier Account Site (only for Delivery Type = TRA) <SAS> - HMRC Type Code <HMRCType> - Site Code <Site> - Supplier Doc Ref <SDocRef> - Supplier Customer DP Ref <SDPRef> DT Segment add the following - Date available as stock (current date in HD shows date arrived) <StockDate> - Date rent started <RentDate> Fields are marked in RED on the wiki format | RFC-189 | No | No | ||
| VEDI453 | EDI - Stock Snapshot | Improvement | 3.2.0 | The site code needs to be added to the outbound XML files Stocks which have no stock to be removed from the file otherwise this bloats the XML. | RFC-191 | No | No | |
| VEDI469 | EPOD: POD for Archived Delivery - Generation | Bug | 3.2.0 | When requesting a POD to be emailed, any requests made on archived deliveries are not being generated or sent to the customer. | VSUP-2436 | No | No | |
| VEDI463 | ePOD template issues | Bug | 3.2.0 | Customer has noticed the below issues when generating ePODs after 3.2.0 upgrade (related to changes made under VEDI-373) 1) - If a order line has been picked from multiple locations it is causing the generated ePOD to show duplicated lines 2) - Pallet amount is being populated in addition to the cases amount and is causing the totals to show incorrectly. 3) - If the delivery failed for any reason the failure reason isn't being displayed on the generated ePOD 4) - The delivered quantity is not being shown on the generated ePOD | VSUP-2436 | No | No | |
| VEDI440 | Purchase order - Missing information | Bug | 3.1.3 | 3.2.0 | When a customer sends in a Purchase order via EDI if the file doesn't include the brand or vintage, the purchase order created in Vision Warehousing will not include this information when the product code already exists with this information. The product description will also be missing from Vision Distribution. | No | No | |
| VEDI436 | PA with ArrangeCollection- Country | Bug | When sending in a Pre-Advice on an EDI file that contains a pickup and return from the customer the country code on the file is not going over to Distribution so the delivery is being created but will not have a country associated with it. | VSUP-1861 | No | No |
Version 3.2.0 ( 31/03/2017)
VEDI309 in this version requires changes in VW v4.5.2 and VCIS v3.4.0 to allow scheduling of reports.
| Issue key | Issue Type | Summary | Affects Version/s | Description | Issue link (VSUP) | Configuration Needed | FusionUID | Licensed Module |
|---|---|---|---|---|---|---|---|---|
| VEDI-425 | Bug | Inwards - SO - Customs Duty - EDI/VCIS | PayCustomsDuty is being unticked when order comes from VCIS/EDI Customer has keyed a Xfer order onto VCIS and has ticked the 'Pay Customs Duty' box, however when the order has been pulled into VW the box has been un-ticked. | VSUP-1293 | No | No | ||
| VEDI-410 | Bug | Inwards - SO - Batch - EDI/VCIS | 3.1.3 | Batch number not being sent across to VW on SO when included in the EDI file Batch number not being sent across to VW on SO | No | VSUP-762 | No | |
| VEDI-409 | Bug | Inwards - File Validation | It was discovered that the code is case sensitive, for example when checking things like the product code. These items fail and then require user correction to be posted into the system. | No | No | |||
| VEDI-408 | Bug | Outbound - Order picking confirmation - VAT | The 'VAT' output is the value for VAT and should be the VAT value itself. | No | No | |||
| VEDI-399 | Bug | Outbound - Excise Summary - PDF Version | Issue noticed where the PDF version of the Excise and Duty summary was only showing 4 characters BEFORE the decimal point on the VAT column under the details heading. | No | JIH-356-97536 | No | ||
| VEDI-396 | Bug | Outbound - Excise Summary - Customer on multiple sites | Excise and VAT Summary was generated for a Customer Code which exists across multiple sites, the summary includes transactions for the multiple sites and shows the details for these, however the header only shows the details for one of the sites and ignores the others. This results in the document not being correct as the details and header do not match. | No | KHR-372-48798 | No | ||
| VEDI-390 | Bug | Inbound - PO - re-post | While trying to re-post the PO order it shows the below message 1 Purchase order(s) have been resubmitted for re validation. 1 Purchase order(s) were not submitted due to changes by other another user. ...meaning the resubmission has not posted. | No | No | |||
| VEDI-389 | Bug | Inbound - SO - Field mapping | <DeliveryIssueDPCustEmailAddress> should be mapped to VW tblOrderHeader.DeliveryPointEmail address This allows the SMS gateway to operate correctly. | No | ZGA-852-40518 | No | ||
| VEDI-388 | Bug | Inbound - PO - Date entered | 3.1.3 | The PO Date is being ignored when the PO is coming from VCIS | No | No | ||
| VEDI-386 | Bug | Outbound - Stock Snapshot by Product | The csv format on the wiki has always shown fields Allocated Stock which are the last 3 on the format (AC / AS / TotalAS) but they were removed after a customer request, these have been re-instated. | No | No | |||
| VEDI-400 | Improvement | Inbound - SO - Validation | Country was not being checked. | No | No | |||
| VEDI-387 | Improvement | Client application login version check | When logging in to the application, it compares it's version number to the server version, if they do not match then the user is not allowed to log in. Version numbers are currently: x.y.z x - Incremented on a major release y - Incremented on an improvement release z - Incremented on a bug fix release With this change, version numbers will be changed to also allow the following format: x.y.z.s x - Incremented on a major release y - Incremented on an improvement release z - Incremented on a bug fix release s - Incremented on a bug fix release, where an application release is not necessary, and only simple changes to the server side are necessary. This will allow us more flexibility in issuing some server side fixes more quickly to customer systems, meaning that the customer does not always have to update their local / terminal server installations. | No | No | |||
| VEDI-383 | Improvement | Inbound - Validation - invalid characters | Customer had an issue where the VCIS > EDI service had stopped processing due to invalid characters in one of the fields. Spoke to JW who thinks there should be some sort of notification if the service stops processing. | No | XAW-715-31802 | No | ||
| VEDI-373 | Improvement | Outbound - ePOD Generation for Customer | The ePOD Delivery Confirmation is still using a very old format and many of the fields are missing. Modify and bring this up to date showing a portrait document and add into outputs of the EPOD document to customer via EDI or Distribution to include Customer PO Ref Vintage Brand Case Size Bottle Size | No | EVU-573-37046 | No | ||
| VEDI-364 | Improvement | Inbound - SO - New XML field | A new field will be introduced to the SO XML inwards file, LabelURL, allowing customers to send in a URL which returns a PDF label. This label is then printed with the despatch paperwork after pick confirmation in the warehouse system. Linked with VW-2458. and VW-2549 | No | No | |||
| VEDI-323 | Improvement | Internal Improvements | Changes need to be made to the back end of the system in preparation for more automated upgrades which are on the horizon. | No | No | |||
| VEDI-432 | Issue | Intra Vision PO report | 3.2.0 | The Intra Vision PO report is an automated report, it cannot be scheduled, currently it's visible in the schedule reports screen and it should not be so we will be removing this. | No | No | ||
| VEDI-426 | Issue | Outbound - Orders picking confirmation | Currently when generating Order Picking Confirmation files we check if movements have posted to Vision Bond, if not then we remove them from the file and send a separate email notification advising that records were removed for this reason. In some circumstances the check is flagging up movements that do not need to post to VB as not being in VB yet, for example picks which were changed to zero quantity picked prior to pick confirmation. | VB-709 | No | No | ||
| VEDI-397 | Issue | Outbound - Goods received | The receipt type is currently outputting the full receipt type description, but the wiki specification says this should be the receipt type code. Here we will change it to output the code instead. | No | No | |||
| VEDI-385 | Issue | Inbound - SO - Line number | Rotation on EDI sales order file has a line number, the corresponding stock in VW doesn't and file fails validation with unhelpful message. | No | No | |||
| VEDI-377 | Issue | Inbound - Products - Capitalisation for Product Code | We force the product codes to be capitalised but in EDI we do not enforce this policy, however lower case product codes does not look correct. We will change the EDI service to automatically make the EDI product codes upper case as the standard system would do. This applies to incoming files which pass validation, and also in validation failures screen product code area. | No | No | |||
| VEDI-309 | New Feature | Report scheduling by customer AND SITE | Currently reports are scheduled by customer code only, this change will introduce the site code as well. Existing report schedules that customers have will be automatically duplicated for all of the sites that the customer exists in. *** PLEASE NOTE THIS IMPORTANT CHANGE *** | No | No | |||
| VEDI-300 | New Feature | VEDI Web API | A new Vision EDI Web API Allowing external applications to call it over the internet for immediate responses. The first web service implemented will be a delivery status API, where callers will be able to pass in their delivery ID and the current delivery status with ETA information will be provided back. This will be followed by Stock Status Order Entry This is a licensed module, each customer using it will require a secure and unique token to be able to request the information securely. | YES | YES |
Version 3.1.3
| UID | Description |
|---|---|
| VEDI-380 | Service Memory issues |
| VEDI-379 | Empty messages - failures and dealing with them improved. |
Version 3.1.2
| UID | Description |
|---|---|
| VEDI-378 | Accepting and item from validation failures vanishes |
| VEDI-376 | Validation failures - blank messages - improvement to logging |
| VEDI-375 | Improvement for failing messages holding up the queue |
| VEDI-374 | PO not processing due to empty customer code |
Version 3.1.1
| UID | Description |
|---|---|
| VEDI-372 | Incoming SO File being rejected was not being logged |
| VEDI-371 | Memeory issue on the service not releasing resources |
| VEDI-370 | Pick Confirmation - if it failed to send it wont resend later |
| VEDI-369 | Outbound Queue - if there is an issue the queue stops and will send nothing further, it now logs the error and continues. |
| VEDI-368 | Preventing invalid report schedules from being created. |
| VEDI-367 | Error Running the stock audit report |
| VEDI-365 | Incomning CSV file rejections |
Version 3.1.0 (21/06/2016)
This would have been a bug release but we have added some new queue features to the EDI system which take this way beyond a bug fix release.
We can now control the incoming queues operational times, we will set this up for you should you want this when you go live, further changes to these schedules beyond the first month would incur an additional engineer time and a charge.
| Key | Summary | Issue Type | Affects Version/s | Fix Version/s | FusionUID | Apply License | System Config | Release Notes |
|---|---|---|---|---|---|---|---|---|
| VEDI360 | Order Pick Confirmation | Bug | 3.0.3 | 3.1.0 | RYK-351-82214 | No | No | Recent changes to the entire suite relating to delivery names missed one field in EDI, which caused order pick confirmation files not to be sent. This has been resolved. |
| VEDI359 | Error creating pickup | Bug | 3.1.0 | No | No | The following error is being logged when creating a pickup: Column, parameter, or variable #3: Cannot find data type TextDeliveryName This was due to using a virtual table instead of a real table. | ||
| VEDI358 | Outwards history not clearing | Issue | 3.1.0 | No | No | The outwards history log was not clearing with the automatic housekeeping routine, it should be reading the 'History' settings in the housekeeping screen. | ||
| VEDI357 | Vision CIS EDI Image Import Service | Issue | 3.1.0 | No | No | When the service stops, it logs to the application event log that the 'Vision Image Uploader' has stopped, which is wrong. | ||
| VEDI355 | SO processing - delays | Improvement | 3.1.0 | No | No | Currently : There is currently one 'awaiting validation' queue, where all incoming SO's, POs, Products, Tasting Notes are queued for processing. The Issue : The entries are treated on a FIFO basis, so if 100 POs arrive, and then later 1 SO arrives, there is a wait to process the 100 POs before the SO will be processed. Resolution : The Awaiting validation will be split into 4 queues (SO, Priority SO, PA, PC) Resubmissions from SO failures will be added to the Priority SO queue to be processed before the standard SO queue. The PC and PO queues can be turned off at specific times of the day in order to prioritise the Sales Order queues. *** This can only be setup by Vision Support Team - it will be setup initially for you but future changes would warrant a charge for the engineers time. | ||
| VEDI354 | Rotation Line Length | Bug | 3.0.3 | 3.1.0 | XXY-244-27951 | No | No | Rotation Line Number length needs to allow up to a 4 digit integer to be added. |
| VEDI352 | Excise and VAT Summary | Issue | 3.1.0 | NOK-869-43061 | No | No | Add a warning to the bottom of the duty and vat summary that states Due to HMRC rounding the values shown in the detail extract will not exactly match the values shown on the tax code summary. This is due to the truncation method we have to use when summarising the figures for HMRC submission. | |
| VEDI348 | Receipt of Sales Order File | Bug | 3.1.0 | No | No | The acknowledgement message sent to customers when we receive a new file is incorect, this example file contains 9 orders but the message stated 1 We have received the following file: Receipt Date : 18/05/2016 12:50:29 File Name : SO160518_124724.XXXXXX File Type : SalesOrder Contents : Headers x 1 / Lines x 57 This is only to confirm receipt of the file, it will now be placed in a queue for processing. | ||
| VEDI347 | Validation Failures - Delivery Instructions | Issue | 3.1.0 | No | No | Change the format of the fields to show one box of 120 which is the total field size. | ||
| VEDI345 | Report Scheduling | Bug | 3.0.3 | 3.1.0 | OAM-865-98489 | No | No | When saving report schedules, users are allowed to select file types which are invalid for the report selected, Vision EDI should not be allowing the users to see / select file types which are not valid for the report selected. |
| VEDI342 | Sales Orders : Priority for resubmission | Issue | 3.1.0 | UHP-908-99526 | No | No | The resubmission of orders into the processing queue currently adds those orders to the end of the queue. Customers would like the ability for resubmissions to be placed at the top of the queue as default. This will allow the resubmitted order to be picked along with the other orders which did not fail in a more timely manor. | |
| VEDI340 | Validation Failures - No reason recorded | Bug | 3.1.0 | No | No | We have noticed that sometimes users are seeing SOs fail validation with no error message shown at the top in the 'DetailLines' grid. After investigation we've found that the the service had picked the message from the queue to deal with, but the DB was unavailable for whatever reason at this time. A similar problem occurred years ago with the SOs waiting to be validated, the fix implemented has prevented this from ever happening again. Changes will be made to all other queues to make the system robust when processing messages | ||
| VEDI339 | Delivery Times - Sense Check | Bug | 3.1.0 | No | No | At present 2nd Delivery times have to start after the first delivery times. This is not sensible and is making customer enter 10:00-12:00 12:01-14:00 Instead we need to allow 10:00-12:00 and 12:00 - 14:00 The second start time should be => the first end time. In addition if the second set are 00:00 then we should wipe those out and accept them as blank fields. Neither should generate an EDI failure. | ||
| VEDI338 | Delivery Point Email Address | Bug | 3.1.0 | No | No | This field is not being populated correctly. It needs to have the email address in full entered when it is saved within Vision warehousing which is not currently happening. | ||
| VEDI337 | Notifications being removed after accepting from validation failures | Issue | 3.1.0 | No | No | Notifications should not be removed after being 'accepted' from validation failures screen. | ||
| VEDI333 | Intra vision transfers: UNSPECIFIED / UNKNOWN fields | Issue | 3.1.0 | No | No | When the DP PO Ref is not completed on the source warehouse order, the receiving warehouse can see 'UNSPECIFIED' as the CustomerPONumber. If the orders fail validation, this then incorrectly groups all 'UNSPECIFIED' orders together as one PO. Resolution : This will be changed, to have a suffix to the UNSPECIFIED data to prevent the automatic grouping. Sending Warehouse : when the source warehouse order ticks the "I don't know" for the receiving customer code, the receiving warehouse cannot tell which account the stocks should be landed in. Source warehouses usually enter the receiving account name and / or code in the delivery instructions and are encouraged to use the receiving customer code field if it's known, instead of using the delivery instructions. However if the code is unknown, the account name is used instead but the receiving warehouse cannot see this. A change will be made to the intra vision file format to send the delivery instructions and make them visible to the receiving warehouse. | ||
| VEDI332 | Stock Audit showing non physical movements | Bug | 3.1.0 | BYV-724-75164 | No | No | The stock audit report is showing virtual movements in it, when it should only be outputting physical movements. Virtual movements such as bulk excise duty payments, customs duty payments, etc. | |
| VEDI331 | History Search - Time Out | Bug | 3.0.3 | 3.1.0 | No | No | When the system is very busy we have found some customers are excessively using the history search to perform a purpose for which it was not designed. Their constant REFRESH is having an enormous effect on EDI processing which is then causing EDI timeouts for which they are then refreshing even more causing a cascade issue which can last for upto 30 minutes. EDI processing was designed for a single user monotiring a single queue, history was added to look back but not at what is currently happening. As the customer who has this issue will not take restrictive action we have done all we can to relief the situation and to reduce the issue as much as possible but we can not guarantee that this will resolve it fully as the system is being used outside of design parameters. We have suggested that existing functionality which can already perform this function is used instead. | |
| VEDI330 | Performance improvement to scheduled files retrieval | Issue | 3.1.0 | No | No | Back end performance improvement for the retrieval of report schedules. This was sometimes causing issues with scheduled overnight files not sending. | ||
| VEDI329 | Spelling / grammar correction | Issue | 3.0.3 | 3.1.0 | No | No | From VEDI-214 in v3.0.3, when the user hits 'Cancel' in the Validation Failures screen, the message will say 'Are you sure you want to cancel this ?' (there is no question mark at present); and once the item has been cancelled, the message will say '<Type> cancelled successfully' (currently it says 'canceled'). | |
| VEDI322 | Slow processes in the VCIS > VEDI order service | Issue | 3.1.0 | No | No | There was an intermittant issue with the VCIS orders coming through EDI. This was partially due to the history search incorrect use issue. During investigations we also found a newer faster method to speed up VCIS orders and this has been implemented at the same time. Overall this should make VCIS orders faster and more reliable. |
Version 3.0.3 (24/04/2016)
Pre-Requisite : Vision Warehousing v4.3 (if you have customers who do not conform to the EDI standards) or v4.2.28 for any customer using Manufacturing (Fusion or SO Type M)
| Key | Summary | Issue Type | Affects Version/s | Fix Version/s | FusionUID | Apply License | System Config Option | Description |
|---|---|---|---|---|---|---|---|---|
| VEDI321 | Pallet charging using default cases per pallet | Issue | 3.0.3 | No | No | As a part of VDIST-524 changes ,the case per pallet field value need to be passed to Vision EDI for calculating the pallet charge when processing an incoming pickup request. | ||
| VED317 | Incoming Permissions Form | Bug | 3.0.3 | No | No | Incoming permissions should be maintained by Ontech however the customer should have the ability to modify the email address and the flag "Send File Receipt Email" but they are not able to do this prior to this change. | ||
| VEDI316 | Order picking confirmation showing incorrect qty | Bug | 3.0.3 | BIA-637-93624 | No | No | Customer had an Order Picking confirmation file that went over to the end user with some of the products having a doubled up quantity. This looks to have been caused by the Products having additional Tax Codes on them which has created additional movements which have been accounted for in the Order Picking confirmation. | |
| VEDI314 | EDI orders apparently "vanishing" after resubmitting from validation failures | Issue | 3.0.3 | No | No | We have been unable to replicate this and after a thorough review of the code have identified the following improvements that are going to be made to a) help avoid this happening in future / b) help us diagnose the problem should this happen again: 1. The 'Cancel item' process will be recoded to be more robust. This process currently has a very minor flaw which could explain why we are unable to work out why orders have vanished 2. When accepting an item in validation failure, if the unique reference changes, for example an order's document ref, a product's product code, we will audit this change which will allow us to follow the history through of any reported 'vanished orders' | ||
| VEDI312 | Consistency in Field Lengths | Issue | 3.0.3 | No | No | To make best use of the system field lengths are being extended to accommodate maximum database available lengths. Customers should beware that if their print format is NOT wide enough then allowing a customer to use the maximum lengths will result in information being cut off when there is no further space on the printed form. *Sales Order XML* DPAccountRef - 30 DocRef - 30 Customer PORef - 30 ConsigneeName and Address - 50 Delivery Name and Address - 50 Fields exceeding this length on import will be truncated. *Outgoing Files* Transport Invoice Order Ref -> 30 ExciseandVAT DocRef -> 30 StockTransaction DocumentReference -> 30 DeliveryName and Address -> 50 Agent Address -> 50 Held Orders OrderReference -> 30 NewOrdersEnteredndHeld OrderReference -> 30 DeliveryName -> 50 OrdersPickedConfirmation DPAccountRef - 30 POD Order Ref ->30 DocumentRef -> 30 Delivery Name and Address -> 50 | ||
| VEDI302 | Manufacturing complete saving of the customer | Issue | 3.0.3 | No | No | There is an issue with customer reference being saved, it's using the top record found where the customer code matches, instead of using the site code specified in the file. | ||
| VEDI301 | Manufacturing orders setting 'Excise No' | Bug | 3.0.3 | No | No | Manufacturing orders are having the 'Excise No' defaulted incorrectly, with what seems like the site deferment number, when it should be the Excise Registration Number for the receiving site. |
Version 3.0.2 (02/02/2016)
| Key | Summary | Issue Type | Affects Version/s | Fix Version/s | FusionUID | Apply License | System Config Option | Description |
|---|---|---|---|---|---|---|---|---|
| VEDI308 | Allow 30 characters for the CustomerPORef when processing SOs | Improvement | 3.0.2 | No | No | CustomerPORef should allow 30 characters. | ||
| VEDI307 | Truncation in EDI | Bug | 2.6.0 | 3.0.2 | No | No | The system no longer truncates should a customer be sending the wrong length fields, as a temporary measure we will re-instate the truncation to allow the customers to correct their errors. This will be removed in a later version. HD4 DPAccountRef will truncate at 8 HO9 CustomerPORef will truncate at 15 HU8 ConsigneeName will truncate at 30 HO3 DeliveryInstructions willl truncate at 120 HD6 DeliveryName will truncate at 40 HD7 DeliveryAddress1 will trunacte at 50 HU9 ConsigneeAddress1 will truncate at 40 | |
| VEDI305 | Invalid Doc Refs causing EDI to stop processing | Bug | 3.0.2 | CBG-742-95430 | No | No | Customer has had files with doc refs that have either come over blank or with invalid characters in the doc ref such as an apostrophe. This has caused EDI to stop functioning twice with different error. It appears when EDI encounters a problematic Doc Ref it is getting hung up on that line/order and blocking everything behind from processing. | |
| VEDI304 | Rotations are having Line numbers removed when re-submitting | Bug | 3.0.2 | ULE-253-52425 | No | No | Customer has several files that have failed in EDI for a multitude of reasons, all of these files had some rotations on them that contained line numbers. These files were re-accepted and then failed validation again to do with invalid rotations, checking the rotations after this it can be seen that the line numbers have been removed. | |
| VEDI303 | Setting the receiving customer supplier for a fusion order | Bug | 3.0.2 | No | No | When processing a fusion order we have to check to see if the supplier exists for the receiving customer, and if not then we create it. This check is checking if a supplier account code exists which matches the customer code. However sometimes the supplier account will already be set up with a blank supplier account code, but the name matches. In this scenario, as the supplier name is unique, an error occurs when processing the fusion order. |
Version 3.0.1 (11/01/2016)
| Key | Summary | Issue Type | Affects Version/s | Fix Version/s | FusionUID | Apply License | System Config Option | Release Notes |
|---|---|---|---|---|---|---|---|---|
| VEDI297 | Speed up the history search | Issue | 3.0.1 | No | No | The history search is slow and some simple tweaks could make this a lot quicker for users. | ||
| VEDI296 | Move files with no name or no extension to failed queue | Issue | 2.6.2 | 3.0.1 | No | No | If a file is dropped into the EDI Inwards folder that either has '(no name)' or has no extension it should be moved to failed queue as an invalid file format. | |
| VEDI295 | 'Mode of transport' not populating correctly and additional Transport fields needs to populate. | Issue | 2.3.2 | 3.0.1 | No | No | In VEDI-273 & VEDI-285 we've made changes to populate transport fields when transport code is populated in the SO file but in VW-1798 we noticed that 'Mode of transport' is not populating correctly. Also we need to populate following fields when transport code is supplied in the file. VAT number, Excise ID, Guarantee no, Guarantee date | |
| VEDI292 | Validation of EarliestTime/LatestTime not failing SO Files | Bug | 2.6.2, 3.0.0 | 3.0.1 | IFH-417-58944 | No | No | Noticed on customer Live, an SO was inserted into VW via an EDI file that came over. On this EDI file an EarliestTime was supplied however a LatestTime was not, the validation does not look to be working as per the EDI Spec on the wiki as this file had a <HO5> entry but a blank <HO6> entry. |
| VEDI291 | Ampersand '&' in GdsRcvd XML <Notes> or <Supplier> fields causes issue in data | Bug | 2.6.2 | 3.0.1 | No | No | 'amp;' is repeated many times after an '&' is encountered (which then makes the field too long to be processed by external applications/breaks the EDI Outgoing XML spec. XML file generation needs to deal with an ampersand in the field correctly. | |
| VEDI290 | Supplier validation giving misleading failure messages | Bug | 3.0.1 | No | No | When a pre advice file is sent in, missing the Supplier Address Line 1, the screen is giving nonsense error messages back, instead of simply saying that Supplier Address Line 1 is a mandatory field. | ||
| VEDI289 | RotationNumbers longer than 10 characters cause PODExtract Report to fail | Bug | 3.0.1 | JDE-621-53495 | No | No | Rotation Numbers greater than 10 characters cause the POD Extract Report to fail. Need to increase the field length in the report to 20 characters to avoid issues on the rare occasions when the Rotation Number is greater than 10 characters. | |
| VEDI288 | EDI application status screen | Issue | 3.0.1 | No | No | The screen is erroring when opening, it does not appear to be checking the service status' correctly, or is encountering a problem when doing so. | ||
| VEDI287 | License for intra vision PO | Issue | 3.0.1 | No | No | This is now a licensable feature as originally intended. |
Version 3.0.0 (28/09/2015)
The introduction of the Vision to Vision transfer module, sending stock from one bonded warehouse customer to another.
| Key | Summary | Issue Type | Affects Version/s | Fix Version/s | FusionUID | Apply License | System Config | Release Notes |
|---|---|---|---|---|---|---|---|---|
| VEDI285 | Default transport code for Manufacturing orders | Improvement | 3.0.0 | No | No | When processing a manufacturing SO XML file, if the transport code is not supplied, we will use the default now stored in the configuration table. | ||
| VEDI284 | Fusion deferment validation | Issue | 3.0.0 | No | No | We made Fusion order deferment requirements consistent with the main VW requirements which are to use the account field | ||
| VEDI283 | XML PO reference showing incorrectly in notification search | Issue | 3.0.0 | No | No | The PO ref is having ?0 appended to the end when displaying in the notification search screen. | ||
| VEDI282 | New XML output file for frozen stocks | Improvement | 3.0.0 | Yes | No | New Optional Output - This new output XML file will output customer / site / product / rotation / frozen quantity information for stocks which have been frozen, had their frozen quantity adjusted, or which have been unfrozen, requires VW-1806 changes to function. See: https://visionsoftware.atlassian.net/wiki/display/VEDI/Stock+Frozen+Audit for the file format. | ||
| VEDI281 | Additional field for the fusion file | Improvement | 3.0.0 | No | No | Field FH9 has been added to the file format. | ||
| VEDI278 | Validation Failure > Fusion speed | Issue | 3.0.0 | No | No | When clicking the 'Fusion' button the screen is slower to load, compared to the sales order buttonf or example. Also, when clicking on a fusion order, the egg timer flashes a few times before the fields are refreshed with the selected order's data. | ||
| VEDI273 | Under bond fields on SO XML files | Bug | 3.0.0 | No | No | It's been noticed that ConsigneeAddress4 does not get imported into VW if supplied on the XML file, nor do the Transporter fields get populated when only the TransportCode is sent in. | ||
| VEDI229 | Incoming - Ability to control if file received acknowledgement email is sent or not | Improvement | 3.0.0 | No | No | When a file is received into EDI and passes the file level validation checks we email the customer to say it was successfully received and will be processed. We want to control if this email is sent or not as some customers will sent order every 2 minutes and we do not want to bombard them with emails. | ||
| VEDI227 | Validation Failures - Screen not maximising to fill app window | Improvement | 2.6.1 | 3.0.0 | POD-653-41947 | No | No | On opening Validation Failures the screen doesn't maximise to fill app window. If you open another screen (or resize the app window) afterwards it then maximises correctly. |
| VEDI206 | PO - Phase 2: RECEIPT OF FILE - Import enhanced fields from 'Intra Vision PO' file to allow Vision customers to benefit from electronic movement data | New Feature | 3.0.0 | Yes | No | Following on from VEDI-205, we will use the fields which enhance the existing basic PO fields to link Vision systems more closely. 1) Have the 'Intra Vision PO' to create files named VPO 2) Enhance the inwards process for importing XML POs a. The service will need to recognise that VPO... and PO....in the start of the file name both represent a PO b. If the start of the filename is VPO AND the XML contains the special Vision Identifier, then we will import additional fields held sent in the Intra Vision PO file which are not available in the standard PO file | ||
| VEDI205 | PO - Phase 1: GENERATION Extract 'Intra Vision PO' file to allow Vision customers to benefit from electronic movement data | New Feature | 3.0.0 | Yes | No | Introduction of Intra-Vision Purchase Orders - This allows information to be send from Vision to Vision Customer for intra bond transfers. Changes required to Vision EDI which follow on from VW-1136. Phase 1 - Auto extract of an hourly file generated from VW data, this will run a EDI process which will output the XML |
Version 2.7.0 (27/07/2015)
| Key | Summary | Issue Type | Affects Version/s | Fix Version/s | FusionUID | Apply License | System Config | Release Notes |
|---|---|---|---|---|---|---|---|---|
| VEDI272 | Login screen not defaulting username | Issue | 2.7.0 | 2.7.0 | No | No | The login screen is no longer defaulting the username in this test release. | |
| VEDI269 | Vision account licensing issues | Issue | 2.7.0 | No | No | On 1 user license systems, vision users are unable to log in if another user is logged in. | ||
| VEDI268 | EDI service moves file mid-processing causing issues with message queues | Issue | 2.6.6 | 2.7.0 | SAU-286-53338 | No | No | There have been instances where a file has been picked up by the Vision EDI service and has either moved to the archive or failed, however it seems the EDI service is still trying to do something with the file. The affected files primarily look to be Pre-Advice files. This results in the logging of a huge number of errors in the Log as well as entries in the Message Queue. To correct this the message queue has to be manually cleared down to stop the EDI service logging errors to tblLog. |
| VEDI267 | Re-submission of an order after Validation Failure removed Booked Date if present | Bug | 2.6.2, 2.6.6 | 2.7.0 | NJQ-809-86562 | No | No | When an EDI order with a Booked/Collection Date fails EDI for any reason (ie Incorrect Product) upon correcting the order and pushing through EDI, when looking at order on VW it can be seen that the Booked Date is now blank. |
| VEDI265 | Stock snapshot boolean field value corrections | Bug | 2.7.0 | No | No | The stock snapshot files are exporting boolean values as 'true' or 'false' when our wiki document explains that these should be exported as 'yes' or 'no'. | ||
| VEDI253 | Prevent the order picking confirmation from being generated if movement data has not yet been posted to VB | Issue | 2.7.0 | No | No | There can be a number of different occasions when this occurs. - An order is picked, the report is run and the order is pick confirmed after. - There is a delay in information going over to the VB tables - caused by late picking or increased number of records. - Network issues between the servers - Other processes that effect VB but not the operation of EDI The above procedure should not run if any records in stock movement do not have an updated record in VB. | ||
| VEDI252 | SSCC recording & notification | New Feature | 2.7.0 | No | No | New fields added to XML Order Pick confirmation | ||
| VEDI251 | Fusion | New Feature | 2.7.0 | No | No | New inbound format for Type F orders, see wiki for details | ||
| VEDI250 | Bulk to bottle | New Feature | 2.7.0 | No | No | New inbound format for Type M orders, see wiki for details | ||
| VEDI242 | Show the DP PO Ref on the Duty & VAT Extract (VB-402) | Improvement | 2.7.0 | No | No | There is a requirement that after VB-402 is implemented that we show the Delivery Point PO Ref on the Duty & VAT Extract PDF. This is to allow for companies like Tesco / Sainsburys to easily see their own references on the files and to save them from constantly having to ask. |
Version 2.6.6 (13/04/2014)
VEDI-264 (Fusion BGL-774-49131)
Order Pick confirmation was not setting the SENT flag correctly, so the next time it ran it would resend old information.
Now resolved.
Version 2.6.5 (27/03/2014)
| Key | Summary | Issue Type | Affects Version/s | Fix Version/s | FusionUID | Apply License | System Config | Release Notes |
|---|---|---|---|---|---|---|---|---|
| VEDI249 | Having a PALineNo with a value greater than 32767 is causing files to fail | Bug | 2.6.0, 2.6.5 | 2.6.5 | AOP-366-99100 | No | No | <PALineNo> field on incoming pre advice files was increased to accommodate 8 characters however when using a file that has a PALineNo of 123456 which is less than the max 8 characters the attached error is received. Was due to the datatype being used as being an int16 which will note accept a value higher than 32,767. |
| VEDI248 | VB - Missing Product Descriptions on Excise and VAT document | Bug | 2.6.5 | HLB-659-15295 | No | No | The product description is not showing on some rotations on the Excise and VAT document This is due to some of the fields being concatenated having a null column in a process called "Get Excise Duty for Transactions" In this instance it is the vintage column that is showing nulls so the product description is not showing | |
| VEDI247 | EDI Failed SO order with field value exceeding maximum number of allowed characters. | Bug | 2.6.5 | ZRT-326-97300 | No | No | Issue where an order in an inwards EDI xml SO file failed validation because a value in a field 'SOLineNotes' on one order within the file exceeded the maximum number of allowed characters. Replicated on test with 161 characters (max allowed 160). The following happened: - Received email below stating 'File level validation failure' and that the data would be truncated - The file was moved to the Failed\Other folder and the data was NOT truncated like the email said What now happens : The orders which were fine should've gone straight through, and the ones which were truncated should've remained in 'Validation Failures' screen waiting for the user to push through. It should not have generated a 'File Level Validation Failure' and failed the entire file. | |
| VEDI246 | Order picking confirmation showing wrong qtys | Bug | 2.6.5 | XMR-756-86815 | No | No | If an order is placed, where a rotation is picked over multiple locations and the qty picked from each location is exactly the same, the order picking confirmation PDF report from EDI does not total up the qty | |
| VEDI245 | Warehouse Despatch Advice report causing the VW database transaction log file to completely fill up when updating the sent flag | Bug | 2.6.5 | QJV-271-92084 | No | No | The SQL Logs are filling up every week night and it appears to be related to the warehousedespatchadvicereport. This is a customer specific report. | |
| VEDI243 | When the VW server goes down, any new file data received is lost | Bug | 2.6.5 | No | No | We had an instance at where the VW SQL server became unavailable. Message Queues: AwaitingValidationQueue - Messages were in here, none were lost, but the following was repeatedly logged in tblLog every second - Description: Error validating item, Details: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible........................... InwardsQueue - New files were received while the VW server was unavailable, these files were added into the InwardsQueue but then completely lost, and resulted in the following entries in tblLog - Description: Error processing an item from the Inwards Queue. Unable to add item to the Awaiting Validation Q...................... Two changes that were made: 1) When processing messages from the InwardsQueue, we now use the peek function which will ensure messages / data are never lost if there's a problem while we're processing one of them. 2) If the service finds that the SQL server is unavailable when processing messages configure a waiting time to stop it being bombarded. | ||
| VEDI238 | Sales order XML files without the DeliveryTownOrCounty field are being allowed through and should be failing validation | Bug | 2.6.2 | 2.6.5 | AZO-171-75554 | No | No | Noticed when investigating VW-1478 that EDI files that were missing information in the <DeliveryTownOrCounty> tag despite this being a mandatory field (as Per EDI Specifications) were passing Validation. Reinstated the correct format for checking. |
Version 2.6.4 (12/12/2014)
*** YOU MUST BE RUNNING Vision Warehousing v3.20 before installing this version of EDI ***
| Key | Summary | Issue Type | Affects Version/s | Fix Version/s | FusionUID | Release Notes |
|---|---|---|---|---|---|---|
| VEDI236 | XML under bond order files sent in without sales prices are being allowed straight through to the system and should be failing validation | Bug | 2.6.3 | 2.6.4 | EST-583-65167 | When a transfer order is placed via EDI, if there is no sales price or the sales price is 0.00 it should go into validation failures as this movement type requires a sales value This should only occur when the movement type requires the field to be mandatory. |
| VEDI235 | When using the EDI automatic order split feature (at X lines), if any one of the split orders fail, the entire order with ALL lines appears for editing in the validation failures window, and results in duplicate split orders being created in VW | Bug | 2.6.3 | 2.6.4 | CGR-899-94569 | Line splitting on EDI sales order files is working correctly by design and splits the order into smaller orders. However if one of the splitted orders fails validation, on the Details section at the bottom of the screen ALL of the original lines on the order are shown and you then have to correct the lines that have failed and resubmit. For example, set the splitting to occur at 2 lines, and send in an order file of 7 lines with something to force an error on the bottom line like an invalid rotation. 3 orders are created and saved in VW each with 2 lines, yet ALL 7 lines show in validation failures for the user to edit. The user corrects the last line, and the first 3 orders are saved AGAIN, and the last order is saved with 1 line as well this time. |
Version 2.6.3 (13/11/2014)
| Key | Summary | Issue Type | Affects Version/s | Fix Version/s | Apply License | System Config | FusionUID | Release Notes |
|---|---|---|---|---|---|---|---|---|
| VEDI233 | Date/Time field in history search is showing 'pm' times as 'am' and should be in 24h format | Bug | 2.6.3 | No | No | KIY-464-12678 | Customer has report an inconsistency in the EDI Application logs which display a date and time An error shown in the Notification Details window should ordinarily have an entry in the History Logs window.... the time bit of the date/time fields are not the same. In the Notification Details window->Notification Result pane (at the bottom) there is a 'Date of Notification' which uses dd/mm/yyyy hh:mm:ss. In the History Logs window, there is a 'Date of History' field which also uses dd/mm/yyyy hh:mm:ss. If the file fails validation, for example, 02/10/2014 13:17:55pm, then 'Date of Notification' shows it as '02/10/2014 13:17' and 'Date of History' shows it as '02/10/2014 01:17:55'. Seems to be in 24hr and 12hr format. In this example one might believe that the file arrived just after midnight when in fact it arrived in the afternoon. | |
| VEDI232 | Failed Validation message indicates first order in file when issue is in another order. | Bug | 2.6.0, 2.6.2 | 2.6.3 | No | No | GLH-838-57829 | When an Incoming Sales Order file with multiple orders on it fails validation for any order other than the first one. The error message indicates the first order as being the issue. All the orders apart from the first one are then processed (even if they are the ones that cause the validation failure). |
| VEDI231 | EDI files failing on re-submission if CustomerCode exists more than once on different Sites | Bug | 2.6.1 | 2.6.3 | No | No | MMA-443-12409 | When an EDI File fails for a known error (incorrect rotation or product code for example) it produces an nondescript "TERMINATED" error on re-submission if the CustomerCode exists more than once across different Sites (even though all but one of the CustomerCodes is archived). |
Version 2.6.2 (30/09/2014)
| Key | Summary | Issue Type | Affects Version/s | Fix Version/s | Apply License | System Config Option | FusionUID | Release Notes |
|---|---|---|---|---|---|---|---|---|
| VEDI230 | Pickup requests are sending the wrong pickup address through to VD and also the Document Ref is being cut short to 8 characters | Bug | 2.6.1 | 2.6.2 | No | No | CTJ-576-37485 | Pre-advice files issues were identified for Pick up requests: 1) The name and address for the pickup is incorrect, it is populating it with the customers own address not the address where the collection will take place. 2) The document reference field is being truncated to 8 characters and should be upto 30 3) Product codes appear to be making it into VD fine, but the product descriptions are all completely blank |
| VEDI228 | Collection orders that fail EDI validation are coming into VD as deliveries | Bug | 2.6.1 | 2.6.2 | No | No | LLU-990-84042 | Customer logged an issue about Collections (from warehouse) files that come in via EDI are going over to Distribution and showing up as normal deliveries. Upon investigation it was noticed that the problem was localised to COLLECTION orders that had failed in EDI, looking at these it was noticed that when a COLLECTION order fails EDI validation and is modified to correct the problem and re-submitted for validation, upon appearing in VW the OverrideChargeAreaBand field has changed |
Version 2.6.1 (18/07/2014)
| Key | Summary | Issue Type | Affects Version/s | Fix Version/s | Apply License | System Config | FusionUID | Release Notes |
|---|---|---|---|---|---|---|---|---|
| VEDI222 | Divide by zero error received for 'Pick up' pre advices with 0 SinglesPerUnit sent in by the customer | Bug | 2.6.0 | 2.6.1 | No | No | JHX-563-17648 | When a customer is not sending the SPC field the system is assuming a 0 and giving a divide by zero error, but this field is not mandatory so should not be causing the error. |
| VEDI219 | Unable to amend reports | Bug | 2.6.0 | 2.6.1 | No | No | KDH-211-23911 | Restored ability to edit existing reports. |
Version 2.6.0 (07/07/14)
| Key | Summary | Issue Type | Affects Version/s | Fix Version/s | Apply License | System Option | FusionUID | Release Notes |
|---|---|---|---|---|---|---|---|---|
| VEDI217 | PODLineNumber on XML SO file is not being saved into the VW DB | Bug | 2.6.0 | No | No | Occasionally depending on circumstances the POD Line Number was not being saved, this is used when information is send back to the customer, therefore the issue was resolved. | ||
| VEDI214 | HUF-463-73846 - Epod - Epods asking for a PIN when the PIN No field is Non-Null but Empty | Bug | 2.5.1 | 2.6.0 | No | No | HUF-463-73846 | The Pin is 4 digit numeric, some customers were sending words, if it is not 4 digit numeric it will empty the string so that this does not effect the delivery |
| VEDI213 | EDI files for pickup from customer not creating in Distribution | Bug | 2.6.0 | No | No | The creation of a pickup in distribution was not always succesful and creating an error when the pre-advice was sent marked as "COLL" The issue has now been resolved. Pickup requests will be created even if it picks up an issue on the inbound file. | ||
| VEDI212 | Import additional fields on the PO XML file | Improvement | 2.6.0 | No | No | Additional fields added to the EDI inbound file, please see wiki for the fields LO32 - LO39 | ||
| VEDI210 | VEDI-181 was completed incorrectly, a new file format should've been created instead of altering the existing stock snapshot XMLs | Bug | 2.6.0 | No | No | Outbound Stock snapshot was modified but should have been a separate output so as not to effect users of the existing snapshot. This has been corrected. | ||
| VEDI209 | Ensure PO Line number to accomodate 8 characters | New Feature | 2.6.0 | No | No | DEN-497-59297 | Increases the PO Line Number field to accommodate larger number of characters | |
| VEDI208 | Change repeat logging explaining that the email monitor service could not be checked to check if the customer actually uses it | Improvement | 2.6.0 | No | No | Improvements to logging of information to remove items not necessary. | ||
| VEDI207 | EDI - Excise and Duty | Improvement | 2.3.2, 2.4.0, 2.5.1 | 2.6.0 | No | No | WPU-846-46812 | Amend the Excise and Duty report so that the full Product Description and the Pack Size Details are displayed correctly, meaning there should be no overwriting or truncating of the product description, nor should there be blank lines in between. |
| VEDI204 | Unable to resize columns while Validation Failures screen open | Bug | 2.3.2, 2.5.1 | 2.6.0 | No | No | BJE-786-88432 | Ability to resize the columns restored |
| VEDI197 | Log and Audit - automatic cleardown | Improvement | 2.6.0 | No | No | Housekeeping option added. | ||
| VEDI196 | When incoming files fail due to fields being too long an error is logged in tblLog and the data is not saved in the DB allowing the user to correct and resend, the data vanishes | Improvement | 2.6.0 | No | No | Improvements to truncate fields if they are send inbound exceeding the maximum length. | ||
| VEDI195 | Clone Goods received report - Request to include Vintage. | Improvement | 2.6.0 | Yes | Yes | BRD-193-11312 | New Report - Goods Received enhanced which will be PDF/CSV/XML is available. | |
| VEDI191 | Housekeeping for tblEDIEmailMonitorMessage | Improvement | 2.4.0 | 2.6.0 | No | No | Housekeeping services to keep logs clear | |
| VEDI186 | Mail server authentication | Improvement | 2.6.0 | No | No | SMTP Mail server authentication added | ||
| VEDI179 | Notification Issue List | New Feature | 2.6.0 | Yes | Yes | New Report - For Ontech Use to review EDI notifications log. The report should be titled ‘Notification Issue List’ and be accessible from the Reports menu in VEDI The report should show: • Customer Code • Date Raised • Total Detail Lines • Notification Type • File Type • Reference • Line Number • Details The user should be able to run the report by choosing one of the following filters: 1. Customer Code and Date Range (up to 90 days old) 2. Date Range (up to 90 days old) The report format should be either XLS or CSV. The report should be distributed via email to an address provided by the user. |
Version 2.5.1 (10/03/2014)
| Key | Summary | Issue Type | Affects Version/s | Fix Version/s | Apply License | System Config | FusionUID | Release Notes |
| VEDI202 | Scheduled outwards files are regularly failing to send | Bug | 2.5.1 | No | No | Improvements were made when timeout messages were being received during the overnight runs whilst sending the files to the customers. | ||
| VEDI201 | Delivery category is wiped if an order fails validation and the order is then accepted | Bug | 2.4.0 | 2.5.1 | No | No | In the SO XML file there is a field 'DeliveryCategory' in the HO section. Customers use this to send 'HOME' and suchlike, it's working fine when the order does not fail validation. If it does however fail validation, and you open it up on the VEDI screen, the delivery category is not shown in any of the fields. So when the user 'accept item', it's not sent in to workflow. |
Version 2.5.0 (15/01/2014)
| Key | Summary | Issue Type | Affects Version/s | Fix Version/s | Apply License | System Config Option | FusionUID | Release Notes |
| VEDI 200 | Adhoc report details are not being retrieved | Bug | 2.4.0 | 2.5.0 | No | No | JGF-515-56814 | Fixed ad-hoc reports so that they are now sent. The issue was that no ad hoc reports (Excise & VAT Summary & Stock Loss) are being sent out |
| VEDI 199 | Changes to the wording in outgoing email message body | Improvement | 2.5.0 | No | No | In outgoing, in the message body we say: Please find attached <report name> file for detailed reports. Please change this to: Please find attached <report name> file. | ||
| VEDI 194 | Change the outbound filenames - instead of showing the customer name show the unique site code and customer code combination | Improvement | 2.5.0 | No | No | EPS-830-28358 | Change ALL outbound EDI filenames as follows. Currently we put the customer name, replace this with SiteCode_CustomerCode. VC will be updated afterwards with issue VC-257. So we must ensure that this version is live at the warehouse before VC customers can start upgrading to the version for VC-257. Also, add a new column to the reports table, to have a 'ShortName'. The filename will then take this field instead of the full report name when generating the file name being sent. out. |
Version 2.4.0
| Issue ID | Summary | Issue Type | Fix Version/s | Apply License | System Config | FusionUID | Release Notes |
| VEDI 193 | Apostrophe in 'CustomerPONumber' field for 'Goods Received' report causes error when building the XML | Bug | 2.4.0 | No | No | modified to accommodate apostrophe in any fields. | |
| VEDI 190 | Timeout when searching for history logs | Bug | 2.4.0 | No | No | new indexes added | |
| VEDI 189 | Haulier and Vehicle Registration in the SO file | Bug | 2.4.0 | No | No | Modified to work correctly as before If these are supplied without the need for them to be supplied the service reads the file and fails it in the OTHER category. If these fields are filled and not required then just accept it, it is more important to ensure they are completed when they are needed. | |
| VEDI 188 | After a server restart the EDI service no longer starts, reporting that a dependancy is missing, the service has to be reinstalled to start again | Bug | 2.4.0 | No | No | resolved | |
| VEDI 187 | EDI - Incorrect data on product Import | Bug | 2.4.0 | No | No | TRM-461-83071 | EDI product imports were rounding single sizes up, for example if single size in the XML is 0.75 it's getting saved as 1. |
| VEDI 185 | Email monitor, change the process to help prevent reprocessing the same file | Improvement | 2.4.0 | No | No | modified | |
| VEDI 184 | Code workarounds that we'd implemented for incompliant customer files need to be removed, instead we need to insist that customer files are compliant with XML rules and have the correct encoding | Bug | 2.4.0 | No | No | implemented as this was causing issues with customer who were compliant. | |
| VEDI 181 | xml stock file with receipt - based on snapshot | New Feature | 2.4.0 | No | No | TWC-786-77854 | New Report added |
| VEDI 180 | Stock Transaction Audit - Request for Vintage field | Improvement | 2.4.0 | No | No | POK-487-51523 | Vintage fields added to end of report |
| VEDI 176 | If VD thinks a scanned POD is available but EDI doesn't find one, it should log an entry to the log table | Improvement | 2.4.0 | No | No | allows auditing when there are errors. | |
| VEDI 168 | If the query to retrieve excise and vat summary fails it should not stop the other daily reports | Improvement | 2.4.0 | No | No | Modification to be made so that whenever the query to retrieve Excise and VAT Summary fails, then it will not stop any other daily reports from running | |
| VEDI 165 | Product Import - Customer level option to check for duplicates and remove from import | Improvement | 2.4.0 | No | No | Modification to add an option at Customer level, which will remove duplicate Product Codes when the Product XML file is imported. The way to correctly capture ALL duplicates is as follows: 1) Check within the file for any duplicated codes and remove them 2) Check that the code does not exist in tblEDIProduct in VW 3) Check that the code does not exist in tblProduct in VW If a duplicate is found it should be removed, and an entry logged | |
| VEDI 164 | XML Orders Pick Confirmation - add Batch field (30) to output | Improvement | 2.4.0 | No | No | Modification to add the Batch field (Stock Batch field) in to the detail section on the XML output for the Orders Picked Confirmation file. | |
| VEDI 163 | Create new exports - Goods received enhanced, Stock Snapshot by Rotation Enhanced | Improvement | 2.4.0 | No | No | JBI-655-99652 | Take the existing reports and create new reports... Goods Received -> Goods Received Enhanced Stock Snapshot by Rotation -> Stock Snapshot by Rotation Enhanced Stock Snapshot by Product -> Stock Snapshot by Product Enhanced Batch number AND brand, add this to.. - Rotation stock snapshot enhanced - Goods Received enhanced Actual packaging & reserve customer code & name - Goods Received enhanced - Rotation stock snapshot enhanced Both new reports must be available in XML and CSV format. Summarised notes... Goods Received Enhanced - will show stock single size, stock single per case, stock cases per pallet, stock vintage, reserve customer code, reserve customer name, stock packaging description, stock packaging code Stock by Rotation Enhanced - will show stock single size, stock single per case, stock cases per pallet, stock vintage, stock reserve customer code, stock reserve customer name, Stock packaging description, stock packaging code, product brand, and all quantity shown will calculate based on the rotation level record Stock by Product Enhanced - will show product single size, product single per case, product cases per pallet, product vintage, product packaging description and all values in the quantity fields will calculate number of cases/singles based on the product level record |
| VEDI 158 | Ability to Cancel in Validation Failures | New Feature | 2.4.0 | Yes | No | QCT-907-24287 | Modifications being made to give customers the ability to cancel Sales Orders within EDI and also maintain a full audit trail of this facility. |
| VEDI 149 | Inbound Files - email confirmation of receipt | New Feature | 2.4.0 | No | No | Modification to add a new option which will allow users to send a reply email to the customer on receipt of a new file. It will send the email to the email address in the EDI system for that customer. | |
| VEDI 148 | Incoming file restrictions | Improvement | 2.4.0 | No | No | Modifications to be made to incoming file restrictions. Changes will be made to the email process for inbound files to ensure that they all use the EDI email address which is set up rather than the VW Customer email address. | |
| VEDI 147 | Allow ability to specify outbound file types | Improvement | 2.4.0 | No | No | Modification to add the ability to specify which format options we wish to have switched on for report generation i.e. PDF, CSV or XML. |
Version 2.3.2
| Issue ID | Summary | Issue Type | Fix Version/s | Description | Apply License | System Config Option | FusionUID | Release Notes |
| VEDI-183 | Sales Price from order XML file is not updating the correct value in tblOrderDetail in VW ,it save with default value 0. | Bug | 2.3.2 | No | No | Part of EDI173 we stopped the error when characters were being send in the value field from causing an error but this was not working properly, we have now corrected this. All values if specified will be handled correctly and all characters will be ignored. | ||
| VEDI-182 | XML order files are being rejected when the Document Ref > 8 characters long | Bug | 2.3.2 | No | No | No accepting characters but just truncating if they exceed the field limit for the Document Ref | ||
| VEDI-178 | VW - Duplicate lines on XML Picking lists | Bug | 2.3.2 | No | No | PFQ-510-23346 | When line Icase is 0 it was sending duplicate lines on the pick confirmation report. Now resolved | |
| VEDI-175 | Excise and VAT Summary report | Bug | 2.3.2 | No | No | YWZ-880-93536 | The excise and VAT summary report is erroring for some clients, giving the error ‘String or binary data would be truncated’ The W5No and RotationLineNo need to be extended as they are getting too long. | |
| VEDI-174 | Orders failing due to Deadlocks & Timeouts show no validation failure message | Bug | 2.3.2 | No | No | Orders going through EDI are failing due to time outs and deadlocks. the orders go through when resubmitted by the user after 10 mins without changing anything on the order. also the failed orders where showing in Validation failures but were not showing any more details in the Errors section. | ||
| VEDI-173 | Order being deleted when alpha sent in numeric field - sales order value field | Bug | 2.3.2 | No | No | When a sales order is received which has alpha in the sales order price field the system records an error and then looses the order. Sales Price is a decimal field so numbers only not characters…... “NaN” |
Release 2.3.1
**Bugs
Project | Fix Version/s | IssueID | FusionUID | Summary | Release Notes |
Vision EDI | 2.3.1 | When an EDI server is restarted which does not have a default instance of SQL server installed, the service must be reinstalled to start again | |||
Vision EDI | 2.3.1 | EPOD Generation from Vision Distribution | |||
Vision EDI | 2.3.1 | PODs generating for multiple deliveries | |||
Vision EDI | 2.3.1 | Running EDI Management Warehousing reports |
Release 2.3.0
**New Feature
Project | Fix Version/s | IssueID | FusionUID | Summary | Release Notes |
Vision EDI | 2.3.0 | JOM-734-14031 | New Request Despatch File | Modification to add a new file type to EDI. Pick Dispatch File to be produced after picking has been confirmed the full delivery details. |
Release 2.2.6
**Bug
Project | Fix Version/s | IssueID | FusionUID | Summary | Release Notes |
Vision EDI | 2.2.6 | Multiline POD's only sending the first page. | |||
Vision EDI | 2.2.6 | Goods Received CSV File | |||
Vision EDI | 2.2.6 | XML Order Processed - Duplicate lines when stock picked from multiple locations | |||
Vision EDI | 2.2.6 | ePOD Production - Date/Time is missing when the ePOD is output | |||
Vision EDI | 2.2.6 | Users have somehow been able to create realtime reports | |||
Vision EDI | 2.2.6 | The EDI service does not auto create the XML folder in the outwards directory if it doesn't exist, we have to remember to do this manually | |||
Vision EDI | 2.2.6 | Noticed that when sending a 'realtime' Excise & VAT Summary report, the system did not use the 'override' email address specified |
**Improvement
Project | Fix Version/s | IssueID | FusionUID | Summary | Release Notes |
Vision EDI | 2.2.6 | Stock loss emails - reduce server load | Modifications to be made to the way that Stock Loss Reports are generated in order to help reduce the workload on the EDI server. | ||
Vision EDI | 2.2.6 | EDI report procedures linking to other DBs should be reading uncommitted transactions | Modifications to be made so that all EDI Report procedures will read uncommitted transactions. |
Release 2.2.5
** Bug
Project | Fix Version/s | IssueID | FusionUID | Summary | Release Notes |
Vision EDI | 2.2.3, 2.2.2, 2.2.5 | Pre advices edited in 'Validation Failures' are not saving changes when 'Accept Item' is clicked | |||
Vision EDI | 2.2.5 | IsCollection and IsPickup is not set correctly for sales orders where the collection delivery area is specified | |||
Vision EDI | 2.2.5 | Certain failed orders are not appearing on the Failed Validation Screen for resubmission | |||
Vision EDI | 2.2.5 | When generating a POD for an archived delivery, only one email is sent. This email does not contain enough information. | |||
Vision EDI | 2.2.5 | When saving incoming data if there's a connection issue the data is lost | |||
Vision EDI | 2.2.5 | XZQ-705-30530 | Intrastat Report - showing intra UK movements on receipts for internal transfers | ||
Vision EDI | 2.2.5 | Sales Order CSV files - Pickup = Yes - Not sending all address details to VDist | |||
Vision EDI | 2.2.5 | Held orders report is sending out orders which are not on hold! | |||
Vision EDI | 2.2.5 | Issue found whilst testing VEDI 2.2.5 - Orders going straight to validation failures, then fine when reposted from validation failures without making any changes |
** Improvement
Project | Fix Version/s | IssueID | FusionUID | Summary | Release Notes |
Vision EDI | 2.2.5 | Outwards history logging to help diagnose failures in the outwards queue monitor but also to provide more information to us and users about what the service has processed | Modifications to be made to the logged details in Outwards History in order to help diagnose failures in the Outwards Queue monitor, and also to provide more information about what the service has processed. | ||
Vision EDI | 2.2.5 | EPOD data retrieval procedure is only working when VEDI and VD is on the same server | Modifications to be made to the EPOD Data Retrieval procedure. This is currently only working when VEDI and VD are on the same server. |
Release 2.2.4
** Bug
Project | Fix Version/s | IssueID | FusionUID | Summary | Release Notes |
Vision EDI | 2.2.4 | Processing items from Validation Failures are intermittently going missing | |||
Vision EDI | 2.2.4 | Apostrophe in the XML files causes the save to DB to fail | |||
Vision EDI | 2.2.4 | CTA-220-23425 | Order submitted and held orders - reporting cancelled orders which were held | ||
Vision EDI | 2.2.4 | Add 'Filename' to tblLog and populate for inwards files |
Release 2.2.3
** Bug
* [VEDI-119] - Orders on Hold Report is only sending the order one time - it should be each time
* [VEDI-120] - SO file with apostrophe " ' " fails upload and doesn't inform the customer about an error
* [VEDI-122] - Pre advices edited in 'Validation Failures' are not saving changes when 'Accept Item' is clicked
* [VEDI-123] - Awaiting validation queue doesn't show anything in the queue when there are messages there
* [VEDI-125] - Orders from a SO file get rejected with no reason specified in the validation failures window, but when they are accepted (without making any changes) proper errors are then visible to the user
* [VEDI-127] - Duplicated Lines returned on the Goods Received Report
* [VEDI-128] - Transfers - when product description + unit description is too long - order fails
* [VEDI-131] - Product description on the Excise & VAT Summary is cutting the field short
* [VEDI-133] - SOLineNotes - tblTempSalesOrder - DetailedInstruction1 - field too small resulting in orders with SOLineNotes > 40 characters vanishing when failing validation
* [VEDI-134] - When retrieving Duty & VAT reports to generate the system is checking the wrong date field which means that sometimes (rarely) the reports are not sent
* [VEDI-135] - When '<' or '>' is sent within a field, the import fails and no notification is sent
* [VEDI-136] - prc_GetScannedEPODDetails shouldn't require @vdConnection parameter
* [VEDI-138] - Goods received report is using the product vintage and not the stock vintage
Release 2.2.2
** Bug
* [VEDI-121] - Pre Advice import if product code does not exist in the system then EDI rejects the pre advice
* [VEDI-122] - Pre advices edited in 'Validation Failures' are not saving changes when 'Accept Item' is clicked
* [VEDI-124] - Stock Snapshot By Product report is not being produced.
Release 2.2.1
** Bug
* [VEDI-126] - The service fails to upload orders to the awaiting validation queue but it still continues to move the file to the archive folder
Release 2.2.0
** Bug
* [VEDI-110] - User cannot reset their login if their username is greater than 12 characters (15 is the maximum)
* [VEDI-115] - Pre-Advice EDI Format LO Section additional fields
* [VEDI-116] - Validation pattern checks for POs
* [VEDI-117] - PO fields where the spec says "Only supply if different to the product master table"
** Improvement
* [VEDI-62] - Improve VEDI logging for incoming files to make it easier to monitor
* [VEDI-80] - From VW-214 (Goods Received PDF - Show Rotation Notes etc)
* [VEDI-108] - Validation failures screen improvements
* [VEDI-111] - Optimise the service code when calling database queries to obtain report data by removing connection information
* [VEDI-112] - Daily Excise Summary - Add summary to the email body
* [VEDI-113] - Goods Receipt PDF - Additional fields onto report
* [VEDI-118] - Stock Snapshot by Product PDF and CSV - Remove fields Duty Paid, Free Circulation etc.
** New Feature
* [VEDI-9] - XML Pickup Requests via Pre Advices
* [VEDI-79] - VW17 - Stock Inwards Non Conformance - New EDI PDF Report - Originally VW-215
* [VEDI-114] - Order Validation - add ability to remove a line from an order
Release 2.1.3
** Bug
* [VEDI-56] - Database names passed as parameters to procedures are not surrounded with square brackets
* [VEDI-59] - Orders failing validation with no reason specified
* [VEDI-60] - Deadlocked EDI orders with no failure message in Validation Failures
* [VEDI-64] - Orders failed validation not be processed due to timeout error
* [VEDI-74] - Back end reference from tblInwardsPermissonApproval to systblInwardsSubPermissionType
* [VEDI-102] - Vision EDI client config file, link to workflow Security.svc does not work for different connections to live / test environments
* [VEDI-104] - EDI E-mail monitor - Old files reappearing 5 days after they where sent in.
* [VEDI-106] - Transfer Orders failing validation without reasons being specified
* [VEDI-107] - EDI Email Messages say from 'Ontech Solutions', it should say the customers name
* [VEDI-109] - EDI stopped validating new files.
** Improvement
* [VEDI-55] - Report procedures need re-writing to minimise the number of live table queries, as some reports have many unnecessary duplicated queries.
* [VEDI-84] - Doc Ref Field Expansion - (8 - 15tbc)
* [VEDI-92] - Scanned POD sending (instead of EPOD)
* [VEDI-101] - EPOD Changes for new Android signature
* [VEDI-105] - UOM Project - Update Description on D&V
Release 2.1.2
** Bug
* [VEDI-54] - XML PO DutyStamped field is not allowing N / Y
* [VEDI-68] - Excise and VAT summary report cutting off the Value for VAT
* [VEDI-71] - Allow no product code if rotation is present on sales order file
* [VEDI-76] - Failed file formats are not checking if the email address is present in the EDI DB first - it always takes from VW
* [VEDI-103] - Reserve customer not validated
Release 2.1.1
** Bug
* [VEDI-63] - EDI Transfer Orders are setting tblSalesOrderTransferProducts.FKReserveCustomerDetail to 0, the reserve stock is not transferred into the reserve account
* [VEDI-66] - Orders failing Validation but not being saved to the Temp sales order table
* [VEDI-73] - EDI Collection home order, post code is mandatory even though in Vision Warehousing it isn't mandatory
* [VEDI-75] - Initial EDI validation on SO files
* [VEDI-77] - Orders failing validation with deferment number issues
* [VEDI-97] - Stock Snapshot By Product not calculating Stock quantities correctly
* [VEDI-98] - Validation patterns incorrect for XML fields Vision.Model\SalesOrder.cs
* [VEDI-100] - Orders stopped validation due to a order containing a ' in the address lines
Release 2.1.0
** Bug
* [VEDI-61] - Excise Duty and VAT Summary Reports - Sending Duplicate reports for Customs Duty
* [VEDI-67] - Intrastat generation from Vision Warehousing
* [VEDI-72] - Pick Group in the XML file is not saved into tblOrderHeader
* [VEDI-86] - Orders Picking Confirmation CSV showing incorrect quantities
* [VEDI-89] - Error processing attached SO CSV file
* [VEDI-93] - VEDI-85 - Not working, frozen stock calculated incorrectly
** Improvement
* [VEDI-96] - Pick Confirmation XML format
Copyright Ontech Solutions 2017-2024. All rights reserved, no part may be replicated or distributed without the express permission of the owner.