Results for “bom_delete_groups”

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

Overview

BOM_DELETE_GROUPS is a BOM schema table in Oracle E-Business Suite (validated in 12.1.1 and 12.2.2) that organizes groups of Bills of Material and Inventory entities for coordinated deletion. Each row represents a named deletion group that bundles related BOM and INV records so they can be submitted, tracked, and purged as a single unit through the concurrent processing framework. The table acts as the parent container for the deletion workload; individual entities within a group are recorded in BOM_DELETE_ENTITIES, which references this table via the DELETE_GROUP_SEQUENCE_ID foreign key.

From a Data Vault modeling perspective, the documented relationship structure suggests this object is hub-leaning. BOM_DELETE_GROUPS serves as the anchor (hub) identified by the surrogate key DELETE_GROUP_SEQUENCE_ID, with BOM_DELETE_ENTITIES acting as a link or dependent child capturing the entities associated with each group. This heuristic classification reflects the FK topology disclosed in the ETRM metadata rather than a formal Data Vault design in EBS itself.

Key Information Stored

The table spans 20 documented columns. The most significant are:

• DELETE_GROUP_SEQUENCE_ID — Surrogate primary key (BOM_DELETE_GROUPS_PK) and the unique index BOM_DELETE_GROUPS_U1. Referenced by BOM_DELETE_ENTITIES.
• DELETE_GROUP_NAME — Business-key candidate; combined with ORGANIZATION_ID forms unique index BOM_DELETE_GROUPS_U2.
• ORGANIZATION_ID — Inventory organization owning the deletion group; second component of the business key.
• DELETE_TYPE — Classifies the nature of the deletion being performed.
• ACTION_TYPE — Specifies the action to take on the grouped entities.
• ENGINEERING_FLAG — Indicates whether engineering (ECO) context applies.
• DELETE_COMMON_BILL_FLAG — Controls handling of common bill of material structures.
• DELETE_ORG_TYPE and ORGANIZATION_HIERARCHY — Determine the organizational scope of the deletion.
• DATE_LAST_SUBMITTED — Timestamp of the most recent submission of the deletion group.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — Concurrent program audit trail for the submission.
• DESCRIPTION — Free-text description of the group's purpose.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include identifying deletion groups pending submission, tracing which entities belong to a group, and auditing deletions by organization or concurrent request. A user searching on delete_group_sequence_id is usually resolving the parent-child link to BOM_DELETE_ENTITIES or querying group metadata.

• Retrieve group details: SELECT delete_group_sequence_id, delete_group_name, organization_id, delete_type, action_type FROM bom.bom_delete_groups WHERE delete_group_sequence_id = :id;
• List entities by group: SELECT e.* FROM bom.bom_delete_entities e, bom.bom_delete_groups g WHERE e.delete_group_sequence_id = g.delete_group_sequence_id AND g.organization_id = :org_id;
• Business-key lookup: SELECT * FROM bom.bom_delete_groups WHERE organization_id = :org_id AND delete_group_name = :name;
• Submission audit: filter by DATE_LAST_SUBMITTED or REQUEST_ID to reconcile group submissions with concurrent requests.

Related Objects

• BOM_DELETE_ENTITIES — Child table holding the individual BOM/INV entities; joined on DELETE_GROUP_SEQUENCE_ID (FK to BOM_DELETE_GROUPS).
• BOM_DELETE_GROUPS_PK / _U1 / _U2 — Primary and unique indexes enforcing surrogate and business-key uniqueness.
• MTL_PARAMETERS / HR_ALL_ORGANIZATION_UNITS (via ORGANIZATION_ID) — Resolve organization context.
• FND_CONCURRENT_REQUESTS (via REQUEST_ID) — Links groups to the concurrent deletion job.
• BOM Bills of Material and Inventory entity tables — The actual records targeted for deletion through the referenced entities.