Search Results okc_rep_imp_contacts_n1

Overview

OKC.OKC_REP_IMP_CONTACTS_T is a staging (interface) table within the Oracle Contracts (OKC) module of Oracle E-Business Suite. It serves as an intermediate repository for contact-level data extracted from external sources or upstream Oracle applications before that data is validated and promoted into the production contact and party-role tables. In the context of Oracle EBS 12.1.1 and 12.2.2, such interface tables are populated by concurrent programs—commonly the Contracts repository import or bulk migration routines—and are keyed by a REQUEST_ID and RUN_ID so that individually loaded batches can be audited, reconciled, or purged.

From a Data Vault modeling perspective, the table is classified heuristically as a satellite. It records descriptive attributes about contacts and their role assignments in the context of an import request, and it does not itself define independent business hubs. Reusable business keys such as PARTY_ID and CONTRACT_ID are carried as descriptive columns rather than being resolved into hub structures at load time.

Key Information Stored

The physical schema documents twenty columns. The most operationally significant are:

• IMP_CONTACT_ID — Surrogate primary key of the staging row and the single column of the unique index OKC_REP_IMP_CONTACTS_T_U1.
• IMP_PARTY_ID and IMP_CONTRACT_ID — Foreign keys to OKC_REP_IMP_PARTIES_T and OKC_REP_IMP_CONTRACTS_T respectively, anchoring the contact to its imported party and contract.
• PARTY_ID, PARTY_ROLE_CODE, PARTY_ROLE_TXT, and PARTY_NAME_TXT — The resolved or source-party role and name information used during validation.
• CONTRACT_ID — The target contract identifier once the contact is associated.
• CONTACT_ID, CONTACT_NAME, CONTACT_ROLE_ID, and CONTACT_ROLE_TXT — Contact identity and role description carried through the interface.
• CONTACT_INDEX — Sequencing or ordinal value distinguishing multiple contacts within a single import batch.
• REQUEST_ID and RUN_ID — Concurrent request and run identifiers used for batch control and the nonunique index OKC_REP_IMP_CONTACTS_N1.
• VALID_FLAG — Validation status indicating whether a staged row is eligible for promotion into the production tables.
• CREATION_DATE and the PROGRAM_ID / PROGRAM_LOGIN_ID / PROGRAM_APPLICATION_ID audit columns — Standard EBS who/whom audit attributes.

Common Use Cases and Queries

Typical scenarios involve reconciling an import run, diagnosing rejected rows, or reporting on contacts staged for a contract. Because the unique index is on IMP_CONTACT_ID, lookups by business identifier should join to the party or contract staging tables rather than query the surrogate key.

To inspect a specific import request:

SELECT IMP_CONTACT_ID, IMP_PARTY_ID, IMP_CONTRACT_ID,
       CONTACT_NAME, CONTACT_ROLE_TXT, VALID_FLAG
FROM   OKC.OKC_REP_IMP_CONTACTS_T
WHERE  REQUEST_ID = :request_id
AND    NVL(VALID_FLAG,'N') = 'N';

To trace a staged contact back to its originating party and contract:

SELECT c.CONTACT_NAME, c.PARTY_ROLE_CODE, c.CONTRACT_ID,
       p.PARTY_NAME_TXT
FROM   OKC.OKC_REP_IMP_CONTACTS_T c,
       OKC.OKC_REP_IMP_PARTIES_T  p
WHERE  c.IMP_PARTY_ID = p.IMP_PARTY_ID
AND    c.REQUEST_ID   = :request_id;

Reporting use cases include pre-import validation dashboards, batch success-rate metrics grouped by RUN_ID, and duplicate-contact detection using CONTACT_INDEX within a contract.

Related Objects

The documented dependencies establish the following significant relationships:

• OKC_REP_IMP_PARTIES_T — Parent staging party table; joined via IMP_PARTY_ID.
• OKC_REP_IMP_CONTRACTS_T — Parent staging contract table; joined via IMP_CONTRACT_ID.
• OKC_REP_IMP_CONTACTS_T# — The dependent object listed in the dependency report that references this table.
• OKC_REP_IMP_CONTACTS_T_U1 — Unique index on IMP_CONTACT_ID, enforcing row identity.
• OKC_REP_IMP_CONTACTS_N1 — Nonunique index on REQUEST_ID, optimizing batch-level access.
• Production contact and party-role tables within the OKC schema (for example, contact and contact-role entities) that receive promoted rows once VALID_FLAG is set.

These relationships make OKC_REP_IMP_CONTACTS_T the contact-resolution layer of the Contracts import pipeline, bridging upstream party data and downstream contract contact records.