File Mapping Tables

The file mapping tables indicate the location of external Profile, Orientation, Unicode and Material mapping tables in the folder structure. The internal mapping tables may be specific to either the project or the company.

The tables are searched first for a project-specific set before a company-specific set.

The files consist of a first line, then a series of pairs of * separated values (with no spaces), indicating the location of the mapping file.

The first line in each file is a pair of values, the second of which is used to identify the list.

• The first part of this identifier text is either the three-letter name of the project, for example: TST for the TST000 project, or ANY, signifying a companywide table for any project.

The second part must be one of:
The project-specific Profile mapping files for the TST project may be similar to:

TSTPRF*TSTPRF

BOCAD*C:\AVEVA\Plant\Bocad\maps\Bocad\Bocad.map

AVEVA*C:\AVEVA\Plant\AVEVA\maps\xxxx\E3D.map

and a companywide Unicode test string mapping table may look like:

ANYUNI*ANYUNI

BOCAD*C:\AVEVA\Plant\Bocad\maps\Bocad\BocadUni.map

AVEVA*C:\AVEVA\Plant\AVEVA\maps\xxxx\E3DUni.map

The Material mapping tables are defined in a similar way. For example a project-specific Material mapping file, using a previously defined environment variable, BOCDATA, might look like:

TSTMAT*TSTMAT

BOCAD*%BOCDATA%\Bocad\Bocad.map

AVEVA*%BOCDATA%\AVEVA\AVEVAMat.map

A companywide Profile Orientation mapping table would look similar to the following:

ANYORI*ANYORI

BOCAD*%BOCMAIN%\maps\Bocad\BocadOri.map

AVEVA*%BOCMAIN%\maps\AVEVA\AVEVAOri.map

for further information of the format of the external mapping files, consult the relevant section in this guide.