Search Results sales_order_source




Overview

FII_AR_TRX_DIST_FCV is a database view owned by the APPS schema within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. It belongs to the FII (Financial Intelligence) product family, which serves as the E-Business Suite's foundational data model for enterprise data warehousing, analytics, and business intelligence extraction. As indicated by the ETRM metadata, this view is characterized as an "internal view used for warehouse data extraction," meaning it is not intended for direct end-user reporting within the transactional application but rather serves as a curated source for ETL (Extract, Transform, Load) processes feeding the Oracle Business Intelligence Applications (OBIA) or comparable external analytical platforms.

The view is classified as a "FCV" (Financial Collection View) — a naming convention in FII that denotes a flattened, denormalized projection of Accounts Receivable transactional distribution data. Its purpose is to present Accounts Receivable invoice and credit memo distribution lines in a star-schema-friendly format, complete with pre-resolved foreign key surrogates (columns suffixed with _FK) that map dimension attributes to the FII warehouse dimension tables. This design removes the complexity of joins from downstream extraction logic and enforces conformed dimensionality across the AR subject area.

Underlying Base Objects

The ETRM metadata documents no explicit referenced base objects for this view, and the owner is listed as blank in the 12.2.2 catalog. In practice, FII collection views of this type are constructed over the AR transactional distribution tables — principally RA_CUSTOMER_TRX_LINES_ALL, RA_CUST_TRX_LINE_GL_DIST_ALL, RA_CUSTOMER_TRX_ALL, and related interface objects such as RA_INTERFACE_LINES_ALL. The embedded VIEW_TYPE and SEQ_ID columns, together with the literal 'NA_EDW' placeholders and TO_NUMBER(NULL) casts visible in the view text, are consistent with a UNION ALL or partitioned extraction pattern that reconciles multiple AR source streams into a single conformed result set.

Because the referenced base objects are undocumented in ETRM, DBAs should resolve dependencies directly through DBA_DEPENDENCIES or ALL_VIEWS to confirm lineage before modifying or replacing any underlying table.

Key Columns

The view exposes a broad column set organized into three logical groups:

Common Use Cases and Queries

This view is consumed almost exclusively by FII extraction programs and OBIA ETL mappings rather than by ad hoc reporting. Typical scenarios include populating the AR fact tables in the FII warehouse, reconciling AR revenue against General Ledger distributions, and performing customer, product, and sales-channel margin analysis.

A representative inspection query is:

SELECT INVOICE_NUMBER, AMT_T, GL_DATE_FK
FROM   APPS.FII_AR_TRX_DIST_FCV
WHERE  INSTANCE = :p_instance
AND    VIEW_TYPE = 'AR_TRX_DIST';

Because the view is internal and undocumented at the base-object level, direct querying should be limited to diagnostics and reconciliation. All production usage should proceed through the sanctioned FII extraction interfaces.