|
- Standard Referenz Bibliothek
- XE Konverter
- Mapper Entwicklungs-Werkzeuge
- Mapper
Standard Reference Library
The Standard Reference Library includes all the most recent EDIFACT standards releases, as well as a range of ANSI X12, VDA, Eancom and Tradacoms dictionaries.
The Standard Reference Library offers automatic generation of Xlate tables (EDF and HDF definition files) from all the above-mentioned dictionaries, and a reporting capability.
The Xlate translator
The Xlate component is provided primarily to support existing users, who already have Xlate tables in place for their current translation requirements. Xlate may still be used for new mapping, but it has now been superseded by the Xe Mapper.
The Xlate component of Xe provides for the translation of business documents in and out of standard EDI format. Its range of in-house file formats is less than that of Xe, covering only flat files format.
The Xe GUI also provides facilities for creating or editing an existing Xlate index file (IDX) required for Xlate mapping. Xlate is table-driven and supports EDIFACT, UNGTDI and ANSI X12 syntaxes.
Mapper Development Tools
File Investigator
This allows the user to examine the contents of EDI files in a variety of user-friendly ways. EDI data can be displayed in raw or hierarchical views, highlighting errors in syntax and structure.
Object Packager
Enables the creation of an EDI file containing one or more objects. An object is an EDIFACT concept introduced in version 4 of the standard.
Adding an object results in the insertion of a UNO-UNP segment pairing into the EDI file, at the same level as a message i.e. within a group or interchange. A UNO-UNP pairing is inserted for each file or certificate added to the file and acts as an “envelope” for the object.
Hex Viewer
This provides a specialised view on the contents of a file, allowing the user to see at a glance the position of any character in the file and its hexadecimal representation.
The Mapper
The Mapper delivers comprehensive mapping capabilities, enabling business documents of almost any format (i.e. EDIFACT, ANSI X12, UNGTDI, VDA, flat files and CSV), to be converted to different formats, providing a complete Any-to-Any mapping functionality.
The Mapper allows data to be mapped from an input file to one or more output files with the aid of a GUI.
A definition for the input file and the output file must be provided, then the mapping can be performed using a combination of drag-and-drop techniques and some simple programming.
For existing maps, the GUI enables the user to see which source and target fields are involved in the mapping process, and the manner in which each field is mapped.
The Mapper makes use of a scripting language to facilitate its powerful mapping ability.
Xe can perform arithmetic operations and conditional logic and can even utilise C# code snippets to achieve particular mapping requirements.
This allows Xe translation maps to have access to the entire .NET Framework, enabling the Xe scripts to access databases and deliver data in custom formats all within the script itself.
Because of this, there is no need for further applications and additional scripts to manipulate the data before or after the main translation.
In control of the process at runtime is the Xe Index file.
This XML file contains references to entities which combine to specify the actions that Xe takes on encountering a given source document or message type.
Such entities include source and target document definitions and message syntax. By analysing the properties of the file to be transformed and then referencing the Index file, Xe can determine the appropriate mapping to run.
|
|
