Results for “capacity_units”

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

Overview

The WIP_DEPT_RESOURCES_V view is a reporting and integration object owned by the APPS schema in Oracle E-Business Suite, defined within the Work in Process (WIP) product family. Its documented purpose is to present the resources owned by a department, consolidating department-level resource assignments with the underlying resource master data. The view joins resource definitions, department-to-resource assignments, and lookup translations to produce a denormalized, human-readable result set suitable for enquiry screens, concurrent programs, and custom reporting.

The user's search term rate_variance_account maps directly to a column exposed by this view. RATE_VARIANCE_ACCOUNT is sourced from BOM_RESOURCES and identifies the General Ledger account used to absorb the difference between the standard resource rate and the actual rate charged when resource costs are applied to a work order. Its presence in this view makes department-owned resources the natural query point for cost-accounting and variance analysis reporting.

Underlying Base Objects

The view is constructed over the following documented objects:

• BOM_RESOURCES (SYNONYM) — the resource master, supplying resource code, cost element, unit of measure, standard rate flag, absorption account, and the RATE_VARIANCE_ACCOUNT.
• BOM_DEPARTMENTS (SYNONYM) — departmental definitions, supplying department code and organization identifier.
• BOM_DEPARTMENT_RESOURCES_V (VIEW) — the department-to-resource assignment view, supplying capacity units, resource group name, CTP flag, ATP rule, and the 24-hour availability flag.
• MFG_LOOKUPS (VIEW) — referenced three times (aliases ML1, ML2, ML3) to translate coded values into descriptive meanings.

Resource identity is established by the join between BR.RESOURCE_ID and BDR.RESOURCE_ID, while departmental scope is established by BD.DEPARTMENT_ID = BDR.DEPARTMENT_ID. Lookup joins are constrained to BOM_RESOURCE_TYPE, SYS_YES_NO, and CST_BASIS, with the basis-type lookup defaulted through NVL(BR.DEFAULT_BASIS_TYPE, 1).

Key Columns

Column groups of practical importance include:

• Department and organization context: DEPARTMENT_ID, DEPARTMENT_CODE, ORGANIZATION_ID.
• Resource identity and grouping: RESOURCE_ID, RESOURCE_CODE, RESOURCE_DESCRIPTION, RESOURCE_GROUP_NAME, RESOURCE_TYPE.
• Capacity and planning: CAPACITY_UNITS, CTP_FLAG, AVAILABLE_24_HRS_FLAG, EXCEPTION_SET_NAME, ATP_RULE_ID, SHARE_FROM_DEPARTMENT.
• Costing: COST_ELEMENT_ID, STANDARD_RATE_FLAG, DEFAULT_BASIS_TYPE and its translated BASIS_TYPE, ABSORPTION_ACCOUNT, ALLOW_COSTS_FLAG, AUTOCHARGE_TYPE, FUNCTIONAL_CURRENCY_FLAG, and RATE_VARIANCE_ACCOUNT.
• Purchasing linkage: PURCHASE_ITEM_ID, EXPENDITURE_TYPE.

Descriptive columns RESOURCE_DESCRIPTION and SHARE_FROM_DEPARTMENT are wrapped in NVL(..., ' ') to return a blank rather than null, simplifying concatenation and display in reports.

Common Use Cases and Queries

Typical uses include departmental resource listings, rate and variance account review, and feeding custom cost reports. A query targeting the searched column might read:

• SELECT department_code, resource_code, rate_variance_account FROM apps.wip_dept_resources_v WHERE organization_id = :org_id;
• SELECT department_code, resource_code, absorption_account, rate_variance_account FROM apps.wip_dept_resources_v WHERE resource_code = :resource;
• SELECT resource_group_name, COUNT(*) FROM apps.wip_dept_resources_v GROUP BY resource_group_name;

Because RATE_VARIANCE_ACCOUNT is a copied attribute of the resource master rather than an assignment-level attribute, results are consistent across every department sharing the resource.