Results for “pv_ge_chklst_items_tl_u1”

12 results




Overview
Explore in AI Chat

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

Overview

PV.PV_GE_CHKLST_ITEMS_TL is the translation table (the "_TL" suffix denotes translated) for Oracle Property Manager checklist items in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the language-dependent, user-facing description of each checklist item defined in the base entity, PV_GE_CHKLST_ITEMS_B. In Oracle EBS multilingual (MLS) architecture, a base ("_B") table holds language-independent columns and the translated table holds the same entity's descriptive attributes per installed language, keyed by a language code. This table's status is VALID and it resides in the APPS_TS_TX_DATA tablespace with PCT Free 10.

Under the heuristic Data Vault classification mined from the foreign-key structure, this object is satellite-leaning. Interpreted as a modeling suggestion, it behaves as a descriptive satellite attached to the checklist-item hub/link represented by PV_GE_CHKLST_ITEMS_B: it carries change-tracked, attribute-bearing rows (name, source language, WHO audit columns) whose grain is one row per checklist item per language rather than an independent business entity.

Key Information Stored

The most significant columns, grounded in the documented metadata, are:

  • CHECKLIST_ITEM_ID (NUMBER) — Foreign key to Checklist Item Id for which translatable data is being collected; joins back to PV_GE_CHKLST_ITEMS_B.
  • LANGUAGE (VARCHAR2) — The language being translated to (e.g., an NLS-style language code).
  • CHECKLIST_ITEM_NAME (VARCHAR2(2000)) — The translated checklist item name that must be checked; the principal payload attribute.
  • SOURCE_LANG (VARCHAR2) — The source language for the translation.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns recording creation and last-update identity, timestamp, and login.

The composite primary key is PV_GE_CHKLST_ITEMS_TL_PK (CHECKLIST_ITEM_ID, LANGUAGE), which also forms the unique index PV_GE_CHKLST_ITEMS_TL_U1 on APPS_TS_TX_IDX. This makes (CHECKLIST_ITEM_ID, LANGUAGE) the documented business-key candidate; the surrogate component is the numeric CHECKLIST_ITEM_ID inherited from the base table. There are nine documented columns in total.

Common Use Cases and Queries

Typical reporting and compliance scenarios join the translated table to its base entity to resolve language-specific checklist item names, or filter by active session language using the EBS USERENV('LANG') function.

  • Resolve the display name of a checklist item for a specific language: SELECT CHECKLIST_ITEM_NAME FROM PV.PV_GE_CHKLST_ITEMS_TL WHERE CHECKLIST_ITEM_ID = :id AND LANGUAGE = USERENV('LANG');
  • Report all translations and trace translation provenance through SOURCE_LANG.
  • Audit recently created or modified translations using CREATED_BY/LAST_UPDATED_BY and their date columns.
  • Diagnose missing translations by comparing base rows against translated rows for a target language.

Related Objects

  • PV.PV_GE_CHKLST_ITEMS_B — The base table holding language-independent checklist item data; join on CHECKLIST_ITEM_ID. The translated table has a foreign key to it and is "referenced by" nothing else per the documented dependency data.
  • PV_GE_CHKLST_ITEMS_TL (the APPS synonym) — Application-facing synonym used by concurrent programs and forms.
  • PV_GE_CHKLST_ITEMS_TL_U1 — Unique index supporting the composite key and enabling efficient lookups.
  • PV_GE_CHKLST_ITEMS_TL_PK — The primary key constraint (CHECKLIST_ITEM_ID, LANGUAGE).

Because the documented dependencies show this table references only PV_GE_CHKLST_ITEMS_B and is referenced by no further objects, the base entity remains the principal join target for all checklist-item reporting.