Vendor Entry Group EDI Invoice Processing Report ranges and options

Ranges

There are no ranges for this report.

Options

Group Name

Specify the group name in which you want to create the new transactions. The group name must already be set up in Vendor Entry Invoice Group Setup. If you specify an invalid group name, processing is terminated. Establish a naming convention for EDI groups. You must select One Time in the Type field when you set up the EDI group in Vendor Entry Invoice Group Setup.

Update? (If ‘no’ Error Check Only)

Select Yes to process the report and create accounts payable group files

Select No to view an exception report before you update files. Generate this report in non-update mode to review the data. The report can be printed in non-update mode as many times as necessary.

Printer for Log

Specify the name of the disk file to be used for the log.

A log is a listing of the records as they were encountered during the processing. Use the log to find the point at which the system stopped processing, if there is a problem. The only information in this file is the partner identifier and the first six characters of each record (for example, the record type identifier). Click Printer Options to define printing parameters for the log.

Set Print Status for Notes?

Select Yes to print notes and comments that are printed on generated documents, and they can be maintained or deleted in Vendor Invoice Center Entry.

Note:  If you select Yes, any notes that exist are created as unsecured notes in Distribution SX.e. Any user with access to Vendor Invoice Center Entry can view unsecured notes. If you select No, they are secured, and users must have security to view them.

Allow Invoice Without Purchase Orders?

Select Yes to process invoices that do not contain associated purchase order data. These are invoices without item or ituser records in the flat file.

Select No to prevent invoices without associated purchase order data from being processed.

GL Account # to Post Discrepancies

Specify the General Ledger account number to be used to post differences between the total invoice amount and the accumulated total of purchase orders, capitalized and expensed addons.

EDI Flat File Directory

Specify the directory of the flat file you are creating so multiple users can create multiple EDI documents at the same time. This entry is appended to /usr/sps/dat2_6/.

Specify the portion of the directory name where your flat file should be created after it is appended to the standard portion of the directory name. If this field is left blank, the file will be created in /usr/sps/dat2_6/mac.

If you retain the default blank, the directory name automatically usese the directory identified in SA Company Setup.

Use EDI/PO/APSV Terms Hierarchy?

Use this option to determine the hierarchy to use for terms processing. Select Yes and the system sets the terms type, due date, discount date, and amount as follows:

If the EDI file has an EDI terms code that exists in the SA Table Code Value Setup file, the system uses that terms type.

If the EDI file has a due date, discount due date, discount amount, discount percent, or discount days, the system uses those values and those values supersede values computed from the terms type if the terms record has both.

Note:  For example, if the terms type calls for a 2% discount and there is a value in the discount amount or percent field on the terms record that is different, the system uses the EDI file amount. If there is a discount date on the EDI file record that is different from the date based on the terms type, the system uses the date from the EDI record. If there is no EDI file terms type, the system loads a terms type (and resulting due date, discount date, and amount fields) from the purchase order if available, or from the vendor record. Then, if specific dates, discount amounts, etc. exist on the EDI file, the EDI file values take priority and are used instead.

If the EDI file does not have a terms type and the POs for the invoice do not have a terms type or the invoice does not have any POs associated with it, the system uses the terms type from the Vendor Setup record.

If you leave the default of No, PO term values are not included in the hierarchy.

Note:  The due date and discount dates are loaded as described above, regardless of the setting of this option.

Inbound EDI File Name

Use this field to process multiple groups of AP invoices and then upload them into specific AP batches, rather than importing an EDI file into a single batch with the hard-coded name of edi810_i.dat. The inbound file name can be any name, as long as it is appended with the .dat file extension. It should coincide with the Group Name so that it is imported into a specific group of invoices.

If you retain the default blank, the SX.api call creates a one-time copy of this report and loads the appropriate file name, which is located in the EDI Flat File Directory.

The SX.api Vendor [Accounts Payable] Invoice Import logic writes to a unique and sequenced file named “api810_innnn.dat” where “nnnn” is sequenced from 0001-9999. If an existing file exists in the specified directory, the logic appends the file name. For example, if filename "api810_i0219.dat" or "api810_i0219.bak" exists, it then creates "api810_i0219_1.dat".

This filename is passed to Vendor Entry Group EDI Invoice Processing Report when the scheduling record is created. The directory where the files are created defaults to the EDI Output directory in SA Company Setup, but can be overridden by report option #7 in the Vendor Entry Group EDI Invoice Processing Report “@apeiapi” stored report for each company. The file name itself cannot be overridden by the user. The RDCLEAN process cleans up any of the ".bak" files 24 hours after the file is processed.

Apply Over Receipt to Last Suffix

Select Yes to assign the over-received quantity to the last available suffix.

Select No to assign the over receipt to a fake PO suffix, which requires manual correction of the over receipt.

If you have integrated with Infor Lawson Enterprise Financial Management, any time your warehouse receives more quantity than what is on the purchase order, the SyncSupplierInvoice BOD updates this information in Distribution SX.e. If you set the option, Apply Over Receipt to Last Suffix, to Yes, then, the over-received quantity is assigned to the last available suffix. Setting this option to No, assigns the over receipt to a fake PO suffix, which does not process properly. You would have to manually correct this over receipt.

Note: This option may affect your GL posting on Not for Resale items. If the option is set to Yes, then the posting is likely correct. If the option is set to No, then the posting may be incorrect.