Search Results bom_delete_entities




Overview
Explore in AI Chat

Overview

The BOM_DELETE_ENTITIES table is a critical technical object within the Bills of Material (BOM) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It functions as a central logging and control table for the deletion of master data entities, specifically bills of material and operational routings. Its primary role is to support the multi-step, validation-intensive deletion processes in BOM and Inventory (INV). When a user initiates a mass deletion through the standard "Delete Bills and Routings" or similar concurrent programs, the system populates this table with a record for each entity slated for removal. This design allows for transactional integrity, error tracking, and the ability to manage complex deletions that may span multiple related tables.

Key Information Stored

The table's structure is designed to link deletion requests to specific data entities and group them for processing. The primary key, DELETE_ENTITY_SEQUENCE_ID, uniquely identifies each entity record within the deletion framework. Two other crucial foreign key columns establish the core relationships: BILL_SEQUENCE_ID links to a specific bill of material in the BOM_STRUCTURES_B table, and ROUTING_SEQUENCE_ID links to a routing in the BOM_OPERATIONAL_ROUTINGS table. A given record will typically populate one of these two IDs, depending on whether it represents a bill or a routing for deletion. Furthermore, the DELETE_GROUP_SEQUENCE_ID column associates the entity with a broader deletion transaction batch recorded in the BOM_DELETE_GROUPS table, enabling the management of grouped deletion jobs.

Common Use Cases and Queries

The most direct use case is investigating pending or failed deletion jobs. Administrators can query this table to see what items, bills, or routings are queued for deletion within a specific group. A common diagnostic query joins BOM_DELETE_ENTITIES with BOM_DELETE_GROUPS and the main data tables to list entities in a failed or pending state. For example:

  • Identifying all bills in a specific deletion group: SELECT bed.delete_entity_sequence_id, bed.bill_sequence_id, bs.assembly_item_id FROM bom_delete_entities bed, bom_structures_b bs, bom_delete_groups bdg WHERE bed.delete_group_sequence_id = bdg.delete_group_sequence_id AND bed.bill_sequence_id = bs.bill_sequence_id AND bdg.group_name = '&GROUP_NAME';
  • Troubleshooting errors by joining to the BOM_DELETE_ERRORS table to see why specific entity records failed to delete.

Direct manipulation of this table is strongly discouraged; all deletions should be driven through the standard Oracle APIs and concurrent programs.

Related Objects

As indicated by the foreign key relationships, BOM_DELETE_ENTITIES is the central node in a deletion control schema. It has a mandatory parent relationship with BOM_DELETE_GROUPS, which defines the overall deletion job. Its links to BOM_STRUCTURES_B and BOM_OPERATIONAL_ROUTINGS tie it to the core manufacturing data. Furthermore, it is a parent table to two important logging tables: BOM_DELETE_ERRORS, which stores specific error messages for failed entity deletions, and BOM_DELETE_SUB_ENTITIES, which may track dependent components or operations within the main entity. This network of tables ensures the system maintains a complete audit trail and can roll back or report on deletion processes comprehensively.