Search Results recv_no

Overview

The PO_RECV_HDR table is a core data object within the Process Manufacturing Logistics (GML) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It functions as the primary receipt header table, storing high-level transactional and logistical information for material receipts. Each record represents a distinct receipt document, serving as the parent entity for detailed receipt line information. Its role is central to the inbound logistics and procurement processes, providing the foundational header data that links to vendor, shipping, organizational, and financial details.

Key Information Stored

The table's structure captures comprehensive receipt metadata. The primary identifier is RECV_ID, which is the unique system-generated key. The business key is a composite of ORGN_CODE (operating unit) and RECV_NO (receipt number), enforcing uniqueness at the document level. Key foreign key columns define critical relationships: SHIPVEND_ID and PAYVEND_ID link to the vendor master (PO_VEND_MST) for shipping and paying parties; TO_WHSE links to the warehouse master (IC_WHSE_MST); and SHIPPER_CODE and SHIP_MTHD link to shipping master tables (OP_SHIP_MST, OP_SHIP_MTH). Additional columns manage financial aspects like BILLING_CURRENCY and DEMURRAGE_CURRENCY (linked to GL_CURR_MST), and document attributes such as TEXT_CODE for header notes and REASON_CODE for transaction rationale.

Common Use Cases and Queries

This table is essential for reporting and data extraction related to inbound shipments and receipts. Common use cases include generating receipt summaries, tracking shipment methods by vendor, and auditing receipt transactions by organization and date. A typical query to join header information with vendor details for analysis would be:

• SELECT prh.RECV_NO, prh.ORGN_CODE, pvm.VEND_NAME, prh.SHIPPER_CODE, prh.RECEIPT_DATE FROM GML.PO_RECV_HDR prh, PO_VEND_MST pvm WHERE prh.SHIPVEND_ID = pvm.VEND_ID AND prh.ORGN_CODE = :p_org_code AND prh.RECEIPT_DATE BETWEEN :p_date_from AND :p_date_to ORDER BY prh.RECEIPT_DATE DESC;

For troubleshooting or data validation, queries often join PO_RECV_HDR to its child table, PO_RECV_DTL, to ensure header records have corresponding lines and to calculate total received quantities or values per receipt document.

Related Objects

PO_RECV_HDR has extensive relationships within the GML and broader EBS schema. Its primary child tables are PO_RECV_DTL and PO_RTRN_DTL, which store receipt and return line details, respectively, linked via the RECV_ID column. As indicated by its foreign keys, it is a dependent table referencing numerous master data tables, including SY_ORGN_MST (organization), PO_VEND_MST (vendor), IC_WHSE_MST (warehouse), and GL_CURR_MST (currency). It also references transactional tables like PO_TEXT_HDR for descriptive flexfields. This network of relationships underscores its position as a pivotal junction table connecting procurement execution with master data and financial controls.