Migrating Configuration Data

A main use of CMA is to migrate configuration data, where the source environment is considered a kind of system of record and the target environment is getting updates based on changes to the source environment. Alternatively you may be seeding a new environment. The expectation is that the target record is updated to look like the source record.

Configuration data may include a mixture of records that have an owner flag and ones that do not. The comparison step of the import process will generate appropriate insert or update SQL statements for the following data found in the export:

• Configuration data in a maintenance object with no owner flag. This is purely implementation data.
• Configuration data in a maintenance object with owner flag, where the owner is Customer Modification. For example, implementer-specific business objects.
• Configuration data in a maintenance object with owner flag, where the main record is owned by the product but where a child record exists with an owner of Customer Modification. For example, implementer-specific algorithms added to a base owned business object.
• Customizable fields in a record that is owned by the product. For example, the priority of a based owned To Do type.