Search Results okc_launch_khist_grid_v




Overview
Explore in AI Chat

Overview

OKC_LAUNCH_KHIST_GRID_V is a database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the OKC — Contracts Core product family within the Oracle EBS Trade Management (formerly ETRM/OKS/OKC) module stack. The view exists specifically to populate the Contract Status Change History grid on the Launchpad Overview tab of the Contract authoring user interface. Rather than exposing raw contract history records, it presents a presentation-ready, language-aware result set in which internal status codes, lookup codes, and numeric identifiers have been resolved into human-readable meanings suitable for grid display.

From a reporting and integration standpoint, the view is valuable because it centralizes the join logic required to translate the OKC_K_HISTORY_B status history table into descriptive text. Analysts and integration developers frequently reuse it as a source for contract lifecycle reporting, audit extracts, and OAF-based customizations that need to reproduce the Launchpad history experience without reverse-engineering the underlying joins.

Underlying Base Objects

The view is defined over a set of base objects documented in the ETRM metadata: FND_USER, OKC_K_HISTORY_B, OKC_K_HISTORY_TL, OKC_STATUSES_TL (referenced twice), and FND_LOOKUPS (referenced four times). The metadata also lists FND_GLOBAL (PACKAGE) and OKC_K_LINES_B as referenced objects that support the view's runtime behavior.

  • OKC_K_HISTORY_B — the primary transactional table holding each contract status change event, keyed by ID and joined to its translated text.
  • OKC_K_HISTORY_TL — the translation table supplying the free-text COMMENTS column, filtered by the session language.
  • OKC_STATUSES_TL — joined twice (aliases ST1 and ST2) to translate the from-status and to-status codes into descriptive status meanings.
  • FND_LOOKUPS — joined four times (aliases FND, FND2, FND3, FND4) to resolve reason codes and the manual indicator. Lookup types used include OKC_STS_CHG_REASON, OKC_TERMINATION_REASON, YES_NO, and OKS_CANCEL_REASON.
  • FND_USER — supplies the USER_NAME of the person who created the history record.
  • FND_GLOBAL — provides session context, including the language setting used throughout the joins.

All lookup joins are outer joins (indicated by the (+) operator), ensuring history rows are returned even when a lookup code is missing.

Key Columns

  • ID — unique identifier of the status history record from OKC_K_HISTORY_B.
  • CHR_ID — identifier of the contract header to which the history event belongs.
  • CLE_ID — contract line identifier associated with the event.
  • CREATION_DATE — timestamp of the status change.
  • FROM_STATUS — translated description of the prior status (from OKC_STATUSES_TL alias ST1).
  • TO_STATUS — translated description of the new status (from OKC_STATUSES_TL alias ST2).
  • REASON_MEANING — decoded reason text, using termination, status change, or cancellation lookups depending on context.
  • COMMENTS — free-text notes from OKC_K_HISTORY_TL.
  • CONTRACT_VERSION — version of the contract at the time of the change.
  • MANUAL_YN — YES/NO meaning indicating whether the change was performed manually.
  • USER_NAME — the application user who performed the change.

Common Use Cases and Queries

Typical uses include contract audit reports, lifecycle dashboards, and troubleshooting status transitions for a specific contract.

SELECT id, chr_id, creation_date, from_status, to_status,
       reason_meaning, user_name, contract_version
FROM   apps.okc_launch_khist_grid_v
WHERE  chr_id = :contract_id
ORDER  BY creation_date DESC;

To summarize manual versus automatic changes by user:

SELECT user_name, manual_yn, COUNT(*)
FROM   apps.okc_launch_khist_grid_v
GROUP  BY user_name, manual_yn;

Because the view honors USERENV('LANG'), results are automatically returned in the session language, making it directly suitable for localized reporting and OAF grid rendering without additional translation logic.