Search Results bom_department_classes_pk

Overview

BOM.BOM_DEPARTMENT_CLASSES is a Bills of Material (BOM) module table that stores department class definitions used within Oracle E-Business Suite manufacturing and shop floor operations. Department classes provide a grouping mechanism for departments in a manufacturing organization, allowing departments to be categorized by functional type or reporting purpose. The table serves as a reference and classification object that supports resource assignment and department-level reporting across BOM and related Work in Process (WIP) functionality.

The object is owned by the BOM schema and holds a VALID status in both Oracle EBS 12.1.1 and 12.2.2. Per the provided metadata, its heuristic Data Vault classification is satellite-leaning. This classification is a modeling suggestion: the table behaves primarily as a descriptive satellite attached to an organizational hub, since its principal foreign key points to MTL_PARAMETERS.ORGANIZATION_ID and its unique key combines a descriptive code with the organization identifier. It is not a pure transaction or link table.

Key Information Stored

The table's documented physical schema contains 28 columns. The most operationally significant are described below.

• DEPARTMENT_CLASS_CODE — The user-defined identifier (business code) for the department class. It forms part of the composite primary key and is the primary human-readable reference.
• ORGANIZATION_ID — The inventory/manufacturing organization to which the department class belongs. It is the foreign key referencing MTL_PARAMETERS and scopes the class definition per organization.
• DESCRIPTION — Free-text description of the department class, used in reports and lookup windows.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit (WHO) columns tracking creation and modification.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard DFF (Descriptive Flexfield) columns, enabling customers to add org-specific classification attributes without schema changes.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program/request tracking columns populated when the row is created or updated through a concurrent manager job.

The surrogate primary key is BOM_DEPARTMENT_CLASSES_PK, defined over DEPARTMENT_CLASS_CODE and ORGANIZATION_ID. The unique index BOM_DEPARTMENT_CLASSES_U1 mirrors the same two columns, making them the documented business-key candidates and enforcing uniqueness of a department class code within an organization.

Common Use Cases and Queries

Typical uses include validating department class assignments during department setup, populating LOVs in Oracle Forms, and driving departmental reporting and resource utilization analysis.

To retrieve all department classes for an organization:

• SELECT department_class_code, description FROM bom.bom_department_classes WHERE organization_id = :org_id ORDER BY department_class_code;

To join to the owning organization record (leveraging the documented foreign key):

• SELECT c.department_class_code, c.description, p.organization_code FROM bom.bom_department_classes c, mtl_parameters p WHERE c.organization_id = p.organization_id;

To audit recently changed classes using the WHO columns:

• SELECT department_class_code, last_updated_by, last_update_date FROM bom.bom_department_classes WHERE last_update_date > SYSDATE - 30;

Related Objects

The following objects are significant dependencies or references, based on the documented foreign-key relationship and standard BOM/WIP modeling.

• MTL_PARAMETERS — Referenced via BOM_DEPARTMENT_CLASSES.ORGANIZATION_ID; defines the organization context.
• BOM_DEPARTMENTS — The related department master that references department classes for grouping.
• BOM_DEPARTMENT_RESOURCES — Links departments (and indirectly their classes) to resources.
• BOM_RESOURCES — Resource definitions associated with departments grouped by class.
• WIP_DEPARTMENTS / WIP entities — Consume department class information in shop-floor reporting.
• HR_ORGANIZATION_UNITS — Underlying organization/department definitions in some configurations.
• FND_FLEX_VALUES / FND_LOOKUPS — Where DFF attributes and related lookups may be validated.

These relationships should be confirmed against the specific 12.1.1 or 12.2.2 schema, as subsequent point releases may add columns or constraints.