Vendor Setup - eCommerce field descriptions

The fields are listed alphabetically within each section. Click a link to advance to that section.

Document Send Types

Payments (EDI 820)

Select a method by which to electronically send payments to the vendor.

Select one of these values:

Note: The Credit ACH and ION options are available only if the Allow AP Credit ACH option in SA Administrator Options-Vendors-Print Forms is selected.

Blank: Leave blank if the payments are not sent through EDI flat files, CenPOS, or ION BODs.
EDI: Select to send the document in the output format that is selected in the EDI Format field for Payments (EDI 820) in SA Administrator Options-Vendors-Print Formats.
Credit ACH: If you have implemented the electronic AP payment remittance feature, you can send a payment for this vendor to the bank electronically through CenPOS.. CenPOS manages the bank relationships and certifications and sends data directly to the vendor’s bank for processing of a payment. This option is best for distributors who must meet NACHA formatting requirements. CenPOS handles the NACHA formatting. The payment request generates a Sync.RemittanceAdvice BOD, and ION sends the BACS payment to the bank. If you have specified an email address, CenPOS also sends a transaction receipt.
The Sync.RemittanceAdvice BOD can be used for remittance advice. If the vendor can process an XML file with the remittance data, sending the vendor the RemittanceAdvice BOD is recommended. If you use Infor Document Management (IDM) to send the remittance advice, you can use the remittance template, created for IDM, to send a formatted remittance advice.
ION: Select to generate SyncRemittanceAdvice BODs that contain the information that is included in the EDI 820 Payment Order/Remittance Advice document. For ION transactions that use BOD-based electronic AP payment remittance, including BACS, you must select this option.

Purchase Orders (EDI 850)

Select a method by which to electronically send purchase orders to the vendor.

Select EDI to send the document in the output format that is selected in the EDI Format field for Purchase Orders in SA Administrator Options-Documents-Purchase Orders-Printing.

Select ION to generate SyncPurchaseOrder BODs.

The method by which a purchase order has been submitted to a vendor is stored on the PO Header record (POEH). The POEH is updated when the purchase order is first printed through EDI, Email, Fax, Print, or an ION BOD. It is also updated when a PO Header is sent to a supplier with whom you have a Vendor Managed Inventory (VMI) relationship and confirmed or set when a PO is received through an EDI855 in response to an outbound EDI850 or EDI852.

If a PO is submitted through EDI, VMI, or ION, it is considered electronically transmitted or received. If it is faxed, emailed, or printed, it is considered manually transmitted. This distinction is important if you are utilizing the Vendor Scorecard metric analysis to identify those transactions that are submitted electronically or not.

Note: The Document Send Types for Purchase Orders of XML is available only for custom use. Do not select XML unless you have a custom program in place that uses the data in the sxxmldoc.

Quotes

Select Fax if you send requests for quotes to this vendor using your fax machine. Quotes are not set up to print through EDI at this time. You can select whether to send the quote to the vendor or ship from.

Select E-mail to submit quotes by email. You must also set up the vendor’s email address in Vendor Setup, Vendor Ship From Setup, or Contact Manager before you can send quotes through email.

Rebates (EDI 844)

Select a method by which to electronically send rebate claims to the vendor. If Yes is selected for the Print to eCommerce Data Where Appropriate? option on the SM Rebate Report, the value in this field determines the type of output that is generated.

Select one of these values:

EDI: Select to send the document in the output format that is selected in the EDI Format field for Rebates (EDI 844) in SA Administrator Options-Vendors-Print Formats.
ION: Select to generate SXVendorRebateClaim BODs that contain the information that is included in the EDI 844 Product Transfer Account Adjustment document.
XML: Select to generate XML files.
The XML files are saved to the outbound EDI directory that is specified in SA Company Setup or the directory that is specified on the report. These XML files are not processed by Infor ION.

Each type of output contains the information that is contained in the EDI 844 Product Transfer/Account Adjustment document. ION and XML output contain additional information.

See the Infor Distribution SX.e Setup and Administration Guide for EDI.

Product Transfer/Resale (EDI 867)

Select a method by which to electronically send product transfer and resale information to the vendor. The value that you select overrides the output method that is specified on the SM Product Transfer/Resale-EDI867 Report. If you leave this field blank, the method that is specified on the report is used.

Select one of these values:

