Transformation terminology
When you use the
area, you should know these terms:Terms | Definitions |
---|---|
message standard | Defines the format or structure of the message. Examples are ASC X12, UN-EDIFACT, XML, or BOD. |
message type | Defines the content of the message and the business process. Examples are VDA 4905, VDA 4915, ASC X12 830 Planning Schedule with Release Capability, or ASC X12 862 Shipping Schedule. |
style sheet | Defines the rules to transform an input
XML file into an output
XML file.
|
format file description (FFD) | Describes the structure of the input file or structured output file. A source FFD is used to convert a structured message file such as ASC X12 or UN-EDIFACT to XML. A target FFD is used to convert an XML output file to a structured message file such as ASC X12 or UN-EDIFACT. |
partner | Classifies business partners or system
partners who exchange standardized messages with you:
|
partner hierarchy | Represents a list of business partners or system partners who are organized and grouped in a hierarchical tree structure. The tree structure of the partner hierarchy consists of one or several partner IDs. |
partner ID | Represents an element of the partner hierarchy. Each partner ID can consist of child nodes. For example, GM is a partner ID of the "partners" hierarchy. Opel, Vauxhall, and Bertone are from this perspective child nodes of GM. |