Data migration flow on RIA Docs

CX Tables

Mon, 01 Jan 0001 00:00:00 +0000

CI Views

The STGADM schema has the same table structures as CISADM. For example, the CI_ACCT table in STGADM is identical to the CI_ACCT table in CISADM.

When mapping from legacy source tables to the OUAF application’s target tables, the tool must generate the new primary key values and link them to their respective legacy values. A specific set of CX staging tables is utilized to facilitate this process. These tables closely resemble their CI counterparts but include an additional CX primary ID. For child tables, there is also a CX foreign key that links to the parent CX row. The CX IDs are defined with a VARCHAR2(128) data type, which provides ample space for any legacy key value and allows for the concatenation of legacy values to create unique keys if needed. To create a CX table, see create_cx_table in the Miscellaneous procedures.

CI tables

Mon, 01 Jan 0001 00:00:00 +0000

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.