Results for “pobv_receiving_transactions”

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

Overview

POBV_RECEIVING_TRANSACTIONS is an APPS-owned database view in the Oracle E-Business Suite Purchasing (PO) module. It is a "Business View" (denoted by the POBV prefix) that presents receiving transaction data for use by the Oracle Application Framework (OAF) and Business Components for Java (BC4J) business components, and for the Oracle EBS Attachments/descriptive flexfield logic. The view is retrofitted, meaning it was re-established against the current RCV schema to preserve backward compatibility for the applications that reference it. It is validated and available in both 12.1.1 and 12.2.2.

The view's role is to expose a denormalized, display-ready projection of the receiving transaction entity. Its defining characteristic is the pervasive use of the _LA:...:PO_LOOKUP_CODES:...:DISPLAYED_FIELD pseudo-column notation, which the EBS business component layer interprets to render translated lookup meanings instead of raw codes. This makes the view suitable for user-facing inquiry screens and reporting rather than for set-based batch processing.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, the view is defined over two base objects:

• RCV_TRANSACTIONS (referenced through a SYNONYM) — the core receiving transaction table, aliased as RT in the view text. It supplies the overwhelming majority of the projected columns.
• MTL_TRANSACTION_REASONS (referenced through a SYNONYM) — aliased as RE, joined to supply the REASON_NAME column.

The join is effectively a left outer association on the reason identifier, so that receipts without an associated reason still appear with a null reason name. Because the view is a thin projection over RCV_TRANSACTIONS, the columns it exposes align closely with the underlying table's transactional attributes plus lookup-display wrappers.

Key Columns

The most relevant columns include:

• TRANSACTION_ID — primary identifier of the receiving transaction.
• TRANSACTION_TYPE and DESTINATION_TYPE_CODE — lookup-driven codes describing the receipt or return action and its destination; exposed as displayed fields.
• QUANTITY, PRIMARY_QUANTITY, SECONDARY_QUANTITY, SOURCE_DOC_QUANTITY — quantities expressed in the transaction, primary, and secondary UOMs.
• UNIT_OF_MEASURE, PRIMARY_UNIT_OF_MEASURE, SOURCE_DOC_UNIT_OF_MEASURE, SECONDARY_UNIT_OF_MEASURE, and SECONDARY_UOM_CODE — this family of columns is directly relevant to the "transaction_unit_of_measure" search term: they carry the UOM in which each corresponding quantity is measured.
• PO_HEADER_ID, PO_LINE_ID, PO_LINE_LOCATION_ID, PO_DISTRIBUTION_ID — the purchasing document references.
• SHIPMENT_HEADER_ID, SHIPMENT_LINE_ID, INV_TRANSACTION_ID — receipt shipment and inventory transaction linkage.
• INSPECTION_STATUS_CODE, INVOICE_STATUS_CODE, MATCH_FLAG, QUANTITY_BILLED, AMOUNT_BILLED — inspection, invoicing, and matching state.
• VENDOR_ID, VENDOR_SITE_ID, ORGANIZATION_ID, SUBINVENTORY, LOCATOR_ID — receiving organization and location context.
• REASON_NAME — the human-readable reason from MTL_TRANSACTION_REASONS.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns.

Common Use Cases and Queries

The view is typically queried when the goal is to report receipts with descriptive lookup text, or to trace a receipt back to its purchasing and inventory references. A representative query for transaction unit of measure analysis is:

• SELECT transaction_id, transaction_type, quantity, unit_of_measure, primary_quantity, primary_unit_of_measure FROM apps.pobv_receiving_transactions WHERE po_header_id = :po_header_id;
• SELECT transaction_id, transaction_date, quantity, unit_of_measure, reason_name FROM apps.pobv_receiving_transactions WHERE shipment_line_id = :shipment_line_id;
• SELECT po_line_id, SUM(quantity) qty, unit_of_measure FROM apps.pobv_receiving_transactions WHERE transaction_type = 'RECEIVE' GROUP BY po_line_id, unit_of_measure;

Because the lookup-display markers are not evaluated in plain SQL, consumers reading the view directly will see the underlying code values; the translated descriptions are rendered only when the view is accessed through the EBS business component layer. Reporting against the UOM columns should therefore join to the appropriate UOM tables where a normalized description is required.