Publish Service Transactional Data (tsbod0200m000)

Use this session to publish Service LN data to Infor ION for transfer to other software applications.

With this session, you can transfer service orders.

Usually, you publish data from this session once. However, if errors occur during the publication process or if other software applications need a new set of data, you can rerun this session.

Note:

The tabs in this session represent the nouns in a Business Object Document (BOD).
Publishing is not target specific, which means that messages are delivered to all subscribers.

Field Information

Options

Mode

Count

Data is not published, but counted. The number of records is displayed on the report.

Simulate

A report is generated that simulates the publication of data. The transfer of data is only displayed, not processed.

Note: The entire XML message is composed and saved in the Infor ION outbox. However, the transaction is aborted and not committed as in the real situation. This allows you to view and solve the errors that are displayed on the report before you publish your data.

Publish

Data is published.

Size

The number of records that must be simulated.

If you enter a value of 100, the first 100 records that fall within the selection criteria must be simulated.

Default value

The default value is zero, which means all records that fall within the selection range are simulated.

Company

The company range for which the data must be published.

Use Verb

Specify what is published.

Allowed values

Use Process/Sync Verb: Based on the routes in Infor ION, the session publishes Process or Sync BODs.
Use Show Verb: The session publishes Show BODs.

Logical ID(s)

Show BODs do not use ION routes and are sent directly to other applications. Use this field to specify the logical ID(s) of the receiving application.

Logging

If this check box is selected, published BODs are logged.

Output

Specify the log output.

Allowed values

DocumentID: Only the IDs of the published BODs are logged in a file.
BOD: The entire XML file is logged for the published BODs.

Single XML-file per BOD

If this check box is selected, a separate log file is generated for each published BOD.

If this check box is cleared, one log file is generated with the xml of all published BODs.

Note: This check box is only available if the Output is BOD.

Location

The server or client to which the output files must be written.

Directory

The directory on the server or client to which the output files must be written.

ProductionOrder

Maintenance

Enterprise Asset Management (EAM) can generate service orders from production requests, which are communicated by ProductionOrder BODs. If this check box is selected, service orders that are generated from Enterprise Asset Management (EAM) are published as ProductionOrder BODs.

ServiceContract

If this check box is selected, service contracts are published.

ServiceOrder

If this check box is selected, service orders are published.

CustomerCall

If this check box is selected, calls are published.