Results for “fv_inv_statcust_v”

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

Overview

The view FV_INV_STATCUST_V is an APPS-owned, VALID database view delivered within the Federal Financials (FV) product family of Oracle E-Business Suite, applicable to both release 12.1.1 and 12.2.2. Its documented purpose is to store information used for the "invoice status find" function, which is the inquiry and search mechanism by which users locate invoices and their associated receivables status within the federal receivables and billing flow. Rather than presenting a single normalized table, the view consolidates customer identity, organization context, and a decoded receivable type description into a single de-normalized result set, making it suitable for direct consumption by reporting tools, Oracle Forms LOV queries, and integration extracts. Because the view resolves the receivable type to a human-readable description through a lookup join, consumers do not need to replicate the decode logic themselves, which reduces inconsistency across custom reports built on the FV schema. The view is read-only in practical terms and is exposed under the APPS schema, so it is normally accessed through a custom synonym or by direct qualified reference.

Underlying Base Objects

The view text joins three base objects. FV_INV_STATUSES_V is the primary driver, supplying organization, customer, and receivable type identifiers, and is itself a view over the invoice status data. FV_RECEIVABLE_TYPES, documented as a synonym in the ETRM metadata, provides the receivable type definition and is joined on RECEIVABLE_TYPE_ID. FV_LOOKUP_CODES, also documented as a view, supplies the descriptive text; the join matches FV_RECEIVABLE_TYPES.RECEIVABLE_TYPE to FV_LOOKUP_CODES.LOOKUP_CODE, constrained to LOOKUP_TYPE = 'RECEIVABLE_TYPE'. The documented reference list also includes FND_GLOBAL as a package, which indicates the view depends on session-level context such as organization or user identifiers resolved at runtime. A SELECT DISTINCT is applied across the projection, eliminating duplicate rows that arise when the same customer and receivable type combination appears more than once in the underlying status view.

Key Columns

• ORG_ID — operating unit identifier, enabling multi-organization filtering.
• CUSTOMER_ID — internal surrogate key for the customer account.
• CUSTOMER_NAME — the customer name as held in the receivables source data.
• CUSTOMER_NUMBER — the customer account number used for user-facing search and display.
• RECEIVABLE_TYPE_ID — the numeric identifier linking to the receivable type definition.
• DESCRIPTION — the decoded receivable type description obtained from FV_LOOKUP_CODES.

The DESCRIPTION column is the element most directly associated with the user's search term, "receivable_type," since it expresses the receivable type in business language rather than as an identifier.

Common Use Cases and Queries

The most frequent use is populating a receivable type list of values on an invoice status inquiry form, or supplying a report parameter that filters invoices by type. A second common use is data extraction for reconciliation or analytics, where the decoded description is required alongside customer and organization attributes.

A representative query retrieves all receivable types for a given customer within an operating unit:

• SELECT customer_number, customer_name, receivable_type_id, description FROM fv_inv_statcust_v WHERE org_id = :p_org_id AND customer_id = :p_customer_id ORDER BY description;

To enumerate the distinct receivable types available across an organization, useful when validating lookup configuration, a caller can select DISTINCT receivable_type_id, description filtered by ORG_ID. Because the view joins through FV_LOOKUP_CODES, any receivable type that lacks a matching active lookup code entry will not appear, so completeness checks on the lookup configuration should be performed separately when reconciling counts against FV_RECEIVABLE_TYPES.