Windchill System Administrator's Guide

You can import objects to destination contexts that have specified
correspondences to the contexts from which the objects were exported. The
specifications that control the destination contexts for imported objects are called
context mapping files. You may select a context mapping file in the import
graphical user interface.
When objects are imported without a context mapping file in control, all the
objects are imported into the target context where the import process launched.
This context file is ignored during import into a Project because to do so would
violate Windchill ProjectLink security guarantees. If you wish to override this
behavior, you must use the Export/Manager for Windchill ProjectLink by
importing into the Organization container level.
The context mapping file allows the distribution of imports into multiple targets.
The context mapping file is intended only for advanced users who cannot find
another resolution. The context mapping file hard-wires the container paths in
your import set, so this approach requires detailed synchronization between the
source and target system which is typically only achievable via pilot to production
export scenarios. A better approach is to analyze what your transport needs really
are, and then to streamline the creation of appropriate export sets. PTC does not
recommend extensive use of the context mapping file functionality at your site.
The context mapping file has the following syntax:
Windchill Import and Export 6-7