Search Results p_display_debug

Overview

APPS.CE_BANK_GROUPINGS is a public PL/SQL package in Oracle E-Business Suite that supports the bank data grouping program within the Cash Management (CE) module. Its central responsibility is to consolidate and organize bank-related master data — banks, branches, and bank accounts — into groupings that downstream Cash Management and Treasury processes can consume. In the 12.1.1 and 12.2.2 release streams, this package is closely associated with bank upgrade and migration activity, as evidenced by its references to the CE_UPG_* and CE_UPGA_* tables. The package header carries a header comment dated 2005 (cebugrps.pls 120.1), indicating it has been a stable component of the CE schema across multiple release cycles. The API classification is OTHER, meaning it is not a standard public-API surface such as an Open Interface or a formally versioned API, but rather an internal utility exposed at the schema level. Because the package body is not part of the documented metadata, the visible contract is limited to the specification: a single public procedure named GROUPING plus its argument documentation.

Key Procedures and Functions

The documented specification exposes exactly one public procedure, GROUPING. It is described as the main procedure of the bank grouping program, capable of grouping bank data at the BANK, BRANCH, or ACCOUNT level as requested. Its documented arguments, as declared in the package specification, include:

• errbuf — the standard concurrent program error buffer used to return messages to the Concurrent Manager.
• retcode — the standard concurrent program return code indicating success, warning, or error.
• p_bank_entity_type — the bank entity type for the program run, which drives whether grouping is performed at bank, branch, or account level.
• p_display_debug — a debug message flag with values Y or N. This is the parameter referenced by the search term "p_display_debug"; when set to Y, the procedure emits diagnostic messages during execution.
• p_debug_path — the debug path name, used when a debug file destination is specified.
• p_debug_file — the debug file name, used when debug output is directed to a file rather than only to the log.

No functions are documented for this package, and no additional procedures are listed. The errbuf and retcode signature confirms that GROUPING is intended to run as a concurrent program entry point.

Tables Accessed

The documented table references, resolved through APPS synonyms, reveal the package's data footprint. The upgrade and staging tables — CE_BANK_UPGRADE_ERRORS, CE_BANK_UPGRADE_MODES, CE_UPGA_BANK_REC, CE_UPG_BANK_ACCOUNTS, CE_UPG_BANK_REC, CE_UPG_BA_USES_ALL, CE_UPG_CONT_POINT_REC, and CE_UPG_LOC_REC — support the migration and grouping of bank, branch, account, contact-point, and location records. CE_BANK_UPGRADE_ERRORS captures validation failures encountered while processing bank records, and CE_BANK_UPGRADE_MODES stores the upgrade mode configuration that governs how grouping behaves. PLITBLM is the standard Oracle Applications PL/SQL index-by table of VARCHAR2, typically used as an in-memory collection for messages or identifiers. Collectively, these references show that the package reads and writes staging and error-tracking data while building grouped bank structures.

Usage Notes

CE_BANK_GROUPINGS is normally invoked through a Cash Management concurrent program rather than interactively from a form. Because its parameters conform to the standard concurrent program interface, it can also be called from custom PL/SQL with errbuf and retcode variables declared as VARCHAR2 and NUMBER respectively. Debugging is controlled by p_display_debug, with optional output routing through p_debug_path and p_debug_file. The package is referenced by zero other documented packages, so its invocation is driven by the concurrent program definition and by custom code rather than by package-to-package dependency. Administrators and developers troubleshooting bank upgrade or grouping runs should set p_display_debug to Y to obtain diagnostic output in the concurrent request log or the designated debug file.