Results for “csi_statuses_mig_interface”
24 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
CSI_STATUSES_MIG_INTERFACE is a temporary staging table owned by the CSI schema within the Oracle E-Business Suite Install Base (CSI) module. Its documented purpose is to support the migration of Customer Product Statuses data — the status values applied to customer products (instances) tracked in the Install Base — into the production CSI data model. In Oracle EBS 12.1.1 and 12.2.2, migration utilities and conversion scripts for Install Base frequently rely on interface tables of this kind to receive externally sourced or legacy data, validate it, and then push it into the base tables via concurrent programs or PL/SQL APIs. Because this object is described as holding temporary data, rows are generally short-lived, existing only for the duration of a migration or conversion run.
From a modeling perspective, the ETRM metadata classifies this object heuristically as standalone under the Data Vault scheme. This suggests that, in dimensional or Data Vault modeling terms, it does not behave as a hub, link, or satellite but rather as an independent staging or work table. No foreign-key dependencies were mined from the documented structure, reinforcing the observation that it serves as a landing area for data prior to validation and load, rather than as an integrated member of the operational relationship network.
Key Information Stored
The documented physical schema for release 12.2.2 records two columns, and the primary key is named CSI_STATUSES_MIG_INTERFACE_PK.
- CUSTOMER_PRODUCT_STATUS_ID — The single documented key column, forming the primary key CSI_STATUSES_MIG_INTERFACE_PK. It also appears in the unique index CSI_STATUSES_MIG_IF_U01, making it both the surrogate primary key and the sole documented business-key candidate. In the CSI model, this identifier corresponds to the identifier of a customer product status record, the value that will ultimately be assigned in the production statuses table.
- MIGRATED_STATUS_FLAG — A processing flag used to track whether the row has been processed and migrated into the destination structure. Flags of this type in CSI interface tables are typically set or cleared by the migration program so that already-processed rows are not reprocessed on a subsequent run.
Because the documented column count is limited to two, the table should be regarded as a minimal interface object. In practice, an interface table of this nature may also be accompanied by unlisted technical columns (for example, creation and update audit columns or request identifiers), but only the two columns above are confirmed in the ETRM metadata. The ID column is the definitive link to the destination record; the flag column governs migration lifecycle state.
Common Use Cases and Queries
The primary use case is Install Base conversion: legacy or external customer product status data is loaded into CSI_STATUSES_MIG_INTERFACE, validated, and then written to the production status structure. Typical operational and reporting queries include:
- Counting pending versus completed work:
SELECT MIGRATED_STATUS_FLAG, COUNT(*) FROM CSI.CSI_STATUSES_MIG_INTERFACE GROUP BY MIGRATED_STATUS_FLAG; - Identifying unprocessed rows prior to rerunning a migration:
SELECT CUSTOMER_PRODUCT_STATUS_ID FROM CSI.CSI_STATUSES_MIG_INTERFACE WHERE MIGRATED_STATUS_FLAG IS NULL OR MIGRATED_STATUS_FLAG = 'N'; - Checking for duplicate or conflicting staging rows by key:
SELECT CUSTOMER_PRODUCT_STATUS_ID, COUNT(*) FROM CSI.CSI_STATUSES_MIG_INTERFACE GROUP BY CUSTOMER_PRODUCT_STATUS_ID HAVING COUNT(*) > 1; - Validating that staged identifiers resolve to existing destination records before promoting the rows, which supports reconciliation reporting during a conversion.
Because the table is a work area, queries against it are best confined to migration windows; it is not intended as a long-term reporting source.
Related Objects
The documented metadata shows no foreign-key relationships, so related-object guidance is inferential rather than confirmed:
- CSI_ITEM_INSTANCES — Install Base instance table whose status is the ultimate migration target.
- CSI_STATUSES_MIG_INTERFACE_PK / CSI_STATUSES_MIG_IF_U01 — The primary key constraint and unique index defined on CUSTOMER_PRODUCT_STATUS_ID within this same table.
- Destination customer product status structure in the CSI schema, keyed on the same CUSTOMER_PRODUCT_STATUS_ID value.
- Install Base migration/concurrent programs that read the staging rows and set MIGRATED_STATUS_FLAG upon completion.
- Other CSI interface tables used in the same conversion, such as related item instance and status history staging objects.
These objects should be treated as candidate dependencies; the sole documented, definitively verifiable relationships are the internal primary key and unique index on CUSTOMER_PRODUCT_STATUS_ID.
-
Customer Product Statuses data Migration Interface (temporary data).
-
Customer Product Statuses data Migration Interface (temporary data).
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - CSI Tables and Views 12.1.1
Temporary table that holds the unprocessed XNP messages during data correction process.
-
eTRM - CSI Tables and Views 12.2.2
Temporary table that holds the unprocessed XNP messages during data correction process.
-
eTRM - CSI Tables and Views 12.1.1
Temporary table that holds the unprocessed XNP messages during data correction process.
-
12.2.2 DBA Data 12.2.2
-
eTRM - CSI Tables and Views 12.2.2
Temporary table that holds the unprocessed XNP messages during data correction process.
-
12.1.1 DBA Data 12.1.1