Search Results debug_log

Overview

CE_CUSTOM_BANK_VALIDATIONS is a customization stubs package in the APPS schema for Oracle E-Business Suite, categorized under Cash Management (CE). Its purpose is to provide a controlled extension point where site-specific validation logic for banking information can be implemented without modifying Oracle's seeded Cash Management validation code. Oracle's standard bank setup flow invokes the public entry points in this package at key validation moments; the default implementation ships as a no-op shell, allowing customers and integrators to insert their own business rules for validating banks, branches, and bank accounts.

The package header comment identifies it as an unsupported customization module ("noship") whose body was last revised in December 2009 (120.1.12010000.3). It forms part of the bank account validation framework used by the Bank Setup and related Cash Management user interfaces.

Key Procedures and Functions

The ETRM metadata documents three public procedures. Parameter lists are intentionally not reproduced here.

• CE_USR_VALIDATE_BANK — Invoked when a bank is validated from the Bank Setup UI. It receives bank attribute values such as country, bank number, bank name, alternate bank name, tax payer ID, and bank ID (the latter available only when updating an existing bank), and returns a status plus a formatted bank number to be stored.
• CE_USR_VALIDATE_BRANCH — Invoked when a bank branch is validated, allowing custom verification of branch-level attributes before the branch record is accepted.
• CE_USR_VALIDATE_ACCOUNT — Invoked when a bank account is validated, permitting custom checks on account data before the account is committed.

Two private helper procedures support these entry points. debug_log is the procedure most relevant to the user's search; it accepts a message text and delegates to cep_standard.debug, writing diagnostic output to the Cash Management debug log. set_error_text populates the error message stack via fnd_message.set_name and fnd_msg_pub.add, using messages defined under application Cash Management (CE), so that validation failures surface in the user interface.

Tables Accessed

Per the documented metadata, the package references the APPS synonym for HZ_ORGANIZATION_PROFILES. This TCA table stores party-level organization details, including the profile attributes associated with banks as trading partners. Custom validation logic can therefore read registered organization profile values when confirming that a bank or branch meets site-defined criteria. No other tables are documented as being accessed by this package.

Usage Notes

CE_CUSTOM_BANK_VALIDATIONS is not intended to be called directly from forms or concurrent programs. It is invoked indirectly through Oracle's standard Cash Management bank validation APIs, which route control to these procedures so that customer-specific rules execute within the seeded validation cycle. Implementers typically copy or adapt the shipped shell, add rule logic to CE_USR_VALIDATE_BANK, CE_USR_VALIDATE_BRANCH, and CE_USR_VALIDATE_ACCOUNT, and use set_error_text to raise user-visible messages when validation fails. The debug_log helper referenced in the user's search is disabled by default; enabling Cash Management debugging (via the FND debug/profile mechanisms honored by cep_standard.debug) causes messages passed to it to appear in the debug log, which is useful for troubleshooting custom validation behavior. Because the package is flagged noship and is referenced by one other package, upgrades should be treated with care: the shipped body may be overwritten, so customizations should be preserved and re-applied in line with Oracle's customization standards for EBS 12.1.1 and 12.2.2.