Data Management Capabilities > Using Packages to Import and Export Data for Offline Collaboration > Converting Local Data to Replicated Data > Package Types Used in Replication Overwrite > Managing the Local Changeable Objects with Defined Effectivities > Managing the Local Changeable Objects with the Actual Effectivity
Managing the Local Changeable Objects with the Actual Effectivity
Effectivities that existed on the target system before replication, such as those with a Local context and an InTransit lock, or those associated with a part and a Readiness lock, are preserved after replication. All other effectivities are deleted.
Actual Effectivities associated with each changeable object, whether they have a replicating Effectivity Context or no Effectivity Context, are replicated to the target system.
For example, on the source system, PartA has two iterations, A.1 and A.2, with effectivities such as Lot, Block, MSN, Serial, and Date. These effectivities are associated with the PartA context.
Source System
Part Name
Actual Effectivity Type/Context
Value
PartA A.1
Lot Effectivity/PartA
11-15,16-20
Block Effectivity/PartA
21-25,26-30
MSN Effectivity/PartA
31-35,36-40
PartA A.2
Serial Effectivity/PartA
41-45,46-50
Date Effectivity/--
20th May-21st May
Target System Before Replication
For example, on the target system, PartA has iteration A.1 with effectivities such as Lot, Block, MSN, Serial, and Date. These effectivities are associated with various contexts, as shown in the following table—such as PartA, Local, Replicated, InTransit, and Readiness. The Replicated, InTransit, and Readiness contexts correspond to parts that have the Product Design Package, InTransit, and Readiness locks applied to them, respectively.
Part Name
Actual Effectivity Type/Context
Value
PartA A.1
Lot Effectivity/PartA
LA30-LA40
Block Effectivity/Local
BL30-BL40
MSN Effectivity/Replicated
MR30-MR40
Serial Effectivity/InTransit
SI30-SI40
Serial Effectivity/Readiness
SR30-SR40
Date Effectivity/--
29th April-30th April
Target System After Replication
Part Name
Actual Effectivity Type/Context
Value
PartA A.1
Lot Effectivity/PartA
11-15,16-20
Block Effectivity/Local
BL30-BL40
Block Effectivity/PartA
21-25,26-30
Serial Effectivity/InTransit
SI30-SI40
PartA A.2
Serial Effectivity/Readiness
SR30-SR40
MSN Effectivity/PartA
31-35,36-40
Serial Effectivity/PartA
41-45,46-50
Date Effectivity/--
20th May-21st May
After the replication, you can observe the following on the target system:
• Any Actual Effectivities that are associated with each changeable object with a local Effectivity Context in the target system.
• All replicating Changeable objects and Actual Effectivities have an appropriate administrative lock indicating that they are being replicated.
• All Actual Effectivities with a replicating Effectivity Context and without an Effectivity Context are deleted.
• All Actual Effectivities with a replicated Effectivity Context and without an Effectivity Context come from the source system.
• Any Actual Effectivity with a Local Effectivity Context is always preserved for iteration cases.
• The local Actual Effectivity is never preserved across revisions of the Effectivity Managed object.
• The local Actual Effectivity is cleaned up when the Effectivity Context is replicated.
Isto foi útil?