Results for “sql_statement_name”

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

Overview

BOM_DELETE_ERRORS_V is a dictionary view owned by the APPS schema in Oracle E-Business Suite, belonging to the Bills of Material (BOM) product family. As its description states, the view exposes "errors occurring when deleting entities" — specifically failures raised by the concurrent programs that purge or delete bill of material structures, components, and operations. During such delete processes, the BOM deletion engine executes a defined series of SQL statements; when any statement fails, diagnostic information is captured in the underlying error table and surfaced through this view. The view is documented as VALID and is available in both EBS 12.1.1 and 12.2.2.

Its principal role is diagnostic and reporting-oriented. Rather than presenting raw foreign-key identifiers alone, the view joins the error table to the SQL statement definition table so that each error row is accompanied by a human-readable message name. This makes the view suitable for troubleshooting concurrent delete requests, building exception reports, and integrating error data into custom monitoring or reconciliation solutions.

Underlying Base Objects

Per the documented ETRM metadata, BOM_DELETE_ERRORS_V is defined over two base objects (represented in APPS as synonyms):

• BOM_DELETE_ERRORS (BDE) — the primary transactional table holding one row per delete failure, including the entity identifiers, statement name, sequence numbers, and standard WHO/request audit columns.
• BOM_DELETE_SQL_STATEMENTS (BDSS) — a reference table mapping each SQL statement name to a descriptive message name.

The two objects are joined on SQL_STATEMENT_NAME. Because the join is an inner equi-join, an error row is returned through the view only when its statement name has a corresponding entry in BOM_DELETE_SQL_STATEMENTS. All columns except MESSAGE_NAME are sourced from the error table; MESSAGE_NAME is the single attribute contributed by the statement definition table. The view text also exposes the underlying BDE.ROWID aliased as ROW_ID, providing a direct handle to the physical row for updatable or drill-down purposes.

Key Columns

• ROW_ID — the ROWID of the underlying BOM_DELETE_ERRORS row.
• DELETE_ENTITY_SEQUENCE_ID — the sequence identifier of the delete entity, the primary key and the column most commonly used to locate a specific delete failure. This is the column associated with the user search term "delete_entity_sequence_id".
• COMPONENT_SEQUENCE_ID — identifies the bill component involved in the failed deletion.
• OPERATION_SEQUENCE_ID — identifies the routing operation involved in the failed deletion.
• ERROR_SEQUENCE_NUMBER — ordering number assigned to the error occurrence.
• SQL_STATEMENT_NAME — internal name of the SQL statement that raised the error; the join key to the statement definitions.
• MESSAGE_NAME — descriptive message associated with the failed SQL statement.
• Audit and concurrent request 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, which together identify who created the error record and which concurrent request produced it.

Common Use Cases and Queries

The most frequent use is investigating a delete request that completed with errors. Because REQUEST_ID is exposed, the view can be filtered by the concurrent request that failed, and the results grouped by MESSAGE_NAME to reveal the dominant failure mode.

Sample query — all errors for a specific delete entity:

• SELECT delete_entity_sequence_id, component_sequence_id, operation_sequence_id, sql_statement_name, message_name FROM bom_delete_errors_v WHERE delete_entity_sequence_id = :entity_id ORDER BY error_sequence_number;

Sample query — errors associated with a concurrent request:

• SELECT request_id, sql_statement_name, message_name, COUNT(*) FROM bom_delete_errors_v WHERE request_id = :request_id GROUP BY request_id, sql_statement_name, message_name;

Sample query — most recent failures across the instance:

• SELECT delete_entity_sequence_id, component_sequence_id, message_name, creation_date, created_by FROM bom_delete_errors_v ORDER BY creation_date DESC;

Because the view is a read-only projection over transactional and reference tables, it should be queried for diagnostics only; corrections are made by resolving the condition reported in MESSAGE_NAME and resubmitting the delete process. The view is not designed to be updated directly.