Search Results payment_term

Overview

FII_AP_PTRM_PAY_TERM_LCV is a Financial Intelligence (FII) reporting view owned by the APPS schema. It presents a consolidated list of payment terms drawn from both the Payables (AP) and Receivables (AR) sides of Oracle E-Business Suite, exposing them in a denormalized, extract-friendly shape intended for ETRM (Enterprise Transactional Reporting Model) loading and downstream analytics. The view is registered as VALID and forms part of the FII data warehouse layer that feeds financial subject areas such as payment-terms and cash-management reporting in both 12.1.1 and 12.2.2.

The view name carries the LCV suffix, denoting a "loadable/conformed view." Its purpose is to produce a uniform, source-system-tagged dataset of payment terms that can be joined to transactional facts (invoices, payments, receipts) during ETRM refresh cycles. The most notable characteristic is the ALL_FK column, which is a hard-coded literal that lets downstream consumers join every row without a discriminating key — this is the column that typically drives searches for "all_fk" in the ETRM schema.

Underlying Base Objects

Unlike most FII views, the ETRM metadata documents no referenced base objects for this view. In practice, the view text draws directly from two base tables, combined with a UNION ALL:

• AP_TERMS — the Payables payment-terms table, filtered by NVL(ENABLED_FLAG, 'Y') = 'Y' so only active terms are surfaced. This is the source of the ENABLED_FLAG, RANK and TYPE (TERM_TYPE) values.
• RA_TERMS — the Receivables payment-terms table, contributing the AR-side rows. Because RA_TERMS does not carry the same enabling/rank attributes, those columns are deliberately returned as NULL (via TO_CHAR(NULL) and TO_NUMBER(NULL)).
• EDW_INSTANCE — a Financial Intelligence utility referenced through the function EDW_INSTANCE.GET_CODE, which returns the current instance/source identifier used to stamp each row.

The AP and AR rows are aligned into a single column set by the UNION ALL, ensuring one homogeneous projection regardless of source, and the two branches are distinguished only by the literal inserted into the PAY_TERM_PK key (the 'AP-' or 'AR-' token).

Key Columns

• PAY_TERM_PK — Synthetic primary key formed as TO_CHAR(TERM_ID) || '-' || 'AP|AR-' || instance code. It uniquely identifies a payment term within a source (AP vs AR) and instance.
• ALL_FK — A literal constant 'ALL' repeated on every row. It provides a join key for "all rows" style lookups, so a fact table can be linked to every payment term without a source-specific predicate.
• DESCRIPTION — The term description from the underlying AP_TERMS or RA_TERMS row.
• ENABLED_FLAG — Populated only for AP rows (always 'Y' due to the filter); NULL for AR rows.
• INSTANCE — Source instance code from EDW_INSTANCE.GET_CODE (truncated to 40 bytes).
• NAME / PAYMENT_TERM — Both columns carry the payment term name; PAYMENT_TERM is a friendly alias for reporting.
• RANK / TERM_TYPE — Populated for AP rows only (from AP_TERMS.RANK and AP_TERMS.TYPE); NULL for AR rows.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Validity window of the term.
• LAST_UPDATE_DATE — Row-change timestamp used for incremental ETRM extracts.

Common Use Cases and Queries

The view is typically used to build payment-term dimensions and to enrich AP/AR transaction extracts with due-date and discount logic. A typical extraction joins facts to terms through ALL_FK or PAY_TERM_PK:

• List all active payment terms by source:

  SELECT PAY_TERM_PK, PAYMENT_TERM, INSTANCE
  FROM   APPS.FII_AP_PTRM_PAY_TERM_LCV
  WHERE  ENABLED_FLAG = 'Y';

• Joining a fact to every term via ALL_FK:

  SELECT t.PAYMENT_TERM, f.*
  FROM   APPS.FII_AP_PTRM_PAY_TERM_LCV t, my_fact f
  WHERE  t.ALL_FK = f.ALL_FK;

• Incremental ETRM load filtered by LAST_UPDATE_DATE:

  SELECT *
  FROM   APPS.FII_AP_PTRM_PAY_TERM_LCV
  WHERE  LAST_UPDATE_DATE >= :last_run_date;

Because AP-only attributes (ENABLED_FLAG, RANK, TERM_TYPE) are NULL on the Receivables branch, consumers should apply source-aware logic when relying on those columns, and should always use PAY_TERM_PK rather than NAME as the unique identifier.