Transformation Services

ConsumptionPurposeCodes

This code list is used by the Transformation Services area to evaluate the consumption purpose code. This code is provided in the posting key of the Inventory Consumption message that is sent to the supplier in the sequencing process. The code is used by trading partner A0013 Smart Europe.

The code list includes these property values:

• ASC X12 Code: ASC X12 code of the consumption purpose code.
• EDIFACT Code: EDIFACT code of the consumption purpose code.
• VDA Code: VDA code of the consumption purpose code.

ExceptionCodes

This code list includes the exception codes that are used by the Transformation Services area to refuse shipments. The code list is required to support the Infor Transportation Management integration.

You can edit these property values:

• ASC X12 Code: ASC X12 code of the exception code.
• EDIFACT Code: EDIFACT code of the exception code.
• VDA Code: VDA code of the exception code.

FileEncodings

This code list defines the encoding that is used by the directory reader in the Transformation Services area to import files.

JobApplicationAdviceTracker

This code list defines the configuration of the ApplicationAdviceTracker job that checks for published ASN messages for which an application advice has not yet been received (check if the status Application Advice Received? is Pending). After a defined waiting time is reached, an alert is created to inform the user about the missing application advice.

• Name: Defines the name of the ApplicationAdviceTracker job configuration. The ApplicationAdviceTracker job entry that has the name "parameter" is used as the default job configuration.
• Active: Activates the job declaration. 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: Specifies the job type that triggers the scheduled job. 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 or runs permanently with a scheduled job frequency in milliseconds.
• Scheduled Job Frequency: Defines the Cron expression for the ApplicationAdviceTracker job. The default Cron expression is 0/10 * * * * ?.
• Repeat Count for Simple Trigger Jobs: Defines whether a job of type Simple Job runs permanently or only once:
  • -1: If the run interval is -1, the job is started automatically and runs permanently. For example, the job MessageImportFromEXS is of type Simple Job. The job is started automatically and runs permanently in contrast to a Cron job.
  • Greater than -1: If the run interval is greater than -1, the job can only be started manually and run once.
• Job User: Defines the user that is used to run the ApplicationAdviceTracker job. By default, the user is TFSSystemUser.

JobMessageCleanup

This code list defines the configuration of the MessageCleanup job that cleans up the Transformation Services messages periodically.

• Name: Defines the name of the MessageCleanup job configuration. The MessageCleanup job entry that has the name "parameter" is used as the default job configuration.
• Active: Activates the job declaration. 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: Specifies the job type that triggers the scheduled job. 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 or runs permanently with a scheduled job frequency in milliseconds.
• Scheduled Job Frequency: Defines the Cron expression for the MessageCleanup job. The default Cron expression is 0 0 23 1/1 * ? *.
• Repeat Count for Simple Trigger Jobs: Defines whether a job of type Simple Job runs permanently or only once:
  • -1: If the run interval is -1, the job is started automatically and runs permanently. For example, the job MessageImportFromEXS is of type Simple Job. The job is started automatically and runs permanently in contrast to a Cron job.
  • Greater than -1: If the run interval is greater than -1, the job can only be started manually and run once.
• Job User: Defines the user that is used to run the MessageCleanup job. By default, the user is TFSSystemUser.

JobMessageImportConsumer

This code list defines the configuration of the MessageImportConsumer job that checks the database for messages to import to the Transformation Services area.

• Name: Defines the name of the MessageImportConsumer job configuration. The MessageImportConsumer job entry that has the name "parameter" is used as the default job configuration.
• Active: Activates the job declaration. 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: Specifies the job type that triggers the scheduled job. 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 or runs permanently with a scheduled job frequency in milliseconds.
• Scheduled Job Frequency: Defines the Cron expression for the MessageImportConsumer job. The default Cron expression is 0/10 * * * * ?.
• Repeat Count for Simple Trigger Jobs: Defines whether a job of type Simple Job runs permanently or only once:
  • -1: If the run interval is -1, the job is started automatically and runs permanently. For example, the job MessageImportFromEXS is of type Simple Job. The job is started automatically and runs permanently in contrast to a Cron job.
  • Greater than -1: If the run interval is greater than -1, the job can only be started manually and run once.
