Results for “curr_code”

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

Overview

FII_BIS_FIIARTR1_V is an internal Oracle E-Business Suite view that belongs to the FII (Financial Intelligence) product family, identified in EBS 12.1.1 and 12.2.2 documentation as Obsolete. Its documented purpose is to serve as the data source for the AR Collection Indicators Turnover Drill Down PM Viewer Report, a Business Intelligence System (BIS) style extract that feeds a presentation-layer viewer with receivable turnover detail.

The view returns a single, denormalized result set in which each row represents a receivable payment schedule line (an invoice, debit memo, deposit, or chargeback) enriched with customer, site, ledger, and GL period context. It is not an end-user-facing object; it is an implementation artifact deployed only when the associated Financial Intelligence reporting package was installed. The ETRM record explicitly notes that the view is not implemented in this database, so in most current 12.1.1 and 12.2.2 environments the object does not exist and queries against it will raise ORA-00942.

The user search term curr_code maps directly to the CURR_CODE column, which is the aliased form of PS.INVOICE_CURRENCY_CODE from AR_PAYMENT_SCHEDULES_ALL. This column identifies the transaction currency in which the receivable amount is denominated, and it is the value most commonly used to break turnover figures out by currency in the drill-down report.

Underlying Base Objects

The ETRM metadata documents no formal base-object dependencies, but the view text itself discloses the complete FROM clause. The view is defined over the following Oracle EBS tables and views:

• AR_PAYMENT_SCHEDULES_ALL (aliased PS) — the driving table, supplying transaction amounts, currency, GL dates, customer identifiers, and payment class.
• RA_CUSTOMER_TRX_ALL (TRX) — supplies the transaction header and set of books linkage.
• RA_CUSTOMERS (CUST) — supplies the customer name.
• RA_SITE_USES_ALL (SITE) — supplies the customer site location.
• GL_SETS_OF_BOOKS (GSOB) — supplies the ledger, period set name, and accounted period type.
• GL_PERIODS (GP) — supplies the period start and year-start dates.
• GL_DATE_PERIOD_MAP (PD) — supplies the accounting date that resolves a GL date to a period.

The joins are conventional: payment schedules to transactions on CUSTOMER_TRX_ID, transactions to ledgers on SET_OF_BOOKS_ID, payment schedules to customers on CUSTOMER_ID, payment schedules to sites on CUSTOMER_SITE_USE_ID, and the GL tables on PERIOD_SET_NAME and PERIOD_NAME. Filter conditions restrict rows to CLASS IN ('INV','DEP','DM','CB'), exclude the placeholder schedule PAYMENT_SCHEDULE_ID = -1, and require GL_DATE_CLOSED to fall after the GL year start date.

Key Columns

• REPORT_NAME — literal 'BIS_FIIARTR1', used by the viewer to identify the source report.
• ORG_ID — operating unit identifier from the payment schedule.
• SET_OF_BOOKS_ID — ledger identifier.
• GL_DATE, START_DATE, REPORT_DATE — the GL date, the GL year start date, and the mapped accounting date, providing the period context for turnover aging.
• CUSTOMER_ID, CUSTOMER_NAME, LOCATION — customer and site identity for drill-down grouping.
• TRX_NUM — the transaction number.
• CURR_CODE — the invoice currency code (source of the user's search term); the currency in which ORIG_AMT is expressed.
• ORIG_AMT — AMOUNT_DUE_ORIGINAL, the original amount due in transaction currency.
• FUNC_AMT — AMOUNT_DUE_ORIGINAL * NVL(EXCHANGE_RATE, 1), the functional-currency equivalent, defaulting to a rate of 1 when no rate is stored.

Common Use Cases and Queries

Because the view is obsolete and typically absent, its practical use is limited to historical Financial Intelligence implementations, migration analysis, and reverse-engineering of the BIS turnover report. Where present, it supports currency-level turnover drill-down and reconciliation of transaction-currency versus functional-currency receivable balances.

A representative query filtering by currency:

• SELECT customer_name, trx_num, curr_code, orig_amt, func_amt FROM fii_bis_fiiartr1_v WHERE curr_code = 'USD' ORDER BY customer_name, trx_num;

An aggregation by currency and ledger for turnover reporting:

• SELECT curr_code, set_of_books_id, SUM(orig_amt) orig_total, SUM(func_amt) func_total FROM fii_bis_fiiartr1_v GROUP BY curr_code, set_of_books_id;

In supported environments, equivalent data is obtained directly from AR_PAYMENT_SCHEDULES_ALL joined to RA_CUSTOMER_TRX_ALL and RA_CUSTOMERS, using INVOICE_CURRENCY_CODE in place of CURR_CODE. This direct-table approach is recommended for any new development, since the FII view is neither implemented nor supported in 12.1.1 or 12.2.2.