Processing Notes for Specific Objects

The following limitations apply to certain Oracle Utilities Customer Care and Billing objects when using Content Migration Assistant:

• An Issuing Center object references a User. If this user does not exist in the target system, Content Migration Assistant cannot apply the requested changes.
• A Case Type object references an Application Service. If this service does not exist in the target system, Content Migration Assistant cannot apply the requested changes.
• Collection Agency and Service Provider objects reference a Person. If this person does not exist in the target system, Content Migration Assistant cannot apply the requested changes.
• Service Provider and Tender Source objects reference a Service Agreement. If this service agreement does not exist in the target system, Content Migration Assistant cannot apply the requested changes.
• If your migrateable object includes log tables, you may add your log entity to the characteristic type F1-MGO. You should also mark the log table as a “Non-Migrateable Table” in the Maintenance Object options.
• Transactions are applied in an unspecified order (and probably in order numerically by a randomly generated ID value). CMA only looks at "hard" constraints when determining what to put into the same transaction. Any "soft" constraints such as characteristics and algorithm parameters that might have FK references to other objects are not processed by CMA. Unless the migration plan ensures that related items go into the same transaction, they will end up in different ones, and must need to apply again and again until eventually all gets applied.