Search Results okc_rep_imp_contacts_t

Overview

OKC_REP_IMP_CONTACTS_T is an interface (staging) table in the OKC – Contracts Core module of Oracle E-Business Suite. It belongs to the repository import facility that loads external contract, party, and contact data into the Contracts repository through the standard import programs. Records are written into this table by external feeders or conversion routines, validated and processed by concurrent programs within OKC, and then merged into the permanent contract repository tables. The table holds one row per contact associated with an imported party and, where applicable, with an imported contract.

Under the heuristic Data Vault classification mined from the foreign key structure, this object is treated as a standalone table. The classification is a modeling suggestion only: although the table carries foreign keys to OKC_REP_IMP_PARTIES_T and OKC_REP_IMP_CONTRACTS_T, it does not resolve cleanly into a canonical hub, link, or satellite pattern because it is a transient staging structure rather than a persistent warehouse entity. Its natural affinity in Data Vault terms would be a link-satellite construct joining contract and party hubs at a point in time, but the documented FK analysis does not assign it to that category.

Key Information Stored

The table contains 20 documented columns. The most significant are:

• IMP_CONTACT_ID – surrogate primary key for the import row; it is also the single documented unique index candidate (OKC_REP_IMP_CONTACTS_T_U1) and therefore the business-key candidate within the interface.
• IMP_PARTY_ID – foreign key to OKC_REP_IMP_PARTIES_T; identifies the imported party that owns the contact.
• IMP_CONTRACT_ID – foreign key to OKC_REP_IMP_CONTRACTS_T; links the contact to an imported contract when the contact is contract-specific.
• CONTACT_INDEX – ordinal position of the contact within the imported party or contract record set.
• CONTRACT_ID and PARTY_ID – target identifiers in the production Contracts repository, populated or resolved during import processing.
• PARTY_ROLE_CODE and PARTY_ROLE_TXT – coded and descriptive values of the party's role on the contract.
• PARTY_NAME_TXT – the party name as supplied by the source system for matching and reporting.
• CONTACT_NAME – the name of the contact person or point of contact being imported.
• CONTACT_ROLE_TXT and CONTACT_ROLE_ID – textual and coded role assigned to the contact.
• CONTACT_ID – the resolved or target contact identifier in the repository.
• VALID_FLAG – validation status used by the import process to determine whether the row may be processed.
• REQUEST_ID and RUN_ID – concurrent request and run identifiers that group the rows belonging to a single import execution.
• CREATION_DATE, PROGRAM_ID, PROGRAM_LOGIN_ID, and PROGRAM_APPLICATION_ID – standard audit columns recording when and by which program the row was created.

Common Use Cases and Queries

Typical uses include diagnosing import failures, auditing which contacts were staged for a given run, and reconciling interface rows against the permanent repository. A representative query retrieves all contacts for 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;

Validation reporting identifies rows that failed pre-processing:

SELECT c.imp_contact_id, c.party_name_txt, c.contact_name, c.valid_flag
FROM okc.okc_rep_imp_contacts_t c
WHERE c.valid_flag = 'N';

Joining to the parent staging tables provides a complete picture of the imported contract–party–contact hierarchy:

SELECT ct.imp_contract_id, p.party_name_txt, c.contact_name
FROM okc.okc_rep_imp_contacts_t c,
     okc.okc_rep_imp_parties_t p,
     okc.okc_rep_imp_contracts_t ct
WHERE c.imp_party_id = p.imp_party_id
  AND c.imp_contract_id = ct.imp_contract_id;

Related Objects

• OKC_REP_IMP_PARTIES_T – referenced by OKC_REP_IMP_CONTACTS_T.IMP_PARTY_ID; the parent staged party record.
• OKC_REP_IMP_CONTRACTS_T – referenced by OKC_REP_IMP_CONTACTS_T.IMP_CONTRACT_ID; the parent staged contract record.
• OKC_CONTACTS – the permanent Contracts repository table into which validated contact rows are ultimately merged.
• OKC_REP_IMP_CONTACT_ROLES_T – role assignments associated with imported contacts, when present in the repository import schema.
• OKC_REP_IMP_CONTACT_POINTS_T – contact point (address, phone, e-mail) staging rows linked to imported contacts.
• OKC_REP_IMP_ERRORS_T – error log populated by the import programs for rows, including contacts, that fail validation.
• OKC_REP_IMP_CONTRACTS_ALL_T and related repository import views – reporting views over the OKC import schema.
• Contracts Repository Import concurrent programs – the OKC/OKL processes that read this table, validate each row, and load the resolved CONTACT_ID, PARTY_ID, and CONTRACT_ID values.