Search Results quantity_per_assembly




Overview

APPS.BOMBV_BOM_COMPONENTS is a reporting view in the Oracle E-Business Suite Bills of Material module. It presents the individual component lines that make up an engineering or manufacturing bill of material, denormalized for direct consumption by reports, concurrent programs, and integration interfaces. Rather than exposing the normalized component identifiers alone, the view resolves keys into human-readable values such as the organization code, organization name, alternate BOM designator, and decoded lookup meanings for a large set of descriptive flexfield-style flags.

The view is registered in ETRM with owner APPS and status VALID, and is available in both 12.1.1 and 12.2.2. A distinctive feature is the internal naming convention applied to several columns: values prefixed with _KF: denote key flexfield references (component item and bill item names), while values prefixed with _LA: denote lookup-backed attribute displays translated through MFG_LOOKUPS. The user search term "quantity_per_assembly" maps directly to the view column QUANTITY_PER_ASSEMBLY, which is the aliased form of BOM_INVENTORY_COMPONENTS.COMPONENT_QUANTITY.

Underlying Base Objects

ETRM documents the following referenced base objects for this view:

  • BOM_BILL_OF_MATERIALS (VIEW) — supplies the bill header context, including the alternate BOM designator, organization, and assembly item identifiers.
  • BOM_INVENTORY_COMPONENTS (VIEW) — the primary source of component lines, yielding quantity, yield factor, effectivity dates, operation sequence, supply information, and component-level flags.
  • FND_GLOBAL (PACKAGE) — provides session context such as the current organization and user identifiers.
  • HR_ALL_ORGANIZATION_UNITS (SYNONYM) — resolved to obtain the organization name associated with the inventory organization.
  • MTL_PARAMETERS (SYNONYM) — the organization parameters source, supplying the organization code.
  • MTL_SYSTEM_ITEMS_B (SYNONYM) — the item master, providing item names and the assembly item ID.

The view therefore joins bill header, component detail, item master, and organization context into a single flattened result set, which is why it is suitable for direct reporting without additional joins.

Key Columns

Common Use Cases and Queries

Typical usage includes BOM explosion reports, cost rollup preparation, and component-level interfaces. Because the view already resolves organization and lookup values, it is convenient for ad-hoc queries and custom concurrent programs. A representative query filtering on the searched column follows:

SELECT organization_code, alternate_bom_code, quantity_per_assembly, projected_yield, start_effective_date, end_effective_date FROM apps.bombv_bom_components WHERE organization_code = :p_org AND quantity_per_assembly > 0 ORDER BY alternate_bom_code, item_sequence_number;

Analysts frequently join this view back to MTL_SYSTEM_ITEMS_B for extended item attributes, or filter on the decoded flags to identify components that are optional, mutually exclusive, or excluded from cost rollup. The effectivity columns support point-in-time reconstruction of a bill, and the supply columns (SUPPLY_SUBINVENTORY, WIP_SUPPLY_TYPE) support shop-floor and supply-type reporting. Note that _KF: and _LA: columns are internal display constructs and should not be referenced directly in custom SQL.