EDI

This section contains enhancements in Infor Financials and Supply Management.

Display EDI 810 REF segments on invoice screens

The EDI 810 REF segment for element L1 in which an invoice note or comment is added is not found in the invoice that is being interfaced.

Program/Business class/Process affected:

  • EDI Invoice Match Interface
  • EDI 810 process

Requirements:

Enabled mapping of the Invoice Line REF segment/ L1 element to the Comment Text of the Distribution record.

Use these steps to test the enhancement:

  1. Process EDI 810 with the added invoice note or comment on the Invoice Line REF segment.
  2. Process EDI 810 without the REF segment L1 element value.

JT-1472045

Map Ship To Account Number from PurchaseOrderEDIOutput if present

This enhancement enables using the PurchaseOrderEDIOutput Vendor Ship To Location Account field instead of using a <tpid>_O_SHIPTO Data Substitution record.

JT-1623685 Vendor Account Numbers for a Ship To Location enabled maintaining Vendor Ship To Accounts on a Purchasing Vendor. If a record exists, it is written to the Vendor Ship To Location Account on the Purchase Order EDI Output.

Program/Business class/Process affected:

Translate Outbound mapping Ship To Account number in N1ST04 for Purchase Order to 850.

Requirements:

Define the Vendor Ship To Location Account on a Purchasing Vendor.

Enable the use of the Vendor Ship To Location Account through this EDI Data Substitution record:

  • List Name: MAP_SHIPTO_ACCOUNT
  • Your Value: <trading partner id> or * for all partners.
  • Partner Value: O or B
    • O: Use the PurchaseOrderEDIOutput VendorShipto Location Account field value.
    • B: Use the PurchaseOrderEDIOutput VendorShipto Location Account field if it is populated. If not, use the <tpid>_O_SHIPTO lookup.
    • If a MAP_SHIPTO_ACCOUNT does not exist or the Partner Value is not O or B, the <tpid>_O_SHIPTO lookup is used.

Use these steps to test the enhancement:

Process EDI 850 with this setup:

  • MAP_SHIPTO_ACCOUNT = O (Only) with Vendor Ship To Location Account
  • MAP_SHIPTO_ACCOUNT = O (Only) without Vendor Ship To Location Account
  • MAP_SHIPTO_ACCOUNT = B (Both) with Vendor Ship To Location Account
  • MAP_SHIPTO_ACCOUNT = B (Both) without Vendor Ship To Location Account
  • Without Data Substitution set up MAP_SHIPTO_ACCOUNT

Dependencies:

See JT-1623685 Vendor Account Numbers for a Ship To Location for more information about defining those records.

JT-1673121

Update Delivered Inbound DataExchange flows to include processedFileCount and processedFileList in email notifications

Added File Count and File List to the email notification nodes in the EDIDataExchangeInbound process files to enable customers to know which files were retrieved and the number of files.

Program/Business class/Process affected:

The Email notification from the delivered Application Defined EDIDataExchangeInbound and EDIDataExchangeInbound_Translate process files.

The File Count lists the number of Files that were pulled from the remote FTP server.

The File List lists the names of the files that were pulled from the remote FTP server.

Use these steps to test the enhancement:

  1. Trigger an EDIDataExchangeInbound or EDIDataExchangeInbound_Translate process.
  2. Verify that the Success and Failure emaill notifications include the File Count and File List.

JT-1662237