Search Results source_doc_unit_of_measure




Overview
Explore in AI Chat

Overview

RCV_RECEIVING_ACCT_DISTR_V is an APPS-owned view in the Oracle E-Business Suite Purchasing (PO) module, documented as VALID in release 12.1.1 and 12.2.2. Its ETRM description reads "10SC ONLY - Retrofitted - Retrofitted," indicating the object originated as a custom retrofit object for a 10SC (Oracle Contracts/ Services Procurement) implementation and was subsequently carried forward into later releases without redesign. The view consolidates receiving accounting distribution data drawn from purchasing, receiving, and general ledger sources into a single reporting-friendly projection.

Its role is to expose receipt-driven accounting distributions and the associated transactional attributes — quantity, unit of measure, price, currency conversion, and destination — without requiring the consumer to join the underlying receiving and purchasing tables directly. Because it is a view, it carries no independent storage; all values are resolved from the base objects at query time.

Underlying Base Objects

The documented base objects are:

  • RCV_TRANSACTIONS (synonym) — the primary receiving transaction row; supplies transaction ID, subinventory, locator, organization, WIP references, and source document UOM.
  • RCV_RECEIVING_SUB_LEDGER (synonym) — the accounting sub-ledger entries; supplies accounting date, currency conversion fields, and source document quantity.
  • RCV_ACCOUNTING_EVENTS (synonym) — provides corrected/override values for quantity, UOM, price, and conversion details, applied through NVL() precedence.
  • RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES — receipt number, shipment number, packing slip, vendor, item revision, and item description.
  • PO_HEADERS, PO_LINES, and PO_REQUISITION_LINES — PO number, line number, item, and requisition line number.
  • PO_LOOKUP_CODES (view) — resolves destination type and transaction type display values.
  • GL_CODE_COMBINATIONS (synonym) — the accounting flexfield code combination ID.
  • HR_LOCATIONS (view) — deliver-to location code.
  • Package calls to FND_GLOBAL and HR_GENERAL supply session/organization context.

Key Columns

The view exposes several categories of columns. Identity and sourcing columns include PO_NUMBER, RECEIPT_NUMBER, SHIPMENT_NUMBER, TRANSACTION_ID, LINE_NUMBER, and REQUISITION_LINE_NUMBER. Accounting-oriented columns include CODE_COMBINATION_ID, ACCOUNTING_DATE, and the currency triad CURRENCY_CODE, CURRENCY_CONVERSION_TYPE, CURRENCY_CONVERSION_DATE, and CURRENCY_CONVERSION_RATE, each resolved with NVL(RAE.*, RCT/RRSL.*) precedence.

Quantity and pricing are represented by QUANTITY, PRIMARY_QUANTITY, PRIMARY_UOM, and PO_UNIT_PRICE. The column directly relevant to the user's search, SOURCE_DOC_UNIT_OF_MEASURE, is projected straight from RCV_TRANSACTIONS.SOURCE_DOC_UNIT_OF_MEASURE, while SOURCE_DOC_QUANTITY uses a DECODE against the sub-ledger's value. Physical and locational columns include ORGANIZATION_ID, SUBINVENTORY, LOCATOR_ID, DELIVER_TO_LOCATION, and DEPARTMENT_CODE. WIP integration columns (WIP_ENTITY_ID, WIP_LINE_ID, WIP_REPETITIVE_SCHEDULE_ID, and operation/resource sequence numbers) support manufacturing-related receipts. Descriptive lookups include DESTINATION_TYPE and TRANSACTION_TYPE.

Common Use Cases and Queries

Typical uses include reconciling receipt accruals to the general ledger, auditing source document quantities and units of measure against primary UOMs, and feeding downstream reporting or interface programs. A representative query filtering on the column of interest:

  • SELECT po_number, receipt_number, transaction_id, source_doc_unit_of_measure, source_doc_quantity, primary_uom, quantity, accounting_date FROM apps.rcv_receiving_acct_distr_v WHERE source_doc_unit_of_measure IS NOT NULL AND accounting_date BETWEEN :p_start AND :p_end;
  • Joining to GL_CODE_COMBINATIONS on CODE_COMBINATION_ID to translate distributions into accounting flexfield segments for GL reconciliation.
  • Aggregating QUANTITY and PO_UNIT_PRICE by PO_NUMBER and CURRENCY_CODE to validate receipt valuation.

Because the object is a view over volatile transactional tables, queries should be constrained by organization and accounting period to avoid full scans of the receiving transaction history.