Search Results std_time




Overview
Explore in AI Chat

Overview

APPS.PMIFV_PROD_EFFI_V is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite. It is registered under FND Design Data as PMI.PMIFV_PROD_EFFI_V and is documented with the functional title "Batch Efficiency." The view consolidates production batch outcome data drawn from the Oracle Process Manufacturing (OPM) batch, material, and item master tables, presenting yield quantities, standard quantities, standard time, and yield values in a flattened, reporting-ready form.

Its primary role is to support production efficiency analysis and integration scenarios. Because it pre-joins batch headers to material details, item masters, plant inventory, organization masters, and the GL calendar, it allows report authors and downstream interfaces to query batch-level performance without reconstructing the underlying relational joins. The view is defined as VALID at the documented release levels (12.1.1 and 12.2.2). It carries no dependent objects — no database object references PMIFV_PROD_EFFI_V — confirming it is a terminal reporting object rather than a foundation for further views.

Users searching on the term "std_time" typically arrive here because STD_TIME is one of the view's exposed numeric columns, which is central to measuring planned versus actual batch duration and efficiency.

Underlying Base Objects

The view is defined over the following documented base objects, most resolved as synonyms in the APPS schema:

  • GME_BATCH_HEADER — the OPM batch master, supplying batch identity, plant, and item context.
  • GME_MATERIAL_DETAILS — batch material transactions, contributing actual yield quantities and material consumption.
  • FM_FORM_MST_B — formula master information relevant to the batch's planned composition.
  • IC_ITEM_MST — item master, supplying item numbers and descriptions.
  • IC_PLNT_INV — plant inventory parameters linked to the batch's plant and warehouse.
  • SY_ORGN_MST — organization master, providing company and plant/warehouse codes.
  • PMI_GL_CALENDAR_V — GL calendar view, used to derive fiscal year and period attributes.
  • GMICUOM (PACKAGE), PMI_COMMON_PKG, and PMI_SECURITY_PKG (PACKAGE) — PL/SQL packages invoked by the view for unit-of-measure conversion, common OPM logic, and organization-level security filtering.

Because PMI_SECURITY_PKG participates in the definition, result sets are subject to the invoking user's plant/organization security profile, which is a critical consideration when the view is queried directly rather than through a secured application screen.

Key Columns

The view exposes both descriptive dimensions and numeric measures:

Common Use Cases and Queries

Typical scenarios include batch yield variance reporting, standard-time versus actual-duration efficiency studies, period-based production summaries, and data extraction for BI or data-warehouse loads. A minimal query is:

  • SELECT PLANT_CODE, BATCH_NO, ITEM_NO, FISCAL_YEAR, PERIOD_NAME, ACTUAL_YIELD_QTY, STD_QTY, STD_TIME FROM APPS.PMIFV_PROD_EFFI_V;
  • Filtering by period: ... WHERE FISCAL_YEAR = :year AND PERIOD_CODE = :period;
  • Efficiency analysis: ... WHERE STD_TIME IS NOT NULL ORDER BY STD_TIME DESC;
  • Yield variance: ... WHERE ACTUAL_YIELD_QTY <> STD_QTY;
  • Item-level rollup: SELECT ITEM_NO, SUM(ACTUAL_YIELD_QTY), SUM(STD_QTY), SUM(STD_TIME) ... GROUP BY ITEM_NO.

Because organization security is enforced within the view definition, queries executed under a restricted responsibility will return only batches visible to that organization, making the view suitable both for secured operational reporting and for controlled integration extracts.