Search Results init_variables

Overview

CE_PURGE_TRX_CODES_XML is a PL/SQL package body owned by the APPS schema that supports the Cash Management (CE) module's purge and XML reporting infrastructure for transaction codes. Its source header identifies it as part of the ceputxcb.pls file family (version 120.1, last modified 2009), which places it among the internal utility packages used to clean up obsolete transaction code records and to feed associated XML-based reporting. Functionally, the package combines two concerns: housekeeping logic that removes or archives stale CE_TRANSACTION_CODES and related bank/branch/account data, and the retrieval of descriptive attributes (bank name, branch name, account number, account type) that are required to render purge output or XML report payloads. Although its API classification is listed as OTHER — meaning it is not a public, globally callable API — it is a genuine internal worker object referenced by Oracle's Cash Management purge flows rather than by any external package.

Key Procedures and Functions

The ETRM metadata documents two procedures, BEFOREREPORT and AFTERREPORT, which is consistent with an Oracle Reports integration pattern: BEFOREREPORT executes setup logic prior to report data retrieval, and AFTERREPORT executes cleanup or summary logic after the report completes. Their precise parameter lists are not exposed in the documented metadata and should not be assumed.

Beyond the documented procedures, the source excerpt reveals the internal procedure init_variables, which is the object the user's search term refers to. init_variables is a private initialisation routine that populates package-level global variables before the main purge or reporting logic runs. It reads the bank name from HZ_PARTIES using the party identifier, the bank branch name from HZ_PARTIES using the branch party identifier, the bank account number from CE_BANK_ACCOUNTS, and the bank account type by looking up the BANK_ACCOUNT_TYPE lookup meaning in CE_LOOKUPS. Each value is null-guarded, and a companion private procedure, debug_log, wraps cep_standard.debug to emit trace messages. This design allows the purge and XML routines to work against resolved, human-readable descriptions rather than raw identifiers.

Tables Accessed

The package reads and writes a defined set of CE and HZ objects through APPS synonyms. CE_TRANSACTION_CODES is the central transactional table subject to purge. CE_ARCH_LINES and CE_ARCH_INTRA_LINES hold archived statement and intra-statement line data; CE_STATEMENT_HEADERS, CE_STATEMENT_LINES, and CE_INTRA_STMT_LINES supply the statement context purged alongside transaction codes. CE_BANK_ACCOUNTS and CE_JE_MAPPINGS provide account and journal-entry mapping references. CE_TRX_CODES_UTIL_GT is a global temporary table used as a working set during the purge operation. HZ_PARTIES is read for bank and branch party names, and CE_LOOKUPS is read for lookup meanings such as the account type description.

Usage Notes

This package is invoked indirectly rather than through a user-facing API. Typical callers are the Cash Management purge concurrent program, its associated Oracle Reports XML report definition (which triggers BEFOREREPORT and AFTERREPORT), and internal CE batch processes. Because it is classified as OTHER and is referenced by zero other packages, custom code should not call it directly. Implementations extending CE purge behavior should treat CE_PURGE_TRX_CODES_XML as unstable and rely on supported public APIs or the standard concurrent program interface instead.