Search Results payment_method




Overview
Explore in AI Chat

Overview

FII_AP_AP_APPY_PYMT_MTHD_LCV is a collection view within the Oracle Financial Intelligence (FII) product family, historically shipped as part of the Oracle E-Business Suite 12.1.1 and 12.2.2 technology stack. FII is the predecessor architecture to the Oracle Business Intelligence Applications (OBIA) and Enterprise Performance Management (EPM) integration layers, and it supplied pre-built dimensional extract views used to populate the AP (Accounts Payable) analytical warehouse. This particular view represents the Payment Method level of the AP Payment dimension. In other words, it exposes the distinct set of payment methods (for example, check, wire, electronic funds transfer, or clearing) that can be associated with an AP payment record, formatted as dimension rows suitable for extraction and loading into an OLAP or BI target.

The view is classified in ETRM as Obsolete and is marked "Not implemented in this database." This indicates that although the object definition is catalogued in the ETRM metadata repository, the view is not present in the current database instance. It survives as documentation of a prior FII delivery and should be treated as a legacy artifact rather than an active query target on supported releases.

Underlying Base Objects

The documented ETRM metadata records none for referenced base objects and does not identify an owner. The view is defined over a single source object, FIIBV_AP_AP_APPY_PYMT_MTHD_LCV, where the FIIBV_ prefix denotes a base view in the FII naming convention. That base view—rather than a physical table—supplies all projected columns, and the collection view performs a straight column projection with no joins or filters. Because the base view is not catalogued here, the ultimate tables beneath it are not documented, but by FII design such base views typically resolve to AP lookup or payment-method reference data. Notably, the final five projected positions are literal NULL values, mapping to the USER_ATTRIBUTE1 through USER_ATTRIBUTE5 slots.

Key Columns

  • PAYMENT_METHOD_PK — Surrogate primary key for the payment-method dimension row.
  • ALL_FK — The "All" foreign key, used to link the dimension to its parent or "All Payment Methods" aggregate member.
  • INSTANCE — Identifies the source instance or warehouse load context.
  • NAME — Display name of the payment method dimension member.
  • PAYMENT_METHOD — The operational payment-method code or value.
  • DESCRIPTION — Descriptive text for the payment method.
  • LAST_UPDATE_DATE / CREATION_DATE — Standard audit timestamps supporting incremental (delta) extraction.
  • DELETION_DATE — Soft-delete marker enabling logical removal handling during loads.
  • PAYMENT_METHOD_DP — The "DP" (data-provider or display-path) attribute accompanying the member.
  • USER_ATTRIBUTE1–5 — Reserved extension slots, currently emitted as NULL literals.

Common Use Cases and Queries

In its original FII role, this view populated the AP Payment dimension, enabling analyses of spend and disbursement grouped by payment method. Because it is obsolete and not implemented, live queries will fail unless the object is manually recreated; the sample below is illustrative of the intended structure.

SELECT PAYMENT_METHOD_PK, NAME, PAYMENT_METHOD, DESCRIPTION, LAST_UPDATE_DATE FROM FII_AP_AP_APPY_PYMT_MTHD_LCV WHERE DELETION_DATE IS NULL ORDER BY NAME;

A typical incremental extract filters on the audit timestamps: WHERE LAST_UPDATE_DATE >= :last_run_date. On supported releases, the functional equivalent of this dimension is obtained from the AP payment-method lookup values rather than from FII views.