EDI

This section contains enhancements in Infor Financials and Supply Management.

Add additional date qualifiers for mapping acknowledgment early delivery date

There were existing qualifiers related to delivery and shipments that are supported. Adding a new qualifier to reference 068 Current Schedule Ship.

Currently supported date qualifiers:

  • 017 Estimated Delivery
  • 035 Delivered
  • 067 Current Schedule Delivery

Program/Business class/Process affected:

Added support to new date qualifier 068 Current Schedule Ship for EDI 855 Translate Inbound processing for PO Acknowledgement.

Other qualifier codes related to delivery and shipment were also added and are now supported:

  • 011 Shipped
  • 069 Promised for Delivery
  • 070 Scheduled for Delivery (After and Including)
  • 072 Promised for Delivery (After and Including)
  • 073 Scheduled for Delivery (Prior to and Including)
  • 075 Promised for Delivery (Prior to and Including)
  • 079 Promised for Shipment
  • 080 Scheduled for Shipment (After and Including)
  • 082 Promised for Shipment (After and Including)
  • 083 Scheduled for Shipment (Prior to and Including)
  • 085 Promised for Shipment (Prior to and Including)
  • 102 Issue

Screens affected:

Screens used by EDI 855 process for PO Acknowledgment

Use these steps to test the enhancement:

  1. Test a scenario with ACK03 containing the newly added date qualifiers.
  2. Process an 855 with the newly accepted Date Qualifiers. In the PO EDI Acknowledgement List, a record 70 is created and the Early Delivery Date is mapped from ACK04.

JT-1633710

Make EDIDataExchange Message Field Editable on the List View

The Message field on the EDI Data Exchange List View is not editable.

Program/Business class/Process affected:

EDI Data Exchange List

Use these steps to test the enhancement:

  1. Navigate to the Data Exchange List.
  2. Add or edit the text in the Message field. Verify that you can save the message.

JT-1664188

Use Header Requesting Company and Requesting Location for SDQ03 LOOKUP if there are no PurchaseOrderEDIOutput RequestingLocation records

SDQ03 lookup did not work for Purchase Order with manually created source record for PO Line specifying a different Operating Company than the Purchase Order Company.

Current functionality enables customers to send an SDQ segment for each line in an 850 and to specify a value to send in SDQ03 through data substitution records.

If line has a Requisition Source document, a Line Requisition (LR) record is created for each requisition line containing requesting (operating) company and requesting location.

SDQ03 lookup uses the LR requesting company and req location.

If a PO does not originate from a requisition, a customer can manually add a Line Source to a Purchase Order Line, specifying the requesting (operating) company, requesting location, requester etc. However, the Source will be Purchase Order.

When the PurchaseOrderEDIOutput records are created, the Header Requesting Company and Requesting Location are set to values from the first line source record. If there is no Requisition source records, no POEDI Output LR records are created.

Current functionality uses the Header Requesting location and Purchasing Company (not Requesting Company) for SDQ creation.

Program/Business class/Process affected:

An enhancement was made to the Purchase Order to 850 mapping. If SDQ03 lookup is enabled and there are no Line Requesting Location records, the Header Requesting Company and Requesting Location is used by the mapping. If that is not successful, the Purchasing Company and ShipTo location are used by the mapping.

Use this information to test the enhancement:

  1. GIVEN

    PurchaseOrderEDIOutputRecords exist for EDI and

    SDQ creation is enabled

    WHEN

    Performing an outbound 850 translation and

    an LR record exists for a Line

    THEN

    the LR Requesting Company and Requesting Location are used in SDQ creation.

  2. GIVEN

    PurchaseOrderEDIOutputRecord exist for EDI and

    SDQ creation is enabled

    WHEN

    there are no LR records for a Line and

    Header record Requesting Company and Requesting Location are not empty

    THEN

    Header Requesting Company and Requesting Location are used in SDQ creation.

  3. GIVEN

    PurchaseOrderEDIOutputRecord exist for EDI and

    SDQ creation is enabled

    WHEN

    there are no LR records for a Line and

    Header record Requesting Company and Requesting Location are empty

    THEN

    Header Purchasing Company and Ship To Location are used in SDQ creation.

JT-1610934