Search Results bom_delete_entity_type

Overview

APPS.BOM_DELETE_ENTITIES_V is a reporting and inquiry view in Oracle E-Business Suite (12.1.1 and 12.2.2) that presents the contents of the Bill of Materials entity deletion staging table in a decoded, human-readable form. The base table BOM_DELETE_ENTITIES records the discrete work items that the BOM deletion concurrent programs are asked to process—individual bills, routings, or item-level deletion requests—together with their processing status. The view joins that table to the manufacturing lookup views to translate the internal code values held in DELETE_ENTITY_TYPE and DELETE_STATUS_TYPE into their lookup meanings, and to MTL_PARAMETERS to supply the inventory organization code.

The user search term "bom_delete_entity_type" corresponds directly to the lookup type referenced in the view definition and to the DELETE_ENTITY_TYPE column it decodes. This view is therefore the standard access point for anyone investigating what the BOM deletion process has queued, what it has completed, and what remains outstanding.

The view is a non-key-preserving, read-only construct; it exposes no DML of its own and is not part of the core transactional model. Its role is purely diagnostic and reporting-oriented.

Underlying Base Objects

The view is defined over four documented objects:

• BOM_DELETE_ENTITIES (synonym to the underlying application table) — the driving table, aliased BDE, from which all processing rows originate.
• MFG_LOOKUPS (view, aliased ML1 and ML2) — joined twice via outer joins to resolve lookup meanings. ML1 resolves DELETE_ENTITY_TYPE against lookup type 'BOM_DELETE_ENTITY_TYPE'; ML2 resolves DELETE_STATUS_TYPE against lookup type 'BOM_DELETE_STATUS_TYPE'.
• MTL_PARAMETERS (synonym, aliased MP) — joined on ORGANIZATION_ID to return the inventory organization code.

An inner join is used between BOM_DELETE_ENTITIES and MTL_PARAMETERS, so rows with an ORGANIZATION_ID that does not resolve to a defined organization (for example, rows logged against a disabled or purged parameter record) will not appear.

Key Columns

• DELETE_ENTITY_SEQUENCE_ID / DELETE_GROUP_SEQUENCE_ID — surrogate identifiers for the individual deletion work item and the group it belongs to.
• DELETE_ENTITY_TYPE / DELETE_ENTITY — the coded entity type and its BOM_DELETE_ENTITY_TYPE lookup meaning (for example, bill, routing, or item-level entity).
• DELETE_STATUS_TYPE / DELETE_STATUS — the coded status and its BOM_DELETE_STATUS_TYPE lookup meaning, indicating pending, processed, failed, or similar states.
• BILL_SEQUENCE_ID / ROUTING_SEQUENCE_ID — references to the specific bill or routing being removed.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, ORGANIZATION_CODE — the item and inventory organization context.
• ALTERNATE_DESIGNATOR, ITEM_DESCRIPTION, ITEM_CONCAT_SEGMENTS — descriptive item attributes denormalized onto the row.
• DELETE_DATE, PRIOR_PROCESS_FLAG, PRIOR_COMMIT_FLAG — timing and processing state indicators.
• Audit and concurrent columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical uses include auditing a deletion request, verifying which entity types are pending, and diagnosing failures by status. A basic status listing:

SELECT organization_code, delete_entity, delete_status, item_concat_segments, delete_date FROM apps.bom_delete_entities_v WHERE delete_status_type NOT IN (SELECT lookup_code FROM mfg_lookups WHERE lookup_type = 'BOM_DELETE_STATUS_TYPE' AND meaning = 'Processed') ORDER BY delete_date;

To enumerate the decoded entity types for a specific concurrent request:

SELECT delete_entity, COUNT(*) FROM apps.bom_delete_entities_v WHERE request_id = :req_id GROUP BY delete_entity;