Tool for Conversion of Replicated Data to Local Data
This topic guides users identify and convert specific objects, libraries, and product contexts from a replicated state to a local one, ensuring they no longer retain replication properties. In their replicated form, data is administratively locked, preventing any modifications to business metadata, such as attribute details or associations with other business entities.
Due to changing business needs, you may need to disown replicated data turning it into local data that can be modified. To do this, a tool is used that allows selective disowning of replicated data in the target system. This tool removes the replication lock while preserving data integrity throughout the replication disowning process.
The table below illustrates how replicated data can be transitioned to a local state through the replication disowning process.
Target System (Initial State)
Selected for Disowning
After Disowning (Final State)
Disowning by Replication Behavior
PartP1 A.1 (replicated)
ChildC1 A.1 (replicated)
ChildC2 A.1 (replicated)
ChildC1 A.1
PartP1 A.1 (replicated)
ChildC1 A.1 (local)
ChildC2 A.1 (replicated)
Only ChildC1 A.1 becomes local. Part P1 A.1 and ChildC2 A.1 remain replicated.
PartP1 A.1 (replicated)
ChildC1 A.1 (replicated)
ChildC2 A.1 (replicated)
ChildC1 A.1
ChildC2 A.1
PartP1 A.1 (replicated)
ChildC1 A.1(local)
ChildC2 A.1 (local)
ChildC1 A.1 and ChildC2 A.1 become local. Part P1 A.1 remains replicated.
PartP1 A.1 (replicated)
ChildC1 A.1 (replicated)
ChildC2 A.1 (replicated)
PartP1 A.1
ChildC1 A.1
ChildC2 A.1
PartP1 A.1 (local)
ChildC1 A.1(local)
ChildC2 A.1 (local)
All elements are disowned and converted to local data.
Important Replication Disowning Rules
When converting replicated data to local data:
Strong-side replicated links are converted to local
Weak-side replicated links remain in their replicated state
* 
Managed baselines and electrical parts are not eligible for conversion from replicated to local data.
When a Family Table is replicated, both the original Family Table (Generic) and all its instances are automatically disowned by the replication process to maintain data integrity.
For example, if a user includes a specific Family Table Instance in the Object Collector Package, any other instances or the Generic that exist in different contexts will also be included in the disowning process.
Was this helpful?