Search Results oki_sales_k_headers_v




Overview
Explore in AI Chat

Overview

OKI_SALES_K_HEADERS_V is a reporting view belonging to the OKI (Contracts Intelligence) product family, a module that Oracle has designated as obsolete in Oracle E-Business Suite 12.1.1 and 12.2.2. The view exposes contract header information specifically filtered to contracts that carry a sell intent, providing a denormalized, query-friendly representation of sales-oriented contract data. Its primary purpose is to support analytical reporting and integration scenarios where sell-side contracts must be summarized by category, status, party, amount, and lifecycle dates without requiring the reporting layer to join the numerous underlying header and lookup tables directly.

The presence of STATUS_TYPE_CODE in the column list is significant, as this identifier is the attribute most frequently used to classify contracts along their lifecycle — for example distinguishing active, terminated, canceled, or expired contracts. Reporting consumers typically reference this column in filters and groupings to segment sales contracts by lifecycle state.

Underlying Base Objects

According to the ETRM metadata, no base objects are formally documented for this view, and the implementation is not present in the reference database. The view text, however, reveals the driving table as an alias SHD, which is the sales contract header table that supplies the majority of columns, including CHR_ID, CONTRACT_NUMBER, AUTHORING_ORG_ID, and all amount and date fields. Three lookup tables are joined to translate coded values into descriptive meanings:

The view therefore serves as a single join point that flattens contract header attributes together with their associated lookup descriptions, a common pattern in Contracts Intelligence reporting objects.

Key Columns

The view exposes several logical groupings of columns. Identifying attributes include CONTRACT_ID, CONTRACT_NUMBER, CONTRACT_NUMBER_MODIFIER, and COMPLETE_CONTRACT_NUMBER, along with AUTHORING_ORG_ID and ORGANIZATION_NAME. Classification attributes include CATEGORY_CODE/CATEGORY_MEANING and STATUS_CODE/STATUS_MEANING.

The STATUS_TYPE_CODE and its companion STATUS_TYPE_MEANING are the principal lifecycle descriptors, while TERMINATION_MEANING provides termination context. Party information is supplied through CUSTOMER_PARTY_ID and CUSTOMER_NAME. Financial measures include CONTRACT_AMOUNT, FORECAST_AMOUNT, CONTRACT_AMOUNT_RENEWED, and their set-of-books and base-currency equivalents, each defaulted to zero via NVL. Lifecycle dates include START_DATE, END_DATE, DATE_APPROVED, DATE_SIGNED, DATE_RENEWED, DATE_CANCELED, DATE_TERMINATED, and EXPECTED_CLOSE_DATE. Period, quarter, and year columns support time-based analytics, and the attribute columns provide descriptive flexibility. A documented defect maps ATTRIBUTE2 through ATTRIBUTE7 to the same source as ATTRIBUTE1, which should be accounted for in any query relying on descriptive flexfield attributes.

Common Use Cases and Queries

Typical usage includes sales pipeline reporting, contract lifecycle analysis, and revenue forecasting by organization or customer. A representative query grouping contracts by status type is:

  • SELECT STATUS_TYPE_CODE, STATUS_TYPE_MEANING, COUNT(*) FROM OKI_SALES_K_HEADERS_V GROUP BY STATUS_TYPE_CODE, STATUS_TYPE_MEANING;
  • SELECT CONTRACT_NUMBER, CUSTOMER_NAME, CONTRACT_AMOUNT FROM OKI_SALES_K_HEADERS_V WHERE STATUS_TYPE_CODE = :p_status_type;
  • SELECT START_YEAR, START_QUARTER, SUM(BASE_CONTRACT_AMOUNT) FROM OKI_SALES_K_HEADERS_V GROUP BY START_YEAR, START_QUARTER;

Because the module is obsolete, consumers should treat the view as read-only, avoid dependencies on the duplicated attribute columns, and validate column behavior against the actual database release prior to production reporting.