Results for “batch_close_date”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PMIFV_BATCH_LOTS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, classified under the Process Manufacturing Intelligence (PMI) product family. Its documented purpose is to report the lots produced by a batch. The view joins pending production transaction data to batch headers, lot master records, item definitions, organization definitions, and formula definitions, producing a consolidated, security-filtered result set of completed production output at lot and sublot granularity. Because the view is defined WITH READ ONLY, it is intended strictly for query and reporting use rather than for transactional data manipulation.

The view is a common discovery target when users search on the column batch_close_date, since that attribute is exposed directly from the batch header and is central to batch closure reporting. It is typically used in PMI dashboards, batch genealogy reports, and downstream integrations that require lot-level production output tied to batch closure.

Underlying Base Objects

The documented ETRM metadata for release 12.2.2 lists the following referenced base objects, all resolved through APPS synonyms: FM_FORM_MST_B, GME_BATCH_HEADER, IC_ITEM_MST, IC_LOTS_MST, IC_TRAN_PND, and SY_ORGN_MST, plus the PMI_SECURITY_PKG package.

The join logic documents the following relationships: lot item identifiers match between IC_LOTS_MST and IC_ITEM_MST; inventory transactions in IC_TRAN_PND are restricted to completed production (COMPLETED_IND = 1, DOC_TYPE = 'PROD'); the transaction document identifier equals the batch identifier (B.BATCH_ID = T.DOC_ID); the formula on FM_FORM_MST_B links to the batch formula on GME_BATCH_HEADER; and SY_ORGN_MST is outer-joined to the transaction organization code. Lines with LINE_TYPE = -1 and lots with LOT_ID = 0 are excluded. Row-level security is enforced through PMI_SECURITY_PKG.SHOW_RECORD, which filters results by the calling user's organization access.

Key Columns

• ITEM_NUMBER / ITEM_DESCRIPTION / ITEM_ID — Item identity and description of the produced lot.
• LOT_ID / LOT_NUMBER / SUBLOT_NUMBER — Lot and sublot identification.
• ORGN_CODE / ORGN_NAME — Inventory organization code and its descriptive name.
• BATCH_NUMBER / BATCH_ID — Batch that produced the lot.
• BATCH_CLOSE_DATE — Date the batch was closed; the primary target of the search that surfaced this view.
• TRANS_QTY / TRANS_UM — Produced transaction quantity and unit of measure.
• COMPLETED_IND — Completion flag; hard-coded to 1 by the view definition.
• LINE_TYPE — Transaction line type; the value -1 is excluded.

Common Use Cases and Queries

Typical scenarios include reconciling production output to closed batches, producing batch-to-lot genealogy reports, and feeding quality or yield analytics. Because BATCH_CLOSE_DATE is exposed directly, it is frequently used as a period filter.

SELECT BATCH_NUMBER,
       BATCH_CLOSE_DATE,
       ITEM_NUMBER,
       LOT_NUMBER,
       SUBLOT_NUMBER,
       ORGN_CODE,
       TRANS_QTY,
       TRANS_UM
FROM   APPS.PMIFV_BATCH_LOTS_V
WHERE  BATCH_CLOSE_DATE BETWEEN :start_date AND :end_date
ORDER  BY BATCH_CLOSE_DATE DESC;

A second common pattern aggregates produced quantities by organization and item for closed batches within a period:

SELECT ORGN_CODE,
       ITEM_NUMBER,
       SUM(TRANS_QTY) AS TOTAL_QTY
FROM   APPS.PMIFV_BATCH_LOTS_V
WHERE  BATCH_CLOSE_DATE IS NOT NULL
GROUP  BY ORGN_CODE, ITEM_NUMBER;

In all cases the security package limits the returned rows to organizations the current user is authorized to see, so no additional organization filter is required for standard reporting.