Search Results obj_name




Overview
Explore in AI Chat

Overview

APPS.BOM_BILL_OF_MATERIALS is a reportable view in the Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2 data model that exposes bill of materials (BOM) header information stored in the base table BOM_STRUCTURES_B. It presents one row per bill structure definition, keyed by assembly, organization, and alternate BOM designator, and is intended for reporting, inquiry, and integration purposes across the Bills of Material and related manufacturing modules.

The view applies a responsibility-sensitive filter at runtime through the FND_GLOBAL package. The WHERE clause restricts returned rows based on fnd_global.resp_app_id: rows are returned when resp_app_id equals 431, when resp_app_id equals -1, or when the responsibility is not 431 and the structure's effectivity control value defaults to 1 or is less than or equal to 3. Because of this dependency, query results vary by the responsibility under which the session is authenticated, and the view should be treated as an inquiry layer rather than an unrestricted table.

Underlying Base Objects

The view is defined over two documented referenced objects:

  • BOM_STRUCTURES_B (SYNONYM) — the base table that physically stores bill of materials header records. All columns projected by the view originate from this table. The synonym provides the APPS-owned access path to the underlying BOM schema object.
  • FND_GLOBAL (PACKAGE) — the Oracle Applications runtime package that supplies session context values, specifically fnd_global.resp_app_id, used in the view's restrictive WHERE predicate to enforce responsibility-based record visibility.

The view does not perform joins to item, resource, or component tables. It is a straight projection with a context filter over BOM_STRUCTURES_B, and it should not be confused with the component-level BOM views that expose bill lines rather than bill structures.

Key Columns

Common Use Cases and Queries

The view is commonly used to list bill structures for an organization or assembly, to identify preferred structures, to audit structure effectivity and engineering change references, and to feed integrations that require bill header data without accessing BOM_STRUCTURES_B directly. Because row visibility depends on fnd_global.resp_app_id, reports and interfaces should be executed under a responsibility whose application context satisfies the filter.

A typical query retrieving bill structures for a specific assembly and organization:

  • SELECT bill_sequence_id, assembly_item_id, organization_id, alternate_bom_designator, assembly_type, structure_type_id, is_preferred, implementation_date, effectivity_control
  • FROM apps.bom_bill_of_materials
  • WHERE assembly_item_id = :assembly_item_id
  • AND organization_id = :organization_id
  • AND alternate_bom_designator = :alternate_designator;

To identify preferred structures for an organization:

  • SELECT assembly_item_id, alternate_bom_designator, bill_sequence_id, implementation_date
  • FROM apps.bom_bill_of_materials
  • WHERE organization_id = :organization_id
  • AND is_preferred = 1;

Queries returning no rows for an authorized assembly typically indicate that the executing responsibility's application identifier does not satisfy the view's context filter, rather than the absence of bill data in BOM_STRUCTURES_B.