Search Results debug_switch

Overview

AP_IMPORT_VALIDATION_PKG is the core validation engine for the Payables Open Interface Import process in Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its principal business function is to inspect invoice header and invoice line records staged in the AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE tables before they are converted into permanent Payables transactions. The package applies the full set of trading-partner, currency, tax, terms, distribution, and matching validations that Oracle Payables requires, returning fatal or non-fatal error conditions to the calling import program so that rejected rows can be reported on the Payables Open Interface Import execution report and corrected by the user.

The package belongs to the APPS schema and is classified under the OTHER API category. Function V_CHECK_INVOICE_VALIDATION is the primary entry point; it accepts an in-out invoice record of type AP_IMPORT_INVOICES_PKG.r_invoice_info_rec together with base currency, set of books, tolerance, match mode, and prepayment parameters, and returns status and error indicators. The 48 documented procedures and functions operate almost exclusively as helper routines subordinate to this driving routine.

Key Procedures and Functions

The documented routines are grouped by the validation domain they cover. The user's search term "debug_switch" relates to the diagnostic tracing conventions used inside these routines, which emit debug output controlled by the standard FND debug mechanism rather than a dedicated public parameter; no separate DEBUG_SWITCH procedure is documented in the ETRM metadata.

• Trading-partner validations: V_CHECK_INVALID_PO, 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, purchasing document, and party identifiers supplied on the interface record exist, are active, and are valid for the operating unit.
• Invoice attribute validations: V_CHECK_INVALID_INVOICE_NUM, V_CHECK_INVALID_INV_CURR_CODE, V_CHECK_INVALID_PAY_CURR, V_CHECK_INVOICE_TYPE_AMOUNT, V_CHECK_EXCHANGE_RATE_TYPE, V_CHECK_NO_XRATE_BASE_AMOUNT, and V_CHECK_INVALID_TERMS verify the structural correctness of the invoice itself, including amount-to-type consistency and, where multi-currency processing applies, the presence of an exchange rate.
• Withholding tax: V_CHECK_INVALID_AWT_GROUP and V_CHECK_INVALID_PAY_AWT_GROUP validate the withholding tax group and payment withholding tax group against the withholding tax definitions.
• Legal entity and miscellaneous header data: V_CHECK_LEGAL_ENTITY_INFO and V_CHECK_MISC_INVOICE_INFO validate the legal entity context and remaining header-level attributes.
• Prepayment processing: V_CHECK_PREPAY_INFO resolves and validates prepayment references and periods.
• Line-level validation: V_CHECK_LINES_VALIDATION and V_CHECK_INVOICE_LINE_AMOUNT validate invoice lines and their calculated amounts within the context established by the header routine.

Tables Accessed

The package reads and writes the staging and transaction tables that participate in open interface processing. AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE hold the inbound rows being validated. AP_INVOICES_ALL, AP_INVOICE_LINES_ALL, AP_INVOICE_DISTRIBUTIONS, and AP_HISTORY_INVOICES supply existing transaction data used for duplicate-checking and cross-reference. Supplier and site validation draws on AP_SUPPLIER_SITES_ALL. Withholding tax checks reference AP_AWT_GROUPS, while distribution validation reads AP_DISTRIBUTION_SETS and AP_DISTRIBUTION_SET_LINES. Income tax validation uses AP_INCOME_TAX_REGIONS and AP_INCOME_TAX_TYPES.

Usage Notes

AP_IMPORT_VALIDATION_PKG is invoked internally by AP_IMPORT_INVOICES_PKG and its companions during the Payables Open Interface Import concurrent program. It is not intended for direct invocation by end users or custom forms; Oracle's documented guidance is to submit the standard import program rather than call the package directly. Custom code that does call these routines must supply the complete parameter set required by the header validation function, including tolerances, set of books, and base currency, and must handle both fatal_error_flag and the returned invoice status. Debug tracing follows the FND debugging conventions, so DBMS output can be enabled through the standard profile options rather than through the package's public interface.