Data Management Capabilities > Using Packages to Import and Export Data for Offline Collaboration > Define Mapping > Defining Received Delivery Version Mapping
  
Defining Received Delivery Version Mapping
Version information mapping, which is an implicit one, for received deliveries provides the ability to implicitly translate version information from the source system to its equivalent using the series definition configured in the target system. This mapping is based on the position of the label in the series. For example, “A” is position one and “B” is position two in the default Harvard series configuration. Similarly, “1” is position one and “2” is position two in the default Integer series configuration. Let’s say, the source system sends Revision “A” and “B” of an object using the default Harvard series configuration. The target system that is configured to use the default Integer series for the same object type will receive these revisions as “1” and “2”, respectively.
Implicit mapping is enabled by default. To disable implicit mapping, that is set the imports to use the version information from the source system, configure the property com.ptc.windchill.rd.labelBasedImportHandling.trackedSenders in the wt.properties file. For more information on this property, see Configuring Version Mapping for Imports.
* 
If a versioning scheme is not configured in the target system, a conflict is reported when importing a package.
Only users who are a member of the PLM Connector Importable Package license or are accessing a system where the PLM Connector Server license profile is enabled, can import packages without implicit mapping.
If you are not a member of the PLM Connector Importable Package license or are not accessing the system where the PLM Connector Server license is enabled, and the system is configured to use the version information from the source system, the packages are not imported and the RDImportExecutor Queue does not get triggered.