Results for “calendar_day”

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

Overview

FII_AR_OLTP_CASH_V is an internal Oracle EBS view owned by the APPS schema and classified under the FII (Financial Intelligence) product family. It is not an end-user reporting object; the ETRM metadata explicitly states that it exists to support the Operations Indicators Portlet, a dashboard component delivered as part of the Financial Intelligence application stack. The view distills cash receipt activity from Oracle Receivables into a compact, portlet-friendly result set that presents one row per cash receipt, carrying converted and functional-currency receipt amounts alongside calendar and currency context.

The view is a key integration point between the transactional subledger data (AR cash receipts, receipt history, and accounting distributions) and the analytical presentation layer used by Financial Intelligence dashboards. Because the view is internal, Oracle does not document a supported public interface for it and its definition may change between point releases. In 12.1.1 and 12.2.2 the view is present and valid in the seeded APPS schema.

Underlying Base Objects

Though the 12.2.2 ETRM metadata records no referenced base objects, the view text is available and shows the tables joined. The view is defined over five seeded objects:

• AR_CASH_RECEIPT_HISTORY_ALL — joined twice. One alias isolates the first posted record (FIRST_POSTED_RECORD_FLAG = 'Y'); the second isolates the current record (CURRENT_RECORD_FLAG = 'Y'). This dual join is what allows the view to report both the original posting date and the currently effective receipt state.
• AR_CASH_RECEIPTS_ALL — the receipt header, supplying organization, set of books, customer, currency, receipt date, exchange rate type, status, and confirmation flag.
• AR_DISTRIBUTIONS_ALL — supplies the accounting amounts, joined on SOURCE_ID = CASH_RECEIPT_HISTORY_ID with SOURCE_TABLE = 'CRH'.
• GL_SETS_OF_BOOKS — supplies the period set name, accounted period type, and functional currency code of the ledger.
• EDW_LOCAL_INSTANCE — a Financial Intelligence infrastructure table providing the instance code used to scope data to a local installation.

The underlying tables are partitioned transaction tables, which explains the deliberate restriction to the first posted and current history records — it prevents distribution-level fan-out from inflating the receipt count while still capturing the authoritative accounting entries.

Key Columns

• CASH_RECEIPT_ID — primary identifier of the receipt; the grain of the view.
• INSTANCE_CODE — identifier of the local EBS instance, sourced from EDW_LOCAL_INSTANCE.
• ORG_ID — operating unit context of the receipt.
• SOB_ID / PERIOD_SET / PERIOD_TYPE — the set of books, its period set name, and accounted period type, used to align receipts to the correct accounting calendar.
• CUSTOMER_ID — pay-from customer; defaulted to -1 when null, producing an "unknown/on-account" bucket rather than a blank.
• CALENDAR_DAY — the GL date of the first posted receipt history record.
• FUNCTIONAL_CURRENCY — ledger currency derived from GL_SETS_OF_BOOKS.
• CASH_G — receipt amount converted into the functional (ledger) currency via EDW_CURRENCY.CONVERT_GLOBAL_AMOUNT, using the receipt's exchange rate type and receipt date.
• CASH_B — the accounted amount in ledger currency, computed from AR_DISTRIBUTIONS_ALL as ACCTD_AMOUNT_DR minus ACCTD_AMOUNT_CR.

Common Use Cases and Queries

The view is typically queried by the Financial Intelligence portlet infrastructure rather than by end users. Analysts writing custom portlets or validating dashboard numbers may query it directly. Because the view filters out unconfirmed receipts and receipts with status NSF, REV, or STOP, it naturally represents cash that was actually collected.

• Daily cash collections by operating unit: SELECT org_id, calendar_day, SUM(cash_g) FROM apps.fii_ar_oltp_cash_v GROUP BY org_id, calendar_day;
• Receipt count and value per functional currency: SELECT functional_currency, COUNT(*), SUM(cash_b) FROM apps.fii_ar_oltp_cash_v GROUP BY functional_currency;
• Comparing converted versus accounted amounts to detect exchange-rate variance: SELECT cash_receipt_id, cash_g - cash_b diff FROM apps.fii_ar_oltp_cash_v WHERE cash_g <> cash_b;
• Reconciling a portlet figure back to AR_CASH_RECEIPTS_ALL and AR_DISTRIBUTIONS_ALL for a specific receipt ID.

Because the view is internal and unsupported, direct dependencies should be limited to diagnostic and reconciliation work, and any production logic should be re-expressed against the documented AR base tables.