Search Results oks_cancel_reason

Overview

APPS.OKC_LAUNCH_KHIST_GRID_V is a supplementary Oracle E-Business Suite view owned by the APPS schema and registered in FND Design Data as OKC.OKC_LAUNCH_KHIST_GRID_V. Its status is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. Oracle classifies this object as a supplementary view intended to simplify forms coding. The ETRM metadata carries an explicit warning: Oracle does not recommend querying or altering data through this view, since its definition may change dramatically in subsequent minor or major releases.

The object presents contract launch key-history records in a flattened, grid-oriented format suitable for display in an Oracle Forms block. The view joins header-level launch history with translated history rows, status translations, line information, and user/quickcode lookups, so consumers see meaningful values (reason meanings, status descriptions, user names) rather than raw code identifiers. Because it is a forms-support view rather than a public interface, it should be treated as a read-only presentation layer over the underlying contract launch history data.

Underlying Base Objects

The documented dependencies for OKC_LAUNCH_KHIST_GRID_V are:

• OKC_K_HISTORY_B — the base contract key-history table holding status change events.
• OKC_K_HISTORY_TL — the translation table supplying language-specific history attributes.
• OKC_K_LINES_B — the contract lines base table, joined for line-level context.
• OKC_STATUSES_TL — translated status definitions resolving FROM_STATUS and TO_STATUS codes.
• FND_LOOKUPS — the Oracle Application Object Library lookup view, supplying quickcode meanings such as REASON_MEANING.
• FND_USER (synonym) — the application user repository resolving USER_NAME.
• FND_GLOBAL (package) — supplies runtime session context such as the current user and language.

The view is not referenced by any other database object, confirming it is a terminal consumer of these base objects rather than a dependency of downstream code.

Key Columns

• ID, CHR_ID, CLE_ID — Numeric identifiers linking the row to its contract history record and associated line context.
• CREATION_DATE — Date the history record was created; the primary chronological attribute for change tracking.
• FROM_STATUS, TO_STATUS — The status transition captured by the history event, each VARCHAR2(90).
• REASON_MEANING — VARCHAR2(80) quickcode meaning, typically the user-facing reason for the status change.
• COMMENTS — VARCHAR2(4000) free-text user-entered comment on the change.
• CONTRACT_VERSION — VARCHAR2(24) contract version associated with the history record.
• MANUAL_YN — VARCHAR2(80) indicator of whether the change was applied manually rather than through automated processing.
• USER_NAME — VARCHAR2(100) application user who performed the change.
• CHANGE_LEVEL — VARCHAR2 flag identifying the level at which the change occurred (for example header or line scope), which is the column most directly relevant to change-level reporting.
• LINE_NUMBER — VARCHAR2(301) line identifier presented for grid display.

Common Use Cases and Queries

Typical uses center on auditing contract status transitions and presenting them in a form grid. A representative query retrieves the change history for a specific history identifier:

SELECT ID, CHR_ID, CLE_ID, CREATION_DATE, FROM_STATUS, TO_STATUS, REASON_MEANING, COMMENTS, CONTRACT_VERSION, MANUAL_YN, USER_NAME, CHANGE_LEVEL, LINE_NUMBER FROM APPS.OKC_LAUNCH_KHIST_GRID_V WHERE CHR_ID = :p_chr_id ORDER BY CREATION_DATE DESC;

To examine changes by scope, filter on CHANGE_LEVEL, for example WHERE CHANGE_LEVEL = 'HEADER', and to distinguish manual interventions use WHERE MANUAL_YN = 'Y'. Analysts auditing transitions can group by FROM_STATUS and TO_STATUS over a date range. Because Oracle documents this as a forms-support view subject to change without notice, production reporting and integrations should preferentially read the base OKC history tables and reserve this view for diagnostics or replication of form behavior.