Results for “delete_entity_type”

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

Overview

BOM.BOM_DELETE_SQL_STATEMENTS is a Bills of Material (BOM) configuration and control table that stores the SQL statements Oracle EBS uses to check for and delete entity records during bill of material and component deletion processing. Rather than embedding deletion logic directly in application code, EBS externalizes it: each row defines a named SQL statement, its execution type, the entity type it targets, an execution sequence, and various control flags. This design allows Oracle and, in principle, customers to extend or tune the deletion engine that governs how BOM structures and related entities are removed while respecting referential and business constraints.

From a data modeling perspective, the mined relationship structure suggests this table behaves as a hub-leaning entity: it is the parent referenced by BOM_DELETE_ERRORS via the SQL_STATEMENT_NAME column, and it holds a stable business key rather than merely describing another entity. The SQL_STATEMENTS_PK primary key makes it a candidate hub in a Data Vault model, with the descriptive attributes (flags, dates, SQL text) potentially split into a satellite.

Key Information Stored

The table contains 22 documented columns; the most significant are summarized below.

• SQL_STATEMENT_NAME — The primary key (BOM_DELETE_SQL_STATEMENTS_PK) and the natural business identifier for each deletion statement definition. This column is also the target of the foreign key from BOM_DELETE_ERRORS.
• SQL_STATEMENT_TYPE — Classifies the purpose of the statement (for example, check versus delete). Part of the unique index BOM_DELETE_SQL_STATEMENTS_U2.
• DELETE_ENTITY_TYPE — Identifies which entity the statement operates on. Also part of the U2 business-key candidate.
• SEQUENCE_NUMBER — Controls execution order; combined with the two columns above, it forms the unique business key in SQL_STATEMENTS_U2.
• SQL_STATEMENT — The actual SQL text executed by the deletion engine.
• ACTIVE_FLAG — Enables or disables a given statement during processing.
• DELETE_ON_SUCCESS_FLAG — Determines whether the entity is deleted once the associated check passes.
• MESSAGE_NAME — Reference to a message used when a check fails or validation is reported.
• ARCHIVE_TABLE_NAME — Names the archive target for records displaced during deletion.
• PREDEFINED_FLAG — Distinguishes Oracle-seeded statements from user-defined entries.
• DESCRIPTION and PRODUCT_NAME — Documentation and product attribution.
• ZD_EDITION_NAME — The editioning column supporting Oracle EBS 12.2 online patching; it appears in both unique indexes (U1 and U2).
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and concurrent program columns (REQUEST_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) provide standard EBS who/when tracking.

Common Use Cases and Queries

Administrators and developers inspect this table to determine how BOM deletion is orchestrated before running large purge or cleanup operations, and to diagnose failures reported in BOM_DELETE_ERRORS. A representative query joins the two tables on the statement name:

SELECT s.SQL_STATEMENT_NAME, s.SQL_STATEMENT_TYPE, s.DELETE_ENTITY_TYPE, s.SEQUENCE_NUMBER, e.ERROR_MESSAGE FROM BOM.BOM_DELETE_SQL_STATEMENTS s, BOM.BOM_DELETE_ERRORS e WHERE e.SQL_STATEMENT_NAME = s.SQL_STATEMENT_NAME ORDER BY s.SEQUENCE_NUMBER;

Developers query for active, predefined statements by entity type to understand the delete sequence for a given BOM structure, and DBAs filtering on ZD_EDITION_NAME can isolate statements visible in the current edition during a 12.2 online patch cycle.

Related Objects

• BOM_DELETE_ERRORS — The primary dependent table; its SQL_STATEMENT_NAME column is a foreign key to this table, capturing failures when a deletion statement errors.
• BOM_DELETE_ERRORS.SQL_STATEMENT_NAME — The join column linking error records back to their originating statement definition.
• BOM_DELETE_SQL_STATEMENTS_PK — The primary key constraint enforcing uniqueness of SQL_STATEMENT_NAME.
• BOM_DELETE_SQL_STATEMENTS_U1 and BOM_DELETE_SQL_STATEMENTS_U2 — Unique indexes defining business-key candidates, both including ZD_EDITION_NAME.
• BOM Bills of Material and related entity tables — Referenced indirectly through SQL_STATEMENT text and DELETE_ENTITY_TYPE.