Search Results bom_delete_sub_entities_v




Overview
Explore in AI Chat

Overview

BOM_DELETE_SUB_ENTITIES_V is an APPS-owned database view in the Oracle E-Business Suite Bills of Material (BOM) module. The ETRM documentation describes its purpose concisely as "Component and operations to be deleted," which reflects its function as a reporting and integration surface over the delete-processing infrastructure used by the BOM delete concurrent programs. Rather than exposing raw delete-staging rows, the view joins the underlying staging entity table to the manufacturing lookup set and resolves the internal lookup code stored on each row into a translated meaning.

The view is validated and present in both Oracle EBS 12.1.1 and 12.2.2. It exists primarily so that reports, concurrent program outputs, and custom extensions can present the disposition of pending bill deletions without having to re-implement the lookup join, while preserving the full audit and request context (WHO columns and concurrent request identifiers) attached to each staged deletion record.

Underlying Base Objects

The registered ETRM metadata identifies two referenced base objects:

The join between the two is an outer join: BDSE.DELETE_STATUS_TYPE (+) = ML.LOOKUP_CODE. This means every staged delete row is returned even when no matching lookup code is defined, which is important for troubleshooting rows whose status code is non-standard or obsolete. The ROW_ID column is derived from BDSE.ROWID, preserving a direct row identifier back to the base table for update-oriented integrations.

Key Columns

Common Use Cases and Queries

Typical uses include auditing which components and operations were queued or processed for deletion, reviewing the outcome status of a BOM delete request, and feeding the results into custom reports or downstream interfaces. A representative query listing pending or processed deletions by status is:

SELECT delete_entity_sequence_id,
       component_sequence_id,
       item_num,
       operation_department_code,
       delete_status,
       delete_date,
       request_id
  FROM apps.bom_delete_sub_entities_v
 WHERE delete_status_type = 'PENDING'
 ORDER BY delete_date;

A second common pattern isolates everything staged by one concurrent request, which supports operational troubleshooting of a specific delete run:

SELECT request_id,
       component_concat_segments,
       operation_seq_num,
       from_end_item_unit_number,
       to_end_item_unit_number,
       delete_status
  FROM apps.bom_delete_sub_entities_v
 WHERE request_id = :p_request_id;

Because the view is a pure join with no substitution variables or client-specific context, it can be queried directly, joined to EGP_SYSTEM_ITEMS_VL for item descriptions, or embedded in a BI Publisher data template. It should be treated as a read-only reporting object; updates should target BOM_DELETE_SUB_ENTITIES through supported APIs and concurrent programs rather than through this view.