Results for “sequencing_window”

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

Overview

BOM_DEPARTMENT_RESOURCES is a Bills of Material (BOM) foundation table in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases. It defines the association between a manufacturing department (identified by DEPARTMENT_ID) and the resources that may be used within that department (identified by RESOURCE_ID). Each row therefore represents a Department–Resource assignment, carrying the shop-floor attributes that Oracle uses for capacity planning, scheduling, costing, and constraint-based optimization.

The table sits at the intersection of the departmental hierarchy defined in BOM_DEPARTMENTS and the resource master defined in BOM_RESOURCES. Its rows are consumed by numerous downstream planning and execution objects, most notably the MRP_WIP_RESOURCES table referenced in the original search term, which is keyed on the same DEPARTMENT_ID and RESOURCE_ID columns. From a Data Vault modeling perspective, the heuristic classification suggests a hub-leaning role: the composite key (DEPARTMENT_ID, RESOURCE_ID) behaves as a durable business key anchored in BOM_DEPARTMENT_RESOURCES_PK, with foreign keys to BOM_DEPARTMENTS, BOM_RESOURCES, and MTL_ATP_RULES. The numerous descriptive columns — capacity, utilization, efficiency, and ATP-related attributes — are better regarded as satellite content layered onto that hub.

Key Information Stored

The physical schema documented in ETRM 12.2.2 defines 40 columns. The most significant are the two primary-key members, DEPARTMENT_ID and RESOURCE_ID, which together form BOM_DEPARTMENT_RESOURCES_PK and are additionally enforced by the unique business-key index BOM_DEPARTMENT_RESOURCES_U1. This dual-indexing reinforces that the pair is simultaneously the surrogate identity and the natural business key.

Capacity and scheduling attributes include SHARE_CAPACITY_FLAG and SHARE_FROM_DEPT_ID (for shared resource capacity across departments), CAPACITY_UNITS, AVAILABLE_24_HOURS_FLAG, UTILIZATION, EFFICIENCY, SCHEDULE_TO_INSTANCE, SEQUENCING_WINDOW, and IDLE_TIME_TOLERANCE. Availability and promising logic are governed by CTP_FLAG, ATP_RULE_ID, and EXCEPTION_SET_NAME. Descriptive grouping is provided by RESOURCE_GROUP_NAME. Standard audit and concurrent-program columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE — track row provenance. Fifteen flexfield slots (ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15) support DFF extensions.

Common Use Cases and Queries

Typical queries retrieve resource assignments for a given department or identify which departments exploit a particular resource. A common reporting pattern joins this table to BOM_RESOURCES to surface resource names and units of measure:

• Departmental resource listing: SELECT bdr.RESOURCE_ID, br.RESOURCE_CODE, bdr.UTILIZATION, bdr.EFFICIENCY FROM BOM_DEPARTMENT_RESOURCES bdr JOIN BOM_RESOURCES br ON br.RESOURCE_ID = bdr.RESOURCE_ID WHERE bdr.DEPARTMENT_ID = :p_dept;
• Capacity planning extracts: filter on SHARE_CAPACITY_FLAG or AVAILABLE_24_HOURS_FLAG to identify constrained shops.
• ATP/CTP diagnostics: join to MTL_ATP_RULES via ATP_RULE_ID where CTP_FLAG = 'Y'.
• MRP load analysis: join MRP_WIP_RESOURCES on DEPARTMENT_ID and RESOURCE_ID to compare WIP resource loads against departmental assignments.

These queries underpin capacity dashboards, CRP (Capacity Requirements Planning) reconciliation reports, and shop-floor scheduling extracts.

Related Objects

The most significant dependencies, all confirmed by the documented FK structure, are:

• BOM_DEPARTMENTS (parent) via DEPARTMENT_ID.
• BOM_RESOURCES (parent) via RESOURCE_ID.
• MTL_ATP_RULES (parent) via ATP_RULE_ID.
• BOM_DEPT_RES_INSTANCES (child) via DEPARTMENT_ID and RESOURCE_ID.
• BOM_RESOURCE_SHIFTS (child) via DEPARTMENT_ID and RESOURCE_ID.
• CRP_PLANNED_RESOURCES (child) via DEPARTMENT_ID and RESOURCE_ID.
• CRP_RESOURCE_HOURS (child) via DEPARTMENT_ID and RESOURCE_ID.
• MRP_WIP_RESOURCES (child) via DEPARTMENT_ID and RESOURCE_ID — the object the user searched for.

Together these relationships place BOM_DEPARTMENT_RESOURCES at the center of departmental resource configuration for BOM, CRP, and MRP workloads in EBS 12.1.1 and 12.2.2.