• Job User: Defines the user that is used to run the MessageImportConsumer job. By default, the user is TFSSystemUser.
• Number of Records to Fetch: 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.

JobMessageImportFromEXS

This code list defines the configuration of the MessageImportFromEXS job that imports messages from Exchange Services.

• Name: Defines the name of the MessageImportFromEXS job configuration. The MessageImportFromEXS job entry that has the name "InChannel" is used as the default job configuration.
• Active: Activates the job declaration. 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: Specifies the job type that triggers the scheduled job. By default, the job is of type Simple Job.
  • Cron Job: The job is started and controlled by a Cron expression.
  • Simple Job: The job runs once or runs permanently with a scheduled job frequency in milliseconds.
• Scheduled Job Frequency: Defines the frequency of starting the MessageImportFromEXS job. The default value is 10000.
• Repeat Count for Simple Trigger Jobs: Defines whether a job of type Simple Job runs permanently or only once:
  • -1: If the run interval is -1, the job is started automatically and runs permanently. For example, the job MessageImportFromEXS is of type Simple Job. The job is started automatically and runs permanently in contrast to a Cron job.
  • Greater than -1: If the run interval is greater than -1, the job can only be started manually and run once.
• Job User: Defines the user that is used to run the MessageImportFromEXS job. By default, the user is TFSSystemUser.

JobMessageImportFromFileSystem

This code list defines the configuration of the MessageImportFromFileSystem job that imports messages from the file system to the Transformation Services area.

• Name: Defines the name of the MessageImportFromFileSystem job configuration. The MessageImportFromFileSystem job entry that has the name "parameter" is used as the default job configuration.
• Active: Activates the job declaration. 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: Specifies the job type that triggers the scheduled job. 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 or runs permanently with a scheduled job frequency in milliseconds.
• Scheduled Job Frequency: 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/10 * * * * ?.
• Repeat Count for Simple Trigger Jobs: Defines whether a job of type Simple Job runs permanently or only once:
  • -1: If the run interval is -1, the job is started automatically and runs permanently. For example, the job MessageImportFromEXS is of type Simple Job. The job is started automatically and runs permanently in contrast to a Cron job.
  • Greater than -1: If the run interval is greater than -1, the job can only be started manually and run once.
• Job User: Defines the user that is used to run the job. By default, the user is TFSSystemUser.
• Number of Records to Fetch: 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: 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: Defines the directory where the messages are located that are read, imported, and transformed by Transformation Services. By default, in an automotive environment the import path is AUTOCONNECT_HOME/tfs/filesystemConnector/in.
• Processed Files Path: Defines the path of the directory where the messages are stored that are processed. By default, in an automotive environment the file path for processed messages is AUTOCONNECT_HOME/tfs/filesystemConnector/processed.
• Error Path: Defines the path of the directory where error messages are stored. By default, in an automotive environment the path of the directory for error messages is AUTOCONNECT_HOME/tfs/filesystemConnector/error.
• File Encoding: 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 ANSI ASC X12, EDIFACT, XML, or BOD.
• Message Type: The message type defines the content of the message. Examples are 4905, 4915, 830, 862, DELFOR, ORDERS, Inventory Consumption, Invoice, Planning Schedule, Shipment Schedule, or Shipment.
• Message Direction: 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 ID: Defines the trading partner ID. You can use the trading partner ID to configure different directories for business partners. The trading partner ID can also be a system partner such as a finance accounting system to read invoices or credit notes. If the trading partner ID is set in this configuration, this trading partner ID is used for the communication process. If the message does not contain a sender ID and receiver ID, you must specify the trading partner ID.

JobMessagePrintRequestUpdater

This code list defines the configuration of the MessagePrintRequestUpdater job that updates print requests in the Transformation Services area.

