Results for “ap_lc_invoice_types_db_v”

16 results




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

Overview

The AP_LC_INVOICE_TYPES_DB_V view is a Payables (AP) module database object owned by the APPS schema in Oracle E-Business Suite. It exposes the set of invoice type lookup values that are eligible for letter of credit (LC) and related invoice processing in early Oracle Payables releases, most notably the 10SC code line. The view is defined as a filtered projection of the AP_LOOKUP_CODES view, restricted to the lookup type 'INVOICE TYPE' and further constrained to exclude a defined set of system-managed or special-purpose invoice types.

In reporting and integration contexts, this view provides a stable, read-only interface for retrieving the invoice type values that a given EBS instance treats as standard, user-selectable invoice types. Because it resolves the legacy INVOICE TYPE lookup codes while specifically omitting internal codes such as INTEREST, PREPAYMENT, and ADJUSTMENT, it is useful where downstream logic must operate only on ordinary invoice categories rather than the full lookup spectrum. The object is documented as Release 10SC only, and later 12.1.1 and 12.2.2 implementations should confirm its presence and behavior before relying on it.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view is defined over two referenced base objects:

  • AP_LOOKUP_CODES (VIEW) — the primary source. This APPS view presents decoded lookup code, displayed field, and description values for Payables lookup types. AP_LC_INVOICE_TYPES_DB_V selects from it with LOOKUP_TYPE = 'INVOICE TYPE'.
  • FND_GLOBAL (PACKAGE) — the Oracle Application Object Library package that supplies session context such as user, responsibility, and application identifiers, which may influence the translated or displayed lookup values returned by AP_LOOKUP_CODES.

The view text filters the AP_LOOKUP_CODES result set using a NOT IN list that removes system-generated or specialized codes: QUICKDEFAULT, QUICKMATCH, INTEREST, PREPAYMENT, ADJUSTMENT, and 'PO PRICE ADJUST'. It additionally applies an effective-date predicate, SYSDATE < NVL(INACTIVE_DATE, SYSDATE+1), so that only currently active invoice types are returned; a lookup code with no INACTIVE_DATE is treated as indefinitely active.

Key Columns

The view exposes three columns inherited from AP_LOOKUP_CODES:

  • LOOKUP_CODE — the internal code identifying the invoice type (for example, STANDARD or CREDIT). This is the value used in validation and foreign-key style references within Payables.
  • DISPLAYED_FIELD — the user-facing name of the invoice type, as rendered on forms and reports.
  • DESCRIPTION — additional descriptive text for the invoice type, where populated.

Although the view does not project INACTIVE_DATE, that column is used in its WHERE clause to enforce active-status filtering, so the effective-date behavior is implicit rather than selectable.

Common Use Cases and Queries

The view is typically used in custom reports, concurrent programs, and integration extracts that must enumerate the standard invoice types available to users while suppressing internal codes. A representative query lists all active invoice types:

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

A more targeted usage validates a single type or populates a list of values:

  • SELECT displayed_field FROM apps.ap_lc_invoice_types_db_v WHERE lookup_code = 'STANDARD';
  • SELECT lookup_code FROM apps.ap_lc_invoice_types_db_v WHERE UPPER(displayed_field) LIKE 'INV%';

Because the view is documented as Release 10SC only, implementers on 12.1.1 and 12.2.2 should verify its existence and validity in the target instance using ALL_VIEWS or the ETRM before embedding it in production code; alternatives such as querying AP_LOOKUP_CODES directly with an equivalent filter may be required where the view is absent.