As described in the previous section, the drivers for which instructions to include in a migration plan differ a bit based on whether the migration plan will be included in a wholesale or a piecemeal migration request. The decision for the base product migration plans was to not provide multiple migration plans for various objects (one for wholesale migrations and one for piecemeal migrations). Rather, the base product provided migration plans supports a reasonable piecemeal migration. In general, sub-instructions are not provided for the foreign keys where there is a reasonable assumption that the data already exists in the target region. For example, the migration plan for any record that has a foreign key to Tax Type will not include a sub-instruction for tax type given that tax type is considered a type of “parent” configuration object that would be copied on its own to a region and not as part of the migration of a lower level entity.
To see the migration plans provided with the base product, navigate to
and view the data that is provided there.The following points highlight some information about the base administrative objects and their migration plans.
A small number of administrative maintenance objects include a Log table. Those MOs have been configured to not migrate the log entries (using the Non-Migrated Table MO option).
The Form Change Reason maintenance objects has been configured to not migrate its related form types (using the Non-Migrated Table MO option).
The following objects do not have their own migration plans but rather are included as a sub-instruction in a related object’s migration plan:
Adjustment Type Extension (part of the adjustment type migration plan)
Form Section (part of the form type migration plan)
Form Line (part of the form type migration plan)
Letter Template (part of the customer contact type migration plan)
Revenue Period (part of the revenue calendar migration plan)
Tender source includes an optional reference to a suspense Obligation ID. CMA cannot copy master and transaction data. As a result, the base migration plan includes an import algorithm to not copy the Obligation ID from the source when adding or updating a tender source in the target region. Note that when the tender source already exists in the target region and has a reference to a valid Obligation ID from the target region, any updates to the tender source via CMA will not change the Obligation ID.
Master configuration, service task type and extendable lookup are Framework owned objects, however special migration plans are provided in the base product to define foreign key references in the BO Data Area for some of the base business objects.
Migration plans were not provided for any functionality that is considered “legacy” functionality and therefore not recommended to use going forward for new installations. For example, administrative data related to classic billing, legacy address, case type or DB processes are not provided.
A migration plan is not provided for Activity Type. If an implementation uses this object and wishes to include it in a migration, a custom migration plan is needed.
A migration plan is not provided for Collection Agency. This object comprises of a code, description and Person ID (to represent the agency). Because CMA cannot copy master or transaction data, and Person ID is a required field, this object cannot be copied. An implementation must manually create collection agency records in the target region.
Refer to the detailed descriptions of the base migration plans for more information.
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]