Results for “embarkation_port”

50+ results




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

Overview

PO_RECV_HDR is the receipt header table within the Process Manufacturing Logistics (GML) module of Oracle E-Business Suite, owned by the GML schema. It stores the top-level record for every goods receipt transaction processed in a process manufacturing environment, acting as the parent entity for receipt line detail and return line detail. Each row captures the commercial, logistical, and documentary context of a receipt event: the receiving organization, the vendor from whom goods were received, transportation and shipping references, weights, currency and exchange information, and a standard set of descriptive flexfield attributes and audit columns. In EBS 12.1.1 and 12.2.2 the table is documented as VALID with 73 columns.

Mined from its foreign key structure, the table carries a heuristic Data Vault classification of satellite-leaning. This classification is a modeling suggestion rather than a physical implementation: the table is keyed by a single surrogate identifier and is rich in descriptive, time-stamped attributes, which is characteristic of satellite-style data. However, because it is heavily referenced by other receipt-related tables, it also behaves as a parent entity in the operational model, and any Data Vault design should account for both traits.

Key Information Stored

The documented primary key is PO_RECV_HDR_PK on RECV_ID, the internal surrogate identifier for a receipt header. A second unique index, PO_RECV_HDR_U1 on ORGN_CODE and RECV_NO, establishes the business-key candidate: a receipt number is unique only within a given organization. The most significant columns include the following.

Common Use Cases and Queries

Typical reporting retrieves receipt headers for an organization and date range, joins to line detail for quantity and item analysis, and joins to vendor or organization masters for enrichment. A representative pattern:

SELECT h.recv_id, h.recv_no, h.recv_date, h.orgn_code,
       h.payvend_id, h.shipvnd_id, h.to_whse
FROM   gml.po_recv_hdr h
WHERE  h.orgn_code = :orgn_code
AND    h.recv_date BETWEEN :from_date AND :to_date
AND    NVL(h.delete_mark, 0) = 0;

Common scenarios include receipt register reporting by organization, vendor receipt volume and on-time analysis using RECV_DATE, inbound freight and weight reconciliation using the three weight columns and BOL_UM, landed-cost style reporting that draws on DEMURRAGE_AMT, DEMURRAGE_CURRENCY, BILLING_CURRENCY, and RECEIPT_EXCHANGE_RATE, and void or reversal audits using VOID_IND. Joining to PO_RECV_DTL on RECV_ID supports line-level drill-down, and joining to IN_STAT_HDR on RECV_ID supports inventory status reporting.

Related Objects

The following objects are the most significant dependents and referenced masters, with join columns as documented.

  • PO_RECV_DTL — receipt line detail; joins on PO_RECV_DTL.RECV_ID = PO_RECV_HDR.RECV_ID. This is the primary child and the most frequent join target.
  • PO_RTRN_DTL — return line detail; joins on PO_RTRN_DTL.RECV_ID = PO_RECV_HDR.RECV_ID.
  • IN_STAT_HDR — inventory status header; joins on IN_STAT_HDR.RECV_ID = PO_RECV_HDR.RECV_ID.
  • PO_VEND_MST — vendor master; referenced through PAYVEND_ID and SHIPVEND_ID.
  • SY_ORGN_MST and SY_ORGN_MST_B — organization masters; referenced through ORGN_CODE.
  • IC_WHSE_MST — warehouse master; referenced through TO_WHSE.
  • OP_SHIP_MST and OP_SHIP_MTH — shipper and shipping method masters; referenced through SHIPPER_CODE and SHIP_MTHD.
  • OP_PORT_MST — port master; referenced through EMBARKATION_PORT and DEBARKATION_PORT.
  • PO_RECV_HDR_EFC and PO_RECV_HST_EFC — receipts-era and history objects keyed on RECV_ID, relevant to archived or historical receipt analysis.