Results for “csi_contacts_mig_interface”

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

Overview

The CSI_CONTACTS_MIG_INTERFACE table is a temporary staging table within the CSI (Install Base) product family in Oracle EBS 12.1.1 and 12.2.2. It serves as the data migration interface for Customer Product Contacts, holding inbound contact records prior to validation and promotion into the permanent Install Base contact structures. Because it is an interface table, it is populated by external extraction routines or conversion programs and is subsequently consumed by migration/import concurrent programs that validate the rows and insert them into the destination CSI tables. Rows that pass validation are marked accordingly, while rejected rows remain for correction and resubmission.

Per the heuristic Data Vault classification provided in the metadata, this object is modeled as a standalone entity. This indicates that it does not participate in a documented foreign-key-dependent hub, link, or satellite pattern at the interface layer — it is an isolated staging structure whose relationships to permanent entities are enforced downstream during the import process rather than at the column level here.

Key Information Stored

The documented physical schema contains three columns, with one unique business-key index and a primary key, as follows:

• CS_CONTACT_ID — The contact identifier for the customer product contact. This column is the primary key (via CSI_CONTACTS_MIG_INTERFACE_PK) and is also the single-column unique index candidate (CSI_CONTACTS_MIG_IF_U01). It is the value most commonly referenced when users search for "cs_contact_id," since it links a staged row back to the contact identity used in the destination Install Base tables.
• CUSTOMER_PRODUCT_ID — Identifies the customer product (the installed base instance) to which the migrated contact applies. This provides the contextual link between the contact record and the specific product installation being tracked.
• MIGRATED_STATUS_FLAG — Indicates the migration processing state of the row (for example, whether it has been staged, validated, or successfully promoted). This drives selection logic in the import concurrent program.

The primary key here is the surrogate/business identifier CS_CONTACT_ID; no separate system-generated sequence key is documented beyond that column. The unique index simply reinforces the uniqueness of the contact identifier within the staging set.

Common Use Cases and Queries

The principal use case is pre- and post-migration validation. Typical queries include checking for duplicate contact identifiers before submitting the import program, and reviewing rows that remain unprocessed.

SELECT cs_contact_id, customer_product_id, migrated_status_flag
FROM   csi.csi_contacts_mig_interface
WHERE  migrated_status_flag IS NULL;

Reporters commonly reconcile staged records against successfully imported contacts using CS_CONTACT_ID as the join key. A second scenario detects duplicate or conflicting contact identifiers within the interface set:

SELECT cs_contact_id, COUNT(*)
FROM   csi.csi_contacts_mig_interface
GROUP  BY cs_contact_id
HAVING COUNT(*) > 1;

Because the table is a staging structure, standard practice is to extract, validate, and purge rows after a successful migration cycle to prevent stale data from affecting subsequent runs.

Related Objects

The interface table is processed by CSI Install Base migration and import routines and ultimately feeds permanent contact and install base structures. The most significant related objects include:

• CSI_ITEM_INSTANCES — The installed base instance records; related by CUSTOMER_PRODUCT_ID context to the customer product.
• CSI_CONTACTS / CSI_INSTANCE_CONTACTS — Permanent contact destination tables receiving validated rows keyed by CS_CONTACT_ID.
• HZ_CONTACTS / HZ_CONTACT_POINTS — TCA contact entities that anchors the contact identities referenced by CS_CONTACT_ID.
• CS_CONTACTS_MIG_INTERFACE_PK and CS_CONTACTS_MIG_IF_U01 — The primary key constraint and unique index enforcing contact identifier integrity.
• CSI Migration/Import Concurrent Programs — The PL/SQL processes that read this interface table and load downstream destinations.