Search Results standard_qty

Overview

APPS.OPI_EDW_OPI_JOB_DETAIL_FCV is a reporting view within the Oracle E-Business Suite Discrete Manufacturing and Enterprise Data Warehouse (EDW) integration layer. It is designed to expose work order (job) detail information in a flattened, analytics-ready form for consumption by Oracle Supply Chain and Manufacturing Analytics, the Oracle Business Intelligence (OBIEE) applications, and other downstream EDW extraction processes. The view consolidates actual and planned metrics for production jobs, including quantity data, valuation in base and global currencies, lead times, and key lifecycle dates.

The naming convention and column aliases (for example, _B for base currency and _G for global currency) confirm that the view is intended as an EDW source interface rather than an operational transactional view. In this capacity it serves as a stable, denormalized layer that isolates downstream reporting systems from the underlying Oracle Manufacturing and Inventory schemas.

Underlying Base Objects

The documented ETRM metadata for this view lists no referenced base objects. This absence is typical for EDW interface views whose definitions are intentionally obscured or whose dependencies are resolved dynamically at runtime.

The view definition itself references several conventional sources:

• MSI — a reference to MTL_SYSTEM_ITEMS, supplying primary UOM codes, standard lot size, lead time lot size, and full lead time attributes.
• JOBS — a reference to the work order master (typically WIP_DISCRETE_JOBS or a derived jobs source), providing JOB_ID, JOB_NO, and JOB_STATUS.
• INST — a reference to the EDW instance source, providing INSTANCE_CODE used in the surrogate key construction.

The composite key column JOB_DETAIL_PK concatenates ORG_ID, JOB_ID, ITEM_ORG, INSTANCE_CODE, and a literal suffix of -OPI, which indicates the view is specific to the Oracle Process/Discrete Manufacturing intelligence schema. This key structure ensures uniqueness across organizations and instances when the data is loaded into the EDW.

Key Columns

The view exposes a broad mix of quantity, valuation, and date fields:

• Quantity columns — ACT_OUT_QTY and PLN_OUT_QTY are scaled by the UOM conversion rate returned by EDW_UTIL.GET_UOM_CONV_RATE, based on the primary UOM of the item. STANDARD_QTY is derived from lead time lot size or standard lot size and similarly converted.
• Valuation columns — ACT_OUT_VAL_B, ACT_INP_VAL_B, ACT_MTL_INP_VAL_B, ACT_SCR_VAL_B, and ACT_BPR_VAL_B carry actual values in base currency; parity global currency columns are set to NULL, indicating base-currency-only reporting for this interface. Planned values use DECODE(ENTITY_TYPE, 4, ACT..., PLN...) logic to select actual or planned amounts depending on the entity type.
• Date columns — ACT_STRT_DATE, PLN_STRT_DATE (the field most relevant to the user search term pln_strt_date), ACT_CMPL_DATE, PLN_CMPL_DATE, and ACT_CNCL_DATE carry the planned and actual start, completion, and cancellation dates.
• Descriptive attributes — JOB_NO, JOB_STATUS, MFG_MODE, ACT_JOB_TIME, PLN_JOB_TIME, STD_TIME, and a production line reference built from PRD_LINE_FK.

Common Use Cases and Queries

This view is typically queried to support production performance analysis, planned-versus-actual variance reporting, and work order scheduling reviews. A representative query filtering on the planned start date, corresponding to the user's search term, follows:

SELECT JOB_NO, ORG_ID, PLN_STRT_DATE, ACT_STRT_DATE, PLN_OUT_QTY, ACT_OUT_QTY FROM APPS.OPI_EDW_OPI_JOB_DETAIL_FCV WHERE TRUNC(PLN_STRT_DATE) BETWEEN :start_date AND :end_date;

Other common scenarios include comparing planned and actual valuations by job, identifying jobs that started late against PLN_STRT_DATE, and aggregating STANDARD_QTY versus ACT_OUT_QTY by organization for capacity analysis. Because valuation columns carry base-currency values only, reporting on global currency requires joining to separate EDW currency conversion sources.