Search Results c_prt_tot_site_funcformula




Overview
Explore in AI Chat

Overview

The APPS.JG_JGZZRDLR_XMLP_PKG package is an Oracle Application Object Library (AOL) generated PL/SQL package that serves as the database-side execution artifact for an Oracle XML Publisher (BI Publisher) concurrent report. The naming convention reflects its origin: the JG prefix designates the Oracle Globalization / Global Accounting family of modules, JGZZRDLR is the internal short name of the specific report definition, and the _XMLP_PKG suffix indicates that the package was auto-generated by the XML Publisher concurrent program framework to wrap the report's data model.

In Oracle EBS 12.1.1 and 12.2.2, XML Publisher reports are registered as concurrent programs whose executable is bound to an AOL-generated package of this type. The package executes the report's SQL query, populates the XML data structure consumed by the RTF or XSL-FO template, and provides the formatting hooks that compute derived and aggregate values at report runtime. Because the package is owned by APPS and depends only on SYS.STANDARD at the PL/SQL level, it is a thin orchestration layer over the underlying AR data model rather than a reusable business API.

Key Procedures and Functions

The ETRM metadata documents 62 procedures and functions, classified as OTHER, reflecting a typical XML Publisher generated package. These fall into three groups:

  • Report lifecycle entry points: BEFOREREPORT and AFTERREPORT are the standard XML Publisher hooks invoked immediately prior to and following data extraction. BEFOREREPORT initializes session context (such as currency and ledger parameters supplied by the concurrent program), while AFTERREPORT performs any post-extraction cleanup.
  • Placeholder return functions (*FORMULA): The majority of the 62 objects are FUNCTION definitions ending in FORMULA, e.g. C_PRT_TOT_NET_FOREIGNFORMULA, C_PRT_TOT_TAX_FUNCFORMULA, C_PRT_TOT_SITE_FUNCFORMULA, C_PRT_ORIG_FRGN_AMOUNTFORMULA, and C_PRT_FRGN_AMT_DUE_REMFORMULA. These are placeholder functions bound to template fields; each computes or returns a scalar value such as a total net foreign amount, total tax in functional currency, total site amount, or foreign amount due on a remittance. Parallel C_OA_PRT_* variants supply the same logic for the Oceanic/alternate presentation blocks within the same template.
  • Grouped formula families: The naming pattern reveals recurring duplications (_REMFORMULA vs. plain FORMULA, _FUNC vs. _FOREIGN) corresponding to separate template sections — original amounts versus remittance amounts, functional versus foreign currency, and current versus original balances.

Tables Accessed

The package reads the following base tables through APPS synonyms, all belonging to the Oracle Receivables schema:

  • AR_CASH_RECEIPTS and AR_CASH_RECEIPT_HISTORY — source of receipt header and status history data used for remittance and cash application reporting.
  • AR_RECEIVABLE_APPLICATIONS — the application lines that link receipts to transactions, driving the "foreign amount due" and "functional amount due" formula calculations.
  • AR_DUNNING_LETTERS — supplies dunning/collection correspondence context where the report includes customer communication status.
  • FND_CURRENCIES — provides currency precision, format masks, and descriptions for foreign versus functional currency display.

All access is read-only; the package contains no DML, consistent with its reporting role.

Usage Notes

This package is never called directly by end users or custom code. It is invoked exclusively by the XML Publisher concurrent program engine when the associated report is submitted from the Concurrent Programs form or the Standard Report Submission (SRS) window. The runtime driver calls BEFOREREPORT, executes the data model SQL, then invokes the individual *FORMULA functions as the template renders each field. In 12.2.2 the package remains registered in the APPS schema with VALID status; it references no other custom packages and is itself referenced only by its own specification. Because the package is regenerated whenever the report definition is edited in the XML Publisher Administrator responsibility, direct modification is not supported and any changes would be overwritten. DBAs should treat it as a generated object for dependency and invalidation tracking rather than a maintenance target.