Search Results currency_conversion_rate_type




Overview
Explore in AI Chat

Overview

APPS.POBV_MC_RECEIVING_TRANSACTIONS is a Business Intelligence System (BIS) view owned by the APPS schema and registered under the FND Design Data reference PO.POBV_MC_RECEIVING_TRANSACTIONS. It exposes receiving transaction information from the Oracle Purchasing module in the context of Multiple Reporting Currencies (MRC). MRC functionality allows an alternative reporting currency to be derived for a transaction based on the Set of Books, enabling organizations that maintain more than one set of books to report receiving activity in a currency other than the primary functional currency.

Because the view carries a VALID status and is defined at the APPS layer, it is intended for read-only reporting and integration consumption rather than for transactional data entry. Users searching for the CURRENCY_CONVERSION_RATE_TYPE attribute will find it here as an exposed column, making this view a convenient single source for rate-type information associated with receiving transactions across reporting sets of books.

Underlying Base Objects

The documented dependency for this view is the synonym APPS.RCV_TRANSACTIONS, which resolves to the base receiving transactions table in the Purchasing schema. The view is not referenced by any other database object, confirming that it is a terminal reporting construct: consumers query it directly, and it does not serve as a dependency for further views, packages, or procedures.

The view applies the MRC abstraction over RCV_TRANSACTIONS, joining set-of-books context to individual receipt and delivery records. In practice this means each row represents a receiving transaction as expressed for a particular reporting set of books, with the associated conversion rate attributes surfaced as separate columns. The design keeps the underlying transactional integrity of RCV_TRANSACTIONS intact while presenting a currency-translated reporting perspective.

Key Columns

  • SET_OF_BOOKS_ID — Identifies the reporting set of books in whose currency the transaction is being expressed. This is the primary discriminator for MRC reporting.
  • SET_OF_BOOKS_NAME — The descriptive name of the reporting set of books, provided for readable reporting output.
  • TRANSACTION_ID — The receiving transaction identifier, linking back to the underlying RCV_TRANSACTIONS record.
  • _LA:TRANSACTION_TYPE — A CHAR(76) column carrying the transaction type attribute, typically resolved through the applications language/attribute mechanism for descriptive reporting.
  • CURRENCY_CONVERSION_RATE_DATE — The date on which the currency conversion rate was effective for the transaction.
  • CURRENCY_CONVERSION_RATE — The numeric rate applied to convert the transaction into the reporting currency.
  • CURRENCY_CONVERSION_RATE_TYPE — A VARCHAR2(30) column identifying the rate type used (for example, the Oracle General Ledger rate type such as Spot, Corporate, or User-defined), which governs how the conversion is performed.
  • PO_UNIT_PRICE — The unit price of the item as recorded on the purchase order line associated with the receipt.

Common Use Cases and Queries

This view is typically used in MRC reporting, reconciliation of receiving activity across sets of books, and integration feeds that require converted receipt values. Analysts investigating how a specific conversion rate type was applied to receipts can filter directly on the rate-type column.

The following query lists receiving transactions for a given set of books together with their conversion rate attributes:

SELECT SET_OF_BOOKS_ID,
       SET_OF_BOOKS_NAME,
       TRANSACTION_ID,
       CURRENCY_CONVERSION_RATE_DATE,
       CURRENCY_CONVERSION_RATE,
       CURRENCY_CONVERSION_RATE_TYPE,
       PO_UNIT_PRICE
FROM   APPS.POBV_MC_RECEIVING_TRANSACTIONS
WHERE  SET_OF_BOOKS_ID = :p_set_of_books_id
ORDER  BY TRANSACTION_ID;

SELECT CURRENCY_CONVERSION_RATE_TYPE,
       COUNT(*) AS TXN_COUNT
FROM   APPS.POBV_MC_RECEIVING_TRANSACTIONS
GROUP  BY CURRENCY_CONVERSION_RATE_TYPE;

The first query supports detail drill-down for a reporting ledger; the second supports distribution analysis of rate types across receiving activity. Because the view is not referenced by other objects and is VALID, it can be safely incorporated into custom reports and extracts without impacting transactional processing.