EGP_SYSTEM_ITEMS_TL
Product: EGPmasterPer inventory orgLanguage-stripedThe item master's translation companion — item description and long description in every installed language, one row per item per organization per language; the only place the item description exists
Filter to one LANGUAGE or item joins multiply by installed languages; SOURCE_LANG marks the row the others were translated from.
What the badges mean
- Product: EGP
- Product: the Oracle product family that owns the object — the short code Oracle's Tables and Views documentation lists as the object owner. Fusion is SaaS, so this isn't a database schema; there's no SQL path to the tables at all (see the quirks guide).
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
- BU-striped (ORG_ID)
- Rows are scoped to a business unit. The column is still named
ORG_ID, but in Fusion it means business unit, not the EBS operating unit — treat any migrated “operating unit” filter as suspect (see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization via
ORGANIZATION_ID— always pair it withINVENTORY_ITEM_IDon item-level joins (see the quirks guide). - Set / ledger / named-BU striped
- Some tables stripe by a named column instead of
ORG_ID: reference data set (SET_ID— see the quirks guide), ledger (LEDGER_IDon the GL journal tables), or a named business-unit column (PRC_BU_ID/REQ_BU_IDin procurement). The table page’s partition line names the column, and the generated SQL anchors on it — never treat these tables as unpartitioned. - Language-striped
- The table carries a
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows. - Date-effective
- This is an
_Ftable — one row per entity per effectivity window, withEFFECTIVE_START_DATEandEFFECTIVE_END_DATEpart of the key. Join without a window filter and every fact multiplies by history (see the quirks guide). - View
- This is a documented convenience view, not a physical table. Extract through the BICC data store that fronts its base objects instead of assuming the view lands as-is.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
Translations
EGP_SYSTEM_ITEMS_TL holds the per-language translation rows for EGP_SYSTEM_ITEMS_B — one row per LANGUAGE. Filter to one LANGUAGE or rows multiply.
Extract access
The delivered surfaces that reach this table — the BICC extract data store (PVO) for bulk extraction and the OTBI subject areas for real-time queries. There is no SQL path to the SaaS database.
- FscmTopModelAM.ScmExtractAM.EgpBiccExtractAM.ItemTranslationExtractPVO
Translated Item Attributes data store — the translatable item attributes, one row per language.
Oracle data-store documentation (opens in new tab)
Fields
6 fields · 3 key
6 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | INVENTORY_ITEM_ID | Item this translation row belongs to | NUMBER | Key |
| 2 | ORGANIZATION_ID | Organization of the item row | NUMBER | Key |
| 3 | LANGUAGE | Language of this row — filter to one or item joins multiply | VARCHAR2 | Key |
| 4 | SOURCE_LANG | The language this row's text was authored in | VARCHAR2 | |
| 5 | DESCRIPTION | Item short description — the only place it exists | VARCHAR2 | |
| 6 | LONG_DESCRIPTION | Item extended description | VARCHAR2 |
Field provenance: hand-curated. 3 key fields.
Boilerplate SQL
Starting point for reading the BICC-landed copy of EGP_SYSTEM_ITEMS_TL on Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark (the column incremental BICC extracts key on) are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
6 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <language>, <INVENTORY_ITEM_ID>, <watermark>
-- ============================================================
-- Table : EGP_SYSTEM_ITEMS_TL — The item master's translation companion — item description and long description in every installed language, one row per item per organization per language; the only place the item description exists
-- Purpose: Column-selected read of EGP_SYSTEM_ITEMS_TL — auto-generated from field metadata
-- Grain : One row per inventory org (ORGANIZATION_ID) + INVENTORY_ITEM_ID
-- Notes : Auto-generated skeleton for Oracle Fusion Cloud data landed in your lakehouse by a BICC extract — there is no SQL path to the SaaS database. Column names follow Oracle's table documentation — if your landed data still carries PVO attribute headers, map names first; see quirks #pvo-drift. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
t.INVENTORY_ITEM_ID AS "Item this translation row belongs to",
t.ORGANIZATION_ID AS "Organization of the item row",
t.LANGUAGE AS "Language of this row — filter to one or item joins multiply",
t.SOURCE_LANG AS "The language this row's text was authored in",
t.DESCRIPTION AS "Item short description — the only place it exists",
t.LONG_DESCRIPTION AS "Item extended description"
FROM <catalog>.<schema>.EGP_SYSTEM_ITEMS_TL t
WHERE
t.ORGANIZATION_ID = <inventory_org_id> -- inventory org, NOT the business unit — see quirks guide #item-org-striping
AND t.LANGUAGE = '<language>' -- one language or rows multiply; translations fall back to SOURCE_LANG
-- AND t.INVENTORY_ITEM_ID = <INVENTORY_ITEM_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- the column incremental BICC extracts key on
ORDER BY t.INVENTORY_ITEM_ID;Verified September 2026 · docs release 26C
Column names differ in BICC extracts — see PVO header drift.
Relationships
Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.
Loading relationship diagram…
Join details
ON EGP_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID = EGP_SYSTEM_ITEMS_TL.INVENTORY_ITEM_ID AND EGP_SYSTEM_ITEMS_B.ORGANIZATION_ID = EGP_SYSTEM_ITEMS_TL.ORGANIZATION_ID AND EGP_SYSTEM_ITEMS_TL.LANGUAGE = '<language>'
More Product Master tables
- EGP_CATEGORIES_BThe category master — one row per category with its user-facing category code and active window; categories are global and keyed by CATEGORY_ID
- EGP_CATEGORY_SETS_BCatalog (category set) definitions — control level, the multiple-assignments flag, hierarchy option, and the default category new items inherit
- EGP_COMPONENTS_BItem structure component lines — one row per component per operation per effectivity window, child of the structure header, with quantity, yield, and WIP supply behavior
- EGP_ITEM_CAT_ASSIGNMENTSThe item-to-category assignment — one row per item, organization, catalog (category set), and category; the bridge every category rollup crosses
- EGP_ITEM_REVISIONS_BItem revisions — one row per revision level of an item in an organization, with effectivity and implementation dates and the change-order line that introduced it
- EGP_STRUCTURES_BItem structure (BOM) headers — one row per manufacturing or engineering bill per named variant, identified by BILL_SEQUENCE_ID, with common-structure sharing and change-order linkage