Results for “department_line_code”

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

Overview

The CRP_PLANNED_RESOURCES_V view is an APPS-owned database object within the Capacity Planning (CRP) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It presents the resource definitions that participate in a capacity plan, joining the transactional planning records held in CRP_PLANNED_RESOURCES with the descriptive and configuration attributes maintained by the Bills of Material and Work in Process modules. The view therefore provides a denormalized, report-friendly projection of resource capacity data, exposing department ownership, resource codes, utilization thresholds, efficiency factors, and line-level rate limits in a single row per planned resource.

Because the object is a view rather than a table, it carries no independent storage and is always read in the context of its base objects. It is typically consumed by capacity reports, custom concurrent programs, and integration extracts that need resource-level detail without navigating the full BOM and WIP table relationships manually.

Underlying Base Objects

The view is defined over the following documented objects:

• CRP_PLANNED_RESOURCES — the driving table, supplying the planning-specific attributes such as utilization, shortage and excess types, and descriptive flexfield columns.
• BOM_RESOURCES — supplies resource code, resource type, and disable date.
• BOM_DEPARTMENT_RESOURCES — supplies the resource group name associated with the owning department and resource.
• BOM_DEPARTMENTS — joined twice, once as OWNING for the owning department and once as USING for the using department.
• WIP_LINES — supplies line code, description, maximum rate, and minimum rate.
• MFG_LOOKUPS — resolves the resource type lookup code to its display meaning.
• MTL_PARAMETERS — supplies the organization code for the inventory organization.

All outer joins to the descriptive objects are marked with the (+) operator, ensuring that a planned resource row is preserved even when its associated department, line, or resource definition is absent or disabled.

Key Columns

Among the most significant columns are ORGANIZATION_ID and ORGANIZATION_CODE, which scope the resource to an inventory organization, and RESOURCE_ID with RESOURCE_CODE, which identify the resource itself. Department context is provided by OWNING_DEPARTMENT_ID, DEPARTMENT_ID, and the resolved department codes and class codes. Utilization controls include MAX_UTILIZATION, MIN_UTILIZATION, OVERUTILIZED_PERCENT, UNDERUTILIZED_PERCENT, RESOURCE_SHORTAGE_TYPE, RESOURCE_EXCESS_TYPE, and EFFICIENCY. Where a resource is tied to a production line, the view exposes MAXIMUM_RATE and MINIMUM_RATE from WIP_LINES; the MIN_RATE term frequently used in ad hoc queries corresponds to the MINIMUM_RATE column, which defines the lower throughput boundary for the line. Standard audit columns and fifteen descriptive flexfield attributes are also passed through.

Common Use Cases and Queries

Typical uses include capacity reporting by department, identifying resources operating below minimum or above maximum line rates, and extracting resource master data for planning integrations. A representative query retrieving minimum rate and utilization data is:

• SELECT organization_code, resource_code, department_code, minimum_rate, maximum_rate, utilization, efficiency FROM crp_planned_resources_v WHERE organization_id = :p_org_id ORDER BY resource_code;
• SELECT resource_code, minimum_rate FROM crp_planned_resources_v WHERE minimum_rate IS NOT NULL AND resource_shortage_type IS NOT NULL;

When the object is queried for min_rate, the resolved column is MINIMUM_RATE. Reports should account for the outer joins, since line-related columns may return null for resources not assigned to a production line.