Search Results okc_time_code_units_v

Overview

OKC_TIME_CODE_UNITS_V is an APPS-owned, VALID database view in the OKC — Contracts Core product of Oracle E-Business Suite (12.1.1 and 12.2.2). It functions as the translatable presentation layer for the time code units entity within Oracle Contracts. The view joins the base table OKC_TIME_CODE_UNITS_B to its translation table OKC_TIME_CODE_UNITS_TL so that descriptive fields are returned in the session language, resolved via USERENV('LANG'). Its primary role is to expose time-and-unit-of-measure combinations (a time code, or TCE_CODE, paired with a unit of measure, or UOM_CODE) together with the user-facing descriptions. The view also exposes the ROWID of the base table row as ROW_ID, enabling the Oracle Forms-based Contracts UI to perform position-sensitive updates on the underlying B table through the view.

Underlying Base Objects

The ETRM metadata documents two referenced base objects, both accessed through synonyms in APPS:

• OKC_TIME_CODE_UNITS_B — the base (non-translatable) table. It supplies UOM_CODE, TCE_CODE, OBJECT_VERSION_NUMBER, QUANTITY, ACTIVE_FLAG, the fifteen descriptive flexfield attribute columns, the WHO audit columns, and the ROWID aliased as ROW_ID.
• OKC_TIME_CODE_UNITS_TL — the translation table. It supplies SFWT_FLAG, SHORT_DESCRIPTION, DESCRIPTION, and COMMENTS, joined to the base on UOM_CODE and TCE_CODE, and filtered to the current runtime language.

The join is an equi-join on the composite key (UOM_CODE, TCE_CODE) restricted by TCUT.LANGUAGE = USERENV('LANG'). This structure follows the standard Oracle EBS "_B / _TL" multilingual pattern, in which language-neutral columns reside in the base table and translated attributes reside in the TL table.

Key Columns

• TCE_CODE — the time code identifier; the column most commonly referenced by users searching for "tce_code." It forms half of the composite primary key with UOM_CODE.
• UOM_CODE — the unit of measure code; the second half of the composite key.
• ROW_ID — ROWID from OKC_TIME_CODE_UNITS_B, used for direct row addressing in Forms.
• OBJECT_VERSION_NUMBER — optimistic locking column maintained by the base table.
• QUANTITY — quantity value associated with the time code / UOM combination.
• SFWT_FLAG — flag sourced from the translation table, distinguishing "short-form / word-token" style translation records.
• SHORT_DESCRIPTION, DESCRIPTION, COMMENTS — user-facing text returned in the session language from OKC_TIME_CODE_UNITS_TL.
• ACTIVE_FLAG — indicates whether the time code unit record is active and selectable.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield columns from the base table.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns, all from the base table.

Common Use Cases and Queries

The view is typically queried to resolve time code units with their translated descriptions, for example when building contract line or billing schedules, validating a TCE_CODE during integration loads, or reporting on active time code / UOM combinations. A straightforward lookup by time code is:

• SELECT TCE_CODE, UOM_CODE, SHORT_DESCRIPTION, DESCRIPTION, QUANTITY, ACTIVE_FLAG FROM APPS.OKC_TIME_CODE_UNITS_V WHERE TCE_CODE = :p_tce_code AND ACTIVE_FLAG = 'Y';
• SELECT TCE_CODE, UOM_CODE, DESCRIPTION FROM APPS.OKC_TIME_CODE_UNITS_V WHERE UOM_CODE = :p_uom ORDER BY TCE_CODE;
• SELECT TCE_CODE, UOM_CODE, CREATION_DATE, LAST_UPDATE_DATE FROM APPS.OKC_TIME_CODE_UNITS_V WHERE LAST_UPDATE_DATE >= TRUNC(SYSDATE) - 7;

Because the view applies the language predicate automatically, queries against it never return duplicate language rows, making it preferable to custom joins written directly against the two base tables.