Search Results wsm_lot_job_interface

Overview

The BOM_BILL_OF_MATERIALS table is the central repository for bill of material (BOM) header information within the Oracle E-Business Suite Bills of Material module. It defines the structure of an assembly, serving as the master record that links a specific item (assembly) to its constituent components. This table is fundamental to manufacturing, costing, and planning processes across both EBS 12.1.1 and 12.2.2. Each row uniquely identifies a bill of material for a specific assembly item within a specific organization and, optionally, an alternate designator. The table's integrity is maintained through a system-generated primary key, BILL_SEQUENCE_ID, which is referenced by numerous child tables containing component details, revisions, and related manufacturing data.

Key Information Stored

While the provided metadata does not list individual columns, the primary and foreign key relationships reveal the critical data entities stored. The table's unique key (ASSEMBLY_ITEM_ID, ORGANIZATION_ID, ALTERNATE_BOM_DESIGNATOR) establishes the core identity of a bill. Key stored information includes the link to the assembly item in MTL_SYSTEM_ITEMS_B, the manufacturing organization from HR_ALL_ORGANIZATION_UNITS, and the alternate bill designation from BOM_ALTERNATE_DESIGNATORS. It also manages engineering change order (ECO) integration via the PENDING_FROM_ECN link to ENG_ENGINEERING_CHANGES. Furthermore, the table supports common bill of material structures through self-referencing foreign keys (COMMON_BILL_SEQUENCE_ID, COMMON_ASSEMBLY_ITEM_ID, COMMON_ORGANIZATION_ID), allowing a single bill definition to be shared across multiple organizations.

Common Use Cases and Queries

This table is primarily accessed to retrieve the definitive bill of material header for an assembly. Common use cases include validating bill existence before creating a discrete job, exploding BOMs for cost rollups or material requirements planning (MRP), and fetching bill details for engineering change management. A fundamental query pattern involves joining to item and organization tables to retrieve a readable bill header. For example, to find all primary bills for an item:

• SELECT bom.ASSEMBLY_ITEM_ID, bom.ORGANIZATION_ID, msib.CONCATENATED_SEGMENTS, hou.NAME FROM BOM_BILL_OF_MATERIALS bom, MTL_SYSTEM_ITEMS_B msib, HR_ALL_ORGANIZATION_UNITS hou WHERE bom.ASSEMBLY_ITEM_ID = msib.INVENTORY_ITEM_ID AND bom.ORGANIZATION_ID = msib.ORGANIZATION_ID AND bom.ORGANIZATION_ID = hou.ORGANIZATION_ID AND bom.ALTERNATE_BOM_DESIGNATOR IS NULL;

As indicated by the user's search for "wsm_lot_job_interface," this table is directly referenced by that interface table to validate the bill (via PRIMARY_ITEM_ID, ORGANIZATION_ID, and ALTERNATE_BOM_DESIGNATOR) when creating or updating jobs via open interfaces.

Related Objects

The BOM_BILL_OF_MATERIALS table has extensive relationships, acting as a hub for BOM data. Key documented foreign key relationships are:

• Referenced by BOM_BILL_OF_MATERIALS (self): COMMON_BILL_SEQUENCE_ID links to BILL_SEQUENCE_ID for common bills.
• Referenced by BOM_BILL_REVISIONS_B: BILL_SEQUENCE_ID links revision history to the bill header.
• Referenced by BOM_INVENTORY_COMPONENTS: BILL_SEQUENCE_ID is the foreign key from component lines to their parent bill.
• Referenced by WSM_CO_PRODUCTS: BILL_SEQUENCE_ID links co-products defined for a bill.
• Referenced by WSM_LOT_JOB_INTERFACE: PRIMARY_ITEM_ID, ORGANIZATION_ID, and ALTERNATE_BOM_DESIGNATOR together reference the bill's unique key to validate job creation.
• Referenced by SO_LINES_ALL and SO_LINE_DETAILS: COMPONENT_SEQUENCE_ID links configuration items to their source bill.

It also references MTL_SYSTEM_ITEMS_B (for assembly and common assembly items), BOM_ALTERNATE_DESIGNATORS, ENG_ENGINEERING_CHANGES, and HR_ALL_ORGANIZATION_UNITS.