Results for “invoice_date”

38 results




Overview
Explore in AI Chat

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

Overview

FII_AR_REC_FCV is an internal Oracle E-Business Suite view owned by the APPS schema and delivered as part of the Financial Intelligence (FII) product family. Its documented purpose is to support the Operations Indicators Portlet, a dashboard component that surfaces key receivables and accounting metrics to business users. The view consolidates receivable activity from two distinct sources within Oracle Receivables: revenue-recognition distributions captured on customer transaction lines and manual or automatic adjustments applied against transactions. By exposing a normalized set of dimensions — ledger, operating unit, customer, transaction date, accounting date, currency, and accounted amount — the view functions as a reporting-friendly projection over core AR and GL tables rather than as a transactional object in its own right.

The view's status is VALID, and it is present in both the 12.1.1 and 12.2.2 environments addressed by this reference. Because it is an internal object, Oracle does not guarantee its structure across patches and releases, and direct modification is not supported.

Underlying Base Objects

The ETRM metadata for 12.2.2 documents no referenced base objects, but the supplied view text reveals the actual dependencies. The view is a UNION ALL of two branches:

EDW_LOCAL_INSTANCE supplies the instance code used to build globally unique dimension keys, and GL_SETS_OF_BOOKS supplies the ledger currency. The outer joins on RA_CUST_TRX_TYPES_ALL ensure transactions without a type definition are still included.

Key Columns

The view exposes eleven projected columns. CUSTOMER_TRX_ID identifies the transaction; SET_OF_BOOKS_ID identifies the ledger. SET_OF_BOOKS_FK concatenates the ledger identifier with the instance code, producing a ledger surrogate key suitable for warehouse loading. CUSTOMER_FK similarly concatenates the bill-to customer identifier with the instance code, defaulting to 'NA_EDW' when no customer is present. ORG_FK combines ORG_ID with the instance code and resolves the operating unit dimension. GL_DATE carries the full accounting date, while GL_DATE_FILTER applies TRUNC to support date-level grouping. INVOICE and TRX_DATE support transaction-level drilldown. INSTANCE_CODE, CURRENCY_CODE, and ACCTD_AMOUNT round out the projection.

Within the second UNION branch, ACCTD_AMOUNT_CR from AR_DISTRIBUTIONS_ALL is subtracted from ACCTD_AMOUNT_DR. This is the column most relevant to searches for "acctd_amount_cr" — the credit accounted amount is not exposed directly but is consumed internally to derive net ACCTD_AMOUNT.

Common Use Cases and Queries

Typical usage centers on receivables indicator reporting: receivable balances by ledger, adjustment volumes, and period-over-period activity trends.

  • Accounted receivable activity by ledger and currency:
    SELECT set_of_books_fk, currency_code, SUM(acctd_amount) FROM apps.fii_ar_rec_fcv WHERE gl_date BETWEEN :start_date AND :end_date GROUP BY set_of_books_fk, currency_code;
  • Adjustment impact per operating unit, using the negative ACCTD_AMOUNT values produced by the second UNION branch.
  • Customer-level drilldown using CUSTOMER_FK joined back to HZ_CUST_ACCOUNTS or RA_CUSTOMER_TRX_ALL.

Because the view is internal and consumes RA_CUST_TRX_LINE_GL_DIST_ALL and AR_DISTRIBUTIONS_ALL, queries should be date-bounded and ledger-filtered to avoid full scans across large distribution tables.