Search Results ar_cust_bal_rpt_pkg

Overview

AR_CUST_BAL_RPT_PKG is an Oracle Accounts Receivable (AR) reporting package owned by the APPS schema. Its documented business purpose is to support the AR Customer Balance Statement Letter Report, a standard Oracle EBS deliverable that produces formatted balance statements for customers and sends them as printed letters or electronic correspondence. The package supplies the runtime bind variables and the report lifecycle hooks that the Oracle Reports executable relies upon when generating the statement letter output.

The package specification is defined in the source file AR_CBSLRPTS.pls, with an original creation date of 02-Feb-2007 (Draft1A, authored by Sajana Doma). The source control header indicates the last file revision was 23-Oct-2007. In the ETRM 12.2.2 data model it is classified as API classification OTHER — that is, an internal reporting construct rather than a public, callable business API. Consequently it is not part of the supported integration surface and should be treated as an Oracle-internal implementation detail of the Statement Generation Program.

The package is declared with global (package-level) public variables that are populated by the Oracle Reports report trigger before the main query executes, together with two report-lifecycle functions. These globals allow the report layout to sort, filter, and display results consistently with the concurrent program parameters the user selected.

Key Procedures and Functions

The package specification exposes two documented functions, both standard Oracle Reports report-level triggers:

• BEFOREREPORT — Executed by Oracle Reports immediately prior to the main data query. Its role is to initialize the reporting environment: it resolves report parameters into the package-level bind variables (P_RESP_APPLICATION_ID, P_CONC_REQUEST_ID, P_SORT, P_SORT_BY_PHONETICS, and P_AS_OF_DATE), validates inputs, and establishes the context needed by the statement letter query. The function returns a BOOLEAN indicating success or failure of initialization.
• AFTERREPORT — Executed after the report has completed formatting and output. It is used for end-of-report cleanup and finalization logic. It also returns a BOOLEAN success indicator.

The package additionally declares global variables used as bind variables in the report query: P_RESP_APPLICATION_ID (responsibility/application context), P_CONC_REQUEST_ID (the concurrent request identifier for the run), P_SORT (the sort expression or order-by clause), P_SORT_BY_PHONETICS (flag controlling phonetic name sorting for customers), and P_AS_OF_DATE (the reporting cut-off date for balances).

Tables Accessed

Documented table access is limited to FND_CONCURRENT_REQUESTS, referenced via its APPS synonym. The package reads this table using the P_CONC_REQUEST_ID bind variable to retrieve attributes of the currently executing concurrent request — typically the request date, parameters, and other run-time context needed to drive the report. No other base or interface tables are documented as being accessed directly by this package; the substantive customer balance and transaction data is obtained by the Oracle Reports SQL query, not by the PL/SQL package itself. The package therefore functions primarily as a parameter and context provider rather than as a data-access layer.

Usage Notes

AR_CUST_BAL_RPT_PKG is typically invoked in the context of the Statement Generation Program, the concurrent program that produces the Customer Balance Statement Letter. Standard usage is through the Oracle EBS concurrent manager: the user submits the report from the AR responsibility (for example, Statements or Print Statements), and Oracle Reports calls the package's BEFOREREPORT function and reads the declared global variables as bind parameters during report execution. The package is also referenced by the Statement Generation Program when that program drives letter generation in batch.

Installation and execution follow standard SQL*Plus conventions for Oracle Reports PL/SQL libraries, as noted in the package header: sqlplus <apps_user>/<apps_pwd> @AR_CBSLRPTS.pls to install the specification. Because the package is classified as OTHER and exposes only report-trigger functions, it should not be invoked directly from custom PL/SQL, forms, or interfaces. Customizations that require customer balance statement data should use supported AR APIs, views, or the standard concurrent program rather than calling this internal package. Any direct calls risk breakage during patching or upgrade, since the implementation is not part of Oracle's published API contract. In 12.1.1 and 12.2.2 the object remains an APPS-owned reporting artifact with no dependents.