Search Results log_error_messages




Overview
Explore in AI Chat

Overview

IBY_PAYMENT_FORMAT_VAL_PVT is a private (PVT) PL/SQL package body in the Oracle Payments (IBY) module of Oracle E-Business Suite. It provides the format-specific validation engine used during payment instruction processing. Individual payment formats — such as FVCONC and related treasury and disbursement formats — require field-level and record-level checks before a payment can be formatted, transmitted, or settled. This package implements those checks as discrete validation procedures, each responsible for a single validation rule.

The package operates on validation error data passed by the caller through the IBY_VALIDATIONSETS_PUB.docErrorTabType collection and an IBY_TRANSACTION_ERRORS%ROWTYPE record, returning error codes and messages to the invoking validation framework. Diagnostic activity is routed through the LOG_ERROR_MESSAGES procedure, which writes to the FND_LOG message stack. The body header identifies the source as ibyfvvlb.pls, version 120.18.12010000.2, last updated in July 2008, confirming the file lineage carried forward into 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes 23 documented procedures and functions covering payment, treasury, and payee validation domains.

  • SCHEDULE_NUMBER — Validates the schedule number (pay_admin_assigned_ref_code) on a payment instruction, applying format-specific rules for designated formats.
  • SUPPLIER_TYPE — Validates the supplier type against format requirements.
  • TREASURY_SYMBOLS_PROCESS and MAX_TREASURY_SYMBOLS — Handle treasury symbol processing and enforce the maximum permitted number of treasury symbols.
  • AGENCY_ADDRESS and AGENCY_LOCATION_CODE — Validate the paying agency address and location code.
  • PAYEE_ADDRESS — Validates the payee address for the payment format.
  • MAX_PAYMENT_AMT and MAX_PAYMENT_AMT_2 — Enforce maximum payment amount thresholds.
  • PAY_TAX_BENEFIT and PAY_SALARY_TRAVEL — Validate payment classification for tax benefit and salary/travel payments respectively.
  • PAYEE_SSN — Validates the payee Social Security Number.
  • TAS_VALIDATION — Validates the Treasury Account Symbol.
  • RTN_NUMBER — Validates the bank routing transit number.
  • PAY_ALONE_OPTION — Validates the pay-alone payment option indicator.
  • DEPOSITER_ACC_NUM and ACCOUNT_TYPE — Validate depositor account number and account type.
  • RFC_ID — Validates the regional finance center identifier.
  • MANDATORY_PPD_PPDP_REASON_CODE — Enforces the mandatory reason code for PPD/PPDP payment types.
  • LOG_ERROR_MESSAGES — Central logging routine invoked throughout the body to write messages to the FND_LOG stack at a specified level. Callers pass FND_LOG constants such as LEVEL_STATEMENT along with a module name and message text; this is the procedure most frequently referenced when tracing validation failures.

Tables Accessed

The package reads and writes several documented tables through APPS synonyms. Payment instruction and payee data are sourced from IBY_PAY_INSTRUCTIONS_ALL, while error state is persisted to IBY_TRANSACTION_ERRORS. Bank and account validation draws on CE_BANK_ACCOUNTS and IBY_EXT_BANK_ACCOUNTS. Supplier checks reference AP_SUPPLIERS and AP_SUPPLIER_SITES_ALL, and invoice-related checks reference AP_INVOICES, AP_INVOICES_ALL, AP_INVOICE_DISTRIBUTIONS, and AP_INVOICE_DISTRIBUTIONS_ALL. Treasury and fund validations use FV_FUND_PARAMETERS, FV_OPERATING_UNITS_ALL, FV_TP_TS_AMT_DATA, and FV_TREASURY_SYMBOLS. Organization and code assignment lookups use HR_ALL_ORGANIZATION_UNITS and HZ_CODE_ASSIGNMENTS.

Usage Notes

IBY_PAYMENT_FORMAT_VAL_PVT is a private package and is not part of the supported public API surface. It is invoked indirectly by the payment validation framework during payment instruction validation, formatting, and transmission, and is referenced by two other packages. The LOG_ERROR_MESSAGES procedure is the standard entry point for diagnosing validation failures, since it records the module name and message text emitted by each validation routine. Custom code should not call this package directly; extensions should use the public IBY_VALIDATIONSETS_PUB interfaces and inspect IBY_TRANSACTION_ERRORS and the FND log for results.