Data Management Capabilities > Using Packages to Import and Export Data for Offline Collaboration > Define Mapping > Defining Received Delivery Mapping > View Mapping
View Mapping
The View tab, which is available on the Define Mapping window, allows you to define translations of a view from the source system to a view on your Windchill system. You can define the view mapping for each source system with which your Windchill system interacts. For more information, see Best Practices for Using Mapping Definitions.
1. Add a row to the table using the add row icon or multiple rows using the add five rows icon .
2. Populate each field with the appropriate source and target mapping information. The fields are described in the table below.
3. Click Apply to define mappings in another tab or click OK to save your changes and close the window.
You can use an asterisk (*) character to represent unknown source system values for the context, folder, and view. For example, if you only know the name of one view on the source system, but suspect that there are additional views represented, you can explicitly map the known source view to an appropriate view on your system in one line on the View tab, and then specify an asterisk (*) in the next line to catch any additional views and map them to an appropriate view on your system. The asterisk (*) should not be used with any other characters in the source field as it will be taken as a literal string.
Source View
Lists the source view name. This value must match the source system view name exactly.
You can copy the source view value from the Preview Received Delivery Import window.
Mapped View
Lists the view applied to objects imported from the source system.
To set the mapped view, click the find icon . The View window opens, which allows you to select the appropriate view from the view hierarchy.
Each view represented in the source system must be mapped to a single different view in the target system. For example, if the source system has the Design, Manufacturing, and Post-Production views, they each must map to a separate view on the target system.
Lists the context in which the values for this row were set.
Indicates whether the values can be modified in lower contexts. For example, if a row is locked in the site context, it cannot be changed in an organization. The value could be modified at the site context level.