Search Results g_failure

Overview

IBY_PAYMENT_FORMAT_VAL_PUB is a public PL/SQL package in the Oracle Payments (IBY) module of Oracle E-Business Suite. Its purpose is to perform format-level validation for payment instructions and payment documents prior to payment processing and payment file generation. The package applies the validation rules associated with a given payment format — such as CCD, CCDP, ACH, PPD, PPP, NCR, and related EFT variants — against the underlying payment data, and returns a result code that indicates whether the record passed or failed validation.

At the top of the package body three global variables are declared: g_EXCEPTION, g_FAILURE, and g_SUCCESS. These constants are initialized once for the session and are used by every procedure as the return values written to the x_result OUT parameter. The source header identifies the file as ibyfvvsb.pls (version 120.14), confirming that this is the validation package body for the IBY payment format validation layer, a companion to the IBY_VALIDATIONSETS_PUB package that owns the shared record and table types used here.

Key Procedures and Functions

The package exposes fifteen documented procedures, each corresponding to a specific payment format and validation stage:

• FVBLCCDP, FVBLPPDP — bulk validation routines for CCDP and PPD payment formats, invoked when a batch or bulk set of instructions must be validated in one call.
• FVBLNCR, FVBLSLTR — bulk validation for the NCR and SLTR formats.
• FVTPCCD, FVTPPPD, FVTPPPDP — transaction-level (single-payment) validation for CCD, PPD, and PPD-plus formats against third-party payees.
• FVSPCCD, FVSPPPD, FVSPPPDP — supplementary/single-payment validations for CCD, PPD, and PPD-plus formats, typically used for supplier or internal payee scenarios.
• FVSPCCDP, FVSPNCR — single-payment validations specific to CCDP and NCR.
• FVTIACHP, FVTIACHB, FVTICTX — validation routines for ACH payment, ACH batch, and CTX formats respectively.

Each procedure accepts the validation assignment and validation set identifiers, plus the payment instruction identifier, and returns an OUT result code populated from the g_SUCCESS/g_FAILURE/g_EXCEPTION globals. Errors encountered during validation are captured in the IBY_TRANSACTION_ERRORS structure so that the calling process can surface them to the user.

Tables Accessed

The package reads from and writes to the following documented synonyms:

• IBY_PAY_INSTRUCTIONS_ALL — source of payment instruction and organization context.
• IBY_PAYMENTS_ALL — payer, payee, bank account, and registration data used for format field checks.
• IBY_EXT_BANK_ACCOUNTS — external bank account and branch details validated for ACH and wire formats.
• IBY_VAL_ASSIGNMENTS — links validation sets to payment formats and instructions.
• FV_TP_TS_AMT_DATA — third-party tax and amount data consumed during validation.
• IBY_DOCS_PAYABLE_ALL — invoice and document information tied to the payment.
• IBY_SECURITY_SEGMENTS and IBY_SYS_SECURITY_SUBKEYS — security segment/subkey lookups used to enforce access restrictions.
• IBY_TRANSACTION_ERRORS — target table where validation failures and exceptions are logged.

Usage Notes

IBY_PAYMENT_FORMAT_VAL_PUB is invoked from the Payment Process Request (PPR) workflow, the Format Payment Instructions concurrent program, and the Payments workbench when a user initiates validation of a payment batch. It is not intended for direct call from custom forms; Oracle Payments calls these procedures internally based on the format assigned to the payment instruction. Because the package is classified PUB and has no dependents listed in the ETRM metadata, customizations should extend validation through the standard IBY_VALIDATIONSETS_PUB interfaces rather than modifying this body. When diagnosing validation failures, developers typically query IBY_TRANSACTION_ERRORS for the instruction ID and compare the returned x_result against the g_SUCCESS or g_FAILURE constant to determine the outcome.