Results for “pmi_production_sum”

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

Overview

APPS.PMI_PRODUCTION_SUM is a PL/SQL package belonging to the Oracle Process Manufacturing (OPM) product family within Oracle E-Business Suite, present and VALID in both release 12.1.1 and 12.2.2. Its name denotes its core responsibility: production summary and batch status aggregation. The package consolidates process manufacturing execution data — batch headers, material issue and consumption transactions, lot information, quality sample counts, and scheduling details — into summarized production metrics. These metrics feed OPM batch summary views such as PMIFV_BATCH_QC_V, PMIFV_BATCH_TRANS_V, and PMIFV_BTCH_QCRSLT_V, which are consumed by production reporting, batch quality review, and yield analysis functions. The package is classified as OTHER in the ETRM API classification scheme, indicating it is an internal supporting package rather than a published open interface. It depends on standard Oracle schemas (SYS, STANDARD) and the APPS schema, and is referenced by three other packages in addition to the views listed above.

Key Procedures and Functions

The ETRM metadata documents nine callable units within the package body. Their names indicate the following responsibilities:

• POPULATE_BATCH_STATUS_SUM — the central aggregation routine that populates the batch status summary, consolidating production figures for a batch into the summary structure consumed by the OPM summary views.
• FIND_PROD_GRADE — determines the production grade associated with a batch, typically derived from quality results and item specifications.
• NO_OF_SAMPLES_TAKEN — returns the count of quality samples taken against a batch.
• NO_OF_SAMPLES_COMPLET — returns the count of quality samples completed, distinguishing them from samples still in progress.
• NO_OF_SAMPLES_PASSED — returns the count of quality samples that passed specification, supporting batch release and disposition decisions.
• NO_OF_TIMES_ADJUSTED — returns the number of times a batch or its production record has been adjusted, a useful indicator of process instability.
• SCHD_WORK_HOUR — computes scheduled work hours for a batch or scheduling entity against the production schedule.
• PLAN_ING_VALUE — returns the planned ingredient value, the expected value of materials consumed per the formula and batch plan.
• ACTUAL_ING_VALUE — returns the actual ingredient value consumed, supporting plan-versus-actual variance analysis.

Tables Accessed

The package references the following tables through APPS synonyms: GME_BATCH_HEADER (batch master data and status), IC_ITEM_MST and IC_LOTS_MST (inventory item and lot master, for material and lot attributes), IC_TRAN_CMP (inventory transactions, the basis for actual consumption values), PS_SCHD_HDR, PS_SCHD_DTL, MR_SHCL_DTL, and MR_SHDY_DTL (production scheduling headers and detail lines, used for scheduled work hours), GME_MATERIAL_DETAILS (batch material requirements and quantities), PMI_BATCH_STATUS (the batch status summary table written by POPULATE_BATCH_STATUS_SUM), GMD_EVENT_SPEC_DISP and GMD_SAMPLE_SPEC_DISP (quality event and sample specification data used in grading and sample evaluation), GMD_SAMPLES (individual quality samples), and SY_ORGN_MST (organization master, ensuring aggregation is scoped to the correct plant). USER_SYNONYMS is also referenced, consistent with a package that resolves object names dynamically.

Usage Notes

PMI_PRODUCTION_SUM is not an end-user API. It is invoked internally when the OPM batch summary views are queried, and by other packages (three documented dependents) that require summarized production or quality figures. Custom code should not call the aggregation routines directly against production data unless the caller accepts responsibility for populating PMI_BATCH_STATUS consistently; the supported path is to query the summary views. Because the package is VALID in both 12.1.1 and 12.2.2, behavior is stable across those releases. As with all APPS-internal packages, Oracle does not guarantee signature compatibility across patches, so customizations should avoid direct dependencies on individual procedure names where a view-based alternative exists.