Search Results bom_bill_revisions_b




Overview
Explore in AI Chat

Overview

The BOM_BILL_REVISIONS_B table is a core data object within the Bills of Material (BOM) module of Oracle E-Business Suite (EBS). It serves as the primary transactional table for storing revision-level information for bills of material. This table is essential for managing the lifecycle of a bill, allowing for controlled changes and versioning over time. Each record represents a specific revision of a bill, linked to its parent bill definition, enabling precise tracking of component changes, effective dates, and engineering change order (ECO) implementations. Its role is critical for maintaining manufacturing accuracy, supporting product configuration, and ensuring that the correct component list is used for production and planning activities based on revision-effective dates.

Key Information Stored

While the provided ETRM excerpt does not list specific columns beyond key identifiers, the table's primary keys and foreign relationships define its core structure. The central column is BILL_REVISION_ID, which is the unique primary key (PK) identifier for each revision record. The BILL_SEQUENCE_ID column is a foreign key (FK) that links the revision to its parent bill definition in the BOM_BILL_OF_MATERIALS table. The REVISION column, part of a unique key constraint (UK1) with BILL_SEQUENCE_ID, stores the alphanumeric revision code (e.g., 'A', 'B', '1.1'). Typically, this table would also contain columns for effective date (EFFECTIVITY_DATE), revision implementation date, associated change order (CHANGE_NOTICE), and a flag indicating the current revision.

Common Use Cases and Queries

A primary use case is retrieving the current or effective revision of a bill for a given date, which is fundamental for manufacturing and procurement systems. Development and reporting often involve queries to audit revision history or list bills pending revision implementation. Common SQL patterns include joining to the bill master and component tables.

  • Find Current Revision for a Bill: SELECT REVISION FROM BOM_BILL_REVISIONS_B WHERE BILL_SEQUENCE_ID = :bill_seq_id AND SYSDATE BETWEEN EFFECTIVITY_DATE AND NVL(DISABLE_DATE, SYSDATE+1);
  • List Revision History for a Bill: SELECT REVISION, EFFECTIVITY_DATE, CHANGE_NOTICE FROM BOM_BILL_REVISIONS_B WHERE BILL_SEQUENCE_ID = :bill_seq_id ORDER BY EFFECTIVITY_DATE DESC;
  • Join to Bill Master and Components: Queries typically join BOM_BILL_REVISIONS_B to BOM_BILL_OF_MATERIALS (for bill header info) and then to BOM_INVENTORY_COMPONENTS to get the component list for a specific revision.

Related Objects

The table exists within a tightly integrated schema. As per the documented relationships:

  • Referenced Parent Table: BOM_BILL_REVISIONS_B.BILL_SEQUENCE_ID is a foreign key to BOM_BILL_OF_MATERIALS. This links each revision to its core bill definition.
  • Dependent Child Table: BOM_BILL_REVISIONS_TL.BILL_REVISION_ID is a foreign key referencing this table's primary key. The TL (Translation) table stores language-specific descriptions for the revision.

In practice, this table is also centrally related to the BOM_INVENTORY_COMPONENTS table, which stores the component items for a specific bill revision, though this relationship is not explicitly listed in the provided metadata.