Search Results bom_department_classes_n1

Overview

BOM.BOM_DEPARTMENT_CLASSES is a reference and grouping table within the Oracle E-Business Suite Bills of Material (BOM) module. It stores the definitions of department classes, which are used to organize and categorize manufacturing departments within a given inventory organization. Department classes provide a classification layer above individual departments, allowing planners, cost accountants, and shop-floor supervisors to group departments that share similar process characteristics, cost behavior, or routing usage. The table is owned by the BOM schema and is flagged VALID in the ETRM 12.2.2 catalog with 28 documented columns. It resides in the APPS_TS_TX_DATA tablespace, and its indexes reside in APPS_TS_TX_IDX. From a Data Vault modeling perspective, this object is heuristically classified as satellite-leaning, since it carries descriptive attributes attached to a composite business key rather than serving as a transaction link.

Key Information Stored

Each row defines one department class scoped to one organization. The business key is composed of DEPARTMENT_CLASS_CODE (VARCHAR2(10)) and ORGANIZATION_ID (NUMBER); together they constitute the primary key BOM_DEPARTMENT_CLASSES_PK. The unique index BOM_DEPARTMENT_CLASSES_U1 enforces the same combination, making it the authoritative unique business-key candidate. The non-unique index BOM_DEPARTMENT_CLASSES_N1 on ORGANIZATION_ID supports organization-scoped lookups.

• DEPARTMENT_CLASS_CODE — user-defined short code identifying the class.
• ORGANIZATION_ID — the inventory organization that owns the class; foreign key to MTL_PARAMETERS.
• DESCRIPTION — free-text description up to 240 characters.
• ATTRIBUTE_CATEGORY — descriptive flexfield structure defining column.
• ATTRIBUTE1 through ATTRIBUTE15 — DFF segments (VARCHAR2(150) each).
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard Who audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent Who columns identifying the concurrent program that last touched the row.

Common Use Cases and Queries

Department classes are typically consumed when defining departments, reporting on routing and resource groups, and building cost-rollup views. A common pattern joins the class to its organization to list class codes for a plant:

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

Reporting queries often join through the DFF attributes for local extensions, or left-join to MTL_PARAMETERS to resolve organization names. Because the DFF segments carry no documented semantic meaning, extracting them requires querying FND_DESCR_FLEX_COL_USAGE_VL to resolve the segment labels for ATTRIBUTE_CATEGORY context.

Related Objects

• MTL_PARAMETERS — parent organization referenced by ORGANIZATION_ID; the documented FK.
• BOM_DEPARTMENTS — departments grouped by a department class.
• BOM_DEPARTMENT_RESOURCES — resources assigned to departments, reported through class groupings.
• BOM_OPERATION_RESOURCES — routing resources that reference departments under a class.
• FND_DESCR_FLEX_COL_USAGE_VL and FND_DESCR_FLEX_CONTEXTS_VL — descriptive flexfield metadata for the ATTRIBUTE* segments.
• FND_CONCURRENT_REQUESTS — resolves the concurrent Who columns (REQUEST_ID, PROGRAM_ID) to the program that last updated the row.