Improved Content Migration Assistant Handling of Shared Maintenance Object Tables

Prior to this release, when maintenance objects share the same table, Content Migration Assistant (CMA) defers applying these objects from the object apply step to the transaction apply step. In large volumes, this delay may have a negative impact on the completion time of a large import data set. While the delay is inevitable for most cases of shared tables, there is one use case that does not require it technically. When the shared table is a child table in one maintenance object and the primary table in another, the dependency between the tables is serial and therefore can be applied at the object level as usual. For example, in Customer Care and Billing the Bill Factor and Bill Factor Value maintenance objects share the same CI_BF_CHAR table which causes all these objects to be delayed and applied as a single transaction.

As of this release, this type of shared table use case, is applied at the object level, thus speeding up the apply step especially when large volumes are involved.

Improved handling of a certain type of shared tables dependency improves the time it takes to import such configuration.

Steps to Enable

You don't need to do anything to enable this feature.