EDI: Select to send the document in the output format that is selected in the EDI Format field for Product Transfer/Resale (EDI 867) in SA Administrator Options-Vendors-Print Formats.
ION: Select to generate SXInventoryMovement BODs.
XML: Select to generate XML files.
The XML files are saved to the outbound EDI directory that is specified in SA Company Setup or the directory that is specified on the report. These XML files are not processed by Infor ION.

Each type of output contains the information that is contained in the EDI 867 Product Transfer and Resale Report document. ION and XML output contain additional information.

See the Infor Distribution SX.e Setup and Administration Guide for EDI.

Web Pages

External: Specify the address for the website that displays when you select External from the web browser.
Internal: Specify the address for the website that displays when you select Internal from the system web browser.

eCommerce Settings

EDI User 1-3

These fields are for custom EDI applications and are reported on Vendor Master List Report or Vendor Ship From Master List Report.

Invoice Advanced Version

Specify the ANSI X12 version of invoices that you use with this trading partner. This value is required if you use EDI flat files.

Purchase Order Version

Specify the ANSI X12 version of purchase orders that you use with this trading partner. This value is required if you use EDI flat files.

Trading Partner

Specify the name of the trading partner for this vendor as defined in your EDI software. This value is required if you use EDI with this vendor.

Use 852 Status

Select this option to include products without activity on EDI 852 Product Activity Data documents for the vendor. The products must meet one of these conditions:

In Product Warehouse Product Setup, one of these events occurred:
- The status was changed from Stock to Do Not Reorder.
- The order point or line point was changed.
In Product UPC Numbers Setup, any section of the UPC code for the product was changed.

If the vendor is specified in the Authorized Replenishment Path section on a warehouse product record, 852 Status Change in Product Warehouse Product Setup-Ordering is automatically selected if one of the previously mentioned conditions is met. When you run the Purchase Entry VMI Product Activity Data EDI 852 Report, products are included if 852 Status Change is selected. The flag is cleared on the warehouse product record after the report is run.

ION Process Invoice Settings

Allow Invoices Without Purchase Orders

Select this option to process invoices that do not contain associated purchase order data. If this option is not selected and an invoice does not contain a purchase order, then Vendor Invoice Center Entry records are not created and a Confirm BOD is sent back to ION with a detail of this error.

If this vendor has associated ship from records, this option from the ship from records is used.

Apply Over Receipt To Last Suffix

Select this option to assign the over-received quantity to the last available suffix. Leave this option blank to assign the over-received quantity to a fake PO suffix in Vendor Invoice Center Entry.

Group Name

Specify the group in which the vendor's invoices are processed in Vendor Invoice Center Entry. Group names are set up in Vendor Invoice Group Entry. If this field is left blank, invoices are received in the APEI810 default group.

Set Print Flag for Notes

Select this option to select the Print Note option for notes that are created when invoice header notes are include in the BOD.

Use EDI/PO/APSV Terms Hierarchy

Use this option to determine which terms to use for processing. Leave this option blank to use the terms from the Vendor Setup-General record. Select this option to use this hierarchy to determine the terms type:

The EDI term code contained in the BOD if the EDI term code is specified on a valid SA Table Code Value Setup record for a Term.
The Terms Type on the PO header record if the purchase order number is included in the BOD.
The Terms value from the Vendor Setup record.

If the EDI document includes a due date, discount due date, discount amount, discount percent, or discount days, these values supersede the values determined from the terms type if the terms record has both.

Process Purchase Order Acknowledgement Settings

Create VMI Orders as Purchase Orders: Select this option to create purchase orders (PO) instead of purchase order quotes (QU) when a purchase order is created by a PO acknowledgment or by the Purchase Entry VMI Product Activity Data EDI 852 Report.
Set Print Status for Notes/Comments: If the notes and comments from the PO acknowledgment are included on the purchase order, select this option to print the notes and comments. The Print Note option is selected for notes, and comments are created as an external comment on the purchase order.
Update Price: Select Yes to override the line item prices on the purchase order with the price in the EDI 855 PO acknowledgment. Select No to prevent the price override.

EDI Payment and Bank

Account #

This is the vendor's bank account number and determines which bank account receives the electronic payment.

Account Type

To enable BACS processing, specify whether the vendor account is a current account or a deposit account. In most cases, the vendor account is a current account.

Advance Control Number

This field is not currently used.

BACS Reference

To enable BACS processing, specify the vendor’s reference identification. This identification is user-defined, descriptive, up to 30 characters, and agreed upon between you, the vendor, and the bank software requirements. For BACS transactions that use BACS flat files, this information is displayed on the remittance and on the vendor’s bank statement. For ION transactions that use BOD-based electronic AP payment remittance, including BACS, this information is contained in the RemittanceAdvice BOD.

