Search Results mrp_planned_resource_reqs




Overview
Explore in AI Chat

Overview

The BOM_DEPARTMENTS table is a core master data table within the Oracle E-Business Suite Bills of Material (BOM) module. It serves as the central repository for defining manufacturing and service departments across inventory organizations. A department represents a distinct physical area or logical grouping within a plant or facility where specific operations, such as assembly, machining, or inspection, are performed. This table is fundamental to defining routing and operational sequences for manufactured items, assigning resources and overheads for costing, and supporting capacity planning and shop floor control. Its integrity is critical for the seamless functioning of manufacturing, cost management, and related enterprise asset management processes.

Key Information Stored

The table's primary identifier is the DEPARTMENT_ID column, which serves as the system-generated primary key (BOM_DEPARTMENTS_PK). Business-unique identification is enforced by a unique key (BOM_DEPARTMENTS_UK1) on the combination of DEPARTMENT_CODE and ORGANIZATION_ID, ensuring department codes are unique within each inventory organization. Key columns include ORGANIZATION_ID, which links the department to a specific inventory organization defined in MTL_PARAMETERS, and LOCATION_ID, which optionally ties the department to a physical address in HR_LOCATIONS_ALL. Other typical attributes stored are the department description, inactive date, and various creation and last update audit columns.

Common Use Cases and Queries

This table is central to numerous manufacturing and costing transactions. Common use cases include defining and maintaining the list of active departments for an organization, setting up routing operations, and assigning departmental overhead rates for product costing. A typical query retrieves all active departments for a specific organization to populate a list of values (LOV) in a form or report. For example:

SELECT department_code, description
FROM bom_departments
WHERE organization_id = :p_org_id
AND NVL(disable_date, SYSDATE+1) > SYSDATE
ORDER BY department_code;

Another critical use is in cost rollup and analysis, where transactional data from cost tables is joined to BOM_DEPARTMENTS to report costs by department. Integration with Oracle Asset Tracking and Service also relies on this table to associate work with specific service departments.

Related Objects

As indicated by its extensive foreign key relationships, BOM_DEPARTMENTS is a heavily referenced master table. Key dependent objects include: