Results for “fv_inv_histstat_v”

18 results




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

Overview

FV_INV_HISTSTAT_V is an APPS-owned database view within the Federal Financials (FV) product family of Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. Its documented purpose is to store and present invoice status history. The view consolidates current invoice status records with their historical counterparts, yielding a single, unified read interface over the temporal lifecycle of an invoice within the Receivables-based federal billing model. Because the object is a view rather than a table, it carries no storage of its own; it projects and unifies rows from its underlying base objects at query time.

In reporting and integration contexts, FV_INV_HISTSTAT_V functions as the canonical access point for invoice status transitions. Federal agencies subject to Treasury, GTAS, and SF-133 reporting obligations rely on this status history for audit trails, aging analysis, and reconciliation of billed versus collected balances. External systems and custom concurrent programs that need a consistent, deduplicated picture of invoice status can query the view without managing the UNION logic themselves.

Underlying Base Objects

The documented view text defines FV_INV_HISTSTAT_V as a UNION of two sources:

  • FV_INVOICE_STATUSES — referenced through a SYNONYM. This object holds the active or current invoice status rows.
  • FV_INVOICE_STATUSES_HIST — also referenced through a SYNONYM. This object holds superseded or historical status rows.

The UNION combines the two sources into a single result set. Notably, the historical branch maps INVOICE_HISTORY_ID to the INVOICE_STATUS_ID column alias, so both halves of the union present an identical column list. Consumers therefore see one logical record per status event, whether that event is currently effective or retained as history. Because the view depends on synonyms, resolution follows the standard APPS synonym chain to the underlying FV tables.

Key Columns

The view exposes twenty-four columns. The principal ones are:

  • CUSTOMER_TRX_ID — the transaction identifier linking the status row to the invoice in Receivables; this is the primary join key to AR invoice data.
  • STATUS — the invoice status value itself (for example, pending, approved, paid, or rejected, per FV status definitions).
  • START_DATE / END_DATE — the effective date range during which the status applied, enabling point-in-time and temporal queries.
  • INVOICE_STATUS_ID — the surrogate identifier; in the historical branch this is populated from INVOICE_HISTORY_ID.
  • COMMENTS — free-text annotation attached to the status event.
  • ORG_ID — the operating unit, supporting multi-org security and filtering.
  • SET_OF_BOOKS_ID — the ledger context for the status record.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard Oracle flexible attribute set for descriptive or extensibility use.

Common Use Cases and Queries

Typical scenarios include reconstructing an invoice's status at a given date, auditing all status changes for a transaction, and reporting current versus historical status counts by operating unit. A representative query for a single invoice's status timeline:

  • SELECT customer_trx_id, status, start_date, end_date, comments FROM apps.fv_inv_histstat_v WHERE customer_trx_id = :trx_id ORDER BY start_date;

To obtain the status effective as of a specific date:

  • SELECT customer_trx_id, status FROM apps.fv_inv_histstat_v WHERE customer_trx_id = :trx_id AND :as_of_date BETWEEN start_date AND NVL(end_date, :as_of_date);

For operating-unit-level distribution of statuses:

  • SELECT org_id, status, COUNT(*) FROM apps.fv_inv_histstat_v GROUP BY org_id, status;

Because the view unions live and historical records, callers should apply appropriate date-range predicates to avoid double counting when a status appears in both sources; the START_DATE and END_DATE columns support this filtering. Access is read-only, and standard APPS schema grants and multi-org security apply.