SA Administrator Options - Documents - Purchase Orders - Printing field descriptions

Select this option to print headings on purchase orders.

When the Purchase Entry Processing Print POs Report is run, the values in these fields determine the format for purchase orders:

• Print Format
• EDI Format
• Fax Format

Select 1 in the Print Format field to print purchase orders in the National Electrical Manufacturers Association (NEMA) standard format.

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 select 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 in the Print Format field to use a custom print routine to print purchase orders. You can also select 2-8. The custom routine must control whether purchase order headings print and the format to print order information. If you select 9, poep9.r is executed when you print purchase orders.

The Output Type field is required if you select 4 as the Print Format type.

Select Infor Reporting to send the purchase order form 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 purchase orders. 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 purchase orders 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 purchase orders. The output is sent to IDM Document Output Management Service in a REST API call.

Select IDM Output Management and Third Party to send purchase orders to both IDM and a third-party forms application. This option should be selected in these cases:

• To generate a SXFileTransport BOD in order to view the values passed in a third-party XML file for each purchase order. The XML output can assist in troubleshooting and to verify that the values on the forms match what is passed from Distribution SX.e.
• To generate a SXFileTransport BOD to use for mapping your own custom form template, instead of using the default SX Form Templates stored in IDM.

  See the Infor CloudSuite Distribution Configuration Guide or Infor Distribution SX.e Configuration Guide for Infor OS for information on enabling IDM for forms printing.

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 an extra fields in the Level 1 and Level 2 Extra Fields to include in the information sent in the BOD or to API Gateway. Separate each extra field with a comma. Extra data fields for purchase orders are retrieved from the POEH table for Level 1, and the POEL 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.

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 purchase order 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 purchase order 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 SXPurchaseOrderTemplate. 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 purchase order 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 purchase orders by email. If these fields are blank, the name and email address from SA Operator Setup for the user running the Purchase Entry Print POs 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.

Select the format to be used to print the purchase order pre-receiving reports when generated through the Purchase Pre-Receiving Report. The possible values range from zero to nine. The formats supported by CloudSuite Distribution are:

• Format 1 - Standard print format: This is the default format.
• Format 4 - XML output format: This format is used to generate XML output that can be configured to send to Infor Document Management (IDM) or a third-party forms printing application, based on the selected Output Type.

Select the output type to be used to generate the report through the Purchase Pre-Receiving Report. The output types supported by CloudSuite Distribution includes:

• Third Party: Sends the purchase order pre-receiving form to a third-party form printing application. An XML-formatted file is sent to ION through the SXFileTransport BOD. You must configure ION to enable connectivity with the third-party forms provider.
• IDM Output Management: Sends the purchase order pre-receiving form to IDM for report generation and storage. The output is sent to the IDM Document Output Management Service through a REST API call.
• IDM Output Management and Third Party: Sends the purchase order pre-receiving form to IDM and a third-party forms printing application. Possible scenarios:
  • Generates an SXFileTransport BOD to review the values passed in the XML file for each purchase order pre-receiving form. The XML output can help troubleshoot issues and verify that the form values match the data sent from CloudSuite Distribution.
  • Generates an SXFileTransport BOD that triggers an ION document flow to handle any variety of business processing requirements.

For information about enabling IDM for forms printing, see the Infor CloudSuite Distribution Configuration Guide or the Infor Distribution SX.e Configuration Guide for Infor OS.

Specify additional fields to include extra information in the data sent through the BOD or to the API Gateway. Each field must be separated by a comma. Extra data fields for purchase order pre-receiving forms are retrieved from these tables:

• Level 1 tables:
  • POEH
  • APSV
  • APSS
  • SASC
  • ICSD
• Level 2 tables:
  • POEL
  • ICSP
  • ICSW
  • POELO

The specified fields are copied to the ESBEXTRADATA table and are used by the SXFileTransport BOD when third-party output is configured.

You can include table array fields by specifying the array number. For example, the poeh.addonamt[2] and poeh.addon[2] fields must be specified in the Level 1 Extra Fields field as poeh.addonamt2,poeh.addonno2.

Specify the Document Type ID configured in the IDM application for the purchase order pre-receiving form template. Possible values:

• SX_Form_Templates: Uses the default form template created for CloudSuite Distribution.
• SX_<Custom>_Form_Templates: Uses a custom form template created for CloudSuite Distribution.

The specified Document Type ID is sent in the API request to the IDM Document Output Management Service.

Specify the template name configured in the IDM application for the purchase order pre-receiving form template. The specified template name is sent in the API request to the IDM Document Output Management Service.

Specify the email address to which the generated purchase order pre-receiving form reports are sent from the IDM application.

Specify the name of the receiver of the purchase order pre-receiving form reports that are generated and sent from the IDM application.