Results for “fv_inv_statuses_v”

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

Overview

FV_INV_STATUSES_V is a reporting view owned by the APPS schema within the FV – Federal Financials product of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its documented purpose is to store invoice status information while specifically including all late invoices. In practice, the view consolidates Accounts Receivable transaction data with customer master information and Federal Financials receivable type and lookup configuration, then restricts the result set to transactions that remain unpaid past their due date.

Because the view aggregates outstanding balances and derives a lateness metric at query time, it functions as a ready-made source for aging and delinquency reporting rather than as a transactional object. It exposes one row per customer transaction, grouped by organization, customer, and receivable type, making it suitable for dashboards, concurrent program data sources, and downstream extracts that need an unfiltered list of delinquent receivables.

The user search term "fv_finance_charge_controls" is directly relevant here: FV_FINANCE_CHARGE_CONTROLS is referenced inside the view definition as an exclusion filter, and therefore materially shapes which transactions appear in the results.

Underlying Base Objects

The view is defined over the following documented base objects:

• RA_CUSTOMER_TRX_ALL — the primary Accounts Receivable transaction header table, supplying transaction identifiers, numbers, bill-to customer, transaction type, and the CREATED_FROM value used for filtering.
• AR_PAYMENT_SCHEDULES_ALL — supplies due date and the remaining amount due, which drive the late-invoice criteria and aggregation.
• HZ_CUST_ACCOUNTS and HZ_PARTIES — provide the customer account number and party name.
• FV_REC_CUST_TRX_TYPES_ALL — Federal Financials extension of transaction types, keyed by ORG_ID and CUST_TRX_TYPE_ID.
• FV_RECEIVABLE_TYPES — maps transaction types to a receivable type identifier.
• FV_LOOKUP_CODES — a view supplying the receivable type description via LOOKUP_TYPE = 'RECEIVABLE_TYPE'.
• FV_FINANCE_CHARGE_CONTROLS — a synonym used in a NOT IN subquery against CHARGE_TYPE, excluding finance-charge-originated transactions from the output.
• FND_GLOBAL — the standard EBS package frequently associated with such views for organization and user context.

The joins enforce organization-level consistency between transactions and Federal Financials transaction types, ensuring only configured Federal receivable activity is reported.

Key Columns

• ORG_ID — operating unit identifier; the primary grouping dimension.
• CUSTOMER_ID, CUSTOMER_NAME, CUSTOMER_NUMBER — customer account identifier, party name, and account number from the trading community model.
• CUSTOMER_TRX_ID, TRX_NUMBER — the AR transaction identifier and its user-visible number.
• RECEIVABLE_TYPE_ID, DESCRIPTION — the Federal receivable type and its lookup description.
• AMOUNT_DUE_REMAINING — the sum of remaining amounts due across matching payment schedule lines.
• DAYS_LATE — computed as MIN(TRUNC(SYSDATE) - APS.DUE_DATE), the smallest number of days any installment on the transaction is past due.

Common Use Cases and Queries

Typical scenarios include federal receivables aging reports, delinquent invoice lists for collections follow-up, and reconciliation of outstanding balances by receivable type. A representative query listing the most delinquent federal receivables is:

SELECT org_id, customer_number, customer_name, trx_number, description, amount_due_remaining, days_late FROM apps.fv_inv_statuses_v WHERE days_late > 30 ORDER BY days_late DESC, amount_due_remaining DESC;

An aggregation by receivable type for a single operating unit:

SELECT description, COUNT(*) invoice_count, SUM(amount_due_remaining) total_due, MAX(days_late) max_days_late FROM apps.fv_inv_statuses_v WHERE org_id = :p_org_id GROUP BY description ORDER BY total_due DESC;

Because the exclusion of finance charge transactions depends on FV_FINANCE_CHARGE_CONTROLS, administrators should verify that table's CHARGE_TYPE entries are current; omissions there will cause finance-charge-created transactions to appear in late-invoice results.