Search Results currency_code_renewed




Overview
Explore in AI Chat

Overview

APPS.OKC_GOVERNING_CONTRACT_V is a view in the Oracle E-Business Suite Contracts Core (OKC) module that exposes the hierarchy of sales contracts. It is owned by the APPS schema and, in the Oracle EBS 12.1.1 and 12.2.2 releases, is documented with a status of VALID, although the ETRM metadata explicitly states that the view has been obsoleted. This designation means the object remains physically present and queryable in many environments but is no longer the recommended interface for new development; it is retained primarily for backward compatibility with pre-existing customizations, reports, and integrations.

Functionally, the view consolidates header-level contract attributes with translated descriptive text and selected rule-based derivations, most notably the billing customer account. Because it flattens the governing-contract relationship into a single rowset, it is typically used for reporting on which contract governs a given sales agreement, for integration extracts that must carry a stable contract identifier plus descriptive and status context, and for ad hoc analysis of contract lifecycle dates.

Underlying Base Objects

The view is defined over the following documented base objects in the APPS schema:

  • OKC_K_HEADERS_B — the main contracts header table (aliased CHRB), supplying identifiers, status, dates, currency, amounts, and descriptive flexfield (attribute) columns.
  • OKC_K_HEADERS_TL — the translated header text table (aliased CHRT), supplying SHORT_DESCRIPTION, COMMENTS, and DESCRIPTION.
  • OKC_RULES_B and OKC_RULE_GROUPS_B — used in a correlated subquery against rule group code 'BILLING' and rule information category 'CAN' to derive the customer account.
  • OKC_SUBCLASSES_B — referenced in the view definition for subclass classification.
  • OKC_UTIL — the package whose GET_K_ACCESS_LEVEL function computes the caller's access level.

The header-centric relationship is explicit: every row is driven by a record in OKC_K_HEADERS_B, with translation, rule, and utility results joined or computed per header. This is consistent with the view's stated purpose of presenting the sales contract hierarchy.

Key Columns

Common Use Cases and Queries

Typical uses include reporting the active governing contract for a customer, extracting contract metadata for downstream systems, and reconciling contract status against lifecycle dates. A representative query listing governed sales contracts with key dates is:

SELECT CONTRACT_NUMBER,
       CONTRACT_NUMBER_MODIFIER,
       STS_CODE,
       START_DATE,
       END_DATE,
       DATE_SIGNED,
       DATE_APPROVED,
       CURRENCY_CODE,
       ESTIMATED_AMOUNT,
       CUSTOMER_ACCOUNT_ID
FROM   APPS.OKC_GOVERNING_CONTRACT_V
WHERE  GOVERNING_CONTRACT_YN = 'Y'
AND    BUY_OR_SELL = 'S'
AND    NVL(DATE_TERMINATED, SYSDATE + 1) > SYSDATE;

Because the view is documented as obsoleted, new development should query the underlying OKC_K_HEADERS_B and OKC_K_HEADERS_TL tables directly, joining the required detail tables to supply any missing attributes such as pricing context. Existing queries against this view should be reviewed during upgrades to 12.2.2 to confirm that no column-level changes affect results, and access to the view should be limited in line with the USER_ACCESS_LEVEL value it computes.