Results for “price_um”

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

Overview

PO_RECV_HST is a GML (Process Manufacturing Logistics) audit table in Oracle E-Business Suite 12.1.1 and 12.2.2. It records the audit trail of quantity and price changes applied to a receipt line or return line. Every time a receipt or return line is adjusted — for example, when received quantity is corrected, when a return is processed against a previously received line, or when unit price is revised during reconciliation — a new history row is written to this table capturing the before/after state of the transaction. As such, PO_RECV_HST is the authoritative historical record for auditing receipt-line changes and reconstructing what occurred on a given receipt over time.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is a link. This suggests PO_RECV_HST functions primarily as an associative entity connecting business keys such as receipt lines, purchase orders, warehouses, and event types, rather than as a descriptive satellite. Its composite primary key (RECV_ID, RECV_LINE_ID, RECV_SEQ_NO, SUB_EVENT_TYPE) reinforces this role, since the records tie together a receipt context and a sub-event classification.

Key Information Stored

The table contains 26 documented columns. The most significant are:

• RECV_ID — Receipt header identifier, part of the composite primary key candidate.
• RECV_LINE_ID — Receipt line identifier; this is the column most frequently used when searching for a specific receipt line's audit history. RECV_ID combined with RECV_LINE_ID links the history row to the receipt line event.
• RECV_SEQ_NO — Sequence number distinguishing multiple history entries for the same receipt line.
• SUB_EVENT_TYPE — Classifies the sub-event type of change; foreign key to GL_SEVT_MST.
• NET_QTY — Net quantity recorded for the line at the time of the change.
• NET_PRICE — Net price recorded for the line at the time of the change.
• PRICE_UM — Price unit of measure; foreign key to SY_UOMS_MST.
• TO_WHSE — Destination warehouse; foreign key to IC_WHSE_MST.
• PO_ID and PO_LINE_ID — Purchase order header and line identifiers associated with the receipt line.
• RECV_DATE — Date the receipt event occurred.
• GL_POSTED_IND — Indicator of whether the related accounting entry was posted to the general ledger.
• TEXT_CODE — Text reference; foreign key to PO_TEXT_HDR.
• DELETE_MARK — Soft-delete flag.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard audit columns capturing who and when the history row was created or modified.

The unique index PO_RECV_HST_PK on (RECV_ID, RECV_LINE_ID, RECV_SEQ_NO, SUB_EVENT_TYPE) serves as the business-key candidate, distinguishing each history event uniquely.

Common Use Cases and Queries

Typical scenarios include auditing price and quantity revisions on a received line, tracing a return back to its original receipt, and reconciling GML receipts with their accounting postings. A common query pattern selecting history for a specific receipt line is:

• SELECT recv_id, recv_line_id, recv_seq_no, sub_event_type, net_qty, net_price, recv_date FROM po_recv_hst WHERE recv_line_id = :line_id ORDER BY recv_seq_no;
• Joining to PO_ORDR_HDR on PO_ID to retrieve purchase order context for each change event.
• Filtering on GL_POSTED_IND to identify changes not yet reflected in the general ledger.

Related Objects

PO_RECV_HST references the following significant objects through documented foreign keys:

• GL_SEVT_MST — via SUB_EVENT_TYPE, defining the sub-event classification.
• IC_WHSE_MST — via TO_WHSE, the destination warehouse master.
• PO_TEXT_HDR — via TEXT_CODE, the text header holding line notes.
• SY_UOMS_MST — via PRICE_UM, the unit-of-measure master.
• PO_ORDR_HDR — via PO_ID, the purchasing order header providing order context.

These relationships make PO_RECV_HST the central audit pivot for GML receipt-line changes, joining receipt, purchasing, warehouse, and event-classification data into a single chronological record.