Results for “p_refresh”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AR_CUMULATIVE_BALANCE_REPORT is an Oracle Receivables (AR) PL/SQL package owned by the APPS schema that supports the Accounts Receivable Cumulative Balance Report. The package name reflects the report's function: producing cumulative balances for a company (reporting entity) across a defined reporting level and accounting period range. In Oracle E-Business Suite 12.1.1 and 12.2.2, the package generates an XML payload that is subsequently processed for output rendering. The business purpose is to enable financial and credit personnel to view customer or entity-level receivable balances, generally for reporting, reconciliation, and credit review purposes. The "CRA report of the company" phrasing commonly refers to this Cumulative Receivables Analysis/balance reporting functionality, which aggregates Receivables data against General Ledger account balances, Code Combinations, and period statuses to present cumulative position information for a specified reporting entity.

The package header carries the identifier $Header: ARXCUABS.pls 120.4, confirming it belongs to the Receivables family of report-generation packages. Its classification as OTHER in the API taxonomy indicates it is a supporting report engine rather than a public business-API used for transactional inserts and updates.

Key Procedures and Functions

• PROCESS_CLOB — Accepts an XML CLOB and processes it. This procedure handles the post-generation processing of the XML document produced by the report, preparing it for consumption by the reporting/output layer (for example, converting generated XML into the rendered report output or applying further transformations).
• GENERATE_XML — Produces the report's XML payload. It accepts parameters defining the scope of the run, including the reporting level, reporting entity identifier, reporting format, set of books, chart of accounts, the low and high ranges for the company and GL account segments, the GL as-of date, a refresh flag, and an output CLOB parameter. This procedure is the core engine: it gathers the relevant cumulative balances for the requested reporting entity and assembles them into structured XML. The p_refresh flag allows the caller to force recalculation rather than relying on previously stored data, and the low/high segment parameters allow selective extraction of ranges of accounts or companies.

Tables Accessed

The package reads from a mix of Receivables, General Ledger, and FND foundation tables through APPS synonyms:

• AR_BASE_GL_ACCT_BALANCES, AR_GL_ACCT_BALANCES, and AR_CCID_BY_GL_ACCOUNTS — provide the GL account balances and the mapping between Receivables and General Ledger code combinations that underpin the cumulative balance figures.
• RA_CUSTOMER_TRX_ALL — transaction data used to derive customer/entity receivable activity.
• AR_CASH_RECEIPTS_ALL and AR_RECEIPT_METHODS — receipt and payment-method data incorporated into balance computations.
• AR_CLOSED_GL_PERIODS, GL_PERIOD_STATUSES — determine period status and open/closed treatment of balances.
• GL_CODE_COMBINATIONS, FND_FLEX_VALUES, FND_SEGMENT_ATTRIBUTE_VALUES — resolve account structures, segment values, and descriptive attributes for reporting.
• AR_SYSTEM_PARAMETERS, AR_SYSTEM_PARAMETERS_ALL — retrieve Receivables system-level configuration.
• FND_CURRENCIES, FND_USER — currency definitions and user context.

Usage Notes

AR_CUMULATIVE_BALANCE_REPORT is typically invoked indirectly rather than called directly by end users. It is most commonly triggered by the concurrent program associated with the Cumulative Balance Report, where the requesting user selects the reporting level, entity, format, set of books, chart of accounts, segment ranges, account ranges, and as-of date. The concurrent manager executes GENERATE_XML to build the XML and then calls PROCESS_CLOB to finalize the output. The package is also referenced by two other packages, indicating it functions as a reusable report-generation component within the Receivables reporting stack. Custom integrations may call the package programmatically when a structured XML representation of cumulative balances is required. Because it is a report engine rather than a transactional API, it performs read-only access and does not commit changes to the core tables it queries.