Results for “bom_delete_errors”

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

Overview

BOM_DELETE_ERRORS is a transactional table in the Oracle Bills of Material (BOM) module that captures error conditions encountered when the deletion engine processes bill of material entities. In Oracle EBS 12.1.1 and 12.2.2, the BOM deletion framework removes components, operations, and related structures in a controlled sequence; when any step of that sequence fails, the failure is recorded here rather than being lost, allowing the deletion process to be diagnosed, retried, or reversed. The table therefore functions as an exception log for the mass-delete utilities rather than as a master or setup table.

Under a heuristic Data Vault classification derived from the foreign key structure, BOM_DELETE_ERRORS most closely resembles a link object. This is a modeling suggestion only: the table sits between the deletion entities that were being removed and the SQL statements that failed, and its primary key is composed entirely of references plus an ordering attribute. It carries no independent business identity of its own, which is characteristic of an associative or link entity in a Data Vault model.

Key Information Stored

The table is owned by the BOM schema and, per the ETRM 12.2.2 physical schema, contains fourteen columns. The most operationally significant are the following:

• DELETE_ENTITY_SEQUENCE_ID — identifies the specific deletion entity (usually the bill or routing being purged) to which the error belongs. This is both a primary key component and a foreign key to BOM_DELETE_ENTITIES.
• COMPONENT_SEQUENCE_ID — the component row involved in the failed deletion, in bill-of-material contexts.
• OPERATION_SEQUENCE_ID — the routing operation involved, when the failed deletion concerns an operation rather than a component.
• ERROR_SEQUENCE_NUMBER — a sequential counter distinguishing multiple errors recorded against the same entity, component, and operation.
• SQL_STATEMENT_NAME — the logical name of the SQL statement that raised the error; this is a foreign key into BOM_DELETE_SQL_STATEMENTS and is the key diagnostic field for identifying the failing step.
• LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Oracle EBS audit Who columns recording creation and modification context.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent request and program attribution, allowing each error row to be tied back to the specific concurrent manager run that generated it.

The surrogate primary key is defined by BOM_DELETE_ERRORS_PK over DELETE_ENTITY_SEQUENCE_ID, COMPONENT_SEQUENCE_ID, OPERATION_SEQUENCE_ID, and ERROR_SEQUENCE_NUMBER. The unique index BOM_DELETE_ERRORS_U1 mirrors this same column set, making it the business-key candidate for the table.

Common Use Cases and Queries

The primary use case is diagnosing why a bill of material deletion or purge failed. Developers and support analysts query the table by REQUEST_ID or by DELETE_ENTITY_SEQUENCE_ID to enumerate the specific statements that did not complete:

• Identifying all failed SQL steps for a given concurrent request: SELECT SQL_STATEMENT_NAME FROM BOM_DELETE_ERRORS WHERE REQUEST_ID = :req_id;
• Reconstructing the full error context for one entity: joining back to BOM_DELETE_ENTITIES on DELETE_ENTITY_SEQUENCE_ID to recover the object being deleted.
• Reporting on error frequency by statement, to determine whether a specific deletion statement is chronically failing.

Typical SQL patterns join to the two referenced tables to resolve names and context, and filter on PROGRAM_ID or PROGRAM_UPDATE_DATE to isolate errors raised by a particular concurrent program run. Because the table records technical failures rather than business data, it is generally used for troubleshooting and cleanup rather than for operational reporting, and rows are commonly purged once the underlying deletion issue is resolved.

Related Objects

The following objects are the most significant in relation to BOM_DELETE_ERRORS, based on the documented foreign key relationships:

• BOM_DELETE_SQL_STATEMENTS — referenced by BOM_DELETE_ERRORS.SQL_STATEMENT_NAME; provides the definitions of the statements that may fail.
• BOM_DELETE_ENTITIES — referenced by BOM_DELETE_ERRORS.DELETE_ENTITY_SEQUENCE_ID; supplies the parent deletion entity context.
• BOM_BILL_OF_MATERIALS and BOM_COMPONENTS — the underlying structures being deleted, including the COMPONENT_SEQUENCE_ID values recorded here.
• BOM_OPERATION_SEQUENCES — the routing operation source for OPERATION_SEQUENCE_ID values.
• BOM_DELETE_ERRORS_PK and BOM_DELETE_ERRORS_U1 — the primary and unique indexes that enforce row identity and support lookups by entity.
• FND_CONCURRENT_REQUESTS — the concurrent request context via REQUEST_ID, used to correlate errors with a specific program run.