Results for “actual_hours”

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

Overview

WIP_BIS_UTZ_CATNOITEM_V is an Oracle EBS 12.1.1 / 12.2.2 APPS-owned reporting view in the Work in Process (WIP) product family. Its documented description — "Resource Utilization including Product Category without Inventory Item" — defines its purpose precisely: it aggregates manufacturing resource utilization (applied versus available hours) across organizational, departmental, geographic, and product-category dimensions, while deliberately excluding the inventory item dimension present in related WIP Business Intelligence System (BIS) views. Because the item-level detail is collapsed, utilization totals are reported at the category level rather than per item.

This view underlies the discrete manufacturing utilization dashboards and BI Publisher extracts commonly published through Oracle Manufacturing Operations Center, OBIEE, and custom concurrent programs in EBS environments. Users searching for "department_code" typically encounter this view while building labor or resource-utilization reports, since DEPARTMENT_CODE is a first-class grouping column rather than a derived attribute.

Underlying Base Objects

The view is defined exclusively over one base object: the APPS synonym WIP_BIS_PROD_INDICATORS, which is the production indicators fact table populated by the WIP BIS data collection program. No joins to WIP resources, departments, or inventory tables are performed by the view itself; instead, denormalized descriptive columns (department, resource, location, area, country, region, category) are already materialized within the base table.

The defining query filters WHERE EXISTING_FLAG = 1 and performs an outer grouping over SUM(NVL(APPLIED_HOURS_UTZ, 0)), so only active-existing records are returned, and null applied-hour values are coerced to zero. AVAILABLE_HOURS and the period columns are carried into the GROUP BY, which means multiple base rows with identical dimensional and available-hour attributes but differing applied hours are consolidated into a single output row.

Key Columns

• LEDGER_ID / LEDGER_NAME — accounting ledger context (rendered as SET_OF_BOOKS_ID / SET_OF_BOOKS_NAME in the view SQL).
• LEGAL_ENTITY_ID / LEGAL_ENTITY_NAME and OPERATING_UNIT_ID / OPERATING_UNIT_NAME — legal and business-unit reporting hierarchy.
• ORGANIZATION_ID / ORGANIZATION_NAME — the inventory organization owning the manufacturing activity.
• DEPARTMENT_ID / DEPARTMENT_CODE — the manufacturing department; DEPARTMENT_CODE is the human-readable key most often used for filtering and grouping.
• RESOURCE_ID / RESOURCE_CODE — the resource whose applied hours are being accumulated.
• LOCATION_ID, AREA_CODE, AREA_NAME, COUNTRY_CODE, COUNTRY_NAME, REGION_CODE, REGION_NAME — geographic attributes of the resource location.
• TRANSACTION_DATE — date of the utilization transaction.
• CATEGORY_ID / CATEGORY_NAME — product category, the aggregation level replacing inventory item.
• ACTUAL_HOURS — summed applied utilization hours (the aggregated APPLIED_HOURS_UTZ).
• AVAILABLE_HOURS — capacity hours for the same dimensional combination.
• PERIOD_SET_NAME, PERIOD_YEAR, PERIOD_QUARTER, PERIOD_MONTH — accounting period attributes for time-based reporting.

Common Use Cases and Queries

The view supports utilization-rate reporting by department, resource, or category, and is frequently queried for period-over-period capacity analysis. A representative query isolating department-level utilization for a single organization and period is:

SELECT department_code, period_year, period_month, SUM(actual_hours) actual_hours, SUM(available_hours) available_hours FROM apps.wip_bis_utz_catnoitem_v WHERE organization_id = :org_id AND period_year = :yr GROUP BY department_code, period_year, period_month ORDER BY department_code;

A second common pattern ranks utilization by product category within a geographic region, exploiting CATEGORY_NAME and REGION_NAME, and joining to WIP departments or resources only when additional descriptive attributes are required beyond the columns already denormalized in the view. Because the view excludes item-level detail, it is not suitable for costed item analysis; item-level questions should be directed to the sibling item-inclusive WIP BIS views.

Reporting caution: the GROUP BY includes AVAILABLE_HOURS, so duplicate available-hour values can produce multiple rows for the same dimensional key. Report authors should aggregate explicitly rather than assuming one row per department, resource, and period.