Search Results v_check_invoice_type_amount

Overview

APPS.AP_IMPORT_VALIDATION_PKG is a server-side PL/SQL validation package in Oracle E-Business Suite Payables. Its purpose is to centralize the business-rule checks that must pass before Payables interface data is accepted into the application tables. The package is declared with AUTHID CURRENT_USER, meaning its unqualified references to APPS objects resolve through the caller's schema and synonym privileges rather than the package owner's. This is significant because the package is designed for use by the Payables open interface and related import routines, which execute under a variety of session identities.

The package exposes a large public surface—48 documented procedures and functions in the 12.2.2 metadata—and defines a record type, r_dset_line_info, whose fields mirror AP_DISTRIBUTION_SET_LINES columns plus quantity and project accounting attributes from AP_INVOICE_DISTRIBUTIONS. This record type supports validation of distribution-set defaults applied to invoice lines. The majority of the package's procedures are prefixed with V_CHECK, indicating that they are validation entry points invoked during the import of invoice headers, lines, and distributions from the interface tables.

Key Procedures and Functions

The documented validation routines fall into several functional groups:

• Invoice-level checks: V_CHECK_INVOICE_VALIDATION, V_CHECK_INVALID_INVOICE_NUM, V_CHECK_INVALID_INV_CURR_CODE, V_CHECK_INVOICE_TYPE_AMOUNT, V_CHECK_MISC_INVOICE_INFO, and V_CHECK_LEGAL_ENTITY_INFO validate header data such as uniqueness of the invoice number, currency code validity, consistency of invoice type relative to amount, and legal entity context.
• Supplier and party checks: V_CHECK_INVALID_SUPPLIER, V_CHECK_INVALID_SUPPLIER_SITE, V_CHECK_INVALID_PARTY, and V_CHECK_INVALID_PARTY_SITE confirm that the supplier, supplier site, and the underlying party/party site referenced on the interface record exist and are valid for the operating context. The user's search term, v_check_invalid_party, corresponds to the routine that validates the party identifier associated with the supplier.
• Purchasing checks: V_CHECK_INVALID_PO verifies that a referenced purchase order is valid for the supplier and invoice.
• Withholding tax checks: V_CHECK_INVALID_AWT_GROUP and V_CHECK_INVALID_PAY_AWT_GROUP validate that the withholding tax group assigned to the invoice or payment is active and appropriate.
• Payment and financial checks: V_CHECK_EXCHANGE_RATE_TYPE, V_CHECK_INVALID_TERMS, V_CHECK_INVALID_PAY_CURR, V_CHECK_NO_XRATE_BASE_AMOUNT, V_CHECK_PREPAY_INFO, and V_CHECK_INVOICE_LINE_AMOUNT validate payment terms, payment currency, exchange rate availability, prepayment application, and line amount integrity.
• Line checks: V_CHECK_LINES_VALIDATION orchestrates validation across invoice lines and distributions.

Each routine raises or records validation errors that the caller surfaces to the user or logs in the interface error tables.

Tables Accessed

The package reads and writes against a defined set of APPS synonyms. Interface tables AP_INVOICES_INTERFACE, AP_INVOICE_LINES_INTERFACE, and AP_INVOICE_LINES_INTERFACE_S hold the staged import data being validated. Base tables AP_INVOICES, AP_INVOICES_ALL, AP_INVOICE_LINES, and AP_INVOICE_LINES_ALL are referenced to confirm existing invoice and line records. AP_INVOICE_DISTRIBUTIONS is used for distribution and project accounting quantities. Supplier validation relies on AP_SUPPLIER_SITES_ALL. Withholding tax validation uses AP_AWT_GROUPS, AP_INCOME_TAX_REGIONS, and AP_INCOME_TAX_TYPES. Distribution-set validation uses AP_DISTRIBUTION_SETS and AP_DISTRIBUTION_SET_LINES. AP_HISTORY_INVOICES supports historical invoice checks. The package is read-mostly against these objects, with error information typically returned to the caller rather than persisted directly.

Usage Notes

AP_IMPORT_VALIDATION_PKG is normally invoked by the Payables open interface import concurrent program and by related import flows, such as credit card or lease invoice import. It should not be called directly from end-user forms; the Payables Invoice Workbench relies on the import process to execute these checks. The package is referenced by three other packages, confirming its role as a shared validation library within the Payables schema. Customizations that bypass the interface import and load AP interface tables directly are the most common reason to call these routines explicitly, and any such usage must respect the AUTHID CURRENT_USER declaration by ensuring the executing schema has the necessary synonym grants. Because the validation logic encodes core Payables business rules, direct calls should be limited to reproducing standard import behavior rather than extending it.