Results for “ap_lc_invoice_types_v”

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

Overview

AP_LC_INVOICE_TYPES_V is a Payables (AP) view owned by the APPS schema in Oracle E-Business Suite. Its name reflects its origin as a letter-of-credit (LC) related report view, but the underlying definition is far more general: it is a filtered projection of the invoice type lookup values defined in the Payables application. The view is documented as valid in the ETRM metadata and appears in both 12.1.1 and 12.2.2 environments, although the original documentation labels it as a Release 10SC-only object. Despite that historical annotation, the object remains present and callable in later releases, where it continues to expose the set of active, reportable invoice types used by the Payables subledger.

The view presents three attributes for each qualifying lookup code: the code itself, a displayed field, and a description. It deliberately excludes invoice types that are internal processing constructs rather than user-selectable invoice classifications. Because the definition embeds a SYSDATE comparison, the view is also self-maintaining with respect to inactive lookups: any lookup row whose INACTIVE_DATE has passed is automatically suppressed from the result set. In reporting and integration scenarios, this view serves as a lightweight, read-only enumerated list of invoice types that can be joined to AP invoice headers, distributions, or custom reporting tables without requiring callers to reconstruct the exclusion and date-filtering logic themselves.

Underlying Base Objects

The view is defined over a single referenced object in the documented metadata: AP_LOOKUP_CODES, which is itself a view in the APPS schema rather than a physical table. AP_LOOKUP_CODES exposes Payables lookup values, including the LOOKUP_TYPE, LOOKUP_CODE, DISPLAYED_FIELD, DESCRIPTION, and INACTIVE_DATE attributes used by AP_LC_INVOICE_TYPES_V. The dependency on FND_GLOBAL is recorded as well; FND_GLOBAL is the standard EBS package that supplies session and responsibility context, and its presence typically indicates that the underlying lookup view applies organization or language context when resolving lookup values.

Functionally, therefore, AP_LC_INVOICE_TYPES_V is a narrow, pre-filtered slice of AP_LOOKUP_CODES. The filter is expressed in the view text as LOOKUP_TYPE = 'INVOICE TYPE' combined with a NOT IN exclusion list and a date predicate. This means the view cannot return data that is not present in AP_LOOKUP_CODES, and any maintenance performed on the underlying invoice type lookup values is immediately reflected in the view.

Key Columns

• LOOKUP_CODE — The coded value of the invoice type. This is the column typically joined to AP invoice header attributes (for example, the invoice type code stored on AP_INVOICES_ALL) to translate a stored code into a readable label.
• DISPLAYED_FIELD — The user-facing displayed value for the lookup code. In the standard EBS lookup model this holds the translatable display text shown to users, and it is the appropriate column to select when producing report output or user-facing lists.
• DESCRIPTION — The longer descriptive text associated with the lookup code, providing additional context beyond the short displayed field.

Because the view derives entirely from AP_LOOKUP_CODES, it exposes no primary key, no foreign keys, and no audit columns. It is a reference or lookup view, not a transactional one.

Common Use Cases and Queries

The view is most often used to populate selection lists, validate values, or resolve invoice type codes in custom reports and integrations. A typical query returning the available invoice types is:

• SELECT lookup_code, displayed_field, description FROM apps.ap_lc_invoice_types_v ORDER BY displayed_field;
• SELECT ai.invoice_num, ai.invoice_type_lookup_code, t.displayed_field FROM apps.ap_invoices_all ai, apps.ap_lc_invoice_types_v t WHERE ai.invoice_type_lookup_code = t.lookup_code;
• SELECT lookup_code FROM apps.ap_lc_invoice_types_v WHERE lookup_code = :p_type; for validation in a concurrent program or form.

Note that the view excludes INTEREST, QUICKMATCH, QUICKDEFAULT, ADJUSTMENT, and PO PRICE ADJUST codes, so it should not be relied upon when those internal types must be reported. For complete coverage, query AP_LOOKUP_CODES directly with LOOKUP_TYPE = 'INVOICE TYPE'. Because the view applies SYSDATE-based filtering, results can vary over time as lookups are end-dated, which is appropriate for user-facing lists but should be considered when historical reporting is required.