Search Results cash_b

Overview

The view APPS.FII_AR_OLTP_CASH_V is an Oracle E-Business Suite internal reporting view owned by the APPS schema and registered under the FND Design Data identifier FII.FII_AR_OLTP_CASH_V. Its status is VALID, and its view type is classified as Internal. It is part of the Oracle Financial Intelligence (FII) layer of objects that expose Accounts Receivable cash receipt activity in a flattened, column-oriented form suitable for downstream analytics, extraction, and integration into external reporting or data warehouse pipelines.

The view is not user-facing in the conventional EBS sense. The ETRM metadata carries the standard warning that access to Oracle applications data through this object is restricted to standard Oracle Applications programs and is not supported directly by Oracle Corporation. This constraint matters operationally: any report, concurrent program, or ETL job that references FII_AR_OLTP_CASH_V should be treated as an Oracle-internal dependency rather than a documented public interface.

The name reflects its purpose. The "OLTP" token indicates the view sits close to the transactional cash receipt tables rather than against a pre-aggregated summary, while the "CASH" token and the presence of CASH_G and CASH_B measures indicate it delivers cash amounts keyed by functional currency, period, and organization. The user query "cash_b" corresponds directly to one of the view's exposed numeric columns.

Underlying Base Objects

Per the documented dependency information, APPS.FII_AR_OLTP_CASH_V is defined over the following objects:

• AR_CASH_RECEIPTS_ALL — the core Accounts Receivables cash receipt header table, providing CASH_RECEIPT_ID and receipt-level attributes.
• AR_CASH_RECEIPT_HISTORY_ALL — cash receipt history records, typically used to derive receipt state, timing, and posting-related attributes.
• AR_DISTRIBUTIONS_ALL — receipt distribution lines, the source of accounting amounts and account assignments associated with each receipt.
• GL_SETS_OF_BOOKS — the General Ledger set of books definition, supplying SOB_ID and functional currency context and linking the ledger to the reporting periods used by the view.
• EDW_CURRENCY — a currency reference object supporting currency-code resolution and conversion context.
• EDW_LOCAL_INSTANCE — a local instance reference used by the EDW/FII framework to identify the source instance.

The view is not referenced by any other database object, which confirms it is a terminal reporting surface rather than an intermediate construct consumed by further packaged logic. From an EBS 12.1.1 and 12.2.2 perspective, the underlying AR tables are consistent across both releases, though ledger-based data model changes in 12.2.x (GL ledger and ledger set terminology replacing set of books) should be considered when interpreting SOB_ID.

Key Columns

• CASH_RECEIPT_ID (NUMBER, length 15) — primary identifier of the cash receipt from AR_CASH_RECEIPTS_ALL; the core join key.
• INSTANCE_CODE (VARCHAR2, 30) — identifies the source instance, sourced through the EDW local instance framework.
• ORG_ID (NUMBER, 15) — Organization identifier, the operational unit or business unit under which the receipt was recorded.
• SOB_ID (NUMBER, 15) — Set of books identifier linked to GL_SETS_OF_BOOKS; determines the ledger context.
• CUSTOMER_ID (NUMBER) — the customer or payer associated with the receipt.
• PERIOD_SET, PERIOD_TYPE, CALENDAR_DAY — the accounting calendar context: period set name, period type (for example, month), and the specific calendar date used for time-based reporting.
• FUNCTIONAL_CURRENCY (VARCHAR2, 15) — the functional currency of the ledger, resolved via GL_SETS_OF_BOOKS and EDW_CURRENCY.
• CASH_G (NUMBER) — a cash amount measure, typically the gross or general ledger-facing cash value.
• CASH_B (NUMBER) — the second cash amount measure, commonly the base or functional-currency equivalent amount. This is the column users searching on "cash_b" are targeting.

Common Use Cases and Queries

The view is typically used for cash receipt analysis by organization, ledger, customer, and accounting period, projecting CASH_G and CASH_B into currency-consistent reporting. Because Oracle restricts supported access, these queries should be confined to controlled reporting or ETL layers, not ad-hoc end-user tooling.

To retrieve cash amounts by period and organization, the following pattern applies:

• SELECT org_id, sob_id, functional_currency, period_set, period_type, calendar_day, SUM(cash_g) cash_gross, SUM(cash_b) cash_base FROM apps.fii_ar_oltp_cash_v WHERE calendar_day BETWEEN :start_date AND :end_date GROUP BY org_id, sob_id, functional_currency, period_set, period_type, calendar_day;

To analyze receipt detail for a specific customer:

• SELECT cash_receipt_id, customer_id, org_id, functional_currency, cash_g, cash_b FROM apps.fii_ar_oltp_cash_v WHERE customer_id = :customer_id ORDER BY calendar_day;

To reconcile base and gross cash amounts by ledger:

• SELECT sob_id, SUM(cash_g) - SUM(cash_b) AS variance FROM apps.fii_ar_oltp_cash_v GROUP BY sob_id HAVING SUM(cash_g) - SUM(cash_b) <> 0;

These scenarios reflect the view's design role: a low-level, transactional-grain cash receipt projection keyed by organization, ledger, customer, and accounting calendar, suitable for downstream aggregation and variance review across Oracle EBS 12.1.1 and 12.2.2 environments.