Results for “ap_invoice_import_sources_v”

16 results




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

Overview

AP_INVOICE_IMPORT_SOURCES_V is a Payables (AP) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the set of valid invoice import sources that can be assigned when importing invoices into Payables, whether through the Payables Open Interface Import process or through associated import workflows. Rather than storing transactional data, the view presents reference (lookup) information: it lists the source values available to categorize how an invoice entered the system.

The view is classified as VALID in ETRM and functions primarily as a reporting and integration convenience layer. It shields consumers from having to know that invoice import sources are modeled as an Oracle Application Object Library (FND) lookup type. Instead of querying the lookup tables directly and filtering on the correct lookup type, developers and integrators can select from AP_INVOICE_IMPORT_SOURCES_V and receive only the relevant import source values. This makes it useful in custom reports, interfaces, and validation logic where the permissible import sources must be presented or verified.

Underlying Base Objects

The view text is a single SELECT over the lookup view AP_LOOKUP_CODES, filtered by the lookup type 'INVOICE IMPORT SOURCES':

  • AP_LOOKUP_CODES — the immediate base object referenced by the view. It is itself a view (per the documented ETRM metadata), providing the decoded lookup values for Payables. The filter LOOKUP_TYPE = 'INVOICE IMPORT SOURCES' restricts the result to import-source entries only.
  • FND_GLOBAL — a documented referenced base object. FND_GLOBAL is the standard Oracle Applications package used to resolve runtime context such as the current user, responsibility, and application. Its presence is consistent with the multilingual (MLS) lookup infrastructure, in which AP_LOOKUP_CODES and its underlying lookup tables filter or translate rows based on the session's language and application context.

Because the view resolves through the lookup framework, the values returned are maintained centrally. Adding or modifying a lookup code for the 'INVOICE IMPORT SOURCES' lookup type is immediately reflected in the view, without any change to the view definition.

Key Columns

The view projects three columns, each inherited from AP_LOOKUP_CODES:

  • LOOKUP_CODE — the internal code that uniquely identifies an import source within the 'INVOICE IMPORT SOURCES' lookup type. This is the value stored on invoice records and referenced by import processes.
  • DISPLAYED_FIELD — the user-facing display text shown in Payables windows and list of values for the corresponding lookup code.
  • DESCRIPTION — the descriptive text associated with the import source, providing additional explanation of the lookup value.

These three columns together provide both the machine-readable code and the human-readable label and description, which is why the view is well suited to reporting and to populating selection lists.

Common Use Cases and Queries

Typical uses include validating an import source before loading invoices, populating a parameter list of values in a concurrent program or custom form, and reporting on invoices grouped by import source.

To list all available import sources:

  • SELECT lookup_code, displayed_field, description FROM apps.ap_invoice_import_sources_v ORDER BY lookup_code;

To resolve the display name for a known code:

  • SELECT displayed_field FROM apps.ap_invoice_import_sources_v WHERE lookup_code = :p_source;

To validate an incoming source during an interface load:

  • SELECT COUNT(*) FROM apps.ap_invoice_import_sources_v WHERE lookup_code = :p_source;

Because the view is a filtered subset of AP_LOOKUP_CODES, it is read-only and should not be used for DML; maintenance of import source values is performed through the lookup maintenance functionality. In 12.1.1 and 12.2.2 the object definition is unchanged, so queries written against it remain portable across both releases.