Release Notes. Infor Supplier Exchange

Transcription

1 Release Notes Infor Supplier Exchange Version October 30, 2015

2 Copyright 2015 Infor All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or related affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners. 2

3 Important Notices The material contained in this publication (including any supplementary information) constitutes and contains confidential and proprietary information of Infor. By gaining access to the attached, you acknowledge and agree that the material (including any modification, translation or adaptation of the material) and all copyright, trade secrets and all other right, title and interest therein, are the sole property of Infor and that you shall not gain right, title or interest in the material (including any modification, translation or adaptation of the material) by virtue of your review thereof other than the non-exclusive right to use the material solely in connection with and the furtherance of your license and use of software made available to your company from Infor pursuant to a separate agreement ( Purpose ). In addition, by accessing the enclosed material, you acknowledge and agree that you are required to maintain such material in strict confidence and that your use of such material is limited to the Purpose described above. Although Infor has taken due care to ensure that the material included in this publication is accurate and complete, Infor cannot warrant that the information contained in this publication is complete, does not contain typographical or other errors, or will meet your specific requirements. As such, Infor does not assume and hereby disclaims all liability, consequential or otherwise, for any loss or damage to any person or entity which is caused by or relates to errors or omissions in this publication (including any supplementary information), whether such errors or omissions result from negligence, accident or any other cause. 3

4 Publication Information Release: Infor Supplier Exchange Version Publication Date: October 30,

5 Table of contents Important Notices... 3 Publication Information... 4 Introduction... 6 Solutions... 7 Shipments... 7 Demand... 8 Gateway... 9 Alerts BOD Processing Defective Material Notice Single Sign On Export Scheduler Proposed Purchase Order User Interface Reports Purchase Orders Supplier Performance Document Management

6 Introduction This document outlines the issues resolved in the Infor Supplier Exchange version service pack. This service pack is intended for all Supplier Exchange customers. Custom code will be overwritten with this service pack. Contact customer support for further information or assistance. 6

7 Solutions Shipments Wrong unit of measure showing on shipment. Adding a part to an existing shipper could result in the part showing the wrong unit of measure. Modifications have been made to correctly pull the unit of measure from the demand type, if available, when adding a line to an existing shipper. Defect ID: /Incident ID: Wrong unit of measure showing on container label. Container labels were using the unit of measure on the part when printing, rather than from the shipment. Modifications have been made to correctly pull the unit of measure from the shipment when printing container labels. Defect ID: /Incident ID: Tare weight not updating. The container edit and add screens do not update the tare weight when changing containers when creating shippers. Modification has been made to correct problem causing the tare weight to not be recalculated on the page as changes are made. Defect ID: /Incident ID: Print Labels button does nothing using Chrome. Clicking the Print Labels button when creating shipments with the Chrome browser has no effect. Labels are not generated and no activity occurs. Modification has been made to properly submit the button on Chrome. Defect ID: /Incident ID:

8 View ASN screen missing Transportation Method. The outbound ASN created from a loaded ASN does not include the transportation method. Modifications have been made to perform proper checks for the transportation method so that it is exported if available, which will cause the value to appear on the View ASN screen as well since that is a representation of the exported ASN. Defect ID: /Incident ID: Demand Load Sheet report not printing if flex fields exist. The load sheet report will not print if flex fields are used for demand. Modifications have been made to the stylesheet generating the PDF to create valid xml if flex field data exists. Defect ID: /Incident ID: Unhandled Data Access Object Exception error adjusting CUMs. An error is returned when adjusting CUMs as a user that has supplier restrictions applied to their login. Modification has been made to the query attempting to use restriction criteria that was not available so the CUM adjustment could complete. Defect ID: /Incident ID: Schedules fail to load when PO # is missing. When loading schedules without a PO # the schedules fail to load at times. Modification has been made to properly account for schedules without a PO # so they will save properly. Defect ID: /Incident ID:

9 Gateway VDA files missing from File Status. VDA documents exporting to the supplier do not appear in the gateway s file status. Modification has been made to write the proper entry in the database for VDA type export documents so they appear as file status entries for user review. Defect ID: /Incident ID: Weight unit of measure invalid on ASN load. When an ASN loads and there is a header error, such as an invalid format for the arrival time, a proper error is not displayed and instead a Weight unit of measure invalid for each ASN line item will appear in the file status. Modification has been made to properly log validation errors for time fields as well as not display misleading measures about ASN line information since it is not checked if there are header errors. Defect ID: /Incident ID: SE count on exported 850 incorrect. The 850 exported out to suppliers for DPO and PPO could have the wrong SE count. Modifications were made to the stylesheets generating the 850 so the SE count would be correct. Defect ID: /Incident ID: Material Release exporting VDA 4905 invalid. The 4905 material release exported in VDA format was invalid due to values not being formatted correctly. Modification has been made to creatd the 4905 in a valid VDA format. Defect ID: /Incident ID: Exported 850 contains * in MSG segment. PO header and detail notes could be exported on the 850 to suppliers with an "*" in the MSG segment. 9

