Results for “bom_delete_sub_entities”

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

Overview

BOM.BOM_DELETE_SUB_ENTITIES is a table within the Oracle EBS Bills of Material (BOM) module, owner schema BOM, documented as VALID in the ETRM repository for releases 12.1.1 and 12.2.2. Its stated purpose is to record the components and operations that are to be deleted as part of a bill of material deletion request. The table functions as a staging or transient repository that captures the specific sub-entities — component assignments and operation sequences — that fall under a broader deletion entity processed by the Bill of Materials application.

From a data modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure is link. This is a modeling suggestion rather than a physical design assertion: the table resolves relationships between the parent deletion entity and the subordinate component and operation records, and its uniqueness is defined across a combination of those foreign-key columns rather than a single natural business identifier. Analysts building a dimensional or Data Vault representation of EBS BOM data should treat BOM_DELETE_SUB_ENTITIES as a many-to-many linking structure between BOM_DELETE_ENTITIES and its component/operation children.

Key Information Stored

The table contains 24 documented columns. The primary key is enforced by BOM_DELETE_SUB_ENTITIES_PK on the DELETE_ENTITY_SEQUENCE_ID column, which is the surrogate identifier for the deletion grouping and also serves as a foreign key to BOM_DELETE_ENTITIES. A unique index, BOM_DELETE_SUB_ENTITIES_U1, spans DELETE_ENTITY_SEQUENCE_ID, COMPONENT_SEQUENCE_ID, and OPERATION_SEQUENCE_ID, making these three columns the documented business-key candidate combination that uniquely identifies a deletion sub-entity row.

The most significant columns include:

• DELETE_ENTITY_SEQUENCE_ID — surrogate primary key and link to the parent deletion entity.
• COMPONENT_SEQUENCE_ID — foreign key to BOM_COMPONENTS_B, identifying the component scheduled for deletion.
• OPERATION_SEQUENCE_ID — foreign key to BOM_OPERATION_SEQUENCES, identifying the operation scheduled for deletion.
• OPERATION_SEQ_NUM — the operation sequence number for reporting and display.
• COMPONENT_ITEM_ID and ITEM_NUM — the inventory item identifier and item number of the component.
• COMPONENT_CONCAT_SEGMENTS — the concatenated item key flexfield segments for the component.
• EFFECTIVITY_DATE, DISABLE_DATE, FROM_END_ITEM_UNIT_NUMBER, and TO_END_ITEM_UNIT_NUMBER — effectivity and end-item range attributes governing the affected component.
• OPERATION_DEPARTMENT_CODE and DESCRIPTION — descriptive attributes of the deleted operation.
• DELETE_STATUS_TYPE and DELETE_DATE — status and timestamp of the deletion action.
• Standard audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical scenarios center on auditing and tracing BOM deletion activity. A common pattern joins the table to its parent deletion entity to determine which structures were affected by a given concurrent request:

• Listing all components and operations scheduled under a deletion entity: SELECT * FROM BOM.BOM_DELETE_SUB_ENTITIES WHERE DELETE_ENTITY_SEQUENCE_ID = :id;
• Tracing deletions issued by a specific concurrent program run using REQUEST_ID and PROGRAM_ID.
• Reconciling component deletions against BOM_COMPONENTS_B via COMPONENT_SEQUENCE_ID, or operation deletions against BOM_OPERATION_SEQUENCES via OPERATION_SEQUENCE_ID.
• Reporting on deletion status type distribution over time using DELETE_STATUS_TYPE and DELETE_DATE.

Because the table stores effectivity and end-item unit number ranges, it also supports analysis of which effectivity windows were impacted by a deletion request.

Related Objects

The following objects are the most significant related tables based on the documented foreign-key relationships:

• BOM_COMPONENTS_B — referenced via COMPONENT_SEQUENCE_ID; holds the base component rows.
• BOM_OPERATION_SEQUENCES — referenced via OPERATION_SEQUENCE_ID; holds operation sequence definitions.
• BOM_DELETE_ENTITIES — parent table referenced via DELETE_ENTITY_SEQUENCE_ID; defines the deletion request header level.

Together these three foreign keys constitute the linking structure that defines the table's role in the BOM deletion workflow.