Results for “ap_pmt_validations_pkg”
36 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.AP_PMT_VALIDATIONS_PKG is an Oracle Payables validation package whose documented entry point, PERFORMVALIDATIONS, extends the standard Oracle Payments (IBY) validation framework with Payables-specific checks. In Oracle EBS 12.1.1 and 12.2.2, payment instruction processing is owned by the Oracle Payments module: instructions are built, formatted, and submitted through validation sets, and each validation set is expected to return a pass or fail result together with an error record. This package participates in that model by evaluating Payables-side conditions on payments that belong to a completed payments group (identified by a completed payments group identifier passed into the routine), and by populating the transaction errors structure (IBY_TRANSACTION_ERRORS) when a payment must be rejected.
Practically, the package acts as a reconciliation and integrity gate between the Oracle Payables subledger and the Oracle Payments execution tables. Its internal cursor, check_sequences, joins the payments view (IBY_FD_PAYMENTS_V), payment instructions (IBY_PAY_INSTRUCTIONS_ALL), payment profiles (IBY_PAYMENT_PROFILES), and bank account uses (CE_BANK_ACCT_USES_ALL) to retrieve payment, payment document, payment method, and bank account use identifiers for the completed payments group. The package then drives a series of count-based validations and per-payment checks derived from those identifiers. Because validation outcomes can block disbursement, the routine is instrumented with FND_LOG debug statements gated by the runtime level, which is the standard technique for diagnosing why a payment instruction failed.
Key Procedures and Functions
- PERFORMVALIDATIONS — The single documented procedure in this package body. It accepts an instruction identifier, a completed payments group identifier, a Boolean validation result (returned as an OUT parameter), and an IBY_TRANSACTION_ERRORS%ROWTYPE error record (IN OUT). It performs the package's validation logic for a payments group, sets the result to indicate whether the payments passed or failed, and populates the error record when a failure is detected. It is the only public program unit exposed by this package.
Tables Accessed
- IBY_TRANSACTION_ERRORS — receives the error row returned when validation fails, supplying the message surfaced to the user in the payment instruction or payment process request.
- IBY_PAYMENTS_ALL and IBY_DOCS_PAYABLE_ALL — the Oracle Payments payment and document payable records that are the subject of validation.
- CE_BANK_ACCOUNTS, CE_BANK_ACCT_USES_ALL, CE_GL_ACCOUNTS_CCID — internal bank account and account use details, including the bank account use identifier and associated accounting flexfield references.
- AP_INVOICES_ALL, AP_PAYMENT_SCHEDULES_ALL, AP_SELECTED_INVOICES_ALL, AP_SUPPLIER_SITES_ALL, AP_AWT_TEMP_DISTRIBUTIONS_ALL — the Payables invoice, schedule, selection, supplier site, and withholding distribution sources used to confirm that the payments are supported by valid, selected Payables documents.
- AP_SYSTEM_PARAMETERS_ALL — Payables system options that influence validation behavior and defaults.
- FND_CURRENCIES, GL_PERIOD_STATUSES, GL_CODE_COMBINATIONS — currency definitions, open/closed accounting period status, and accounting flexfield combinations used to verify currency and accounting period validity.
Usage Notes
The package is invoked from within Oracle Payments payment processing rather than from a standalone form or concurrent program. Its documented dependency metadata shows it is referenced by exactly one other package, indicating that a controlling Payments validation package calls PERFORMVALIDATIONS during payment instruction validation. It is not intended for direct invocation by end users, and customers should avoid calling it from custom code because the signature depends on internal completed payments group identifiers that are only meaningful inside the payment run. For troubleshooting, the FND_LOG debug output written by the routine (module name AP_PMT_VALIDATIONS_PKG.performValidations) can be enabled through the standard logging profile options. The user search term "TALLY E49" does not correspond to this object's module name or documented parameters; it most likely originates from a compiled-body notice or a message code encountered alongside this package name, and should be treated as an application message reference rather than part of the package interface.
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
VIEW: APPS.IBY_FD_PAYMENTS_V 12.2.2
-
VIEW: APPS.AP_LOOKUP_CODES 12.2.2
-
SYNONYM: APPS.FND_CURRENCIES 12.2.2
-
VIEW: APPS.PO_VENDORS 12.2.2
-
VIEW: APPS.GL_SETS_OF_BOOKS 12.2.2
-
Set Distribution Table.
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
Set Distribution Table.