- Acknowledgments - Print Format / EDI Format / Fax Format /
Headings / Output Type / Level 1-2 Extra Fields
-
Select 1 in the Print Format field to use the
regular National Electrical Manufacturers Association (NEMA) standard format. When
acknowledgments are printed, the standard NEMA format is applied to the output, and
order information is included. You also can specify whether the standard headings are
printed. If you are using pre-printed NEMA forms, you do not want the headings to
print.
Select
4 in the
Print Format field to produce XML
output. XML output is required for forms that are sent to Infor Reporting, Infor
Document Management, or some third-party forms printing applications. When you specify
4, you must also select an
Output Type. Format
4 with an
Output Type of
Infor
Reporting is the default format selected for all forms if you are
running
CloudSuite Distribution.
Note: The Acknowledgments Print
Format and Output
Type settings also control Quote Order (QU) printing. The Print Format and Output Type you select for
acknowledgments is also applied to quotes. For example, if your acknowledgments are
set up to use Infor Document Management (IDM) to generate forms, then Quote Orders
are also generated by IDM. You can select a different template for your quote forms.
Note: In
CloudSuite Distribution, Print Format 4 output is not generated
if the EDI Format is
5, the Send By method on the customer record is EDI, and the option, Print to EDI Where Appropriate, is selected on the report.
Select 9 in the Print Format field if you have
developed a custom print routine to print acknowledgements. The custom routine must
control whether acknowledgement headings are printed and the format in which to print
order information. If you select 9, the
utility program oeepa9.p is executed when you print
acknowledgements. Format 9 is not supported for CloudSuite Distribution.
Select the Headings option to print the headings for the document. If you are
using a pre-printed acknowledgement form, do not select this option.
-
The Output Type field is
required if you select 4 for the Print Format type.
-
Select Infor Reporting to send the
acknowledgement to the Infor Reporting application. An XML-formatted file is sent to
ION in the Report BOD. Infor Reporting is the
default Output Type if
you are running CloudSuite
Distribution.
-
Select Third Party if you are using a
third-party forms printing application to print your acknowledgements. An
XML-formatted file is sent to ION in the SXFileTransport BOD. You must set up ION to
enable the connection to your third-party forms provider.
-
Select Infor Reporting and Third Party to
send acknowledgements to both Infor Reporting and a third-party forms application.
Both the Report and SXFileTransport BODs are sent to ION.
-
Select IDM Output Management if you are
using Infor Document Management to generate and store acknowledgements or quotes. The
output is sent to Infor Document Management to generate and store acknowledgements and
quotes. The output is sent to IDM Document Output Management Service in a REST API
call.
-
Select IDM Output Management and Third Party
to send acknowledgements and quotes to both IDM and a third-party forms application.
This option should be select in these cases:
-
If you select an Output
Type of Third Party, Infor Reporting and Third Party, IDM Output Management, or IDM Output Management and Third Party, specify any extra fields in the
Level 1 and Level 2 Extra Fields to include in
the information sent in the BOD or to ION API. Separate each extra field with a comma.
Extra data fields for acknowledgements and quotes are retrieved from the OEEH table
for Level 1, and the OEEL table for Level 2. Extra fields are written to the ESBEXTRADATA table and are used by the SXFileTransport BOD if you are sending third-party output.
Extra fields are written to a POST API request to the IDM Document Output Management
Service REST API if you are sending the form to IDM.
-
Note: To include table array
fields, also specify the array number in the field. For example, oeeh.taxamt[1] and
oeeh.taxamt[2] fields should be specified in the Level
1 Extra Fields as
oeeh.taxamt1,oeeh.taxamt2.
-
If you select an Output
Type of IDM Output Management
or IDM Output Management and Third Party,
specify the document type ID set up in Infor Document Management for the
acknowledgement template. If you are using the default template that was created for
Distribution SX.e, specify SX_Form_Templates. If you are using a custom template for your
acknowledgement form, based on the templates that were created for Distribution SX.e, specify SX_Custom_Form_Templates. The IDM Document Type ID is sent in a POST
API request to the IDM Document Output Management Service. If the IDM Document Type ID field is
blank, the default templates are used.
-
In the IDM Template Name
field, specify SXAcknowledgementTemplate. The
IDM Template Name is sent in a POST API request to the IDM Document Output Management
Service. If the IDM Template
Name field is blank, the default acknowledgement template is used. In
the IDM From Email
Address and IDM From
Email Name fields, specify the email address and person's name to be
used by IDM when generating and sending acknowledgements by email. If these fields are
blank the name and email address from SA Operator
Setup for the user running the acknowledgement report is used. If no
email is assigned to the SA Operator Setup
record, the default email name and address set up in IDM is used.
-
If you select an Output
Type of IDM Output Management
or IDM Output Management and Third Party,
specify the document type ID set up in Infor Document Management for the quote
template in the Quote IDM Document
Type ID field. If you are using the default template that was created
for Distribution SX.e, specify SX_Form_Templates. If you are using a custom template for your quote
form, based on the templates that were created for Distribution SX.e, specify SX_Custom_Form_Templates.
-
In the
Quote IDM Template
Name field, specify
SXQuoteTemplate to use the template designed specifically for quotes.
The default is
SXAcknowledgementTemplate. To
use the order acknowledgement template for quotes instead, specify
SXAcknowledgementTemplate or leave blank. This option
controls the printing of Quote Order (QU) order types when printing acknowledgements
in
Sales Order Entry-Printing or
Sales Entry Processing Acknowledgments Report. It does
not control printing of quotes in
Sales Entry Quote Print
Report.
Note: The standard acknowledgement and quote templates are exactly the
same, they just have different titles ('Quote' or 'Acknowledgement'). You can add or
remove fields from either template to customize them.
-
The IDM Template Name is sent in a POST API request to the IDM Document Output
Management Service. If the Quote IDM
Template Name field is blank, the default acknowledgement template is
used. In the IDM From Email
Address and IDM From
Email Name fields, specify the email address and person's name to be
used by IDM when generating and sending acknowledgements or quotes by email. If these
fields are blank the name and email address from SA
Operator Setup for the user running the Sales
Entry Processing Acknowledgments Report is used. If no email is assigned
to the SA Operator Setup record, the default
email name and address set up in IDM is used.
-
The EDI
Format determines the format of outbound EDI documents at the company
level. In CloudSuite Distribution, you must specify 5 to generate ION BODs.
This setting is ignored if ION output is selected for this document at the trading
partner level.
- Pick Tickets - Print Format / Headings / Language / Output
Type / Level 1-2 Extra Fields
-
Select 1 in the Print Format field to use the standard National
Electrical Manufacturers Association (NEMA) format. As the pick tickets are being
printed, the standard NEMA format and the order information prints. You also can
specify whether the standard heading print. If you are using pre-printed NEMA forms,
you do not want the headings to print.
Select 4 in the Print Format field to produce XML
output. XML output is required for forms that are sent to Infor Reporting, Infor Document Management, or some third-party
forms printing applications. When you specify 4, you must also select an Output Type. Format
4 with an Output
Type of Infor Reporting is the
default format selected for all forms if you are running CloudSuite Distribution.
Select 9 if you have
developed a custom print routine to print pick tickets. The custom routine controls
whether pick ticket headings are printed and the format to print order information. If
you choose 9, the utility program oeepp9.p is
executed when you print pick tickets. Format 9 is not supported for CloudSuite Distribution.
-
Select the Headings
option to print the headings for the document. If you are using a pre-printed pick
ticket form, do not select this option.
-
To print the alternate language product description set up in Product
Setup that matches the language from the sales order header, select
Order in the Language field. It is generally assumed that the pick ticket is a
customer-facing document, therefore, by default it is printed in the language
associated with the customer on the sales order. If you never send picket tickets to
your customers, select Warehouse to use the product's alternate
language description from the Product Setup record that matches
the operator's language. See the information about implementing alternate product
language descriptions in this online documentation.
-
The Output Type field is
required if you select 4 in the Print Format field. Select
Infor Reporting to send the pick ticket to
the Infor Reporting application. An XML-formatted file is sent to ION in the Report
BOD. Infor Reporting is the default
Output Type if you are
running CloudSuite Distribution. Select Third Party if you are using a third-party forms
printing application to print your pick tickets. An XML-formatted file is sent to ION
in the SXFileTransport BOD. You must set up ION to enable the connection to your
third-party forms provider. Select Infor Reporting and
Third Party to send pick tickets to both Infor Reporting and a
third-party forms application. Both the Report and SXFileTransport BODs are sent to
ION.
-
Select IDM Output Management if you are
using Infor Document Management to generate and store pick
tickets. The output is sent to Infor Document Management to
generate and store pick tickets. The output is sent to IDM Document Output Management
Service in a REST API call.
-
Select IDM Output Management and Third Party
to send pick tickets to both IDM and a third-party forms application. This option
should be select in these cases:
-
If you select an Output Type of Third Party,
Infor Reporting and Third Party, IDM Output Management, or IDM Output Management and Third Party, specify any extra fields in the
Level 1 or Level 2 Extra
Fields to include in the information sent in the BOD or to ION API.
Separate each extra field with a comma. Extra fields for pick tickets are retrieved
from the OEEH table for Level 1, and the OEEL table for Level 2. Extra fields are
written to the ESBEXTRADATA
-
If you select an Output
Type of IDM Output Management
or IDM Output Management and Third Party,
specify the document type ID set up in Infor Document Management for the pick ticket
template. If you are using the default template created for Distribution SX.e, specify SX_Form_Templates.
If you are using a custom template for your pick ticket form based on the templates
created for Distribution SX.e, specify SX_Custom_Form_Templates. The IDM Document Type ID is
sent in a POST API request to the IDM Document Output Management Service. If the
IDM Document Type ID
field is blank, the default templates are used. If you are configuring bulk OE pick
ticket forms to be printed to the IDM Output Generator, in the Bulk Pick Ticket IDM Document Type
ID field, specify the document type ID set up in IDM for the OE bulk
pick ticket template.
-
In the IDM Template Name
field, specify SXOEPickTicketTemplate to
generate the landscaped (11 x 8 ½) form. Specify SXOEPickTicketTemplate_Portrait to generate the portrait (8 ½ x 11)
form.The IDM Template Name is sent in a POST API request to the
IDM Document Output Management Service. If the IDM Template Name field is blank, the default pick
ticket template is used. If you are configuring bulk pick tickets, specify SXOEBulkPickTicketTemplate in the Bulk Pick Ticket IDM Template Name
field to generate the landscaped (11 x 8 ½) form. Specify SXOEBulkPickTicketTemplate_Portrait to generate the portrait (8 ½ x 11)
form.In
the IDM From Email
Address and IDM From
Email Name fields, specify the email address and person's name to be
used by IDM when generating and sending pick tickets by email. If these fields are
blank the name and email address from SA Operator
Setup for the user running the pick ticket report is used. If no email is
assigned to the SA Operator Setup record, the
default email name and address set up in IDM is used.
- Bill of Lading - Print / Heading / Output Type
-
If the Sales Order Entry
transaction type is Stock Order (SO), Blanket Release (BR), or Counter Sale (CS) and
the order stage is Stage 3 (Shipped), Stage 4 (Invoiced), or Stage 5 (Paid), a bill of
lading can be printed. The standard bill of lading is printed if you specify
1. The heading option is automatically
selected.
Select 4 in the Print Format field to produce XML
output. XML output is required for forms that are sent to Infor Reporting, Infor
Document Management, or some third-party forms printing applications. When you specify
4, you must also select an Output Type of Infor Reporting, Third
Party, or Both. Format 4 with
an Output Type of
Infor Reporting is the default format
selected for all forms if you are running CloudSuite Distribution.
-
If you have a custom print routine developed for printing bills of
lading, select 9.
-
The Output Type field is required if you
select 4 as the Print
Format type.
Select Infor Reporting to send the bill of lading to the Infor
Reporting application. An XML-formatted file is sent to ION in the Report BOD.
Select Third Party if you are using a third-party forms
printing application to print your bills of lading. An XML-formatted file is sent to
ION in the SXFileTransport BOD. You must set up ION to enable the connection to your
third-party forms provider.
Select Infor Reporting and Third Party to send bills of lading
to both Infor Reporting and a third-party forms application. Both the Report and
SXFileTransport BODs are sent to ION.
Select IDM Output Management if you are using Infor Document
Management to generate and store bills of lading. The output is sent to Infor Document
Management Output Management Service in a REST API call.
Select IDM Output Management and Third
Party to send bills of lading to both IDM and a third-party forms
application. This option should be selected in these cases:
-
If you select an Output Type of Third Party,
Infor Reporting and Third Party, IDM Output Management, or IDM Output Management and Third Party, specify any extra fields in the
Level 1 or Level 2 Extra
Fields to include in the information sent in the BOD or to ION API.
Separate each extra field with a comma. Extra fields for bills of lading are retrieved
from the OEEH table for Level 1, and the OEEL table for Level 2. Extra fields are
written to the ESBEXTRADATA table and are used by
the SXFileTransport BOD if you are sending third-party output. Extra fields are
written to a POST API request to the IDM Document Output Management Service REST API
if you are sending the form to IDM.
-
If you select an Output
Type of IDM Output Management
or IDM Output Mangement and Third Party,
specify the document type ID set up in Infor Document Management for the bill of
lading template. If you are using the default template created for Distribution SX.e, specify SX_Form_Templates. If you are using a custom template for your bill of
lading form based on the templates created for Distribution SX.e, specify SX_Custom_Form_Templates. The IDM
Document Type ID is sent in a POST API request to the IDM Document Output Management
Service. If the IDM Document Type
ID field is blank, the default templates are used.
-
In the IDM Template Name
field, specify SXBillOfLadingTemplate. The
IDM Template Name is sent in a POST API request to the IDM Document Output Management
Service. If the IDM Template
Name field is blank, the default bill of lading template is used. In the
IDM From Email Address
and IDM From Email Name
fields, specify the email address and person's name to be used by IDM when generating
and sending bills of lading by email. If these fields are blank, the name and email
address from SA Operator Setup for the user
running the bill of lading report is used. If no email is assigned to the SA Operator Setup record, the default email name and
address set up in IDM is used.
- Advanced Shipping Notice - EDI Format
-
The EDI
Format determines the format of outbound EDI documents at the company
level. In CloudSuite Distribution, you must specify 5 to generate ION BODs.
This setting is ignored if ION output is selected for this document
at the trading partner level.
- Delivery - Print / Heading / Output Type / Level 1-2 Extra
Fields
-
Select 1 to print the
standard Delivery Document. The Heading option
is automatically selected.
Select 3 if you are using a
third-party form printing solutions, such as Unform or NowDocs. You must install and
configure this utility before, or in conjunction with, setting up Delivery Document
printing. Third-party requirements are subject to change. Check with the appropriate
third-party customer representative. If you select 3, the
utility program oeepd3.p is executed when you print
Delivery Documents.
Select 4 in the Print Format field to produce XML
output. XML output is required for forms that are sent to Infor Reporting or some
third-party forms printing applications. When you specify 4, you must also select an Output Type. Format 4 with an Output Type of Infor Reporting is the default format selected for all
forms if you are running CloudSuite
Distribution. Print Format 4 must be selected to
include product, catalog notes, or order line comments entered on an order in
Sales Order Entry on the Delivery Document. To include these
delivery notes, the Delivery option must be
selected in the Notes context application.
Select 9 if you have a
custom print routine developed for printing Delivery Documents. Formats 2 and 9 are
not supported for CloudSuite
Distribution.
-
The Output Type field is
required if you select 4 in the Print Format field. Select
Infor Reporting to send the delivery
document to the Infor Reporting application. An XML-formatted file is sent to ION in
the Report BOD. Infor Reporting is the
default Output Type if
you are running CloudSuite Distribution. Select Third Party if you are using a third-party forms
printing application to print your delivery documents. An XML-formatted file is sent
to ION in the SXFileTransport BOD. You must set up ION to enable the connection to
your third-party forms provider. Select Infor Reporting
and Third Party to send delivery document to both Infor Reporting and a
third-party forms application. Both the Report and SXFileTransport BODs are sent to
ION.
-
Select IDM Output Management if you are
using Infor Document Management to generate and store delivery notes. The output is
sent to Infor Document Management to generate and store the delivery document. The
output is sent to IDM Document Output Management Service in a REST API call.
-
Select IDM Output Management and Third Party
to send delivery notes to both IDM and a third-party forms application. This option
should be select in these cases:
-
If you select an Output Type of Third Party,
Infor Reporting and Third Party, IDM Output Management, or IDM Output Management and Third Party, specify any extra fields in the
Level 1 or Level 2 Extra
Fields to include in the information sent in the BOD or to ION API.
Separate each extra field with a comma. Extra fields for delivery notes are retrieved
from the OEEH table for Level 1, and the OEEL table for Level 2. Extra fields are
written to the ESBEXTRADATA table and are used by
the SXFileTransport BOD if you are sending third-party output. Extra fields are
written to a POST API request to the IDM Document Output Management Service REST API
if you are sending the form to IDM.
-
If you select an Output
Type of IDM Output Management
or IDM Output Mangement and Third Party,
specify the document type ID that is set up in Infor Document Management for the
delivery template. If you are using the default template that was created for Distribution SX.e, specify SX_Form_Templates. If you are using a custom template for your delivery
form, based on the templates that were created for Distribution SX.e, specify SX_Custom_Form_Templates. The IDM Document Type ID is sent in a POST
API request to the IDM Document Output Management Service. If the IDM Document Type ID field is
blank, the default templates are used.
-
In the IDM Template Name
field, specify SXDeliveryNoteTemplate. The
IDM Template Name is sent in a POST API request to the IDM Document Output Management
Service. If the IDM Template
Name field is blank, the default delivery note template is used. In the
IDM From Email Address
and IDM From Email Name
fields, specify the email address and person's name to be used by IDM when generating
and sendingSA Operator Setup for the user
running the delivery report is used. If no email is assigned to the SA Operator Setup record, the default email name and
address set up in IDM is used.
- Invoices - Print Format / EDI Format / Fax Format / Heading
/ 3rd Party Separate Output / Group Print File / Output Type / Level 1-2 Extra
Fields
-
Select 1 to use the regular
National Electrical Manufacturers Association (NEMA) standard format. As the invoices
are being printed, the standard NEMA format and the order information prints. You also
can specify whether the standard heading print. If you are using pre-printed NEMA
forms, you do not want the headings to print.
Select 4 in the Print Format field to produce XML
output. XML output is required for forms that are sent to Infor Reporting or some
third-party forms printing applications. When you specify 4, you must also select an Output Type. Format 4 with an Output Type of Infor Reporting is the default format selected for all
forms if you are running CloudSuite
Distribution.
When you generate invoices using IDM, you have the option of also printing or
emailing Material Safety Data Sheets (MSDS) for any hazardous products on the invoice.
-
Select 9 or a one-digit
number other than 1 if you have a custom print routine to print
invoices. The custom routine must control whether invoice headings print and the
format to print order information. If you choose 9, the utility
program oeepi9.p is executed when you print
invoices.
Note: In CloudSuite Distribution, Print
Format 4 output is not generated if the EDI Format is 5, the Send
By method on the customer record is EDI, and the option, Print to EDI Where Appropriate, is selected on the Sales Entry Invoice Processing Report.
The Output Type field is
required if you select 4 in the Print Format field. Select
Infor Reporting to send invoices to the
Infor Reporting application. An XML-formatted file is sent to ION in the Report BOD.
Infor Reporting is the default Output Type if you are running
CloudSuite Distribution. Select Third Party if you are using a third-party forms printing application
to print your invoices. An XML-formatted file is sent to ION in the SXFileTransport
BOD. You must set up ION to enable the connection to your third-party forms provider.
Select Infor Reporting and Third Party to
send invoices to both Infor Reporting and a third-party forms application. Both the
Report and SXFileTransport BODs are sent to ION.
Select IDM Output Management if you are
using Infor Document Management to generate and store invoices. The output is sent to
Infor Document Management to generate and store the invoice. The output is sent to IDM
Document Output Management Service in a REST API call.
Select IDM Output Management and Third Party
to send invoices to both IDM and a third-party forms application. This option should
be select in these cases:
If you select Third Party or IDM Output Management
and Third Party, you can also specify whether to generate separate
SXFileTransport BODs for each invoice. Select 3rd Party
Separate Output to create a single SXFileTransport BOD for each order.
If this option is not selected, when invoices are printed in Sales Entry
Invoice Processing Report or Sales Demand Invoices
Report, invoices for all orders in the report run are included in a
single SXFileTransport BOD. This ensures BODs of a manageable size are submitted
through Infor ION. We recommended you select the 3rd
Party Separate Output option if you are using Billtrust as your
third-party billing application.
Select Group Print File to consolidate
multiple IDM invoices into a single PDF when printing from the Sales Entry
Invoice Processing Report or Sales Demand Invoices
Report. The invoice sort order from the report is preserved in the single
PDF file, which reduces manual invoice sorting after printing. If this option is not
selected, IDM invoices are printed individually in a randomized sort order.
Note: The Group Print
File option only applies when printing invoices to PDF. It does not
apply when the print output is email.
Note: If you are integrating to Billtrust, the SXFileTransport
BOD can be blocked when you run the
Sales Demand Invoices
Report to print an on-demand invoice. The BOD element,
oerd, must be added to the SXFileTransport document flow in ION
to enable filtering of this BOD when the
Sales Demand Invoices
Report is run.
See the Infor CloudSuite Distribution
Integration for Billtrust.
If you select an Output
Type of Third Party, Infor Reporting and Third Party, IDM Output Management, or IDM Output Management and Third Party, specify any extra fields in the
Level 1 or Level 2 Extra
Fields to include in the information sent in the BOD or to ION API.
Separate each extra field with a comma. Extra fields for invoices are retrieved from
the OEEH table for Level 1, and the OEEL table for Level 2. Extra fields are written
to the ESBEXTRADATA table and are used by the
SXFileTransport BOD if you are sending third-party output. Extra fields are written to
a POST API request to the IDM Document Output Management Service REST API if you are
sending the form to IDM.
If you select an Output
Type of IDM Output Management
or IDM Output Mangement and Third Party,
specify the IDM Document Type
ID set up in Infor Document Management for the standard invoice
template. Specify the Commercial
Invoice IDM Document Type ID if you generate a commercial invoice. If
you are using the default template created for Distribution SX.e, specify SX_Form_Templates in these
fields. If you are using a custom template for your invoice form based on the
templates that were created for Distribution SX.e, specify
SX_Custom_Form_Templates. The IDM Document
Type ID and Commercial Invoice IDM Document Type ID is sent in a POST API request to
the IDM Document Output Management Service. If either document ID field is blank, the
default templates are used.
In the IDM Template Name
field, specify SXInvoiceTemplate. If you are
generating commercial invoices, specify SXCommercialInvoiceTemplate in the Commercial Invoice IDM Template Name field. The IDM
template name is sent in a POST API request to the IDM Document Output Management
Service. If either IDM template name fields are blank, the default invoice or
commercial invoice template is used. In the IDM From Email Address and IDM From Email Name fields,
specify the email address and person's name to be used by IDM when generating and
sending invoices, standard or commercial, by email. If these fields are blank the name
and email address from SA Operator Setup for
the user running the invoice report is used. If no email is assigned to the SA Operator Setup record, the default email name and
address set up in IDM is used.
The EDI Format
determines the format of outbound EDI documents at the company level. In CloudSuite Distribution, you must specify 5 to generate ION BODs.
This setting is ignored if ION output is selected for this document at the trading
partner level.
- Counter Receipts - Print Format
-
Select 1 to use the regular
format. The standard receipt print program is oeetrpl.p. The number you choose here corresponds to the program number.
No headings print on the receipts, but you can specify the receipt header and footer
information.
Select 9 or any other
one-digit number other than 1 if a custom print routine has been developed to print
receipts. The custom routine must control the format to print order information. If
you choose 9, the utility program oeetrp9.p is executed when you print receipts.
- Manifest - Print Format
-
Select 1 to use the standard
format. You also can specify whether the headings developed by Distribution SX.e are printed.
Select 9 if you have
developed a custom print routine to print manifests. The custom routine must control
whether headings are printed, and the format to print order information. If you select
9, the utility program oeepm9.p is executed when you print manifests.