Search Results get_batch_details

Overview

APPS.AR_ARZACS_XMLP_PKG is the Oracle Reports PL/SQL library package body that backs the ARZACS (Receivables Automatic Clearing and Settlement, batch report variant) concurrent report in Oracle E-Business Suite Release 12.1.1 and 12.2.2. The package is classified as OTHER in the ETRM metadata, meaning it is not a published, supported PL/SQL API but rather an internal report-support package generated and maintained as part of the Oracle Reports XML Publisher (XMLP) migration infrastructure. Its primary purpose is to resolve the report's runtime parameter values, populate cached PL/SQL global variables, and supply derived column values to the report layout before the report body executes.

The package follows the standard Oracle Reports PL/SQL library contract, exposing BEFOREREPORT, BEFOREPFORM, AFTERPFORM, and AFTERREPORT entry points that the Reports runtime invokes at defined points in the report's execution cycle. The BEFOREREPORT function is the orchestration point: it captures the concurrent request identifier via FND_GLOBAL.CONC_REQUEST_ID, then sequences a series of initialization calls including CHECK_GL_DATE, GET_SET_OF_BOOKS, GET_PAYMENT_METHOD, GET_REMITTANCE_BANK_ACCOUNT, GET_BATCH_DETAILS, GET_MAX_CHR, and the YES/NO lookup population routines. This structure reflects the classic Oracle Reports 6i to XML Publisher conversion pattern, in which user exits such as FND SRWINIT and FND SRWEXIT were replaced with native PL/SQL calls while retaining the original procedure skeleton.

Key Procedures and Functions

• BEFOREREPORT — Master initialization routine; sets the concurrent request ID and invokes the subordinate lookup and validation routines.
• AFTERREPORT — Post-report cleanup; retains the original SRW exit stub.
• BEFOREPFORM — Pre-parameter-form initialization; captures the concurrent request ID.
• AFTERPFORM — Post-parameter-form logic; builds the automatic receipt clearing sub-query predicate for the batch report mode (P_BR_REPORT = 'Y').
• CF_TRANS_TYPEFORMULA — Derived column formula returning the transaction type name for the BR transaction type parameter.
• CF_BR_DATE_DISPFORMULA — Derived column formula formatting a BR date using FND_DATE.DATE_TO_CHARDATE.
• C_REC1_P, FUNC_CURRENCY_CODE_P, COMPANY_NAME_P, MAX_CRH_ID_P — Data model query group functions supplying record counts, functional currency, operating unit/company name, and the maximum cash receipt history ID.
• C_NLS_YES_P, C_NLS_NO_P — NLS-aware localized literals for Yes and No lookups.
• C_PAYMENT_METHOD_NAME_P, C_REMITTANCE_BANK_ACC_NAME_P, C_REMITTANCE_BATCH_NAME_P — Descriptive lookup accessors for payment method, remittance bank account, and remittance batch.
• GET_SET_OF_BOOKS — Resolves the set of books / ledger context for the report run, the routine most directly associated with the "get_set_of_books" search term.
• GET_PAYMENT_METHOD, GET_REMITTANCE_BANK_ACCOUNT, GET_BATCH_DETAILS, GET_MAX_CHR — Supporting lookup routines that pre-fetch receipt method, bank account, batch, and cash receipt history identifier data for use in the report layout.

Tables Accessed

The package reads (and in limited cases derives values from) the following APPS synonyms: AR_BATCHES for remittance batch attributes; AR_CASH_RECEIPT_HISTORY for the automatic clearing date range (LP_CLEAR_DATE) and maximum receipt ID; AR_RECEIPT_METHODS for payment method names; AR_SYSTEM_PARAMETERS for Receivables system options including the set of books context; CE_BANK_ACCOUNTS for remittance bank account descriptions; GL_PERIOD_STATUSES for GL date validation via CHECK_GL_DATE; and RA_CUST_TRX_TYPES for the customer transaction type name returned by CF_TRANS_TYPEFORMULA.

Usage Notes

This package is not intended for direct invocation from custom code. It is referenced exclusively by the ARZACS report definition itself and is invoked by the Oracle Reports runtime when the concurrent program is submitted. ETRM records zero dependent packages. The "get_set_of_books" search reference reflects the internal GET_SET_OF_BOOKS routine, which in 12.x resolves ledger context from AR_SYSTEM_PARAMETERS and GL_PERIOD_STATUSES rather than from a legacy SOB table. Customizations should target the report parameters or the Receivables data, not the package body, since any modification risks being overwritten by patch application.