Search Results validate_iban_acc

Overview

HR_BE_VALIDATION is a Belgian localizations validation package owned by APPS and classified under Oracle E-Business Suite's "OTHER" API category. Its purpose is to enforce country-specific formatting and check-digit rules for Belgian bank account numbers, which follow the national format NN-NNNNNNN-NN (a two-digit bank code, a seven-digit account number, and a two-digit check value). The package exposes a single documented entry point, BANK_ACCOUNT_NO, which returns one of two outcomes defined as package constants: hr_be_validation.success when the supplied account number is well-formed and its check digits are correct, or hr_be_validation.failure when either the format or the calculated modulus-97 check digit does not match.

The package body carries the version header hrbevali.pkb 120.0.12010000.2, indicating it is part of the R12 code line and carried forward into 12.1.1 and 12.2.2 without functional change. Its stated primary purpose is to be referenced from the Bank Account key flexfield definition, where the returned success/failure value drives cross-validation rules at data-entry time.

Key Procedures and Functions

• BANK_ACCOUNT_NO — The core validation function. It accepts a Belgian bank account number and returns the success or failure constant. Internally it first verifies the literal NN-NNNNNNN-NN pattern, rejecting any input containing alphabetic characters or any string that fails a TRANSLATE-based character-class test. It then concatenates the first three and subsequent seven digits into a ten-digit number, truncates division by 97 and multiplies the truncated quotient back by 97, and subtracts the product from the original ten digits to derive the expected check value. The result is left-padded to two characters and compared against the final two digits of the input; a special branch treats a computed check value of zero as equivalent to 97, since modulus 97 cannot otherwise produce the two-digit value 97. Any discrepancy raises the internal invalid_bank_acc_no exception and returns failure.
• VALIDATE_ACCOUNT_ENTERED — The second documented program unit in the package, providing the entry point used to determine whether an account value has actually been entered on a form or interface record, complementing the format and check-digit test performed by BANK_ACCOUNT_NO.

Tables Accessed

The ETRM metadata records no table references for this package through APPS synonyms. This is consistent with its design: HR_BE_VALIDATION is a pure computation utility that evaluates the string passed to it rather than querying or updating database tables. All logic is self-contained within package variables and exceptions, so validation results do not depend on external data and no DML is performed.

Usage Notes

The package is invoked most commonly from the Bank Account key flexfield, where cross-validation rules call BANK_ACCOUNT_NO to enforce the Belgian format and check-digit algorithm as users enter supplier, customer, or employee bank details. Because it returns a simple success/failure token rather than raising propagated exceptions, it can also be called from Forms triggers, concurrent program validation steps, and custom PL/SQL that populates bank account tables such as IBY or AP/AR payment setup.

The metadata records no packages referencing HR_BE_VALIDATION, so it is treated as a leaf utility rather than a shared internal API. Any search for "validate_iban_acc" should note that this package does not contain a procedure of that name; IBAN validation for Belgian accounts is handled elsewhere, while HR_BE_VALIDATION remains dedicated to the legacy domestic NN-NNNNNNN-NN account number format. Implementers migrating data should therefore call this function explicitly before loading records, since it will reject IBAN-formatted values.