Configuring the file import job

Name

The field entry defines the name of the MessageImportFromFileSystem job configuration. The MessageImportFromFileSystem job configuration with the name "parameter" is used as default configuration.

Short Description

Specify a short description of the file import job. The short description can consist of a maximum of 512 characters.

Description

Specify a description of the file import job.

Effective from Date

Specify the start date of the file import job.

Note: If changes of the specified data are planned in the future, define a follow-up code for the subsequent time period and the same hierarchy.

Effective to Date

Specify the end date of the file import job.

Accounting Entity

Select the accounting entity for which the file import job is defined from the drop-down list.

Active

To activate the job declaration, select this check box. The Job Manager Service automatically creates a job instance for each active job declaration. You can define a job declaration on accounting entity level.

Job Trigger Type

The trigger type defines how the scheduled job is triggered. By default, the job is a Cron job.

• Cron Job: The job is started and controlled by a Cron expression.
• Simple Job: The job runs once at a specific time followed by repetitions at defined run intervals.

Scheduled Job Frequency

The field entry defines the frequency for starting the job MessageImportFromFileSystem. If the job has been defined as a Cron job, the frequency is defined as a Cron expression to schedule the job. The default Cron expression is 0/20 * * * * ?.

Repeat Count for Simple Trigger Jobs

The field entry defines the run interval of a Simple Job in seconds. Scheduled jobs that are controlled by a Cron expression do not require a run interval.

• -1: If you specify the run interval -1, the job is started automatically and runs permanently. For example, the job MessageImportFromEXS of type Simple Job is started automatically and runs permanently in contrast to a Cron job.
• Greater than -1: If you specify a run interval greater than -1, a job of type Simple Job can only be started manually.

Job User

The field entry defines the user of Transformation Services that is used to run the job. By default, the user is TFSSystemUser.

Number of Records to Fetch

The field entry defines the number of records a job instance processes before it stops running. This option can improve the scalability of multiple instances of a job running in a cloud environment and the load balancing. With the default setting "0", a job instance continues to run until all records are processed.

File Filter Pattern

The field entry defines the file pattern that is used to separate files of different message types in the same directory. For example, invoices and credit notes are separated if you use a file pattern.

Import Path

The field entry defines the directory where the messages are located that are read, imported, and transformed by Transformation Services. By default, the import path is AUTOCONNECT_HOME/tfs/filesystemConnector/in.

Processed Files Path

The field entry defines the path of the directory where the messages are stored that are processed. By default, the file path for processed messages is AUTOCONNECT_HOME/tfs/filesystemConnector/processed.

Error Path

The field entry defines the path of the directory where error messages are stored. By default, the path of the directory for error messages is AUTOCONNECT_HOME/tfs/filesystemConnector/error.

File Encoding

The field entry defines the character encoding that is used by the file reader to import files, for example, ISO 8859-1 or UTF-8. By default, UTF-8 is used.

Message Standard

The message standard defines the format or structure of the message. Examples are ASC X12, UN-EDIFACT, XML, or BOD.

Message Type

The message type defines the content of the message. Examples are VDA 4905, VDA 4915, ASC X12 830 Planning Schedule with Release Capability, or ASC X12 862 Shipping Schedule. The message type depends on the message standard.

Note: For trading partners who require the Shipment Cancellation message to be sent to a different data source name (i.e., final recipient) than the regular shipment, a new code list must be activated in FeatureActivation code list. On this code list, add the Code value UseShipmentCanceledMessageType. Activating this code results in process shipments with the status of Canceledto be created as messages with the message type Shipment Canceled BOD instead of Shipment. See Configuring ASN cancellation and replacement for more details.

Message Direction

The field entry defines the message direction. The message direction is Inbound for incoming messages and Outbound for outgoing messages. The message direction is required to access the correct transformation rule, because a business partner can send and receive the same message type. By default, the message direction is Inbound.

Trading Partner

The field entry defines the trading partner that is used by the file import job. You can use the trading partner to configure different directories for business partners. The trading partner can also be a system partner such as a finance accounting system to read invoices or credit notes.

For example: You can configure that the import process reads messages from a file system for a trading partner, a message standard, or a message type. These configuration parameters are optional and can be used to specify how the file import works.

See the description of code lists in Administrative Functions.