Results for “ce_check_numeric”

26 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.CE_BANK_AND_ACCOUNT_VALIDATION package body is a central validation utility within the Oracle Cash Management (CE) module of Oracle E-Business Suite. Its principal business function is to enforce data integrity and business rules governing banks, bank branches, bank accounts, and the payment documents and account uses associated with them. Rather than exposing a standalone user interface, the package provides a reusable library of validation routines that other Cash Management and Payments components call before persisting or acting upon bank and account data.

The package consolidates validation logic that spans multiple functional domains: bank and branch definition, organizational access security, currency and country validation, IBAN formatting, and payment document categorization. It is classified as an "OTHER" API in the ETRM registry, indicating that it is an internal validation package rather than a published public API. It is referenced by seven other database objects, confirming its role as a foundational dependency for higher-level Cash Management and Payables processing.

Key Procedures and Functions

The package body documents 21 procedures and functions. The validation routines fall into several logical groups:

Tables Accessed

The package reads and validates against core Cash Management, Trading Community, and HR tables. Bank and account data is drawn from CE_BANK_ACCOUNTS, CE_BANK_ACCT_USES_ALL, and CE_PAYMENT_DOCUMENTS. Payment document categories come from CE_AP_PM_DOC_CATEGORIES. Reference data is supplied by FND_CURRENCIES, FND_TERRITORIES, and FND_TERRITORIES_VL. Organization and party data is read from HZ_PARTIES, HZ_ORGANIZATION_PROFILES, HZ_CODE_ASSIGNMENTS, HR_ORGANIZATION_INFORMATION, and PER_EMPLOYEES_X. Validation scratch data uses HZ_BANK_VAL_GT and HZ_ORG_PROFILE_VAL_GT. Security profiles come from CE_SECURITY_PROFILES_V.

Usage Notes

This package is invoked indirectly rather than directly by end users. It is typically called from the Bank and Bank Account setup forms in Cash Management, from Payables payment creation flows, and from other PL/SQL packages that must verify bank or account data before committing. Because it is not referenced by any database object itself and is referenced by seven other packages, customizations should treat it as an internal dependency. Developers extending Cash Management validation should reuse these routines to preserve consistent business rule enforcement.