Results for “prior_commit_flag”

4 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BOM.BOM_DELETE_ENTITIES is a Bills of Material (BOM) module table that tracks individual entities deleted from the BOM and Inventory (INV) schemas during Oracle EBS deletion runs. It is a supporting table within the BOM delete-processing framework, which is used to remove bills of material, operational routings, and related component records while capturing the audit trail, status, and any resulting errors for each deleted object. The table is owned by the BOM schema and is documented in ETRM 12.2.2 with 23 columns.

Functionally, BOM_DELETE_ENTITIES records one row per deleted entity (a structure, a routing, or a related inventory item), grouped under a higher-level delete group. It therefore serves as a child detail table beneath BOM_DELETE_GROUPS, with sub-entity detail and error records hanging beneath it. Based on the foreign-key structure and the presence of descriptive attributes (item description, concatenated segments, alternate designator) alongside temporal audit columns, the heuristic Data Vault classification is satellite-leaning. In a data-vault modeling sense, it would most naturally be treated as a satellite attached to the delete-group hub/business key, carrying the descriptive and status context of each deletion event.

Key Information Stored

The table's surrogate primary key is DELETE_ENTITY_SEQUENCE_ID, enforced by BOM_DELETE_ENTITIES_PK and also underpinned by the unique index BOM_DELETE_ENTITIES_U1. Because the unique index is defined on the same sequence column, no separate business-key candidate is documented beyond this surrogate.

Common Use Cases and Queries

The primary use case is auditing and troubleshooting BOM/INV delete concurrent programs. Administrators query the table to confirm which structures or routings were removed in a given delete group, and to correlate failures with BOM_DELETE_ERRORS.

  • List all entities removed within a specific delete run:
    SELECT e.delete_entity_sequence_id, e.delete_entity_type,
           e.bill_sequence_id, e.routing_sequence_id,
           e.inventory_item_id, e.delete_status_type, e.delete_date
    FROM   bom.bom_delete_entities e
    WHERE  e.delete_group_sequence_id = :group_id
    ORDER BY e.delete_entity_sequence_id;
  • Identify entities that produced errors by joining to BOM_DELETE_ERRORS on DELETE_ENTITY_SEQUENCE_ID.
  • Reconcile the concurrent request that performed a deletion using REQUEST_ID and PROGRAM_ID.
  • Report on deletion history by item and organization using INVENTORY_ITEM_ID, ORGANIZATION_ID, and DELETE_DATE.

Related Objects

  • BOM.BOM_DELETE_GROUPS — Parent delete group; joins on DELETE_GROUP_SEQUENCE_ID.
  • BOM.BOM_STRUCTURES_B — Deleted bills of material; joins on BILL_SEQUENCE_ID.
  • BOM.BOM_OPERATIONAL_ROUTINGS — Deleted routings; joins on ROUTING_SEQUENCE_ID.
  • BOM.BOM_DELETE_ERRORS — Child error records; references DELETE_ENTITY_SEQUENCE_ID.
  • BOM.BOM_DELETE_SUB_ENTITIES — Child sub-entity records (for example, components); references DELETE_ENTITY_SEQUENCE_ID.
  • INV inventory item and organization tables — referenced indirectly via INVENTORY_ITEM_ID and ORGANIZATION_ID.