Search Results failed_by_calling_app

Overview

IBY_UTILITY_PVT is a private utility package in the Oracle Payments (IBY) module of Oracle E-Business Suite, used across both 12.1.1 and 12.2.2. As a PVT-classified package, it is not a public API; it is an internal library of shared low-level helpers invoked by many other IBY packages and by dependent applications. The ETRM metadata records that IBY_UTILITY_PVT is referenced by 44 other packages, confirming its role as a common foundation routine.

The package bundles several unrelated categories of helper logic: Base64 encoding and decoding (used for message and payload handling), NLS and character-set resolution, numeric and string conversion, property and profile retrieval, view-parameter handling for OA Framework style pages, and a set of validation routines covering parties, applications, territories, and lookup values. It also includes generic exception handling and status lookup helpers that other IBY programs rely on.

Key Procedures and Functions

The documented 34 procedures and functions include the following categories:

• Encoding and text utilities: ENCODE64 and DECODE64 perform Base64 conversions, backed by the package-level INIT_MAP function that maps numeric values 0 through 63 to Base64 character literals. MAKE_ASCII returns the ASCII representation of a value and is a frequent search target for developers converting character data.
• NLS and locale: GET_LOCAL_NLS returns the local NLS settings, and GET_NLS_CHARSET returns the character set associated with the NLS environment.
• Numeric and string helpers: TO_NUM converts a value to a number, and ISNUMERIC tests whether a string represents a valid number.
• Property and parameter handling: GET_PROPERTY, SET_PROPERTY, and GET_JTF_PROPERTY manage property values, including JTF (CRM) properties. SET_VIEW_PARAM and GET_VIEW_PARAM manage view parameters, and GET_CALL_EXEC supports call execution context.
• Validation routines: CHECK_LOOKUP_VAL validates a value against FND lookup values, VALIDATE_PARTY_ID validates an HZ party, VALIDATE_APP_ID validates an FND application, and VALIDATE_TERRITORY validates a territory. IS_TRIVIAL tests whether a value is trivial.
• Exception handling: HANDLE_EXCEPTIONS and HANDLEEXCEPTION provide centralized error handling and message construction for callers.

Tables Accessed

The package reads and writes through APPS synonyms. Validation routines query FND_APPLICATION, FND_TERRITORIES, HZ_PARTIES, and FND_LOOKUP_VALUES. Payment-related logic touches IBY_CREDITCARD, IBY_TRXN_SUMMARIES_ALL, IBY_PAYMENTS_ALL, IBY_PAY_INSTRUCTIONS_ALL, IBY_PAY_SERVICE_REQUESTS, IBY_FNDCPT_PMT_CHNNLS_B, and IBY_FORMATS_B. View-parameter handling uses IBY_VIEW_PARAMETERS_GT, and AP_INV_SELECTION_CRITERIA_ALL appears in payment batch selection logic. XDO_TEMPLATES_B supports template resolution, and DBMS_TRANSACTION is referenced for transaction control.

Usage Notes

Because IBY_UTILITY_PVT is a private package, it should not be called directly from customer extensions where a public API exists; Oracle recommends treating its signatures as subject to change between patch levels. In practice it is invoked internally by IBY payment, credit card, and payment instruction processing packages, and indirectly from Oracle Payments forms and concurrent programs. Developers investigating Base64 handling or MAKE_ASCII behavior should note that these routines operate on the package's internal mapping table, which is initialized once per session for performance.