Results for “po_unit_price”

50+ results




Overview
Explore in AI Chat

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

Overview

The APPS.POBV_MC_RECEIVING_TRANSACTIONS view is a Purchasing (PO) module reporting object that exposes multi-currency receiving transaction information in a business-user-friendly form. It joins receiving transaction currency conversion attributes with the corresponding set of books name and purchasing unit price, allowing reporting and integration consumers to reconcile receipt accounting entries against the ledger in which they were recorded. The view is defined with a WITH READ ONLY clause, confirming that it is intended strictly for query and extraction purposes and cannot be used as an update target. Its name prefix "POBV" follows the Oracle EBS convention for Purchasing Business Views, indicating the object is a curated, denormalized presentation layer rather than a base transactional entity.

The object carries a "Retrofitted" description in the ETRM metadata, indicating it was adapted or re-pointed as part of an upgrade or architectural change while preserving its external contract for downstream consumers. The view is marked VALID in the APPS schema and is available in both Oracle EBS 12.1.1 and 12.2.2 environments, making it a stable reference for multi-currency receipt reporting across releases.

Underlying Base Objects

The documented view text is defined over three objects:

  • RCV_MC_TRANSACTIONS — the primary source of multi-currency conversion attributes for receiving transactions (set of books, conversion date, rate, and rate type).
  • GL_SETS_OF_BOOKS — the ledger definition table, joined on SET_OF_BOOKS_ID to resolve the human-readable ledger name.
  • RCV_TRANSACTIONS — the core receiving transaction table, joined on TRANSACTION_ID to supply the purchasing unit price and transaction type context.

The ETRM documented metadata lists RCV_TRANSACTIONS as a referenced base object (exposed in the APPS schema via synonym). The joins are all equality joins on TRANSACTION_ID and SET_OF_BOOKS_ID, producing one row per receiving transaction per set of books context represented in RCV_MC_TRANSACTIONS.

Key Columns

  • SET_OF_BOOKS_ID / SET_OF_BOOKS_NAME — identifier and descriptive name of the ledger associated with the currency conversion.
  • TRANSACTION_ID — the receiving transaction identifier, linking back to RCV_TRANSACTIONS.
  • "_LA:TRANSACTION_TYPE" — a Descriptive Flexfield (DFF) style attribute sourced from PO_LOOKUP_CODES (RCV TRANSACTION TYPE), exposed as a displayed field for reporting the receipt transaction type. The quoted, colon-prefixed name reflects the Oracle Application Framework flexfield display convention and must be referenced with double quotes in SQL.
  • CURRENCY_CONVERSION_DATE (CURRENCY_CONVERSION_RATE_DATE) — the date on which the currency conversion rate was effective, the key column matching the user search term "currency_conversion_rate_date."
  • CURRENCY_CONVERSION_RATE — the exchange rate applied to the receiving transaction in the associated ledger.
  • CURRENCY_CONVERSION_TYPE — the rate type (for example, Corporate, Spot, User-defined) used to derive the conversion rate.
  • PO_UNIT_PRICE — the purchasing unit price from the receiving transaction, useful for value comparisons in the target currency.

Common Use Cases and Queries

Typical consumers use this view for multi-currency receipt analysis, ledger reconciliation, and exchange rate audit reporting. A representative query filtering on the conversion rate date is:

  • SELECT set_of_books_name, transaction_id, currency_conversion_rate_date, currency_conversion_rate, currency_conversion_type, po_unit_price FROM apps.pobv_mc_receiving_transactions WHERE currency_conversion_rate_date BETWEEN :p_from AND :p_to ORDER BY currency_conversion_rate_date;
  • Audit of missing or zero rates: SELECT transaction_id, currency_conversion_rate FROM apps.pobv_mc_receiving_transactions WHERE currency_conversion_rate IS NULL OR currency_conversion_rate = 0;
  • Ledger-level rate comparison: group by SET_OF_BOOKS_NAME and CURRENCY_CONVERSION_TYPE to detect rate-type drift across receipts.

Because the view is read-only and its joins are inner joins, transactions without a matching RCV_MC_TRANSACTIONS row are excluded; queries requiring the full receipt population should union or left-join against RCV_TRANSACTIONS directly.