Search Results cf_acctg_cost

Overview

GME_GMEMUSBV_XMLP_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that serves as the supporting program unit for an Oracle Reports XML Publisher (XMLP) concurrent program. Within the Process Manufacturing (OPM) modules, the name convention "GMEMUSBV" indicates a Material Usage Summary by Batch report or a closely related Material Usage/ Variance report. The "_XMLP_PKG" suffix identifies this as the auto-generated or manually maintained report logic package invoked by the Report Builder/XML Publisher runtime engine. Its purpose is to gather, calculate and format the values that populate the report layout, particularly accounting cost, quantity variance, value variance and batch-related header information.

The package provides global variables and functions used as formula columns and summary columns in the report, and it implements the BEFORE REPORT and AFTER REPORT triggers. It is not called by any other package in the EBS code base (referenced by 0 other packages), confirming that it is a leaf-level report support package invoked only through the concurrent manager.

Key Procedures and Functions

The package exposes 27 documented procedures and functions, largely organized around report formula computation and header parameter handling:

• CF_ACCTG_COST and CF_ACCTG_COST2FORMULA — derive accounting cost values for a given item and completion date. CF_ACCTG_COST2FORMULA converts a transaction quantity into an accounting cost basis for display.
• CF_QUANTITY_VARIANCE, CF_VARIANCE_PCT, CF_VALUE_VARIANCE — compute the quantity variance between actual and transaction quantity, its percentage, and the corresponding monetary value variance.
• CF_U_VALUE_VARIANCEFORMULA, CF_S_VALUE_VARIANCEFORMULA, CF_TOTAL_VARIANCEFORMULA — value variance calculations at the UOM and summary levels, with the total variance formula consolidating the report output.
• CF_ACTL_QTY_ITEMUMFORMULA, CF_ITEMUMFORMULA, CF_BATCH_SIZEFORMULA, TRANS_QTYFORMULA_005 — retrieve actual quantity in the item UOM, the item UOM itself, the batch size for a recipe validity rule/batch, and the transaction quantity derived from the formula line context.
• CF_BATCHRANGEFORMULA, CF_DATERANGEFORMULA, CF_ITEM_RANGE, CF_WIPCODE, CF_DELETE_TRANSFORMULA — build the descriptive range/filter strings (batch, date, item, WIP code) shown as report headers, and handle deletion or transformation flags.
• G_MAINGROUPFILTER — returns a Boolean controlling the main group-level filter applied to the report query.
• BEFOREREPORT and AFTERREPORT — standard report triggers that initialize parameters and clean up after report execution.

Tables Accessed

The package reads from the following documented tables through APPS synonyms:

• GME_BATCH_HEADER, GME_MATERIAL_DETAILS, GME_SCALE_DETAIL — batch, material and scale detail data driving the material usage report content.
• GMD_RECIPE_VALIDITY_RULES, GMD_ROUTINGS_B, FM_ROUT_HDR, FM_MATL_DTL — recipe validity, routing and formula detail information used to compute batch size and item UOM.
• MTL_SYSTEM_ITEMS_B, MTL_PARAMETERS — item master and organization parameter attributes (e.g., UOM, organization defaults) used in conversion and range logic.
• FND_DUAL — used for single-row assignments typical in formula functions.
• PLITBLM — a PL/SQL internal table typically used by Oracle Reports for temporary numeric storage in formula columns.

Usage Notes

This package is invoked exclusively by the Oracle Reports runtime when the associated concurrent program (the Material Usage Variance/Summary XMLP report) is submitted from the Concurrent Programs form or a standard OPM report menu. It is not designed for direct invocation from custom code, and the ETRM metadata records no inbound dependencies from other packages. Parameters such as P_CODE, FROMBATCH, TOBATCH, FROMDATE, TODATE, FROMITEM, TOITEM, CURR_CODE, P_CONC_REQUEST_ID and P_ORG_ID correspond to the report's submitted concurrent program parameters and drive the formula functions that build the batch, date and item range headers. Any customization should be performed on the underlying report definition or the documented formula functions, taking care to preserve the APPS synonym references and the BEFORE/AFTER REPORT contract expected by the Reports engine in EBS 12.1.1 and 12.2.2.