Results for “oke_approval_paths_tl_u2”

12 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKE_APPROVAL_PATHS_TL is the language-specific (translation) table for the contract document approval hierarchy within the Oracle E-Business Suite OKE – Project Contracts module. In a multi-language EBS 12.1.1 or 12.2.2 installation, Oracle stores translatable descriptive text separately from the base transactional record so that the same approval path definition can be presented in each installed language. This table holds the non-key descriptive attributes — specifically the path NAME and DESCRIPTION — while the corresponding base table, OKE_APPROVAL_PATHS, holds the language-independent control columns.

From a Data Vault modeling perspective, the mined foreign key structure classifies this object as satellite-leaning. The APPROVAL_PATH_ID column functions as the link back to the hub represented by OKE_APPROVAL_PATHS, while LANGUAGE supplies the additional grain required to store each translation. The descriptive columns (NAME, DESCRIPTION) are the descriptive satellite attributes. This is offered strictly as a modeling suggestion; in EBS terms, the table is simply a translated child of the base approval path entity.

Key Information Stored

The table contains eleven documented columns. The most operationally significant are:

  • APPROVAL_PATH_ID – Surrogate identifier of the approval hierarchy definition. It is part of the composite primary key and the foreign key to OKE_APPROVAL_PATHS.
  • LANGUAGE – The NLS language code for the translated row. Combined with APPROVAL_PATH_ID, it forms the primary key OKE_APPROVAL_PATHS_TL_PK, ensuring one translation per language per path.
  • NAME – The translated display name of the approval path. Together with LANGUAGE it appears in the unique index OKE_APPROVAL_PATHS_TL_UK, making it a business-key candidate.
  • DESCRIPTION – The translated long description or purpose of the approval hierarchy.
  • SOURCE_LANG – Identifies the source language of the row, used for translation maintenance and fallback logic.
  • ZD_EDITION_NAME – The editioning column introduced for Oracle EBS 12.2 online patching. It participates in the unique indexes OKE_APPROVAL_PATHS_TL_U1 (APPROVAL_PATH_ID, LANGUAGE, ZD_EDITION_NAME) and OKE_APPROVAL_PATHS_TL_U2 (NAME, LANGUAGE, ZD_EDITION_NAME). This column is absent in 12.1.1 and is a distinguishing feature of 12.2.2.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard EBS who-columns for audit and row-level change tracking.

The surrogate primary key (APPROVAL_PATH_ID plus LANGUAGE) is distinct from the business-key candidates documented in the unique indexes, which additionally include the descriptive NAME column.

Common Use Cases and Queries

Translation tables are most frequently queried to resolve the display name of a code value in a specific language, or to audit missing translations. Typical reporting patterns include:

  • Resolving the display name for a known path: join the base table to the translation table on APPROVAL_PATH_ID and filter by the desired LANGUAGE.
  • Listing approval hierarchies for contract approval setup reporting: select from OKE_APPROVAL_PATHS_TL where LANGUAGE = USERENV('LANG').
  • Detecting missing translations: identify paths in the base table with no matching translation row, using an outer join.
  • Edition-aware queries in 12.2.2: include ZD_EDITION_NAME in the WHERE clause or rely on the editioning view to restrict to the current edition.

A representative query:

SELECT tl.APPROVAL_PATH_ID, tl.NAME, tl.DESCRIPTION
FROM   OKE.OKE_APPROVAL_PATHS_TL tl
WHERE  tl.LANGUAGE = USERENV('LANG')
AND    tl.ZD_EDITION_NAME = 'ORA$BASE';

Related Objects

The following objects are the most significant to this table:

  • OKE_APPROVAL_PATHS – The base (language-independent) approval path table. The relationship is via OKE_APPROVAL_PATHS_TL.APPROVAL_PATH_ID → OKE_APPROVAL_PATHS.APPROVAL_PATH_ID.
  • OKE_APPROVAL_PATHS_TL_PK – Primary key constraint over APPROVAL_PATH_ID and LANGUAGE.
  • OKE_APPROVAL_PATHS_TL_UK – Unique key constraint over NAME and LANGUAGE.
  • OKE_APPROVAL_PATHS_TL_U1 / U2 – 12.2.2 editioning-aware unique indexes covering ZD_EDITION_NAME.
  • OKE_APPROVAL_PATHS_VL – The translated view commonly exposed in EBS forms, which joins the base and translation tables.
  • OKE Contract Approval APIs / OKE_APPROVAL_PATHS package logic – The DML layer through which approval hierarchies are maintained and which relies on the translated NAME for validation.

These dependencies confirm the table's role as the descriptive satellite of the approval path entity, referenced primarily through the APPROVAL_PATH_ID foreign key into OKE_APPROVAL_PATHS.