• Name: Defines the name of the MessagePrintRequestUpdater job configuration. The MessagePrintRequestUpdater job entry that has the name "parameter" is used as the default job configuration.
• Active: Activates the job declaration. 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: Specifies the job type that triggers the scheduled job. 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 or runs permanently with a scheduled job frequency in milliseconds.
• Scheduled Job Frequency: Defines the Cron expression for the MessagePrintRequestUpdater job. The default Cron expression is 0/10 * * * * ?.
• Repeat Count for Simple Trigger Jobs: Defines whether a job of type Simple Job runs permanently or only once:
  • -1: If the run interval is -1, the job is started automatically and runs permanently. For example, the job MessageImportFromEXS is of type Simple Job. The job is started automatically and runs permanently in contrast to a Cron job.
  • Greater than -1: If the run interval is greater than -1, the job can only be started manually and run once.
• Job User: Defines the user that is used to run the MessagePrintRequestUpdater job. By default, the user is TFSSystemUser.
• Number of Records to Fetch: 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.

JobMessagePublisher

This code list defines the configuration of the MessagePublisher job that publishes messages in the Transformation Services area.

• Name: Defines the name of the MessagePublisher job configuration. The MessagePublisher job entry that has the name "parameter" is used as the default job configuration.
• Active: Activates the job declaration. 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: Specifies the job type that triggers the scheduled job. 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 or runs permanently with a scheduled job frequency in milliseconds.
• Scheduled Job Frequency: Defines the Cron expression for the MessagePublisher job. The default Cron expression is 0/10 * * * * ?.
• Repeat Count for Simple Trigger Jobs: Defines whether a job of type Simple Job runs permanently or only once:
  • -1: If the run interval is -1, the job is started automatically and runs permanently. For example, the job MessageImportFromEXS is of type Simple Job. The job is started automatically and runs permanently in contrast to a Cron job.
  • Greater than -1: If the run interval is greater than -1, the job can only be started manually and run once.
• Job User: Defines the user that is used to run the MessagePublisher job. By default, the user is TFSSystemUser.
• Number of Records to Fetch: 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.

JobMessageResolver

This code list defines the configuration of the MessageResolver job that parses messages in the Transformation Services area.

• Name: Defines the name of the MessageResolver job configuration. The MessageResolver job entry that has the name "parameter" is used as the default job configuration.
• Active: Activates the job declaration. 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: Specifies the job type that triggers the scheduled job. 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 or runs permanently with a scheduled job frequency in milliseconds.
• Scheduled Job Frequency: Defines the Cron expression for the MessageResolver job. The default Cron expression is 0/10 * * * * ?.
• Repeat Count for Simple Trigger Jobs: Defines whether a job of type Simple Job runs permanently or only once:
  • -1: If the run interval is -1, the job is started automatically and runs permanently. For example, the job MessageImportFromEXS is of type Simple Job. The job is started automatically and runs permanently in contrast to a Cron job.
  • Greater than -1: If the run interval is greater than -1, the job can only be started manually and run once.
• Job User: Defines the user that is used to run the MessageResolver job. By default, the user is TFSSystemUser.
• Number of Records to Fetch: 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.

JobMessageTransformer

This code list defines the configuration of the MessageTransformer job that transforms messages in the Transformation Services area.

• Name: Defines the name of the MessageTransformer job configuration. These job configuration variants can be used:
  • Publish Daily
  • Publish Immediately
  • Publish Monthly
  • Publish Weekly
• Active: Activates the job declaration. 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: Specifies the job type that triggers the scheduled job. 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 or runs permanently with a scheduled job frequency in milliseconds.
• Scheduled Job Frequency: Defines the Cron expression for the MessageTransformer job. The default Cron expression for the job configuration variant Publish Daily is 0/50 * * * * ?. The default Cron expression for the job configuration variant Publish Immediately is 0/20 * * * * ?.
• Repeat Count for Simple Trigger Jobs: Defines whether a job of type Simple Job runs permanently or only once:
  • -1: If the run interval is -1, the job is started automatically and runs permanently. For example, the job MessageImportFromEXS is of type Simple Job. The job is started automatically and runs permanently in contrast to a Cron job.
  • Greater than -1: If the run interval is greater than -1, the job can only be started manually and run once.
