Search Results ce_purge_trx_codes_xml




Overview
Explore in AI Chat

Overview

The APPS.CE_PURGE_TRX_CODES_XML package is a database-resident PL/SQL report logic package belonging to the Cash Management (CE) module of Oracle E-Business Suite. Its principal business function is to support the purge and archival reporting of cash transaction codes, statement lines, and their associated reconciliation data. The name and structure indicate that the package serves as the XML Publisher (BI Publisher) report data definition shell for the "Purge Transaction Codes" concurrent program, which allows Cash Management users to remove obsolete transaction codes and related bank statement transactions from the active tables after they have been archived or are no longer required.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer, which is typical of report trigger packages invoked from the concurrent manager under the APPS schema context. The header comment places the source file at version 120.0.12010000.1, dated 2009, consistent with the 12.1.1 and 12.2.2 code lines.

Key Procedures and Functions

The package exposes two documented functions, both of which are standard Oracle Reports/XML Publisher report triggers:

  • BEFOREREPORT — A Boolean function executed before the report body is rendered. In this package it initializes the global and parameter variables (such as the process option, request ID, bank, branch, and account identifiers) and validates the purge parameters supplied by the user, returning TRUE to allow the report to proceed or FALSE to halt execution when the request is invalid.
  • AFTERREPORT — A Boolean function executed after the report is produced. It finalizes processing, records the delete count (referenced by the G_DELETE_COUNT global), and performs any post-purge cleanup or logging required by the concurrent request.

The package additionally declares a set of parameter variables (process option, request ID, bank, branch, bank account, and account type) and global variables used to hold descriptive names (bank name, branch name, account number, account type) for rendering in the report output. No business API procedures beyond the two report triggers are documented.

Tables Accessed

The package reads and writes the following objects via APPS synonyms, which define the scope of the purge operation:

Usage Notes

This package is not intended for ad hoc invocation. It is executed indirectly when the Cash Management "Purge Transaction Codes" (or equivalent bank statement purge) concurrent program is submitted, with XML Publisher rendering the output. Because it carries AUTHID CURRENT_USER, it must be granted execute permission to the calling APPS user. The package is referenced by no other documented packages, confirming it is a terminal report driver rather than a shared utility. In 12.2.2 the implementation is unchanged from the 12.1.1 code line, so behaviour is consistent across both releases.