Results for “ap_invoice_import_rejection_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AP_INVOICE_IMPORT_REJECTION_V is a read-only view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is a component of the Oracle Payables (AP) module and exposes the seeded lookup values that define the set of invoice import rejection reasons recognized by the Payables Open Interface Import program. When the Payables Open Interface Import concurrent program processes inbound invoice records from the AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE tables, records that fail validation are written to the interface rejection tables along with a rejection code. That rejection code is validated against the lookup type INVOICE IMPORT REJECTION, and this view is the supported reporting window onto those lookup values.

The view presents a compact, three-column projection of the lookup repository, filtered to the single lookup type INVOICE IMPORT REJECTION. Its role is primarily diagnostic and reference-oriented: it allows implementation teams, support analysts, and reporting developers to translate the opaque rejection codes stored on rejected interface rows into human-readable descriptions, and to enumerate the complete taxonomy of rejection conditions that the import process can emit.

Underlying Base Objects

The documented definition of the view is a simple filtered select over AP_LOOKUP_CODES, itself a view in the APPS schema that resolves the lookup types, codes, and translated meanings used throughout Oracle Payables. The view is defined logically as selecting LOOKUP_CODE, DISPLAYED_FIELD, and DESCRIPTION from AP_LOOKUP_CODES where LOOKUP_TYPE equals the literal value ‘INVOICE IMPORT REJECTION’. Because AP_LOOKUP_CODES is a view, the ultimate base storage resides in the Oracle Application Object Library (FND) lookup tables, which hold the seeded and user-maintained lookup values for all products. The documented metadata for the view also references FND_GLOBAL, the standard package used across EBS for session context such as the current user and responsibility; this reflects the row-level security and language/translation behavior that the underlying lookup views inherit at runtime. No other base objects are documented for this view.

Key Columns

• LOOKUP_CODE — The internal code value that is stored against a rejected interface record. This is the join key used when reconciling rejection rows back to their descriptive text.
• DISPLAYED_FIELD — The field or attribute against which the rejection was raised, indicating which part of the inbound invoice record failed validation.
• DESCRIPTION — The translated, user-facing meaning of the rejection, suitable for display in reports, forms, and diagnostic queries.

Common Use Cases and Queries

Typical usage falls into three categories: documentation of the available rejection reasons, translation of codes captured on rejected interface records, and validation of lookup configuration after patching or upgrade.

• Enumerating all possible rejection reasons for reference or training documentation.
• Joining rejection codes on interface exception records to obtain readable text for a reconciliation report.
• Confirming that the INVOICE IMPORT REJECTION lookup type is populated and enabled in a given environment.

A representative query is:

SELECT lookup_code, displayed_field, description
FROM ap.ap_invoice_import_rejection_v
ORDER BY lookup_code;

Because the view is already filtered, no WHERE clause on lookup type is required. Filtering by DISPLAYED_FIELD is useful when diagnosing a specific class of failure, and the view can be outer-joined to interface rejection data on LOOKUP_CODE to enrich exception reporting.

Considerations and Limitations

The view is read-only and exposes only three columns; it does not surface the enabled flag, start and end dates, or other control attributes present on the underlying lookup records. Organizations that add custom rejection reasons through the lookup maintenance forms will see those values reflected here, but should exercise caution: modifying or disabling seeded rejection lookups can obscure diagnostics produced by the Payables Open Interface Import process and complicate support escalation.