EDI

This section contains enhancements in Infor Financials and Supply Management.

Create expense invoice as basic invoice with no distributions

A customer requested to create expense invoices from 810 without including the distribution details. This enhancement disables the creation of distribution records in an 810 Invoice.

Program/Business class/Process affected:

  • Translate Inbound mapping Invoice from 810

Requirements:

Disable the creation of Distribution records through the CREATE_DISTRIBUTION EDI Data Substitution record.

  • List Name: CREATE_DISTRIBUTION
  • Your Value: N
  • Partner Value: <Trading Partner ID> or * (for all Trading Partners)

If the Partner Value is Y or there is no CREATE_DISTRIBUTION Data Substitution record that is set up, the Distribution records will be created and the details will be included.

This list shows the expectations when the CREATE_DISTRIBUTION = N is set up:

  • When a Data Substitution for DEFAULT_TAX_CODE is set up, it is expected to have a Distribution record for the Tax Code on FSM's Invoice.
  • When there is no Data Substitution set up for DEFAULT_TAX_CODE, it is expected not to have any Distribution record on FSM's invoice.

Use these steps to test the enhancement:

  1. Process EDI 810 with this setup:
    • CREATE_DISTRIBUTION = N
    • CREATE_DISTRIBUTION = Y
    • No Data Substitution record created for CREATE_DISTRIBUTION

JT-1697983

Improve content of EDIDataExchange process flow email notifications

This is an enhancement to include additional information in the email notification of success or failure in the delivered DataExchangeInbound and DataExchangeOutbound process flows used to exchange data with an EDI carrier.

Program/Business class/Process affected:

The email notifications from delivered processes contain these updates:

  • Include the process trigger name in the email subject line.
  • Change the failure notifications subject from "Failed" to "Errors" and include the Work Unit to make it easier to identify the work unit. The format is Error: <process description> - WorkUnit <workunit> - <EDI carrier name>, for example, Error: EDI Inbound - WorkUnit 153 - INFORPROD.
  • Add the WorkUnit, Work Title, and Process Name to the email content.
  • Remove the Carrier Count from the email content. This was a loop index if multiple carriers were contacted but the Carrier Name is already part of the email.
  • Move the error message to the end of the email content instead of the beginning. The process information and file counts are at the top so a recipient does not need to scroll to see that information.

The EDIDataExchange_Inbound.lpd and EDIDataExchange_Inbound_Translate.lpd contain these updates:

  • Change "File Count" to "Total Files Successfully Retrieved". This will show 0 if no files were successfully retrieved instead of "undefined."
  • Change "File List" to "Successful File List". This will be a list of the names of the files successfully retrieved. It will be empty if no files were retrieved instead of "undefined".

The EDIDataExchange_Outbound.lpd and EDIDataExchange_Outbound_Single.lpd contain these updates:

  • Removed the "Data:" field/content from the body of the email.

Use these steps to test the enhancement:

  1. Upload files to the inbound directory identified on the EDI Carrier record as the Inbound and trigger the DataExchangeInbound process to test the inbound process.
  2. Set up EDI Data Exchange records with a direction of "OUT" and a Status of "New" and trigger the DataExchangeOutbound process to test the outbound process.
  3. Test failures by specifying an invalid value on the EDI Carrier record such as Host Name or directory. Inbound failures can also be tested by uploading empty files to the Inbound directory specified on the EDI Carrier record.

JT-1685972