Results for “inv_type”

50+ results




Overview
Explore in AI Chat

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

Overview

FIIBV_AP_IVTY_INV_TYPE_LCV is a Financial Intelligence (FII) extraction view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its name follows the FIIBV prefix convention used by Oracle Financial Intelligence / Enterprise Data Warehouse (EDW) staging objects, where "AP" denotes the Payables source, "IVTY" denotes invoice activity, "INV_TYPE" denotes the invoice type dimension, and "LCV" denotes a lookup-code-based value view. The view exposes invoice type reference data in the flat, surrogate-keyed format required by the FII warehouse load process rather than the normalized, multi-language structure in which Oracle Payables stores lookups.

Rather than holding transactional data, the object supplies a conformed dimension of invoice types (for example, Standard, Credit Memo, Debit Memo, Prepayment, and Expense Report) that downstream financial analytics and star schemas join to invoice fact tables. Because the view is described in the ETRM metadata as an internal table with no external description, it is not intended as an end-user query surface; it is consumed by FII extraction programs and the EDW interface layer.

Underlying Base Objects

The view is defined over two documented base objects in the APPS schema: AP_LOOKUP_CODES and FND_LOOKUP_VALUES. The join is constrained on LOOKUP_TYPE equal to 'INVOICE TYPE' and on the matching LOOKUP_CODE and DISPLAYED_FIELD / MEANING values, which restricts the result set to the invoice type lookup set while guaranteeing consistency between the Payables lookup definition and the common FND lookup table used across EBS.

  • AP_LOOKUP_CODES — supplies the primary key value (LOOKUP_CODE), the display name (DISPLAYED_FIELD), the description, and the effective start date.
  • FND_LOOKUP_VALUES — provides the multilingual meaning and enforces the referential linkage to the global lookup framework (FND_COMMON_LOOKUPS).
  • EDW_INSTANCE.GET_CODE — used to stamp the INSTANCE column with a substring of the current instance code, enabling multi-instance warehouse consolidation.

The view is therefore read-only and inherits its refresh characteristics from the underlying lookup tables; no materialization is documented, so results reflect the current state of the lookup definitions at query time.

Key Columns

  • INV_TYPE_PK — the invoice type lookup code, functioning as the warehouse surrogate/business key for the dimension.
  • ALL_FK — a constant value of 'ALL', used as a default foreign key for "all members" aggregation rows in the FII model.
  • INSTANCE — the source EBS instance identifier derived from EDW_INSTANCE.GET_CODE, truncated to 40 bytes.
  • NAME and INV_TYPE — both mapped to the displayed field of the lookup, providing the descriptive invoice type label.
  • DESCRIPTION — the lookup description text.
  • LAST_UPDATE_DATE and CREATION_DATE — both derived from NVL(START_DATE_ACTIVE, SYSDATE-1) to satisfy warehouse auditing requirements.
  • DELETION_DATE and INV_TYPE_DP — NULL placeholders reserved for incremental load and dimension-processing logic.

Common Use Cases and Queries

Typical usage involves joining invoice fact extracts to this dimension to obtain readable invoice type descriptions, and validating that all Payables invoice types are represented in the warehouse. A representative query follows:

SELECT inv_type_pk, name, description, instance FROM apps.fiibv_ap_ivty_inv_type_lcv ORDER BY inv_type_pk;

Analysts may also filter by instance for multi-org consolidations or use the view as a validation source when reconciling FII invoice activity extracts against AP_LOOKUP_CODES.