Search Results validate_account_entered




Overview

APPS.PER_NL_BANK_DETAILS_PKG is a Netherlands-specific (NL) localization package within the Oracle EBS Human Resources (PER) schema. Its business purpose is to validate bank account numbers entered against Dutch banking rules and formats, including the handling of IBAN-based account numbers. The package header declares it with AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking user rather than the definer, which is typical consumable for validation-only utilities that do not require elevated definer rights. The package is classified in ETRM as API classification OTHER, indicating it is not a fully documented public API with the guarantees and lifecycle support of a certified interface, but a supporting PL/SQL unit used internally by the Dutch localization of Oracle HR/Payroll.

Key Procedures and Functions

The ETRM metadata documents two functions, both of which return a NUMBER and are therefore intended to communicate a validation outcome rather than to raise exceptions directly.

  • VALIDATE_ACCOUNT_NUMBER — Validates a bank account number supplied as an input. Based on the inline comment in the package header ("Validate the bank account number"), this function is the general-purpose account number validator, applying the Dutch account number format checks appropriate to the localization.
  • VALIDATE_ACCOUNT_ENTERED — The function returned by the user's search term. It accepts an account number value and a flag indicating whether the account is an IBAN account, and returns a numeric validation result. The presence of the p_is_iban_acc parameter indicates the function distinguishes between legacy Dutch domestic account numbers and IBAN-formatted account numbers, applying the relevant validation logic for each case. This is the entry point typically called when an account has just been keyed in, hence the "entered" naming, and is the function most associated with the user's query.

Neither function is documented by ETRM as exposing a table-based record or an OUT parameter list; both communicate results solely through their NUMBER return value.

Tables Accessed

The ETRM metadata lists no tables referenced via APPS synonyms for this package. Consistent with its role as a pure validation utility, the package appears to perform format and check-digit style validation on the values passed into its functions rather than querying or maintaining database tables. No documented reads or writes to HR, Payroll, or external bank tables are attributed to it in the ETRM extract. Any dependency on configuration data would reside in the undocumented implementation body rather than the declared package specification.

Usage Notes

ETRM records that this package is referenced by 0 other packages, indicating that within the documented dependency graph it is a leaf-level unit not called by other documented PL/SQL packages. This does not preclude invocation from Oracle Forms, OA Framework pages, or custom code that is not tracked as a documented package dependency. In Oracle EBS 12.1.1 and 12.2.2, Netherlands payroll and HR localization code typically calls such validators from the bank details maintenance forms and from concurrent or online processes that populate employee payment methods, so VALIDATE_ACCOUNT_ENTered is most plausibly invoked at the point of data entry or pre-commit validation. Because the package is classified OTHER and carries no documented API guarantee, customizations should call it defensively, expect only a NUMBER result, and avoid assuming a specific numeric encoding for success or failure without inspecting the implementation body. The package header source date (2009/11/27) indicates the specification has been stable across the 12.1.x and 12.2.x releases, so behavior should be consistent in both versions.