Defining Received Delivery Mapping

The Define Mapping action allows you to translate source system attribute values into values that are meaningful on the target system. It is intended to provide a translation when systems have different ways to identify the same business intent. It is not intended to provide a means to alter the business intent of the source system information.

Define Mapping provides the ability to map Owning Organization, View, Context, Folder, Life Cycle, and Security Labels. Version mapping is controlled by a system-wide property. For more information on version mapping, see Defining Received Delivery Version Mapping.

When alternate resolutions, such as making consistent definitions, are not possible, mapping the source system information to corresponding areas in the target system, allows you to resolve conflicts that may arise when importing the data to your Windchill system. You can map attributes such as context and folder location. For example, if the objects were in Product A in the source system and your target system has Product 1 instead, you can set any object from Product A to be imported into your Product 1 context. For additional information, see Best Practices for Using Mapping Definitions.

2. At the top of the Define Mapping window you can browse to the context from which you want to establish the import mapping. By default, the mapping is defined in the current context.

Different mappings can be defined at different locations in the context hierarchy. Some can be defined at the site or organization level, while others are available at the product or library level as well. The mapping definitions can be inherited by lower levels in the hierarchy unless they are explicitly overridden at a lower level.

You can get the exact source system values for the Source Value information from on the conflict report in the Preview Received Delivery Import window.