Results for “edw_item_itemorg_lcv”

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

Overview

The APPS.EDW_ITEM_ITEMORG_LCV view is an Engineering (ENG) module reporting object that exposes item–organization level information in a flattened, denormalized form. It is part of the Oracle E-Business Suite EDW (Enterprise Data Warehouse) family of "LCV" (logical/derived view) objects, and its name reflects its dual scope: item master attributes combined with organization-level item attributes. The view joins the item definition (ITEM_NUMBER, DESCRIPTION, and the full set of planning, costing, and control flags) to the specific inventory organization in which the item is defined, driven by INVENTORY_ITEM_ID and ORGANIZATION_ID. Its status is VALID and it is owned by the APPS schema, the standard owner for secured EBS reporting views.

The view is not a transactional object; it is intended for read-only reporting, extract-transform-load (ETL) feeds, and integration layers. It presents a single row per item–organization combination, which makes it well suited for bulk extraction into external analytics platforms, data marts, or custom concurrent programs.

Underlying Base Objects

The view text is defined over a single documented source: EDWBV_ITEM_ITEMORG_LCV. This base view, in turn, resolves to the standard EBS item/inventory tables, principally MTL_SYSTEM_ITEMS_B and its organization-scoped columns (INVENTORY_ITEM_ID, ORGANIZATION_ID) and MTL_ITEM_CATEGORIES for category assignments. The ETRM metadata lists no additional referenced base objects, indicating that EDWBV_ITEM_ITEMORG_LCV encapsulates the join logic and the LCV layer simply projects the required columns outward.

Because the documented definition is limited, the following relationships can be inferred from the exposed columns: ITEM_ORG_PK and INSTANCE provide surrogate and instance identifiers; ITEM_NUMBER_FK, PROD_FAMILY_FK, and CATSET_CATEGORY_FK provide foreign-key style references to dimensional entities; and BUYER_FK and PLANNER_FK reference the purchasing and planning personnel dimensions. The trailing NULL literals in the SELECT list are positional placeholders mapped to USER_ATTRIBUTE columns and category FK columns preserved for schema stability across releases.

Key Columns

• EFFECTIVITY_CONTROL — Indicates whether effectivity (date range) control is enabled for the item in the organization. This is the column most closely associated with the user's search term. Values are typically derived from MTL_SYSTEM_ITEMS_B.EFFECTIVITY_CONTROL and govern whether revision/effectivity rules apply.
• INVENTORY_ITEM_ID / ORGANIZATION_ID — The composite key identifying the item within a specific inventory organization; the natural grain of the view.
• ITEM_NUMBER, DESCRIPTION, SEGMENT1 — Descriptive and legacy segment identifiers for the item.
• MAKE_OR_BUY_FLAG, PURCHASABLE_FLAG, STOCKABLE_FLAG, INTERNAL_ORD_FLAG — Sourcing and planning controls determining how the item is procured, stocked, and ordered.
• REVISION_CONTROL, LOT_CONTROL, SERIAL_CONTROL, LOCATOR_CONTROL — Inventory control flags governing revision, lot, serial, and locator tracking.
• MRP_PLN_METHOD, INV_PLANNING_CODE, SHELF_LIFE_CODE, SHELF_LIFE_DAYS — Planning and shelf-life attributes used by MRP and inventory planning.
• UNIT_LIST_PRICE, MARKET_PRICE, TAX_CODE, PRICE_TOL_PERCENT — Pricing and tax attributes relevant to order management and purchasing.
• BUYER_FK, PLANNER_FK, HAZARD_CLASS_ID, UN_NUMBER_ID — Reference and compliance attributes linking to buyer, planner, and hazardous material definitions.
• CREATION_DATE, LAST_UPDATE_DATE, OPERATION_CODE — Audit and change-data-capture (CDC) columns; OPERATION_CODE typically supports incremental extraction (insert/update/delete indications).
• USER_ATTRIBUTE1–5 — Descriptive flexfield segments carried through for extensibility.

Common Use Cases and Queries

Typical uses include periodic full extracts of item–organization masters into a data warehouse, incremental CDC loads keyed on OPERATION_CODE and LAST_UPDATE_DATE, and ad hoc reporting on effectivity and control attributes. A representative query for effectivity-controlled items in a given organization is:

• SELECT INVENTORY_ITEM_ID, ORGANIZATION_ID, ITEM_NUMBER, DESCRIPTION, EFFECTIVITY_CONTROL, REVISION_CONTROL FROM APPS.EDW_ITEM_ITEMORG_LCV WHERE ORGANIZATION_ID = :org_id AND EFFECTIVITY_CONTROL IS NOT NULL;
• SELECT OPERATION_CODE, COUNT(*) FROM APPS.EDW_ITEM_ITEMORG_LCV WHERE LAST_UPDATE_DATE >= :start_date GROUP BY OPERATION_CODE;

Because the view is read-only and pre-joined, it reduces the need to replicate the MTL_SYSTEM_ITEMS_B join logic in every report. Reporting against a VALID APPS view also ensures consistent row-level security and naming across the 12.1.1 and 12.2.2 releases.