Search Results area_name




Overview
Explore in AI Chat

Overview

APPS.WIP_BIS_UTZ_NOCAT_V is a reporting view in Oracle E-Business Suite that exposes production utilization and applied-hours data from the Work in Process (WIP) Business Intelligence System (BIS) schema. The view is designed to support utilization reporting by presenting aggregated applied hours against available hours, broken down across the full organizational and geographic hierarchy used within EBS: set of books, legal entity, operating unit, inventory organization, department, resource, and location. The view name and the "UTZ" (utilization) and "NOCAT" (no category) tokens indicate that it is intended for utilization analysis where resource or department categorization is not applied — that is, there is no categorization dimension in the query, so all qualifying rows are aggregated together by the dimensions listed in the GROUP BY clause.

Because it is a view rather than a table, it does not store data; it is a stored SQL statement executed at query time. It is typically consumed by Oracle BIS/OBIEE-based manufacturing dashboards, Discoverer workbooks, or custom reports that need a consolidated view of applied versus available resource hours by area, department, or organization. The view deliberately filters on EXISTING_FLAG = 1, restricting output to currently valid indicator records and excluding historical or superseded rows.

Underlying Base Objects

The view is defined over a single documented base object: the synonym WIP_BIS_PROD_INDICATORS. This base object holds production indicator facts, including applied hours, available hours, and the dimensional keys and descriptive attributes used for reporting. The view does not join to additional tables; instead, it selects from WIP_BIS_PROD_INDICATORS, applies the EXISTING_FLAG = 1 predicate, and aggregates APPLIED_HOURS_UTZ using SUM(NVL(..., 0)). All other columns are carried through and listed in the GROUP BY clause, which means the view produces one row per unique combination of the listed dimensional and period attributes at which the applied hours are summed, while AVAILABLE_HOURS is treated as a non-additive measure and included in the grouping.

Key Columns

Common Use Cases and Queries

Typical uses include utilization percentage reporting (applied hours divided by available hours), area-level capacity analysis, and period-over-period comparison of resource consumption. A common query filters or groups on AREA_NAME:

  • Utilization by area: SELECT area_name, SUM(SUM(NVL(applied_hours_utz,0))) applied, available_hours FROM apps.wip_bis_utz_nocat_v GROUP BY area_name, available_hours;
  • Period utilization: SELECT year, quarter, month, area_code, SUM(NVL(applied_hours_utz,0)) FROM apps.wip_bis_utz_nocat_v WHERE area_name = :area GROUP BY year, quarter, month, area_code;
  • Organization-level rollup: SELECT organization_name, department_code, resource_code, SUM(NVL(applied_hours_utz,0)) hours FROM apps.wip_bis_utz_nocat_v GROUP BY organization_name, department_code, resource_code;

Because the view aggregates at query time, filtering on AREA_NAME or AREA_CODE is the most direct way to answer "area_name"-oriented questions about utilization in EBS 12.1.1 and 12.2.2.