Results for “csi_parameters_mig_interface”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CSI_PARAMETERS_MIG_INTERFACE is a temporary staging table in the CSI (Install Base) product schema of Oracle E-Business Suite, documented as VALID in both release 12.1.1 and 12.2.2. Its described purpose is to hold Customer Product Parameters data migration interface records — that is, the transient set of install base parameter rows collected from a legacy or external source before they are validated and promoted into the permanent CSI install base structures. Because it is a migration interface object, records are expected to have a short lifecycle: they are loaded, checked, consumed by a concurrent program or API, and then removed or archived. The table is not a transactional or reference entity used at runtime by end-user forms; it exists to support data conversion and onboarding activities.

The supplied metadata classifies the object heuristically as standalone in Data Vault terms, and none of its documented columns participate in a foreign-key relationship. As a modeling suggestion, this makes it a candidate satellite-like staging object rather than a hub or a link: it carries descriptive payload (status, parameter identity) with no mined dependency edges to other entities. Any relationship to the real install base model is therefore established by application logic during the migration process, not by declarative constraints.

Key Information Stored

The documented physical schema for 12.2.2 shows only two columns, so the table's information content is deliberately narrow. The essential columns are:

• CP_PARAMETER_ID — the single documented column identifying the customer product parameter being migrated. It is the target of the primary key constraint CSI_PARAMETERS_MIG_IF_PK and is also the business-key candidate exposed through the unique index CSI_PARAMETERS_MIG_IF_U01. In practice this value is the surrogate identifier assigned to, or carried forward for, the parameter row in the interface, and it is the column most frequently used in filtering and lookup queries — which is consistent with the user's search on "cp_parameter_id".
• MIGRATED_STATUS_FLAG — the processing status of the interface row, indicating whether the record is pending, processed, or otherwise excluded from the migration run. This flag drives the selection logic of the migration program and is the primary column used to stage and re-drive failed rows.

Because the primary key and the unique index both resolve to CP_PARAMETER_ID, the surrogate key and the business key are effectively the same attribute here. Note that the ETRM excerpt documents only these two columns; additional descriptive attributes such as parameter name, value, or owning product instance are not evidenced in the supplied metadata and should be confirmed against the deployed table definition before being relied upon in code.

Common Use Cases and Queries

Typical usage centres on monitoring and troubleshooting a conversion run. Operational queries check how many rows remain unprocessed, or locate a specific record by identifier:

• Counting outstanding work: SELECT COUNT(*) FROM csi.csi_parameters_mig_interface WHERE migrated_status_flag = 'N';
• Point lookup by the searched key: SELECT cp_parameter_id, migrated_status_flag FROM csi.csi_parameters_mig_interface WHERE cp_parameter_id = :cp_parameter_id;
• Reconciliation of loaded versus processed volumes prior to a migration program's restart.

Reporting against this table is strictly diagnostic and time-bounded. It should not be used as a source for install base reporting after the conversion is complete, because the interface rows are transient; historical reporting should read the corresponding permanent CSI tables instead.

Related Objects

On the evidence supplied, the table is standalone with no mined FK edges, so related objects are established by functional role rather than by constraints:

• CSI_PARAMETERS_MIG_IF_PK — the primary key constraint enforcing uniqueness of CP_PARAMETER_ID.
• CSI_PARAMETERS_MIG_IF_U01 — the unique index on CP_PARAMETER_ID, acting as the business-key candidate.
• CSI_ITEM_INSTANCES — the install base instance entity whose parameters the interface rows ultimately populate.
• CSI_ITEM_INSTANCE_PARAMETERS — the permanent parameter store that receives validated interface data.
• CSI_INSTANCE_MIG_INTERFACE and companion CSI migration interface tables — sibling staging objects loaded in the same conversion batch.
• CSI_parameters public APIs and install base concurrent programs — the consumers that read these rows, set MIGRATED_STATUS_FLAG, and delete or archive processed records.

All joins to these objects are logical and must be coded explicitly using CP_PARAMETER_ID or the associated instance identifier; no database-enforced relationship exists.