Results for “iby_build_utils_pkg”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The APPS.IBY_BUILD_UTILS_PKG package body is a utility package within the Oracle Payments (IBY) module of Oracle E-Business Suite. It provides shared internal services that support the construction, validation, error handling, and diagnostic reporting of payment build processes. Rather than exposing a public business API, this package functions as a reusable helper library invoked by the higher-level payment build engine and its related packages.
In the context of Oracle EBS 12.1.1 and 12.2.2, the package operates in the APPS schema and is recorded as VALID in the ETRM metadata, with an API classification of OTHER. It is not itself referenced by any database object, but it references numerous payment-related tables, public packages such as DBMS_LOB, and standard oracle utilities including FND_FILE, FND_GLOBAL, FND_LOG, and FND_MESSAGE. The metadata confirms it is referenced by 13 other packages, indicating its role as a shared dependency across the IBY build framework.
Key Procedures and Functions
The documented package exposes 16 procedures and functions, summarized below by purpose.
- PRINT_DEBUGINFO — Emits diagnostic and debugging information, typically gated by logging or profile settings.
- PRINTXMLCLOB — Outputs XML content stored in a CLOB (using
DBMS_LOB) for inspection and troubleshooting. - CHECKFORINVALIDCHARS — Scans input strings for characters that are invalid or non-permitted in payment build output.
- GETCHAR — Retrieves a single character, commonly used in string parsing or delimited-value handling.
- DIFFSTRINGS — Compares two strings and identifies differences, useful for validation and reconciliation debugging.
- CREATEERRORRECORD — Creates a transaction error record capturing build failures.
- CREATEPMTERRORRECORD — Creates an error record specific to payment-level processing.
- GETPROFLISTFROMPROFILEDRIVERS — Derives a list of payment profiles from configured profile drivers.
- GETPROFILEMAP — Returns a mapping of payment profiles for lookup and resolution.
- GETPROFILECODEFROMID — Resolves a profile code from a profile identifier.
- PRINTWRAPPEDSTRING — Prints a string with line wrapping for readable log or report output.
- INACTIVATEOLDERRORS — Marks prior error records as inactive before reprocessing.
- RESETPAYMENTERRORS — Clears or resets payment-related error entries.
- RESETDOCUMENTERRORS — Clears or resets document-level error entries.
- RESETPAYMENTINSTRUCTIONERRORS — Clears or resets payment instruction error entries.
Tables Accessed
The package reads and writes several core IBY tables to support its error, profile, and build operations.
- IBY_TRANSACTION_ERRORS and IBY_TRXN_ERROR_TOKENS — store and tokenize transaction-level errors created by the error-record procedures.
- IBY_PAYMENTS_ALL, IBY_DOCS_PAYABLE_ALL, and IBY_PAY_INSTRUCTIONS_ALL — provide the payment, document, and instruction context used during build and error-reset processing.
- IBY_ACCT_PMT_PROFILES_B, IBY_SYS_PMT_PROFILES_B, IBY_APPLICABLE_PMT_PROFS, and IBY_PAYMENT_PROFILES — supply profile definitions and applicability rules for the profile-resolution functions.
- IBY_PAY_SERVICE_REQUESTS — supports payment service request processing.
- DBMS_LOB and DUAL — provide CLOB handling and standard single-row queries.
Usage Notes
As an internal utility package, IBY_BUILD_UTILS_PKG is not typically invoked directly by end users or through standard forms. It is called programmatically by the payment build engine and the 13 dependent IBY packages during concurrent program execution, such as payment process requests and payment instruction builds. The diagnostic procedures (for example, PRINT_DEBUGINFO, PRINTXMLCLOB, and PRINTWRAPPEDSTRING) rely on FND_LOG and FND_FILE, making them relevant when troubleshooting build output through log files. Customizations should avoid modifying this package and instead extend behavior through supported APIs such as IBY_VALIDATIONSETS_PUB.