Results for “enforce_int_requirements_desc”

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

Overview

BOM_INVENTORY_COMPONENTS_V is a denormalized reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the Bills of Material (BOM) product. It exposes the component lines that make up a bill of material, joining the base component structure to item master and lookup attributes so that a single query returns not only the component quantity and sequence information but also the descriptive and transactional characteristics of the component item itself. The view is documented in ETRM as "Bill of material components" and is validated in both 12.1.1 and 12.2.2.

Its principal role is to support reporting, inquiry, and integration scenarios where the full context of a BOM component must be retrieved without navigating the underlying normalized structures. Because it presents both the bill-level attributes (sequence, quantity, supply type) and item-level attributes (UOM, description, locator control, shippable flag), the view is convenient for extracts, custom concurrent programs, and interfaces that populate external planning, costing, or manufacturing systems.

Underlying Base Objects

The view is defined over several documented base objects: BOM_BILL_OF_MATERIALS, BOM_INVENTORY_COMPONENTS, FND_COMMON_LOOKUPS, MFG_LOOKUPS, MTL_SYSTEM_ITEMS_B_KFV, and MTL_SYSTEM_ITEMS_TL, and it draws runtime context from the FND_GLOBAL package. BOM_INVENTORY_COMPONENTS supplies the primary component rows, while BOM_BILL_OF_MATERIALS links each component to its parent bill. The lookup views (MFG_LOOKUPS and FND_COMMON_LOOKUPS) resolve coded values such as supply type into user-facing meanings. MTL_SYSTEM_ITEMS_B_KFV and MTL_SYSTEM_ITEMS_TL enrich each component item with its concatenated key, description, primary UOM, engineering item flag, status, and shipping/locator control attributes. FND_GLOBAL is referenced for session-level identifiers such as the organization context.

Key Columns

• COMPONENT_SEQUENCE_ID / BILL_SEQUENCE_ID — Unique identifiers for the component line and its parent bill, used to join back to base tables.
• OPERATION_SEQ_NUM — Routing operation to which the component is assigned.
• COMPONENT_ITEM_ID / ITEM_NUM — The component item and its item number.
• COMPONENT_QUANTITY, COMPONENT_YIELD_FACTOR, PLANNING_FACTOR, COST_FACTOR — The usage quantity and the factors that adjust planning and cost rollup.
• BASIS_TYPE — Indicates whether quantity is per assembly or per unit; defaults to 1 when null via NVL.
• EFFECTIVITY_DATE, DISABLE_DATE, IMPLEMENTATION_DATE — Effective-dating controls; IMPL_CB is derived as a decode of implementation status.
• SUPPLY_TYPE / WIP_SUPPLY_TYPE, SUPPLY_SUBINVENTORY, SUPPLY_LOCATOR_ID — Supply and sourcing attributes for the component.
• OPTIONAL, MUTUALLY_EXCLUSIVE_OPTIONS, CHECK_ATP, SHIPPING_ALLOWED, REQUIRED_TO_SHIP, INCLUDE_IN_COST_ROLLUP — Planning, shipping, and costing behavior flags.
• PRIMARY_UOM_CODE, DESCRIPTION, ENG_ITEM_FLAG, INVENTORY_ITEM_STATUS_CODE — Descriptive and status attributes of the component item.
• ITEM_LOCATOR_CONTROL, RESTRICT_LOCATORS_FLAG, RESTRICT_SUBINVENTORIES_FLAG — Item-level locator and subinventory restriction controls.

Common Use Cases and Queries

Typical uses include bill-of-material explosion reports, component extracts for external ERP or planning tools, cost rollup validations, and queries validating effective-dated component status.

SELECT bill_sequence_id, component_item_id, item_num,
       component_quantity, primary_uom_code,
       effectivity_date, disable_date, supply_type
FROM   apps.bom_inventory_components_v
WHERE  bill_sequence_id = :bill_seq
ORDER  BY component_sequence_id;

A second scenario returns only effective components for a parent assembly at a given date:

SELECT item_num, component_quantity, component_yield_factor, description
FROM   apps.bom_inventory_components_v
WHERE  bill_sequence_id = :bill_seq
AND    NVL(effectivity_date, SYSDATE) <= SYSDATE
AND    NVL(disable_date, SYSDATE) > SYSDATE;

Because the view joins lookup and item master objects, adding restrictive predicates on bill_sequence_id or component_item_id is recommended to avoid unnecessary scans across organizations.