ECMap’s cross-reference tables serve multiple purposes and provide an easy way to convert data during mapping. You can use them to produce pre-assigned EDI codes when application data does not meet the EDI standard format or for any other one-to-one conversion. If an EDI data element has an associated code list in the Standards Tables, you can view the full code list in ECMap.
Use cross-reference tables to convert one code to another code, such as when your trading partner has a code that must be translated to or from your code or when a code in the application data must be converted to or from an EDI code.
An invoice’s Unit of Measure (UOM) field provides a good example of how cross-reference tables convert codes. In the X12 standard, the UOM element is defined as a 2-character ID field with an associated list of valid ID codes, such as EA for each and DZ for dozen. If the application data contains the digit 1 for dozen and the digit 2 for each, you can create a cross-reference table to convert the digit 1 to DZ for dozen and covert the digit 2 to EA for each.
You can also use cross-reference tables to convert codes to text or text to codes. For example, 01 might be the code for January, 02 for February, and so forth. A cross-reference table can look up a value in a list, such as a Weekday list: Monday, Tuesday, Wednesday, and so on.
In addition to simple data transformation, cross-reference tables offer a much wider range of possibilities. For example, EDI-based data dictionaries have code lists with description fields. These codes, called qualifiers in X12 and EDIFACT, tell the user (and the program) what kind of data is associated with that code. You can map an element that has a code list to a field, invoke the cross-reference function, and have the cross-reference function automatically build the table for you, by requesting the option to create entries in the table by filling them with the code description.
Using this method, ECMAp can build a cross-reference table
for PER-01 and PER-03, and map EDI data PER~EX~J.DOE~TE~9735551111 as
follows:
ADMINISTRATIVE COMMUNICATIONS
Expeditor J.DOE
Telephone 973-555-1111
In ECMap, you can add, delete, modify or find cross-reference tables. You can also display a list of cross-reference tables that are in the current map directory but are not defined in the map.
Cross-reference tables are often kept in a common directory
so multiple maps can access them. You can select tables from this
common directory, and ECMap automatically defines them in your map.
Within a cross-reference table, you can add, delete, modify and find entries. You can also automatically populate field values in a cross-reference table entry for EDI-based cross-reference tables.
The cross-reference table windows for transaction maps are slightly different from the windows for any-to-any maps. While the two sides of an entry in a cross-reference table for a transaction map are Standard data and Application data, the two sides of an entry for an any-to-any map are Source data and Destination data. The terminology on certain cross-reference table windows reflects this difference. In addition, less information is required to set up a cross-reference table for an any-to-any map, and there is one less menu option on the Cross Reference Table Properties window for any-to any maps.
You can access the cross-reference table function from the Tools menu ECMap’s main menu or from the Mapping window (through the Build menu selection). While the Tools menu option lets you build cross-reference tables inside or outside of mapping, the Mapping window option lets you build and use cross-reference tables while you are mapping.
