Search Results cp_itemrange

Overview

GME_GMEBCHYV_XMLP_PKG is the generated PL/SQL package body that supports the Oracle E-Business Suite XML Publisher (BI Publisher) report commonly identified as the Batch Yield Variance report in the Process Manufacturing (OPM/GME) product family. In Oracle EBS 12.1.1 and 12.2.2, reports built on the XML Publisher engine are wrapped by an auto-generated package whose naming convention follows the short name of the report definition, here GMEBCHYV. The package supplies the report's data model: it declares the query block, the parameter list, and a set of formula columns and group-level functions that are evaluated by the XML Publisher runtime as the report output is rendered. Functionally, the report compares planned and actual batch quantities and costs, converts units of measure, and calculates yield variances and variance percentages for materials consumed in a batch.

The header comment ($Header: GMEBCHYVB.pls 120.0 2007/12/24) indicates this package was last generated for an older release and has been carried forward unchanged through 12.1.1 and 12.2.2. The API classification of "OTHER" reflects that this is not a public, callable API but an internal report-support package owned by APPS.

Key Procedures and Functions

The package documents 22 procedures and functions. The formula functions each compute a single derived column of the report:

• CF_ACCTG_COST2FORMULA — converts the actual batch quantity to the item's primary unit of measure using INV_CONVERT.INV_UM_CONVERT when the cost UOM differs from the item UOM, then multiplies the converted quantity by the item cost.
• CF_QUANTITY_VARIANCE — returns actual quantity less planned quantity in item UOM.
• CF_VALUE_VARIANCE — returns the accounting cost value difference between the two cost columns.
• CF_VARIANCE_PCT — computes variance as a percentage of planned quantity, handling the divide-by-zero and null-planned-quantity cases explicitly.
• CF_FORMULA_QTY, CF_PLAN_QTY_ITEMUMFORMULA, CF_ACTUAL_QTY_UMFORMULA, CF_UOMFORMULA, CF_ACCTNG_COST1FORMULA — derived report columns for planned and actual quantities, their UOMs, and the primary accounting cost.
• CF_BATCHRANGEFORMULA, CF_DATERANGEFORMULA, CF_ITEM_RANGE, CF_CONTEXT_ORGFORMULA, CF_DELETE_TRANSFORMULA — parameter-display and range-selection helpers for batch, date, item (the "cp_itemrange" selection), operating-unit context, and the delete-transaction flag.
• BEFOREREPORT — the XML Publisher before-report trigger that initializes the data model, loads lexical parameters, and sets the package state used by CP_ITEM_COST_P and CP_BATCHRANGE_P.
• AFTERREPORT — the after-report trigger, typically used to reset package state at completion.
• HEADER — the standard XML Publisher header function returning report metadata such as title, currency, and organization.
• BATCHUM_P — resolves the batch unit of measure associated with the report run.
• CP_ITEM_COST_P and CP_BATCHRANGE_P — data-model query procedures that populate the item cost and batch range result sets.

Tables Accessed

The package reads through APPS synonyms against the following tables:

• GME_MATERIAL_DETAILS, GME_SCALE_DETAIL, FM_MATL_DTL — process manufacturing material and scale detail records supplying actual and planned batch quantities.
• GMD_RECIPE_VALIDITY_RULES — recipe validity windows used to select the correct recipe version for a batch date.
• MTL_SYSTEM_ITEMS_B, MTL_PARAMETERS — item master attributes, primary UOM, and inventory organization parameters.
• FND_DUAL — Oracle's single-row dummy table used by parameter and initialization queries.
• PLITBLM — a temporary/PL-SQL table used to pass the multi-value item range (cp_itemrange) parameter into the report query.

Usage Notes

This package is invoked only by the XML Publisher concurrent program for the Batch Yield Variance report in process manufacturing. It is not called from Oracle Forms, is not exposed as a public API, and the metadata records zero packages referencing it. Customizations should avoid modifying the package body directly because it is regenerated whenever the report definition is edited in the XML Publisher Administrator responsibility. The cp_itemrange parameter is bound via PLITBLM and consumed through the CF_ITEM_RANGE formula, so the item range submitted at the concurrent request is resolved entirely within this package. Any extension should instead be implemented in the underlying report data template or query.