Search Results applied_hours

Overview

WIP_BIS_PRODUCTIVITIES_V is an Oracle E-Business Suite (EBS) reporting view owned by the APPS schema and defined in the Work in Process (WIP) module. Its documented purpose is to report efficiency for hour-based resources. In practical terms, the view aggregates applied hours and standard hours per organization, department, and resource, then derives a productivity percentage. It is part of the Oracle Business Intelligence System (BIS) layer that exposes pre-joined, pre-aggregated WIP data for analysis, dashboards, and downstream integration without requiring report authors to reconstruct the underlying join and aggregation logic. Because the view is a database object in the APPS schema, it can be queried with standard SQL through any reporting tool, a custom concurrent program, or a BI Publisher data model. The user search term "standard_hours" maps directly to a central column of this view, which is one of the principal inputs to the productivity calculation. The object is documented as VALID in both release 12.1.1 and 12.2.2, so the same definition and column set apply across those versions.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms in the ETRM metadata: ORG_ACCT_PERIODS and WIP_BIS_PROD_INDICATORS. WIP_BIS_PROD_INDICATORS is the primary driver, supplying the manufacturing productivity indicator rows, organization identification, transaction date, department code, resource code, applied hours, and standard hours. ORG_ACCT_PERIODS supplies the accounting period context, including period set name, period name, period start date, and schedule close date. The two are joined on organization and on the condition that the transaction date falls between the period start date and the schedule close date, which maps each indicator row to its accounting period. The view definition filters on WBPI.EXISTING_FLAG = 1 and WBPI.STANDARD_HOURS IS NOT NULL, and it groups results by legal entity, organization, transaction date, period attributes, department code, and resource code. The presence of a legal entity column indicates the view supports multi-organization and legal-entity-level reporting from a single query.

Key Columns

• ORGANIZATION_ID / ORGANIZATION_NAME — Identifies the manufacturing organization in which the resource activity occurred.
• LEGAL_ENTITY — The legal entity associated with the organization, exposed as a separate grouping column for statutory or management reporting.
• TRANSACTION_DATE — The date of the underlying indicator transaction.
• PERIOD_SET_NAME / PERIOD_NAME / PERIOD_START_DATE / PERIOD_END_DATE — Accounting period context derived from ORG_ACCT_PERIODS; PERIOD_END_DATE is populated from the period schedule close date.
• DEPARTMENT_CODE — The department in which the resource was applied.
• RESOURCE_CODE — The hour-based resource whose efficiency is being measured.
• APPLIED_HOURS — Sum of applied production hours for the grouping, with nulls treated as zero.
• STANDARD_HOURS — Sum of standard hours for the grouping, with nulls treated as zero; this is the column matching the user's search term.
• PRODUCTIVITY_PERCENT — Calculated as (sum of standard hours / sum of applied hours) * 100, returning zero when either denominator or numerator sums to zero.

The division logic means a value above 100 indicates performance better than standard, while a value below 100 indicates lower efficiency.

Common Use Cases and Queries

Typical scenarios include departmental productivity scorecards, month-over-period efficiency trend analysis, and resource utilization reporting by organization or legal entity. The view is suited to period-based reporting because every row carries both period and transaction date context.

A representative query for resource-level productivity in a given period:

• SELECT organization_name, department_code, resource_code, period_name, applied_hours, standard_hours, productivity_percent FROM apps.wip_bis_productivities_v WHERE period_name = :period AND organization_id = :org ORDER BY productivity_percent DESC;

A departmental rollup across a period set:

• SELECT legal_entity, organization_name, department_code, SUM(standard_hours) total_standard, SUM(applied_hours) total_applied, ROUND(DECODE(SUM(applied_hours),0,0,SUM(standard_hours)/SUM(applied_hours))*100, 2) pct FROM apps.wip_bis_productivities_v WHERE period_set_name = :set AND period_start_date >= :from_date GROUP BY legal_entity, organization_name, department_code;

Because the view already performs the join to ORG_ACCT_PERIODS and the null-safe aggregation, these queries remain simple and avoid duplicating EBS period-mapping logic. Reporting against the view also insulates custom code from changes to the WIP_BIS_PROD_INDICATORS structure, provided the documented column set is retained.