Search Results catset2_category_fk




Overview
Explore in AI Chat

Overview

EDW_ITEM_ITEM_LCV is an Oracle EBS engineering module view that exposes item-level item information in a denormalized, warehouse-oriented format. The "LCV" suffix denotes a load/collection view, indicating its role in the Oracle Enterprise Data Warehouse (EDW) extraction layer used to populate analytical and reporting structures from the E-Business Suite source system. The view holds one row per inventory item definition, carrying both descriptive attributes (name, description) and foreign-key style references to category sets, product groups, and the item number primary key.

The view is documented under the Engineering (ENG) product family and is therefore primarily relevant to item master and engineering change contexts. A critical implementation note accompanies the metadata: the object is not implemented in this database in the documented environment. Consultants should verify existence via ALL_VIEWS or DBA_OBJECTS before referencing it in custom SQL, as availability depends on whether the EDW/ETRM collection layer has been deployed in the target instance.

Underlying Base Objects

Per the documented view text, EDW_ITEM_ITEM_LCV is defined as a thin projection over a single object: EDWBV_ITEM_ITEM_LCV. No additional base tables are documented in the referenced-object list. This layered pattern is typical of ETRM/EDW views — a staging or "BV" (base view) object performs the join and transformation work, while the LCV provides a stable, backward-compatible column contract for downstream consumers.

The projection is effectively a SELECT of named columns from EDWBV_ITEM_ITEM_LCV with no filtering, no joins, and no aggregation at the LCV level. Several trailing columns are returned as literal NULLs (positioned after OPERATION_CODE in the view text), which indicates either reserved placeholder columns or attributes suppressed because they do not apply to this collection scope. Because the base view itself is not documented here, lineage beyond EDWBV_ITEM_ITEM_LCV cannot be confirmed from the metadata; in practice these base views typically resolve to inventory item master tables such as MTL_SYSTEM_ITEMS_B and category assignment tables.

Key Columns

The most relevant column for the searched term is ITEM_NUMBER_PK, which serves as the primary key identifier for the item record in the warehouse model. It is the natural join key for relating this view to other EDW item-level collections.

  • ITEM_NUMBER_PK — Surrogate/primary key for the item in the EDW model; the primary linkage attribute.
  • INSTANCE — Identifies the source EBS instance, supporting multi-instance warehouse consolidation.
  • INVENTORY_ITEM_ID and ORGANIZATION_ID — Native EBS identifiers for the item and its owning inventory organization.
  • ITEM_NAME, NAME, DESCRIPTION — Descriptive attributes for reporting and display.
  • ITEM_NUMBER_DP — Item number descriptive/display value.
  • CATSET1_CATEGORY_FK, CATSET2_CATEGORY_FK, CATSET3_CATEGORY_FK — Foreign keys to category assignments across three category sets.
  • PRODUCT_GROUP_FK — Reference to the associated product group.
  • OPERATION_CODE — Change-data-capture indicator (insert/update/delete) used during incremental loads.
  • LAST_UPDATE_DATE, CREATION_DATE — Audit timestamps for delta processing.
  • USER_ATTRIBUTE1 through USER_ATTRIBUTE5 — Extensible descriptive flexfield placeholder columns.
  • Category FK columns (INV, PO, MRP, SER, CST, ENG, OE, PLA) are listed in the documented column set but are not all projected in the shown view text; CATSET columns are the ones actually selected.

Common Use Cases and Queries

Typical usage centers on item master reporting, category mapping, and incremental EDW loads keyed on OPERATION_CODE and LAST_UPDATE_DATE. Because the object may not be implemented, defensive querying is advisable.

  • Confirming object presence: SELECT object_name, object_type FROM all_objects WHERE object_name = 'EDW_ITEM_ITEM_LCV';
  • Retrieving an item by warehouse key: SELECT item_number_pk, item_name, description FROM edw_item_item_lcv WHERE item_number_pk = :p_item_pk;
  • Incremental extraction: SELECT item_number_pk, operation_code, last_update_date FROM edw_item_item_lcv WHERE last_update_date > :p_high_water_mark;
  • Category analysis: SELECT item_number_pk, catset1_category_fk, catset2_category_fk, product_group_fk FROM edw_item_item_lcv;
  • Instance-scoped reporting: SELECT item_number_pk, organization_id, inventory_item_id FROM edw_item_item_lcv WHERE instance = :p_instance;

All queries should be validated against the target environment, since the ETRM documentation records the view as not implemented in the reference database.