Search Results unset_260

Overview

APPS.CE_CEXAVTRX_XMLP_PKG is the PL/SQL package body associated with the Oracle XML Publisher (BI Publisher) report definition CE_CEXAVTRX, a Cash Management transaction listing report. In Oracle EBS 12.1.1 and 12.2.2, concurrent programs that use the XML Publisher publishing model are generated as a pair of database objects: an XML Publisher data template and a supporting PL/SQL package whose name is derived from the report definition. This package, CE_CEXAVTRX_XMLP_PKG, is that generated support package. Its responsibilities are to declare the report's parameter and formula placeholders, to supply the "before report" and "after report" trigger logic, and to expose the formatted values that the report layout consumes through the XML Publisher data model.

The report is part of the Cash Management (CE) product family and produces a listing of cash transactions (receipts and payments) associated with a bank account. The package is classified as OTHER in the ETRM registry, indicating that it is not a public, callable business API but an internal report driver. It is not intended to be invoked directly by customer code.

Key Procedures and Functions

The metadata documents 71 procedures and functions. The principal groups are described below.

• BEFOREREPORT — Standard XML Publisher report trigger that initializes report state before the data model executes.
• AFTERREPORT — Standard report trigger that performs cleanup after the data model has completed.
• G_TRANSACTION_TYPEGROUPFILTER — Group filter applied to the transaction type query block, restricting rows based on the supplied bank account number.
• C_AMOUNTFORMULA, C_BANK_ACCOUNT_AMOUNTFORMULA, C_ACCOUNT_AMOUNTFORMULA — Formula columns that compute and format the transaction amount, the bank account amount, and the account amount for display, including precision and sign handling.
• C_DATEFORMATFORMULA — Formats date values according to the report's date format convention.
• C_ORDER_BYFORMULA — Resolves the dynamic ORDER BY clause from the P_ORDER_BY parameter.
• P_SHOW_VOID_PAYMENT_FLAGVALIDT, P_ORDER_BYVALIDTRIGGER — Validation triggers for the SHOW_VOID_PAYMENT_FLAG and ORDER_BY parameters.
• Getter functions (suffix _P) — 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 and their peers return the formatted values of the corresponding package-level variables to the report layout.

Tables Accessed

The documented table reference for this package is the APPS synonym FND_NEW_MESSAGES, which is used by Oracle Forms and concurrent programs to retrieve translatable message text. In this package it supports retrieval and translation of report prompts and labels such as the transaction type and receipt translation strings exposed through the C_TRANSACTION_TYPE and C_RECEIPT_TRANSLATION getters.

All other data retrieval for the report is performed inside the XML Publisher data template rather than directly by this package; the package-level variables and cursor placeholders (P_BANK_ACCOUNT, P_ORG_ID, P_LEGAL_ENTITY_ID, P_SOURCE_VIEW, C_BATCH_PAY_SQL_LEX, C_BATCH_REC_SQL_LEX and others) are populated by that data model and merely surfaced here. The package is referenced by zero other packages, confirming its role as a terminal, report-specific driver.

Usage Notes

CE_CEXAVTRX_XMLP_PKG is not called from Oracle Forms or from customer PL/SQL. It is invoked implicitly by the concurrent manager when the CE_CEXAVTRX concurrent program is submitted, either from the Cash Management responsibility or through the standard Submit Request form. Parameters such as P_BANK_ACCOUNT, P_ORG_ID, P_LEGAL_ENTITY_ID, P_TYPE, P_SHOW_VOID_PAYMENT_FLAG, P_ORDER_BY, P_DEBUG_MODE and P_SQL_TRACE are populated from the concurrent program parameter window; P_CONC_REQUEST_ID identifies the submission.

Because the package is regenerated whenever the report definition is re-published through XML Publisher, customizations should not be applied directly to the package body. In the context of the search term "unset_101", this value corresponds to the ORA-06502 / XML Publisher "unset" placeholder pattern used when a parameter or formula variable has not been bound at runtime; it indicates a missing assignment for a report parameter or formula column rather than a defect in the database object itself. Diagnosing such errors typically involves checking the concurrent program parameter definitions and the data template's parameter bindings rather than editing this package.