Search Results payment_method_pk




Overview
Explore in AI Chat

Overview

The view APPS.FIIBV_AP_AP_APPY_PYMT_MTHD_LCV is a Financial Intelligence (FII) base view that supplies the Payment Method level of the Oracle E-Business Suite Accounts Payable (AP) Payment dimension. It is delivered as part of the FII product family, whose views serve as the extract layer for the Enterprise Data Warehouse and associated analytical reporting. In EBS 12.1.1 and 12.2.2, the object is documented as VALID and remains a stable component of the AP Payment dimension hierarchy.

Its central purpose is to expose the set of payment method values available to a payment record so that FII fact tables and downstream BI/ETL processes can join transactional payment data to a normalized payment method key. The column PAYMENT_METHOD_PK, which is the value users most commonly search for when investigating this view, is the surrogate key generated for each payment method and is defined as the lookup code of the PAYMENT METHOD lookup type. The view therefore acts as the conformance layer that maps the operational lookup values used in AP into a warehouse-friendly dimension key.

Underlying Base Objects

The view is defined over two base objects, both in the APPS schema:

  • AP_LOOKUP_CODES (aliased LC) — the AP lookup code table that stores the payment method codes and their descriptive information.
  • FND_LOOKUP_VALUES (aliased FND) — the common Oracle Application Object Library lookup values table.

The two sources are joined on LOOKUP_TYPE and LOOKUP_CODE, with the view filtering LC.LOOKUP_TYPE = 'PAYMENT METHOD' and matching LC.DISPLAYED_FIELD = FND.MEANING. Documented ETRM metadata lists no additional referenced base objects, although the view text references the EDW_INSTANCE.GET_CODE function to populate the INSTANCE column. The result is a de-duplicated, conformed list of payment methods valid for the given instance.

Key Columns

  • PAYMENT_METHOD_PK — the primary key of the dimension member, sourced from LC.LOOKUP_CODE. This is the column most frequently queried when resolving a payment method to its warehouse identifier.
  • ALL_FK — a static 'ALL' value used as a roll-up/aggregation foreign key for "all payment methods" reporting.
  • INSTANCE — the EDW instance code, derived via SUBSTRB(EDW_INSTANCE.GET_CODE, 1, 40).
  • NAME and PAYMENT_METHOD — both populated from LC.DISPLAYED_FIELD, providing the user-facing payment method label.
  • DESCRIPTION — the descriptive text from LC.DESCRIPTION.
  • LAST_UPDATE_DATE and CREATION_DATE — both derived from NVL(LC.START_DATE_ACTIVE, SYSDATE-1), giving a non-null audit timestamp.
  • DELETION_DATE and PAYMENT_METHOD_DP — exposed as NULL, reserved for slowly changing dimension or data-preservation handling.
  • Descriptor/reference columns — the documented _DF entries (for example _DF:FND:FND_COMMON_LOOKUPS:FND, _DF:_DUMMY:SQLAP:AP_CHECKS:AC, _DF:_DUMMY:SQLAP:CHECK ADDRESS:AC, _DF:_DUMMY:SQLAP:AP_GOV_DETAIL_CHECKS:AC, and _DF:_DUMMY:JG:JG_AP_CHECKS:AC) and the corresponding "_DF:LC:_EDW", "_DF:CHK:_EDW", "_DF:ADD:_EDW", "_DF:GOV:_EDW", and "_DF:JGC:_EDW" attributes identify source descriptors used by the Financial Intelligence extract process.

Common Use Cases and Queries

Typical scenarios include validating the payment method dimension during FII ETL loads, resolving a payment method code to its surrogate key when integrating AP payment transactions, and building lookup lists for analytical reports. A representative query is shown below:

SELECT payment_method_pk, name, payment_method, description
FROM apps.fiibv_ap_ap_appy_pymt_mthd_lcv
WHERE payment_method_pk = :p_method_code;

For roll-up reporting, the ALL_FK column allows a report to aggregate all payment methods under a single member. Because the view is instance-aware, queries should be scoped by INSTANCE when multiple EDW instances are consolidated in the same analysis environment.