EDI

This section contains enhancements in Infor Financials and Supply Management.

Changed label for the Application Value field on EDI Transaction History

Program/Business class/Process affected:

EDI Transaction History

Use these steps to test the enhancement:

  1. Navigate to each of these transaction history pages and verify that the Application Value field label is Document Number:
  • EDI Data Menu > Transaction History
  • EDI Administrator Home page > History.
  • EDI Setup > Trading Partners

JT-1633350

Include N1VN segment in Purchase Order 850 mapping

A vendor was unable to return 855 transactions for orders because the 850 did not include a N1VN. This enhancement enables including a N1VN segment in an 850 Purchase Order if a Trading Partner requires one.

Program/Business class/Process affected:

  • Translate Outbound mapping Purchase Order to 850.

Requirements:

  • Enable including the N1VN segment through the CREATE_N1VN EDI Data Substitution record.

List Name: CREATE_N1VN

Your Value: <Trading Partner ID> or * (for all Trading Partners).

Partner Value: Y

  • A N1VN segment will be created with the vendor name in N102.

-N1^VN^VENDOR NAME

>The default value for N103 is “91”.

  • Use a <tpid>_N103_VENDOR_CODE data substitution record if a trading partner expects a different value.

List Name: <tpid>_N103_VENDOR_CODE

Your Value: 850

Partner Value: <value to send in N103>

  • To specify the N104 value, use a <tpid>_O_VENDOR Data Substitution record.

    Create a record for Vendor + Vendor Location if you need a value for a specific Purchasing Location. For example: Vendor = 918, Vendor Location = DGW; the "Your Value" would be "918+DGW".

List Name: <tpid>_O_VENDOR

Your Value: <vendor>+<vendor location>

Partner Value: <value to send in N104>

  • Create a record for Vendor if the value that is valid for Vendor and any Vendor Location if defined.

List Name: <tpid>_O_VENDOR

Your Value: <vendor>

Partner Value: <value to send in N104>

  • If a CREATE_N1VN is enabled but a <tpid>_O_VENDOR data substitution record does not exist, then the N1VN segment is created with just vendor name in N102.

Use this information to test the enhancement:

Process EDI 850 with this setup:

  • CREATE_N1VN = Y
  • With Vendor Lookup and Partner Value contains both the PO Vendor and Vendor Purchase From Location
  • With Vendor Lookup and Partner Value is the PO Vendor
  • Without Vendor Lookup
  • With Vendor Lookup and Partner Value contains an incorrect PO Vendor or Vendor Purchase From Location or both.
  • <tpid>_N103_VENDOR_CODE is set up

JT-1669776