Search Results num_of_emp




Overview

WIP_BIS_PROD_VAL_EMP_V is an Oracle E-Business Suite view owned by the APPS schema and defined in the Work in Process (WIP) product. It is part of the Oracle Business Intelligence System (BIS) family of reporting objects, which supply pre-aggregated operational metrics to embedded dashboards, Discoverer workbooks, and custom reports. The view reports average production value per employee within an inventory organization, allowing manufacturing and costing analysts to measure labor productivity against the value of goods produced.

The view is documented as VALID in ETRM for both 12.1.1 and 12.2.2. Because it is a database view rather than a table, it exposes no physical storage; consumers query it directly for period-based productivity analysis. The user search term item_price corresponds directly to the ITEM_PRICE column generated by the MRP_EPI.MRP_ITEM_SELLING_PRICE function call in the view definition.

Underlying Base Objects

The view is defined over three primary data objects and several supporting packages and views:

  • MTL_MATERIAL_TRANSACTIONS (synonym over the base transaction table) — supplies the inventory item, organization, accounting period, and transaction quantity used in the aggregation.
  • ORG_ACCT_PERIODS — supplies the period set name, period name, period start date, and schedule close date used to bracket the reporting window.
  • ORG_ORGANIZATION_DEFINITIONS (view) — supplies organization name and legal entity attributes.
  • MRP_EPI (package) — invoked as MRP_ITEM_SELLING_PRICE to return the item selling price.
  • WIP_BIS_COMMON (package) — provides the AVG_EMPLOYEE_NUM function that returns headcount for a period and organization.
  • HR_GENERAL and HR_SECURITY (packages) — referenced for employee and security context used by the headcount function.

The joins are driven from MTL_MATERIAL_TRANSACTIONS to ORG_ACCT_PERIODS on ACCT_PERIOD_ID and ORGANIZATION_ID, and to ORG_ORGANIZATION_DEFINITIONS on ORGANIZATION_ID. The transaction source type is restricted to 5, and transaction actions are limited to 1, 31, and 32 — completion, scrap, and return transactions respectively — so the quantity reflects production movement rather than arbitrary inventory activity.

Key Columns

Because GROUP BY includes item, organization, and period attributes, one row is returned per item, organization, and accounting period.

Common Use Cases and Queries

Typical uses include period-over-period productivity trending, value-of-production reporting, and comparison of item value against headcount by organization. A representative query:

  • SELECT organization_name, period_name, inventory_item_id, quantity, item_price, num_of_emp FROM apps.wip_bis_prod_val_emp_v WHERE organization_id = :org_id AND period_name = :period ORDER BY inventory_item_id;
  • Aggregating value: SELECT organization_name, period_name, SUM(quantity * item_price) production_value, AVG(num_of_emp) employees FROM apps.wip_bis_prod_val_emp_v GROUP BY organization_name, period_name;
  • Filtering on price: SELECT * FROM apps.wip_bis_prod_val_emp_v WHERE item_price > :threshold;

Reports should account for the package-based functions, which may return NULL for items without a selling price or organizations without headcount data. Productive use of the ITEM_PRICE column therefore requires validating that the pricing function returns meaningful values for the item and organization combination under review.