• Job User: Defines the user that is used to run the MessageTransformer job. By default, the user is TFSSystemUser.
• Number of Records to Fetch: 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.
• Temporary Files Path: In an automotive environment, the default path for temporary files is AUTOCONNECT_HOME/tfs/transform.
• Trading Partner Style Sheet Path: In an automotive environment, the default path for standard trading partner style sheets is AUTOCONNECT_HOME/tfs/resources/mappings.
• Modified Style Sheet Path: In an automotive environment, the default path for modified trading partner style sheets is AUTOCONNECT_HOME/tfs/resourcesmod/mappings.
• Number of Tasks: Shows the number of created tasks.
• Prefix for the Task Threads: Shows the default prefix TransformerTask- for created task threads.

JobTFSReorganization

This code list defines the configuration of the TFSReorganization job. The job deletes transactional data in the Transformation Services area.

• Name: Defines the name of the TFSReorganization job configuration. The TFSReorganization job entry that has the name "parameter" is used as the default job configuration.
• Active: Activates the job declaration. 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: Specifies the job type that triggers the scheduled job. 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 or runs permanently with a scheduled job frequency in milliseconds.
• Scheduled Job Frequency: Defines the frequency for starting the job TFSReorganization. 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 0 0 31 12 ? 2099.
• Job User: Defines the user of the Transformation Services area that is used to run the TFSReorganization job. By default, the user is TFSSystemUser.
• Repeat Count for Simple Trigger Jobs: Defines whether a job of type Simple Job runs permanently or only once:
  • -1: If the run interval is -1, the job is started automatically and runs permanently. For example, the job MessageImportFromEXS is of type Simple Job. The job is started automatically and runs permanently in contrast to a Cron job.
  • Greater than -1: If the run interval is greater than -1, the job can only be started manually and run once.
• Delete Messages Older than Days: Number of days for which messages should be kept, starting yesterday. By default, this parameter is deactivated (-1 = no deletion).
• Delete in One Transaction (Standard): Number of objects deleted in one transaction (default = 1000).
• Delete in One Transaction (Big Data): Number of objects (containing blobs) deleted in one transaction (default = 10).

MessageDirections

This code list defines the message directions inbound and outbound for the Transformation Services area.

MessageSplitter

To control the splitting of inbound VDA 4916 messages per vehicle, that is, per record type 662, this code list has been introduced. By default, the splitting of the VDA 4916 messages per vehicle is activated. If the message should not be split, the parameter must be deactivated.

MessageStandards

This code list includes the message standard definitions for the Transformation Services area.

You can edit these property values:

Transformation Format: Defines a variable or fixed format for the transformation of messages.

MessageTypes

This code list includes the message type definitions for the Transformation Services area.

MessageVersions

This code list includes the message versions for the Transformation Services area.

PackagingTerms

Returnable code for the container that is used in the Shipping area to qualify the packaging information.

• Non-returnable supplier-paid container
• Non-returnable customer-paid container
• Returnable customer-owned container
• Returnable supplier-owned container
• No packaging: Specify this option if none of the other options are applicable for the container.

You can edit the property value EDIFACT Code: EDIFACT code of the returnable code.

PartnerMappingBusinessKeys

This code list includes the business partner mapping key definitions for the Transformation Services area.

PublishFrequencies

This code list includes the publishing frequencies for messages in the Transformation Services area.

You can edit these property values:

Cron Expression: Cron expression that control in which cycles messages are automatically transformed by Transformation Services.

ReasonCodes

This code list includes the reason codes for the refusal of the shipment. The reason codes are used by the Transformation Services area to support the Infor Transportation Management integration.

You can edit these property values:

• ASC X12 Code: ASC X12 code of the reason code.
• EDIFACT Code: EDIFACT code of the reason code.
• VDA Code: VDA code of the reason code.

StyleSheetRules

This code list includes the style sheet rules for the Transformation Services area.

You can edit these property values:

• Style Sheet File Name: Name of the XSLT style sheet that is used to transform an XML input file into an XML output file.
• Source Format File Description: The XML file is used to convert a structured message file such as ANSI X12 or EDIFACT to XML.
• Target Format File Description: The XML file is used to create the target format of an XML file, for example, a structured message file such as ASC X12 or EDIFACT.
• Message Standard: The message standard that is used for the transformation of the message.