Search Results get_acc_length




Overview
Explore in AI Chat

Overview

APPS.IBAN_VALIDATION_PKG is a PL/SQL package in Oracle E-Business Suite (available in both 12.1.1 and 12.2.2) that provides validation services for International Bank Account Number (IBAN) values used in supplier, employee, and payment-related data. IBAN is the internationally agreed standard for identifying bank accounts across national borders, governed by ISO 13616. Because IBAN structure varies by country — each country defines its own length and format — applications must verify that a given account number conforms to the rules of its registering country before the value is accepted or transmitted to a payment system.

The package is declared AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the invoking user rather than the package owner. Its source header (peribanval.pkh) indicates it belongs to the Payments/HR-family of EBS validation routines. The package is classified as an "OTHER" API in the ETRM repository and is referenced by 12 other database objects, indicating it is consumed broadly rather than being an entry-point API in its own right.

Key Procedures and Functions

  • VALIDATE_IBAN_ACC — A function that accepts a candidate account number and returns a NUMBER. Its purpose is to determine whether the supplied value is a structurally valid IBAN, returning a status indicator (typically 0/1 or a success/failure code) that callers use to gate acceptance of the account number. Typical validation logic includes country-prefix recognition, per-country length checks, and the mod-97 checksum test mandated by the IBAN standard.
  • GET_ACC_LENGTH — A function that takes a lookup code (the country or IBAN country code) and returns a VARCHAR2 representing the expected account/IBAN length for that country. This is the function most directly associated with the user search term "get_acc_length." It allows callers to retrieve the canonical length for a country without hard-coding country rules, supporting both pre-validation checks and display/formatting logic. Because the return type is VARCHAR2 rather than NUMBER, callers should anticipate possible non-numeric or formatted return values and handle conversion defensively.

Tables Accessed

The ETRM metadata for this package does not enumerate any directly referenced tables via APPS synonyms. Country-specific IBAN length and format rules are frequently held in lookup tables (for example, FND_LOOKUP_VALUES) or determined by constant logic embedded in the package body. Where lookups are used, the package reads them rather than writing, consistent with its role as a validation utility. No DML against transactional tables is documented.

Usage Notes

IBAN_VALIDATION_PKG is typically invoked from three contexts:

  • Forms and OA Framework pages — Supplier entry, employee banking detail, and payment instruction screens call VALIDATE_IBAN_ACC to validate an entered IBAN before commit, and GET_ACC_LENGTH to enforce field-length expectations or provide user feedback.
  • Concurrent programs and batch processes — Payment formatting, bank file generation, and data-cleansing routines invoke the package to screen account records before they are dispatched to banking partners.
  • Custom and extension code — Because 12 other packages reference this object, customizations commonly call it to inherit standard IBAN behavior rather than re-implementing country rules. Developers invoking GET_ACC_LENGTH should treat the returned VARCHAR2 as advisory and validate its convertibility before arithmetic use, and should be aware that country rule changes may alter its output between patch levels. As the package executes with caller privileges, the invoking user must have EXECUTE granted on APPS.IBAN_VALIDATION_PKG and any underlying lookup objects.