Results for “inv_t”

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

Overview

APPS.FII_AR_OLTP_INV_V is an internal Oracle E-Business Suite view owned by the APPS schema and registered under FND Design Data as FII.FII_AR_OLTP_INV_V. It belongs to the Financial Intelligence (FII) product family, which supplies the extract and staging layer used by Oracle's financial analytics and data warehouse integrations. The view projects invoice-level receivables transaction data from the Oracle Receivables operational tables, enriched with the accounting period context, functional currency, and balances required for downstream reporting.

The view is documented as Oracle Internal Use Only. Oracle Corporation does not support direct access to application data through this object except from standard Oracle Applications programs. Consequently, customers and integrators should treat it as a supporting object for FII extracts rather than a supported public interface, and should prefer documented public views or APIs where a supported integration path exists.

Because the view exposes PERIOD_SET among its columns, it is a frequent hit for searches such as "period_set." The PERIOD_SET column identifies the accounting calendar associated with each row, allowing consumers to align invoice activity to the correct GL calendar and accounting period context.

Underlying Base Objects

The view's dependency list identifies the following referenced objects: AR_ADJUSTMENTS_ALL, AR_DISTRIBUTIONS_ALL, EDW_CURRENCY, EDW_LOCAL_INSTANCE, GL_SETS_OF_BOOKS, RA_CUSTOMER_TRX_ALL, RA_CUST_TRX_LINE_GL_DIST_ALL, and RA_CUST_TRX_TYPES_ALL. The view is not referenced by any other database object, confirming its role as a terminal extract source.

The principal driving table is RA_CUSTOMER_TRX_ALL, the Receivables transaction header table, joined to RA_CUST_TRX_TYPES_ALL for transaction type classification and to RA_CUST_TRX_LINE_GL_DIST_ALL and AR_DISTRIBUTIONS_ALL for the accounting distributions that carry the accounted amounts. AR_ADJUSTMENTS_ALL contributes adjustment activity associated with the transactions. GL_SETS_OF_BOOKS supplies the set of books (ledger) identifier and its associated period set and functional currency. EDW_CURRENCY and EDW_LOCAL_INSTANCE are warehouse-side reference objects used to normalize currency and instance identity across the extract.

Key Columns

• CUSTOMER_TRX_ID (NUMBER 15) — Identifier of the Receivables transaction; the primary link back to RA_CUSTOMER_TRX_ALL.
• INSTANCE_CODE (VARCHAR2 30) — Source instance identifier, used to distinguish data across multiple EBS instances feeding the warehouse.
• ORG_ID (NUMBER 15) — Operating unit identifier, the multi-org partitioning key for the row.
• SOB_ID (NUMBER 15) — Set of books (ledger) identifier from GL_SETS_OF_BOOKS.
• PERIOD_SET (VARCHAR2 15) — The accounting calendar/period set name associated with the ledger; the key column for period-set searches.
• PERIOD_TYPE (VARCHAR2 15) — The period type within the calendar (for example, monthly), qualifying PERIOD_SET.
• CALENDAR_DAY (DATE) — The calendar date attributed to the row.
• FUNCTIONAL_CURRENCY (VARCHAR2 15) — Functional currency of the ledger.
• INV_G and INV_B (NUMBER) — Invoice amounts in the ledger's functional currency, with the suffix convention distinguishing the accounting/functional measure from the entered or converted measure.

Common Use Cases and Queries

Typical uses are extract validation, reconciliation of receivables activity by ledger and calendar, and period-set-oriented analysis. A minimal projection follows the documented query text:

• SELECT CUSTOMER_TRX_ID, ORG_ID, SOB_ID, PERIOD_SET, PERIOD_TYPE, CALENDAR_DAY, FUNCTIONAL_CURRENCY, INV_G, INV_B FROM APPS.FII_AR_OLTP_INV_V;
• Filter by a specific calendar: ... WHERE PERIOD_SET = :p_period_set AND ORG_ID = :p_org_id;
• Aggregate by period: SELECT PERIOD_SET, PERIOD_TYPE, SUM(INV_G), SUM(INV_B) ... GROUP BY PERIOD_SET, PERIOD_TYPE;
• Join to GL_SETS_OF_BOOKS on SOB_ID to obtain ledger name and currency for cross-ledger reporting.

Because direct query access is restricted, these statements should be executed only within sanctioned Oracle Applications or warehouse processes, and never in place of supported AR reporting interfaces.