10 Modifications have been made to convert any "*" in the header and detail notes to a "#" in the stylesheets that generate the 850 documents. Defect ID: /Incident ID: Error processing inbound VDA 4913 (ASN). The VDA ASN 4913 could fail to load successfully. Modification has been made to allow the VDA ASNs to successfully load. Defect ID: /Incident ID: Alerts Document Management not showing subscribed. Document management alerts do not show as checked when users are subscribed to receive those alerts, which also makes it impossible to unsubscribe. Modification has been made to properly indicate when users have subscribed to document management alerts. Defect ID: /Incident ID: Purchase Order Changed alert not considering Product Group. The purchase order changed alert that is sent to users is not filtering the alert through the product group assigned by the subscribing user so the user only receives the alert for the intended parts. Modification has been made to send the part number to the alert in order for the alert processor to properly filter based on product group for a given user. Defect ID: /Incident ID: PO Change alert missing line number. When a PO BOD loads with a line item note change the alert that is ed specifies it is for a specific line number but it is missing the line number. For example it will show in the alert: Purchase Order detail note was updated for line number: # 10

11 Modification has been made to properly pass the line number to the alert so the pound (#) sign is replaced with the actual line number with the detail note change. Defect ID: /Incident ID: Supplier receiving Infor Supplier Exchange Status Notification. Supplier users receive Infor Supplier Exchange Status Notification instead of the document type specific when they ve subscribed to receive notification when documents are loaded in the Communications, Define Documents menu. Modification has been made to only send the status notification to the users set up on the Communications, Define Hosts menu if applicable so that the other users can receive the proper document specific . Defect ID: /Incident ID: , , BOD Processing File fails when max length exceeded and greater than 500 characters. When a data field has a max length validation error and the data exceeds 500 characters the proper error does not show in the file status. Modification has been made to the generic validator such that if a max length error has occurred only the first 500 characters of the value will be used so it will properly display in the file status. Defect ID: /Incident ID: PO BODs stuck at Import Transformed PO BODs get stuck in Import Transformed when a new Ship To is sent but the Ship To name already exists, even though the proper errors are being written to the file status Modification has been made to properly update the status of the file status record to Failed for this scenario. Defect ID: /Incident ID: InventoryCount BODs fail for Oracle. Inventory count BODs fail to load if Oracle is the underlying database. 11

12 Modification has been made to correct the script creating the inventory document type in Oracle to use the proper values so the BOD can be recognized. Defect ID: /Incident ID: Replacement POs setting lines to Pending. When a replacement PO BOD loads and re-opens a closed or cancelled line it sets the line to Pending instead of Open. Modification has been made to properly set the re-opened line to Open for this scenario. Defect ID: /Incident ID: , Bad quantity on Supplier Invoice BOD. The quantity on the outbound SupplierInvoice BOD can be incorrect when using decimal quantity. For example.33 becomes Modification has been made to properly handle converting decimal quantities for use in the outbound SupplierInvoice BOD. Defect ID: /Incident ID: Defective Material Notice Part missing from EMC and Alerts. Creating a DMN for a part that does not have demand for a supplier failed to create the links needed for the part to be visible in the EMC for the supplier as well as send Alerts to the supplier for the Part. Modifications have been made to create the part/supplier relationship needed for the EMC and Alert processor to identify the part as belonging to the supplier. Defect ID: /Incident ID: Printing DMN Report yielding 404, page not found error. 12

13 When clicking the generate PDF icon from the DMN Management list page the PDF fails to open and a 404, page not found error is returned instead. Modification has been made to extend the timeout so it does not instantly time out when generating the DMN Report. Defect ID: /Incident ID: Response Due Date re-defaulting after being cleared. The containment response due date and corrective response due date could default back in after being cleared when adding a disposition. Modification has been made to properly retain the value of the due date fields when dispositions are added for a new DMN. Defect ID: /Incident ID: Single Sign On Validation error if SSO user ID exceeds 30 characters. When the single sign on user ID for a user exceeds 30 characters a validation error is given and the information is not allowed to be saved. Modifications have been made to allow the single sign on user ID length to be up to 50 characters, which is what the database field allows. Defect ID: /Incident ID: Export Scheduler Documents being sent twice a day. The export scheduler is sending documents twice a day, at both the AM and PM hour, rather than only during the time specified. Modification has been made to properly handle AM versus PM for the export scheduler tasks. Defect ID: /Incident ID:

14 Edifact DELFOR invalid. The DELFOR material release exported to suppliers contained invalid segments when generated from the export scheduler. Modifications to the stylesheet that generates the XML have been applied to send valid DELFOR documents. Defect ID: /Incident ID: , Proposed Purchase Order PPO detail list could have wrong extended price. The proposed purchase order detail list on the header screen could show the wrong extended price than what the lines actually added up to. Modifications have been made to use the value from the database rather than from a faulty query that was trying to recalculate on the fly. Defect ID: ,514487/Incident ID: , Session Expired or Invalid error when clicking to generate PPO PDF. Proposed Purchase Order PDF documents are not generating when the generate PDF icon is clicked. A window opens but it returns an error stating Session Expired or Invalid. Modification has been made to the stylesheet generating the xml for the PDF to be properly formatted for printing. Defect ID: /Incident ID: PO Detail could not be found error negotiating DPO. When a customer clicks negotiate on a discrete purchase order with an unregistered supplier and proceeds to submit the negotiation a PO Detail could not be found error is returned. Modification has been made to give the customer user a message to the effect that the supplier is unregistered, therefore negotiation is not available, when attempting to negotiate a discrete purchase order with an unregistered supplier. Negotiation cannot be initiated until the supplier is registered since the supplier will not be able to log in and negotiate until after registration is complete. Defect ID: /Incident ID:

15 User Interface Unhandled Data Access Object Exception possible when using restriction groups. When more than 1000 Ship To s exist in a customer restriction group assigned to a user then the user would get an error when using filter screens that contained the Ship To field and using Oracle as a backend database. For MSSQL databases this error would occur if there were more than Modifications have been made to the data access layer to properly handle query criteria of over 1000 items. Defect ID: /Incident ID: Reports Powered By logo covering up data. The Powered By logo on PDF documents is very large and covering data. Modification has been made so the Powered By logo on PDF documents will properly appear in the lower right hand corner and at an appropriate size. Defect ID: /Incident ID: Purchase Orders Duplicate 850 documents exported. Duplicate PO EDI is being exported when proposed purchase orders are finalized. Modifications have been made to not export duplicate PO EDI data during PPO finalization. Defect ID: /Incident: Part description incorrect from M3. M3 sends the supplier part description for generic items in the actual part description, causing the part description for the generic part (e.g., TOOLING) to constantly change in the system. 15

16 Modification has been made to load the part description into the notes for PO BODs loading from M3. Defect ID: /Incident ID: Slow response using only PO # as criteria. When choosing just the PO # as criteria in the purchase order filter the system would take an abnormally long time to find the PO #. Modification has been made to correct an inefficiency where all supplier IDs were used as criteria when all suppliers were selected rather than a specific supplier. Defect ID: /Incident ID: ed PO PDF missing line status. ed PO PDF documents sent to suppliers are missing the PO line status for each line causing suppliers to not be able to identify closed or cancelled lines. Modification has been made to the stylesheet used to generate xml for the PDF to include the PO line status. Defect ID: , /Incident ID: , Purchase Order PDF does not show correct price values. Prices on outbound PO documents that were created from BODs are not showing at least two decimal places. Modifications have been made when creating the XML used for the outbound purchase order in order for the prices to have at least two decimal places. Defect ID: /Incident ID: Currency code missing on ed PDF. The currency code was not showing on DPO PDF documents mailed to users if the DPO was closing or cancelling. Modification has been made to properly set the currency for use in the outbound documents when the DPO is being closed or cancelled. 16

17 Defect ID: /Incident ID: Supplier Performance Metrics shows invalid DMN issued count. The DMNs issued per in the generated metrics is incorrect. It always shows the total number of DMNs for the time frame instead of showing the number issued per the time frame specified in the customer profile. Modification has been made to the metrics generation to properly take into account the customer profile setting so the DMN issued count will show the number of DMNs per week, for example, when the setting is set to weekly. Defect ID: /Incident ID: Document Management Viewed information not displaying. The first buyer viewed date and viewed user for a supplier uploaded document is not updating. Modification has been made to commit the update to the database when the customer reviews a supplier document for the first time. Defect ID: /Incident ID: