You can map the data between source and target catalogs using attribute values present in the source catalog and LoVs in the target catalog. This mapping can be done by applying the various attribute mapping rules supported in PCC, for more information refer to section Different Types of Attribute Mapping Rules.
For attribute mapping, select the channel for which you would want to map the attributes. Click on Launch and select the node for which you need to apply the rules.
Based on the SKUs mapped between the source and target catalogs, the mapping relationship is displayed through the arrow indicating the link between them.
Hover the mouse on the gray arrow and it turns blue as shown below.
Hover over 
icon to see the applied rule and when you double click on the plumbing line it initiates attribute mapping. You can view the count of local attributes mapped on this icon but when it's launched for the first time it displays the count as ‘0’.
To view the mapping rules, select either the source or target attribute. However, when you select the source or target attribute only those rules which are applicable to the attribute is enabled and the rest will be disabled. Thus, you can create the attribute mapping rules from this screen.
You can search for an attribute in both the source and target catalogs by typing the attribute name/ID or by attribute value as shown below.
For each attribute in the target catalog, a Show Schema Constraints icon is displayed next to each attribute. Hover the mouse on the icon to view the various schema constraints applied on the attribute as shown below.
The Required Constraint is highlighted in blue icon next to each attribute and the attributes can be sorted using Sort Required Attributes button which will help sort the Required Constraints first followed by Schema Constraints. This provides a clear idea of the various constraints enforced for each attribute. For better understanding, refer to the below screenshots.
