Results for “oki_sales_k_hdrs_u2”

5 results




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

Overview

OKI.OKI_SALES_K_HDRS is a denormalized table within the Oracle E-Business Suite Contracts Intelligence (OKI) schema. It stores contract headers and related attribute information strictly for contracts of the sell intent. The table is populated and maintained by the Load Sales Contract Headers, Contracts Intelligence concurrent manager job. Only contracts that carry the sell intent and are not templates qualify for inclusion. During the load process, some currency conversion is performed: the contract currency is converted to a base currency, defined by the profile option OKI_BASE_CURRENCY_CODE, to accelerate display in HTML bins. If no conversion rate exists between the contract currency and the base currency, the contract is excluded from the table entirely.

The object is stored in the APPS_TS_TX_DATA tablespace with PCT Free of 10. It is registered in FND Design Data as OKI.OKI_SALES_K_HDRS and holds 92 documented columns. Based on the FK structure, a Data Vault modeling suggestion classifies this table as standalone; it does not exhibit the hub, link, or satellite patterns typical of normalized Data Vault constructs, reflecting its nature as a reporting-oriented denormalized store.

Key Information Stored

The table is anchored by the surrogate primary key CHR_ID (NUMBER), which holds the internal contract header identifier. Two unique indexes establish business-key candidates: OKI_SALES_K_HDRS_U1 on CHR_ID, and OKI_SALES_K_HDRS_U2 on the composite of CONTRACT_NUMBER and CONTRACT_NUMBER_MODIFIER. The most significant columns include:

Common Use Cases and Queries

Because OKI_SALES_K_HDRS is denormalized for reporting, it is frequently queried directly rather than joined across normalized contract tables. A common scenario is retrieving newly created sell contracts:

  • Filtering new contracts: SELECT CONTRACT_NUMBER, CUSTOMER_NAME, CONTRACT_AMOUNT FROM OKI.OKI_SALES_K_HDRS WHERE IS_NEW_YN = 'Y'.
  • Current-version reporting: constrain on IS_LATEST_YN = 'Y' to avoid duplicate rows for versioned contracts.
  • Date-range reporting on active contracts, using the indexes on START_DATE, END_DATE, and CLOSE_DATE.
  • Currency-consistent aggregation using BASE_CONTRACT_AMOUNT and BASE_CURRENCY_CODE, which avoids runtime conversion.
  • Customer-centric dashboards joining on CUSTOMER_PARTY_ID or filtering by CUSTOMER_NAME.

Related Objects

The table has documented foreign key relationships and is referenced alongside several key objects:

  • FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID for access control filtering.
  • MTL_INV_PICKING_RULES — joined via INV_RULE_ID for inventory picking rule context.
  • PN_PAYMENT_TERMS_ALL — joined via PAYMENT_TERM_ID for payment term information.
  • OKI_SALES_K_LINES — the line-level counterpart typically joined on contract identifiers to build header-to-line reports.
  • The Load Sales Contract Headers, Contracts Intelligence concurrent program — the source process that refreshes this table.
  • The profile option OKI_BASE_CURRENCY_CODE — governs whether a contract qualifies for inclusion.