Search Results salesrep_fk

Overview

FII_AR_E_REVENUE_FCV is a collection view within the Oracle E-Business Suite Financial Intelligence (FII) product family. It serves as the staging and extraction layer for the FII_AR_E_REVENUE_F fact, which stores Accounts Receivable revenue transaction data used by the Financial Intelligence data warehouse and analytical reporting stack. In EBS 12.1.1 and 12.2.2, FII objects such as this view are typically consumed by ETL processes that move data from the transactional EBS schema into the FII reporting schema, where revenue metrics are aggregated and analyzed across dimensions such as customer, item, sales channel, and GL period.

The view exposes a wide projection of revenue attributes — identifiers, foreign keys to conformed dimensions, transaction amounts, quantity metrics, and descriptive text fields. Because it is a collection view rather than a transactional entity view, its purpose is to present a consistent, denormalized row shape that downstream collection programs can load reliably.

Underlying Base Objects

The documented metadata for this object in ETRM 12.2.2 does not list referenced base objects, and the implementation note states "Not implemented in this database" for the documented environment. This indicates that the view is a delivered FII object whose definition is supplied by the Financial Intelligence product, but whose underlying tables reside in the FII/AR staging schema rather than in a standard transactional schema. In practice, FII collection views of this naming convention (suffix _FCV for fact collection view) are defined over the corresponding _F fact table and related staging tables populated by the FII extraction routines.

Key Columns

• SEQ_ID / BATCH_ID: Surrogate and batch identifiers used to track load runs.
• REVENUE_PK: Primary key for the revenue fact record.
• AR_DOC_NUM_FK, AR_TRX_TYPE_FK, TRX_NUMBER, TRX_CURRENCY_FK: Accounts Receivable transaction identity and currency context.
• BILL_TO_CUSTOMER_FK, SHIP_TO_CUSTOMER_FK, SOLD_TO_CUSTOMER_FK (and associated site FKs): Conformed customer and site dimensions.
• ITEM_FK, INVENTORY_ITEM_ID, ORGANIZATION_FK, UOM_FK, UOM_CONV_RATE: Item, inventory organization, and unit-of-measure attributes.
• GL_PERIOD_FK, GL_SET_OF_BOOKS_FK, SET_OF_BOOKS_ID, GL_POSTED_DATE, INVOICE_DATE, EXCHANGE_DATE: Accounting period, ledger, and date context.
• AMT_B, AMT_G, AMT_T, PROD_AMT_B, PROD_AMT_G, PROD_AMT_T: Entered, accounted (functional), and translated monetary amounts.
• LINE_QTY_INVOICED_NC, LINE_QTY_CREDITED_NC, LINE_QTY_ORDERED_NC and their PROD_ counterparts: Quantity measures for invoiced, credited, and ordered units.
• UNIT_SELLING_PRICE, UNIT_STAN_PRICE, EXCHANGE_RATE: Pricing and currency conversion values.
• JE_DESCRIPTION, JE_LINE_DESC, JE_NAME: Journal entry descriptive text — these fields directly support the "je_description" search term and allow the GL journal description, journal line description, and journal name associated with a revenue line to be reported alongside the AR transaction data.
• ACCOUNT_CLASS, LINE_TYPE, REASON_CODE, DOC_REASON_CODE, CREATED_FROM: Classification and source attributes.
• GL_SEG-derived columns: The view text applies DECODE/RTRIM/SUBSTR logic to split a concatenated GL segment string into individual accounting flexfield segments, with a special literal handling for the NA_EDW value.

Common Use Cases and Queries

Typical usage involves joining the view to FII dimension views for revenue analytics, or filtering by journal description text. For example, to retrieve revenue lines with their GL journal descriptions for a given ledger:

SELECT TRX_NUMBER, INVOICE_DATE, JE_NAME, JE_DESCRIPTION,
       JE_LINE_DESC, AMT_B, AMT_G, AMT_T, LINE_QTY_INVOICED_NC
FROM   FII_AR_E_REVENUE_FCV
WHERE  SET_OF_BOOKS_ID = :p_sob_id
AND    TRUNC(INVOICE_DATE) BETWEEN :p_start AND :p_end
ORDER  BY INVOICE_DATE;

A second common pattern searches for specific journal text, matching the user's "je_description" interest:

SELECT TRX_NUMBER, AR_DOC_NUM_FK, JE_DESCRIPTION, LINE_TYPE,
       LINE_QTY_INVOICED_NC, AMT_T
FROM   FII_AR_E_REVENUE_FCV
WHERE  UPPER(JE_DESCRIPTION) LIKE UPPER('%' || :p_keyword || '%');

Because the object is a collection view intended for bulk FII loads, queries are usually restricted by batch, period, or ledger to limit scan volume. Direct user-facing reporting generally occurs after the underlying fact has been aggregated into FII star-schema views.