Search Results iby_payment_format_val_pub




Overview
Explore in AI Chat

Overview

IBY_PAYMENT_FORMAT_VAL_PUB is a public PL/SQL package in the APPS schema that supports Oracle Payments (IBY) payment format validation in Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its role is to apply format-level validation rules to payment instructions before those instructions are transmitted to a payment system or a bank through a payment file. The package enforces the structural and content requirements that are configured as validation sets and validation assignments, ensuring that each payment instruction conforms to the accepted format for a given payment system, payment method, and disbursement type.

Because the object is classified as a PUB API, it is intended to be callable by other Oracle EBS modules and by authorized custom code, rather than being an internal-only implementation. Its dependencies on IBY_PAY_INSTRUCTIONS_ALL, IBY_VALIDATION_SETS_VL, and IBY_VAL_ASSIGNMENTS confirm that it operates directly on the Oracle Payments transaction validation framework, reading the active validation sets and assignments configured for a payment process profile and reporting validation failures through transaction error records.

Key Procedures and Functions

The ETRM package metadata documents fifteen public procedures and functions. The naming convention encodes the validation operation. The FVTP* members — FVTPCCD, FVTPPPD, and FVTPPPDP — validate payment format data for CCD, PPD, and PPD-style payment formats respectively, including the PPD variant flagged with the trailing P. The FVSP* members — FVSPCCD, FVSPCCDP, FVSPNCR, FVSPPPD, and FVSPPPDP — perform the corresponding validations for the separate (FVSP) context, covering CCD, NCR (non-cash reporting), and PPD formats. The FVBL* members — FVBLCCDP, FVBLNCR, FVBLPPDP, and FVBLSLTR — apply rules to the individual fields within a payment instruction; SLTR relates to the secondary letter or reference element of the format. FVTIACHP, FVTIACHB, and FVTICTX return the format identifiers or validation context for ACH payments and for context-sensitive validation. Collectively these entries provide discrete validation entry points for the ACH transaction elements used by Oracle Payments.

Tables Accessed

The package reads IBY_PAY_INSTRUCTIONS_ALL, which stores payment instruction records and their associated payment format attributes, and IBY_PAYMENTS_ALL, which holds individual payment records. IBY_VAL_ASSIGNMENTS and IBY_VALIDATION_SETS_VL supply the configured validation rules and their assignment to payment process profiles; IBY_DOCS_PAYABLE_ALL and IBY_EXT_BANK_ACCOUNTS provide document and external bank account context used during validation. FV_TP_TS_AMT_DATA supports the amount data used in the ACH and format checks. IBY_SECURITY_SEGMENTS and IBY_SYS_SECURITY_SUBKEYS are read to enforce security-based access restrictions on the records being validated. IBY_TRANSACTION_ERRORS is written to record validation failures so they can be surfaced through the Oracle Payments user interface and correction workflows.

Usage Notes

IBY_PAYMENT_FORMAT_VAL_PUB is invoked during Oracle Payments processing, typically from the payment instruction formatting and validation UI and from the payment processing concurrent programs that build and format payment files. The PL/SQL validation package registered against a payment process profile determines whether this package is called for a given profile; the format-specific procedures are then dispatched according to the payment format configured for the instruction. Custom code may call the public procedures when building a bespoke validation routine, but any such call must respect the existing validation set assignments and error-recording conventions to avoid inconsistent error reporting. Because the package is VALID in APPS and is referenced by no other package in the documented dependency chain, its callers are external — forms, concurrent programs, and customer extensions — rather than sibling IBY packages.