Search Results okc_statuses_v




Overview
Explore in AI Chat

Overview

OKC_STATUSES_V is a seeded, VALID database view owned by the APPS schema within the Oracle E-Business Suite Contracts Core (OKC) module. It serves as the translation and user-facing layer for contract status definitions, presenting the denormalized, language-resolved status information that drives contract lifecycle processing in both EBS 12.1.1 and 12.2.2. Because OKC_STATUSES_B stores language-independent status attributes and OKC_STATUSES_TL stores the translatable text, the view reconciles these two structures into a single consumable recordset. As a result, OKC_STATUSES_V is the object most commonly referenced by Oracle Contracts forms, lookup validation logic, seeded reports, and custom integrations that need to enumerate or resolve contract statuses without handling the underlying translated table joins manually.

Underlying Base Objects

Per the documented view text, OKC_STATUSES_V is defined over two base objects: OKC_STATUSES_B (exposed as a SYNONYM) and OKC_STATUSES_TL (also exposed as a SYNONYM). The join condition is STSB.CODE = STST.CODE, restricted by STST.LANGUAGE = USERENV('LANG'). This pattern is the standard Oracle EBS _B/_TL translation model: the _B table holds non-translatable columns such as the status code, object version number, default flag, and audit columns, while the _TL table holds the SFWT flag, STE code, meaning, and description content that vary by installed language. The language predicate ensures that users see status text in their session language, falling back to the base language where translations are not maintained.

Key Columns

  • ROW_ID — the ROWID of the OKC_STATUSES_B row, used for optimistic locking and row-level addressing.
  • CODE — the unique contract status code; primary identifier joining the _B and _TL tables.
  • OBJECT_VERSION_NUMBER — the OVN used by the framework for change detection and concurrency control.
  • SFWT_FLAG — the "seed flag within territory" indicator carried from the _TL table, controlling seeded behavior.
  • STE_CODE — the associated status transition/entity code used by the status engine.
  • MEANING — the translated, user-visible status name.
  • DESCRIPTION — the translated descriptive text for the status.
  • DEFAULT_YN — flag indicating whether the status is the default for new records.
  • START_DATE / END_DATE — effective dating that controls when a status is active.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

The view is most often queried to enumerate active statuses for lookup lists, to resolve a code into its display meaning, or to validate that a submitted status is permitted. A typical enumeration query is:

SELECT code, meaning, default_yn
FROM   okc_statuses_v
WHERE  NVL(end_date, SYSDATE + 1) >= SYSDATE
ORDER  BY meaning;

To resolve a specific status for display in a report or interface:

SELECT code, meaning, description
FROM   okc_statuses_v
WHERE  code = :p_status_code;

Because the view already applies USERENV('LANG'), applications should query it directly rather than joining OKC_STATUSES_B and OKC_STATUSES_TL themselves; this guarantees consistent language resolution across all consumers and avoids duplicate text rows. Custom dashboards and integrations commonly join OKC_STATUSES_V to OKC_K_HEADERS or contract line tables to present human-readable status context, while workflow and form validation logic reference it to confirm DEFAULT_YN and effective dates before committing a status change.