Bank Account Name

To enable BACS processing, specify the vendor’s bank account name.

Bank Sort Code

To enable BACS processing, specify the vendor’s sort code. The sort code is a six-digit number. It is usually formatted as three pairs of numbers, for example 12-34-56. It identifies both the bank and the branch where the account is held.

Create ACH Token

If you selected Credit ACH in the Payments field, the Create ACH Token button is available. Use this button to initiate creation of the vendor's token identification. When you are creating an ACH token using CenPOS, you input the vendor's bank data directly into CenPOS' stand-alone, secure web browser, in the CenPOS Add Card form. Then, CenPOS sends back a token, which is an alias ID for the vendor's bank data. The token is an alphanumeric ID that is generated by CenPOS. The token is tied to the vendor's bank data, which is stored on the CenPOS server. You cannot change this token ID. You can delete this token with the Delete ACH Token button.

Delete ACH Token

If you selected Credit ACH in the Payments field, and created an ACH token for this vendor, the Delete ACH Token button is available. The reasons to delete a token can vary. For example, perhaps this vendor no longer wants to be paid by Credit ACH. Or, this vendor's back account information may have changed, and you must create a new token with the new vendor bank information.

Because the vendor is required to have a token if the payment type is Credit ACH, after you delete a token, an error is displayed: A Credit ACH payment type requires an ACH token (4218). After you click OK, you must set the Payments field to blank and save the record. At this point you can create a new token if necessary.

eCommerce Type

Use this field to enable communications with this vendor through the eBuy and eSource applications. Leave the field blank if this vendor is a standard EDI vendor. Choose eBuy and EDI documents (POEPP/POEPR) are placed in the eBuy directory set up in SA Company Setup.

Electronic Remittance Email for Supplier

For ION transactions that use BOD-based electronic AP payment remittance, including BACS, specify the email of the vendor receiving the remittance advice. Use this functionality to send remittance advice automatically to the vendor. This is available for United Kingdom, United States, and Canada processing. If you use Infor Document Management (IDM) to send the remittance advice, you can use the remittance template, created for IDM, to send a formatted remittance advice. The template is available for print formats 4 and 5. Birst extracts are also available to create your own remittance. You can also reprint a payment remittance, either with IDM or Birst. For BACS transactions, this functionality replaces the BACS-related AP Print Remittance Report.

Token ID

If you are implementing the electronic AP payment remittance feature, and are sending vendor payments as Credit ACH, this field shows the vendor's token identification. The Token ID is displayed when a token ID is generated by CenPOS after you complete the process to create an ACH token. The vendor is required to have a token if the payment type is Credit ACH. The vendor can only have one token at a time.

Transit Routing #

Specify the vendor's bank transit routing number. This number is set up in CR Bank Setup and determines which bank the payment is sent to.

Type

Specify the EDI specific code to describe the method of payment. The EDI Payment Method Code must be the correct ANSI X12 standard for element 591. If this field is left blank, the Transit Routing # and Account # must be specified.

Update Ship From(s): Use this button to update the related ship from records based on this record.

EDI 845 Defaults

NET Rebate Based From

Select a default value to use when you create or update rebate records in ED Entry Contract Pricing Report if the flat file does not contain a value or the value is invalid. The default is blank. This value corresponds to the Based From required field value for a rebate calculation type Net in PD Pricing Setup.

You may not choose a default value and the flat file field may be blank. If so, the setting in SA Administrator Options-Documents-Purchase Orders-Entry Defaults is used. The Cost field is used for domestic vendors. The Foreign Cost field is used for foreign vendors. Select which cost to use as the default setting for the price of a product in Purchase Order Entry, or wherever the PO line originated. Both the last cost and replacement cost are derived from the Product Warehouse Product Setup-Costs record.

NET Rebate Down To

Select a default value to use when you create or update rebate records in ED Entry Contract Pricing Report and the flat file does not contain a value or the value is invalid. The default is blank. This value corresponds to the Based Down To required field value for a rebate calculation type of Net in PD Pricing Setup.

Percentage (%) Rebate Based On

Select a default value to use when you create or update rebate records in ED Entry Contract Pricing Report and the flat file does not contain a value or the value is invalid. The default is blank. This value corresponds to the Based On required field value for a rebate calculation type of Percent in PD Pricing Setup.