Search Results c_batch_amount_p

Overview

CE_CEXAVBCH_XMLP_PKG is a generated PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It is the supporting package for the XML Publisher (BI Publisher) concurrent program that produces the Bank Account Batches report for Oracle Cash Management. The suffix _XMLP_PKG identifies it as a report template wrapper automatically produced when a report is registered as an XML Publisher data definition; the report itself is driven by the CEXAVBCH executable, and the package provides the runtime anchor, user parameter bind variables, and formula callbacks that the report layout references.

The package is declared AUTHID CURRENT_USER, so it executes with the privileges of the invoking user rather than as definer-rights code. All state is held in package-level variables that are populated during the BEFOREREPORT trigger, then consumed by the report's SQL query and by the formula columns embedded in the RTF template. The package contains no business logic of its own beyond parameter validation, derived display values, and formatting callbacks.

Key Procedures and Functions

• BEFOREREPORT / AFTERREPORT — Standard XML Publisher report triggers that initialize parameter values, resolve derived constants, and perform any cleanup after the report completes.
• G_TRANSACTION_TYPEGROUPFILTER — Group filter that controls which transaction types appear in the report output based on the selected transaction type parameter.
• C_AMOUNTFORMULA, C_BANK_ACCOUNT_AMOUNTFORMULA, C_ACCOUNT_AMOUNTFORMULA — Formula columns that compute batch amounts, bank account amounts, and account-level amounts for each batch row retrieved by the report query.
• C_DATEFORMATFORMULA — Returns a formatted date string using the date format defined for the concurrent request.
• C_ORDER_BYFORMULA — Builds the ORDER BY clause dynamically, allowing the user to select the report sort order through the order-by parameter.
• P_SHOW_VOID_PAYMENT_FLAGVALIDT, P_ORDER_BYVALIDTRIGGER — Validation routines invoked from the concurrent program's parameter form to verify that the "show void payments" flag and the order-by value are valid before submission.
• C_BATCH_AMOUNT_P, C_BATCH_BANK_ACCOUNT_AMOUNT_P, C_THE_END_P, C_BANK_ACCOUNT_NAME_P, C_BANK_ACCOUNT_NUM_P, C_BANK_NAME_P, C_BANK_BRANCH_NAME_P, C_BANK_CURRENCY_CODE_P, C_TRANSACTION_TYPE_P, C_RECEIPT_TRANSLATION_P — Getter functions for the corresponding package-level constants, exposed so that the XML Publisher layout can reference them directly as XML elements.

The package also declares the report's input parameters (bank account, type, debug mode, SQL trace, concurrent request ID, order by, void payment flag, source view, query receipts, query payments, org ID) and derived constants such as batch amount, bank account name, currency code, precision, and the SQL lexical parameters C_BATCH_PAY_SQL_LEX and C_BATCH_REC_SQL_LEX.

Tables Accessed

The only documented table reference is FND_NEW_MESSAGES, accessed through an APPS synonym. This is the Oracle Application Object Library table that stores translatable message text. The report package reads it to resolve the display names, warnings, and translated labels used in the Bank Account Batches output, ensuring the report respects the language and territory settings of the concurrent request.

Usage Notes

The package is not called directly by application code. It is invoked exclusively by the XML Publisher runtime when the Bank Account Batches concurrent program is submitted. The parameter validation triggers fire when the user opens the concurrent program's parameter window, and BEFOREREPORT fires immediately prior to query execution. Because the package is referenced by zero other packages and exposes no public API contract, it should be treated as report-internal plumbing: customized versions should be avoided, and any extension should be implemented through the XML Publisher template or data definition rather than by modifying this generated package, since it is regenerated when the report definition is changed.