Search Results actual_hours




Overview
Explore in AI Chat

Overview

APPS.WIP_BIS_UTZ_CAT_V is a Web-enabled database view owned by the APPS schema in Oracle E-Business Suite, registered under the FND Design Data reference WIP.WIP_BIS_UTZ_CAT_V. Its status is VALID, and its view type identifies it as a Web view designed to simplify access from Oracle Self-Service Web Applications. Functionally, the view presents resource utilization for every hour-based resource within a manufacturing organization on a given date. It is part of the Oracle Manufacturing Business Intelligence System (BIS) family of views, which were introduced to support web-deployed reporting and self-service dashboards without requiring direct query access to the underlying production tables.

The view is particularly relevant to users searching for actual_hours, since ACTUAL_HOURS is one of its core measures. It exposes actual and available hours side by side, allowing straightforward computation of utilization percentages at the resource, department, and organization level.

Underlying Base Objects

The documented base object referenced by this view is WIP_BIS_PROD_INDICATORS, exposed in APPS through a synonym. WIP_BIS_PROD_INDICATORS is the pre-aggregated production indicator table that stores periodic capacity and utilization metrics collected from shop floor transactions, resource assignments, and department calendars. WIP_BIS_UTZ_CAT_V acts as a denormalized, category-oriented projection over that table, joining or resolving identifier columns into their descriptive names (organization, department, resource, location, region, country) so that the view is directly consumable by self-service web pages and ad hoc reporting tools.

As with most BIS views, the underlying indicator data is periodically refreshed rather than calculated in real time. Reporting users should therefore treat the figures as snapshot metrics aligned to the collection run performed by the BIS concurrent programs.

Key Columns

Common Use Cases and Queries

The view is commonly used for resource utilization reporting: identifying under- or over-utilized resources, comparing planned versus actual capacity, and building departmental efficiency scorecards. A typical query computes utilization percentage:

  • SELECT resource_code, organization_name, transaction_date, actual_hours, available_hours, ROUND(actual_hours / NULLIF(available_hours,0) * 100, 2) utilization_pct FROM apps.wip_bis_utz_cat_v WHERE transaction_date BETWEEN :start_date AND :end_date AND organization_id = :org_id;
  • Region-level roll-ups: SELECT region_name, SUM(actual_hours) FROM apps.wip_bis_utz_cat_v WHERE period_year = :year GROUP BY region_name;
  • Period trend analysis: grouping by PERIOD_MONTH and PERIOD_QUARTER to detect seasonal capacity pressure.

Because the view resolves identifiers into descriptive names, it is well suited to self-service dashboards and integration extracts that must display readable labels without additional lookup joins.