Reviewing the details of a transformation rule

Select Transformation Services > Configuration > Transformation Rules.

Click the Drill down button of a transformation rule to display the detail view of the Transformation Rules page.

Review the header information of the selected transformation rule:

Effective from Date: This field defines the start date of the valid period for the configuration.; When editing, click the Calendar button to select the start date from a calendar.
Effective to Date: This field defines the end date of the valid period for the configuration.; When editing, click the Calendar button to select the end date from a calendar.
Partner Hierarchy Name: The partner hierarchy name is a classification for a group of communication partners. A partner hierarchy must exist for this configuration.
Partner ID: The partner ID is the hierarchy node of the configuration that identifies a communication partner or a group of communication partners. When editing, select the partner ID from the drop-down list. The drop-down list shows the entries of the TradingPartners code list.
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.
Message Version: The handling of different message versions is currently supported for UN-EDIFACT and ASC X12 messages. If a new message comes in without defined message version in the transformation rule, the transformation rule is updated automatically by the message version.
Message Direction: The message direction is Inbound for incoming messages or Outbound for outgoing messages.
Accounting Entity: The accounting entity is a corporation or a subset of a corporation. The accounting entity is independent in regard to one or more operational functions or accounting functions. An accounting entity produces a P&L and balance sheet from a complete, balanced set of transactions, and is often a legal entity. An accounting entity is defined within a tenant and can contain locations. The field entry is disabled. The accounting entity is automatically set when you save the data. The default is the accounting entity where you are currently working.
Remark: Review or provide a short description that clarifies the purpose of the configuration.

Review the Note field set. The field set shows comments that are specified for the transformation rule.

Review this information at the bottom of the page:

Style Sheet Rule: The field specifies the name of the XSLT style sheet that is used for the transformation. The XSLT style sheet defines how to transform an XML input file into an XML output file. The Format File Descriptions for incoming and outgoing messages are automatically linked to the style sheet if they are defined in the StyleSheetRules code list.
Test Flag: This check box is used to send out an EDI message with an activated test indicator in the UNB segment. The activated test indicator shows the receiver of the message that the message is used to test the processing and not as a productive message.
Acknowledgment: The sender of a message expects a confirmation that the business partner successfully received the message. A new confirmation message is created based on the incoming message, from the perspective of the receiver.

To review the details of the selected style sheet, click View Details right to the Style Sheet Rule field.

The dialog box Style Sheet Rule Details shows this additional information:

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.