CI tables

CI_K tables

Every CI table with a generated primary ID has a corresponding K table, which holds that generated ID. The K tables do not have equivalent CX tables but have an environment ID, ENV_ID, used by unrelated configuration migration functionality in OUAF. The ENV_ID column can be populated from the ENV_ID column in the F1_INSTALLATION table.

The K tables keep track of all generated IDs, including for those objects that have been archived, to ensure that no new IDs are generated that could cause conflicts with archived objects that may need to be unarchived in the future. The DIH tool and the OUAF application check this table to safeguard against duplicates when generating new IDs. So, if you are converting into an already populated database, such as during a phased conversion, the contents of the K tables must be copied from the CISADM schema to the STGADM schema.

CI config tables

Most importantly, when using services to convert data, the configuration tables that define the OUAF application’s setup must be copied from the CISADM to the STGADM schema before the conversion can be successfully executed. These include CI_LOOKUP_VAL lookup tables, characteristic type tables, metadata tables, and rate configuration tables for billing.