Search Results expct_cmplt_date

Overview

PMIFV_BATCH_DETAILS_V is an APPS-owned database view in Oracle E-Business Suite that exposes batch details for the Process Manufacturing Intelligence (PMI) product. PMI is documented as obsolete in ETRM, and this view should be regarded as a legacy reporting construct rather than a supported integration interface. It is not a table and holds no data of its own; it presents a flattened, security-filtered projection of process batch header and material detail information.

The view joins batch headers to their material lines and enriches each line with plant, organization, item, formula, routing, GL calendar, and costing policy attributes. Its principal role was to feed operational and costing reporting on completed batches, particularly batch material consumption and production quantities expressed in both transaction and primary units of measure, with an accompanying cost valuation.

Underlying Base Objects

The view is defined over the following documented objects:

• GME_BATCH_HEADER (synonym) — batch header, aliased BTCHHDR.
• GME_MATERIAL_DETAILS (synonym) — batch material lines, aliased BTCHDTL.
• SY_ORGN_MST (synonym) — organization master, aliased ORGNMST.
• IC_ITEM_MST (synonym) — item master, aliased ITEMMST.
• FM_FORM_MST_VL (view) — formula master, aliased FORMMST.
• FM_ROUT_HDR (synonym) — routing header, aliased ROUTHDR (outer-joined).
• PMI_GL_CALENDAR_V (view) — GL calendar periods, aliased CALENDR.
• GL_PLCY_MST (synonym) — costing policy master, aliased PLCYMST.
• GMICUOM (package) — UOM conversion via I2UOM_CV.
• PMI_COMMON_PKG (package) — cost retrieval via PMICO_GET_COST.
• PMI_SECURITY_PKG (package) — organization-level row filtering via SHOW_RECORD.

Joins are driven by BATCH_ID between header and detail, PLANT_CODE to organization code, ITEM_ID to item master, FORMULA_ID to formula master, and ROUTING_ID to routing header. The batch's actual completion date is resolved against the GL calendar period boundaries, and the organization's company code links to the costing policy and calendar.

Key Columns

• PLANT_CODE, CO_CODE, WIP_WHSE_CODE — plant, company, and work-in-process warehouse context.
• BATCH_ID, BATCH_NO — batch identifier and user-visible batch number.
• FORMULA_ID, FORMULA_NO, FORMULA_VERS — formula identity and version.
• ROUTING_ID, ROUTING_NO, ROUTING_VERS — routing identity and version.
• PLAN_START_DATE, ACTUAL_START_DATE, PLAN_CMPLT_DATE, ACTUAL_CMPLT_DATE — planned and actual batch scheduling and completion timestamps.
• BATCH_STATUS — batch state; the view restricts rows to statuses 3 and 4.
• ITEM_ID, ITEM_NO, ITEM_DESC1 — material line item identity and description.
• PLANNING_CLASS, INV_CLASS, SALES_CLASS — item classification attributes.
• ITEM_UM, LINE_TYPE, PLAN_QTY, ACTUAL_QTY — line unit of measure, line type (restricted to 1), and planned/actual quantities.
• Cost expressions — unnamed columns computing converted quantity multiplied by PMICO_GET_COST, producing planned and actual cost valuations.
• PERIOD_YEAR, PERIOD_NUM, PERIOD_NAME — GL period attributes derived from the actual completion date.
• BASE_CURRENCY_CODE, GL_COST_MTHD — costing currency and method from the policy master.

Common Use Cases and Queries

Typical usage centres on batch yield, material consumption, and cost reporting for completed batches within organizations the user is authorized to see. Because security filtering is embedded through PMI_SECURITY_PKG.SHOW_RECORD, results are constrained by the responsibility's organization access.

A representative query retrieves batch material consumption and valuation:

• SELECT BATCH_NO, PLANT_CODE, ITEM_NO, LINE_TYPE, PLAN_QTY, ACTUAL_QTY, PERIOD_NAME, BASE_CURRENCY_CODE FROM APPS.PMIFV_BATCH_DETAILS_V WHERE PLANT_CODE = :plant AND ACTUAL_CMPLT_DATE BETWEEN :from_date AND :to_date;

Additional scenarios include reconciling formula and routing versions against actual batch execution, aggregating actual quantities by item and GL period, and comparing planned versus actual cost valuations per batch line. Note that no cost column is explicitly aliased in the defining query, so consumers should reference costing expressions positionally or wrap the view in an outer query with explicit aliases. Given the obsolete PMI status, new development should prefer supported Process Manufacturing reporting views.