Results for “inventory_org_name”

50+ results




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

Overview

OKL_EXT_FA_LINE_SOURCES_TL is a translation table within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 Leasing and Finance Management (OKL) module. It stores language-specific, translated attributes for fixed asset line extension sources associated with lease and finance contracts. The "_TL" suffix identifies it as a translation table, meaning it holds descriptive text in multiple installed languages keyed by a base entity identifier plus a LANGUAGE code. The table resides in the OKL schema and is documented with a status of VALID and a physical footprint of 12 columns.

From a data modeling perspective, the heuristic Data Vault classification for this object is standalone, derived from its foreign-key structure. This suggests the table functions independently of a classic hub-link-satellite pattern and can be treated as a self-contained descriptive store rather than a dependent satellite feeding a central hub. The translation rows anchor to a line extension identifier, with language acting as the discriminating component of the compound key.

Key Information Stored

The table is defined by a composite primary key, OKL_EXT_FA_LINE_SOURCES_TL_PK, spanning LINE_EXTENSION_ID and LANGUAGE. LINE_EXTENSION_ID is the surrogate identifier linking each translated row to its parent line extension source, while LANGUAGE identifies the locale of the translated content. Together these form the unique business key that governs row uniqueness.

Among the documented columns, the most significant descriptive attributes are:

  • SOURCE_LANG — the source language from which the translation was derived, supporting multilingual content management.
  • INVENTORY_ORG_NAME — the translated name of the inventory organization associated with the line source.
  • INVENTORY_ITEM_NAME — the translated name of the associated inventory item.
  • TRANS_LINE_DESCRIPTION — the translated description of the transaction line.
  • SFWT_FLAG — a seeded/standard flag indicating whether the row represents a seed (preseeded) translation versus a user-defined one.

Standard EBS audit columns complete the structure: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. These provide the who-and-when accountability required for translation maintenance and are essential for reconciliation and audit reporting.

Common Use Cases and Queries

Typical use cases center on multilingual reporting and data validation of translated lease line source data. A common pattern retrieves the translated description for a specific language:

  • SELECT line_extension_id, inventory_item_name, trans_line_description FROM okl_ext_fa_line_sources_tl WHERE language = 'US';
  • Joining the translation table back to the base line extension source table using LINE_EXTENSION_ID to compare seeded versus user-maintained text.
  • Auditing recently modified translations using LAST_UPDATED_BY and LAST_UPDATE_DATE to track changes by user and date.
  • Identifying rows where SOURCE_LANG differs from LANGUAGE to detect untranslated or fallback content.
  • Reporting on SFWT_FLAG to separate Oracle-seeded translations from customer-defined entries during upgrades or localization projects.

Related Objects

Because the metadata documents this object as standalone, explicit foreign-key dependencies are not enumerated in the provided schema. The most significant relationships are those implied by its key and descriptive columns:

  • The base (non-translated) line extension source table, joined on LINE_EXTENSION_ID, which supplies the language-independent record.
  • OKL_EXT_FA_LINE_SOURCES (base table) via LINE_EXTENSION_ID — the primary logical parent.
  • Inventory organization reference objects in the INV schema, linked conceptually through INVENTORY_ORG_NAME.
  • Inventory item master objects, linked through INVENTORY_ITEM_NAME.
  • FND_LANGUAGES, joined on LANGUAGE, to resolve the installed language and its description.

Together these objects support the retrieval, validation, and presentation of translated fixed asset line source data across the leasing lifecycle.