Search Results cf_daterangeformula

Overview

GME_GMEBCHPL_XMLP_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Batch Picking List (batch pick/pull) concurrent program report in the Process Manufacturing (OPM/GME) module. The package encapsulates the report-level PL/SQL logic used by the XML Publisher (XMLP) report definition GMEBCHPLS. Its public interface exposes the report's input parameters as package variables, defines report trigger entry points (BEFORE REPORT, AFTER REPORT, AFTER P FORM, HEADER), and provides a set of "CF_*FORMULA" functions that compute derived column values within the report's data model and layout templates.

The package serves as the PL/SQL back end for a batch-oriented picking document. It receives a company code, batch range, warehouse range, date range, sort selection, and organizational context, then drives query and layout logic that produces a printed or electronic picking list for production batches. Consistent with Oracle EBS 12.1.1 and 12.2.2 conventions, the package is compiled against APPS synonyms and relies on the standard Concurrent Processing framework and XML Publisher engine to render output.

Key Procedures and Functions

• BEFOREREPORT / AFTERREPORT — Report-level triggers that initialize and finalize execution context, parameter defaults, and any required setup prior to and following the report's main query.
• AFTERPFORM — Executes after the parameter form is validated, allowing late adjustment of package-level parameter variables before the report runs.
• HEADER — Builds or populates the report header block, including derived organizational and range captions.
• CF_BATCHRANGEFORMULA / CF_WHSERANGEFORMULA / CF_DATERANGEFORMULA / CF_SORTBYFORMULA — Formula columns that format the batch, warehouse, date, and sort ranges into display strings for the report header and selection criteria section.
• CF_TRANS_QTYFORMULA / CF_TRANS_QTY2FORMULA — Convert or format primary and secondary transaction quantities (for example, unit-of-measure conversion or numeric masking) for the picking line output. The function CF_TRANS_QTY2FORMULA, which the user searched for, addresses the secondary quantity column.
• CF_SUM_TRANS_QTYFORMULA / CF_SUM_TRANS_QTY2FORMULA — Compute aggregate totals of the primary and secondary transaction quantities for the report summary lines.
• CF_PLAN_QTY2FORMULA / CF_INV_PLAN_QTYFORMULA — Derive planned and inventory planned quantities using item unit-of-measure values and item identifiers, supporting dual-UOM display.
• CF_ACTUAL_START_DATEFORMULA — Formats the batch actual start date for display.
• SORTRETCFFORMULA / CF_CONTEXTORGFORMULA — Return the sort-key expression and the organization context value used by the report's query and layout.
• CP_BATCHRANGE_P / CP_WHSERANGE_P / CP_DATERANGE_P / CP_SORTBY_P — Accessor functions returning the current values of the corresponding concurrent program parameters, used internally by other formulas.

Tables Accessed

• MTL_PARAMETERS — Read to resolve organization-level inventory parameters, such as the organization code and default UOM context, needed to interpret batch and warehouse selections.
• DUAL — Used for single-row evaluations, typically in formula functions that return computed constants or formatted values.

The package declares no direct DML against transactional tables within its documented interface; the heavy lifting for line data is performed by the report's underlying query, with the package supplying formula and formatting logic.

Usage Notes

The package is invoked indirectly by the Oracle EBS Concurrent Manager whenever the Batch Picking List report is submitted. Users do not call its functions directly; the XML Publisher report definition references the CF_*FORMULA functions by name, and the report engine executes the BEFOREREPORT, AFTERPFORM, HEADER, and AFTERREPORT triggers at the appropriate phases. Because the package is compiled in the APPS schema and is referenced by zero other packages according to ETRM metadata, its coupling is limited to the owning report definition. Customizations should avoid altering the public function signatures, since the XML Publisher templates depend on their return types and behavior. Parameter values such as P_ORG_ID, CP_BATCHRANGE, and CP_WHSERANGE are populated from the concurrent program submission form and drive filtering throughout the report.