Search Results okc_rep_contract_statuses




Overview
Explore in AI Chat

Overview

OKC.OKC_REP_IMP_CONTRACTS_T is a transient interface table that Oracle E-Business Suite uses during the Contracts Repository import process. It temporarily stores the header-level attributes of contracts being imported from external sources or legacy systems before those records are validated and promoted into the operational Contracts Repository schema. Its role is strictly intermediary: rows are inserted, validated against reference data, staged for insertion into persistent repository tables, and then deleted at the conclusion of each import run. The table resides in the APPS_TS_INTERFACE tablespace, consistent with its short-lived, high-churn workload profile, with a PCTFREE of 10.

Under the heuristic Data Vault classification mined from its foreign-key structure, OKC_REP_IMP_CONTRACTS_T is characterized as a standalone object rather than a hub, link, or satellite. Because the table functions as an import staging area whose contents are purged after each process, this classification is best read as a modeling suggestion: the object carries descriptive and transitional attributes rather than the durable, long-lived relationships typical of a canonical hub or link. Downstream child interface tables (risks, contacts, documents, parties, and errors) reference it via IMP_CONTRACT_ID, forming a short-lived parent-child staging hierarchy during the import window.

Key Information Stored

Although the documented physical schema contains 64 columns, the most significant attributes relate to contract identity, ownership, classification, and status:

Common Use Cases and Queries

Report and diagnostic queries typically target the staging table during or immediately after an import run, before the process deletes its rows. Because REQUEST_ID is indexed, filtering by concurrent request is efficient:

  • Identify rejected contracts: SELECT IMP_CONTRACT_ID, CONTRACT_NUMBER, CONTRACT_STATUS_TXT FROM OKC.OKC_REP_IMP_CONTRACTS_T WHERE VALID_FLAG = 'N' AND REQUEST_ID = :request_id;
  • Reconcile imported status values against the lookup: SELECT CONTRACT_STATUS_CODE, CONTRACT_STATUS_TXT, COUNT(*) FROM OKC.OKC_REP_IMP_CONTRACTS_T WHERE REQUEST_ID = :request_id GROUP BY CONTRACT_STATUS_CODE, CONTRACT_STATUS_TXT;
  • Join to OKC_REP_IMP_ERRORS_T on IMP_CONTRACT_ID to surface validation messages per contract.

Because the table is purged per run, it is unsuitable for historical reporting; persistent status information should be sourced from OKC_REP_CONTRACTS_ALL after promotion.

Related Objects

OKC_REP_IMP_CONTRACTS_T is the parent in the interface hierarchy. The following child tables reference it via IMP_CONTRACT_ID:

The promoted record links to OKC_REP_CONTRACTS_ALL through CONTRACT_ID, while supporting reference data is drawn from OKC_BUS_DOC_TYPES_B, FND_CURRENCIES, and the lookup types OKC_AUTHORING_PARTY and OKC_REP_CONTRACT_STATUSES.