Search Results eliminations_id




Overview

FV_FACTS_VENDORS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the FV (Federal Financials) product family. Its documented purpose is to identify the eliminations department for vendors in support of the FACTS I process. FACTS I refers to the federal accounting and treasury reporting stream within Federal Financials, where inter-agency and intra-agency trading partner eliminations must be derived before consolidated reporting. The view provides a single, stable projection that maps a supplier to the department identifier used for eliminations, shielding downstream FACTS I logic from the physical location of the source attribute.

The view is particularly relevant to users who search for eliminations_id, since that column name does not exist as a discrete database column on the underlying vendor entity. It is a derived alias produced by the view itself. This is the central reason the view exists: it abstracts the configuration-driven mapping between a system parameter and one of the fifteen descriptive attributes on the vendor record.

Underlying Base Objects

The ETRM metadata documents exactly two referenced base objects: FV_SYSTEM_PARAMETERS (accessed through a synonym) and PO_VENDORS (itself a view). The join is a Cartesian-style cross join, since no WHERE clause links the two objects. FV_SYSTEM_PARAMETERS contributes the single governing control value, FACTSI_VENDOR_ATTRIBUTE, while PO_VENDORS contributes the vendor identity and the attribute columns.

The mapping is performed with a DECODE expression. FACTSI_VENDOR_ATTRIBUTE holds the name of the vendor attribute column to be treated as the eliminations identifier — for example, ATTRIBUTE1 through ATTRIBUTE15. The DECODE returns the corresponding PO_VENDORS attribute value, so a change in the system parameter immediately redirects which descriptive flexfield attribute supplies the eliminations department, without any modification to the FACTS I code or to the vendor records themselves.

Key Columns

  • VENDOR_ID — The unique identifier of the supplier from PO_VENDORS. It is the primary correlation key used when the FACTS I process joins this view back to vendor, invoice, or payment data.
  • ELIMINATIONS_ID — The derived eliminations department value. It is populated from whichever of the vendor ATTRIBUTE1 through ATTRIBUTE15 columns is nominated by FV_SYSTEM_PARAMETERS.FACTSI_VENDOR_ATTRIBUTE at runtime. Because the column is the output of a DECODE, its semantic content depends entirely on system configuration, and its value is null when the selected attribute is empty for a given vendor.

Because the view exposes only these two columns, it is intentionally narrow, serving strictly as an eliminations-lookup projection rather than a general vendor reporting source.

Common Use Cases and Queries

The principal use case is supplying the eliminations department to FACTS I elimination and consolidation logic. A typical retrieval for a single vendor follows.

  • Single-vendor lookup: SELECT vendor_id, eliminations_id FROM fv_facts_vendors_v WHERE vendor_id = :p_vendor_id; — returns the configured eliminations department for one supplier.
  • Full eliminations population: SELECT vendor_id, eliminations_id FROM fv_facts_vendors_v WHERE eliminations_id IS NOT NULL; — restricts output to vendors that carry a populated eliminations identifier, useful for reconciliation against elimination entries.
  • Join to vendor master: SELECT v.vendor_name, e.eliminations_id FROM po_vendors v, fv_facts_vendors_v e WHERE v.vendor_id = e.vendor_id ORDER BY v.vendor_name; — presents the eliminations department alongside the supplier name for review.
  • Configuration verification: Query FV_SYSTEM_PARAMETERS to confirm which FACTSI_VENDOR_ATTRIBUTE value is active, then compare the returned eliminations_id against the corresponding PO_VENDORS attribute — an effective diagnostic when eliminations values appear unexpected.

Administrators should note that changing the FACTSI_VENDOR_ATTRIBUTE parameter changes the meaning of every row returned by the view. Any extract or report consuming eliminations_id must therefore be revalidated after such a configuration change. The view itself carries no status-based filtering, so callers should apply any vendor or site-level qualifiers required by their reporting requirement.