Third-party forms printing

If you use a third-party forms printing application to create your own formatted forms for such documents as customer statements, checks, or pick tickets, you can configure Distribution SX.e to send the output to your forms application. This requires that you configure each form that is printed by the third-party forms application to create output in Print Format 4. You must also define the Output Type for each form as Third Party. If you use Infor Document Management to print your forms, define the Output Type as IDM Output Management or IDM Output Management and Third Party.

The Print Format and Output Type for each form are specified in SA Administrator Options. Supported forms include the customer statement, bill of lading, check, customer invoice, commercial invoice, delivery note, order acknowledgement, pick ticket, and purchase order.

When you print a form set up with a Print Format of 4 and Output Type of Third Party, the report output is created as XML and sent to ION in a SXFileTransport BOD. The XML data includes the information that is normally included on a standard printed output of the report. Depending upon the form, it may also include Level 1 Extra Fields and Level 2 Extra Fields. These extra fields are defined in SA Administrator Options and are used to add extra header and line level information to the form. In addition, Printer Settings are included in the BOD XML that can be used by your forms application to print the form to the correct printer, fax server, or email address. This is specified when you run the report that creates the for and select a Printer Type.

See the Infor CloudSuite Distribution Configuration Guide or Infor Distribution SX.e Configuration Guide for Infor Operating Service for information on Extra Fields.

You can view the status of the Report or SXFileTransport BODs in SA ION Inbox/Outbox Inquiry. If an error occurs during processing, you can open the ION record and view the XML message to determine the cause of the error. You can also use ION Alerts and ION OneView to track BOD processing.

Foreign language forms

The Language Code set up in SA Table Code Value Setup and assigned to customer, vendor, and system records is used to determine if a Format 4 form output is translated. The Format 4 (XML) output for these forms includes a language code to validate the language code based on the report type:


Report	Language Code based on
AR Entry Statement Print (ARES)	Language code in Customer Setup
OE Entry Processing Acknowledgments (OEEPA)	Language code in Customer Setup or Customer Ship-to Setup
OE Entry Processing Invoice Processing (OEEPI)	Language code on sales order
OE Entry Processing Quote Print (OEEPQ)	Language code in Customer Setup or Customer Ship-to Setup
OE Entry Processing Bill of Lading (OEEPL)	Language code on sales order
OE Entry Processing Delivery Document (OEEPD)	Language code on sales order
OE Entry Processing Pick Tickets (OEEPP)	Language code on sales order
PO Entry Processing Print POs (POEPP)	Language code in Vendor Setup
WT Entry Print Warehouse Transfer (WTEP)	Language code on tied order, or if none, on Product Warehouse Description Setup
AP Entry Check Print (APEC)	Language code in Vendor Setup

Note: If no Language Code is assigned to a customer or vendor record, the Language Code from SA Company Setup is used.

Format 4 must be specified as the Print Format Type for these report documents in SA Administrator Options.

Note: Forms are translated to French and Spanish only. If the Language code is anything other than fr or es, the form is created in English.