Search Results po_rtrn_dtl




Overview
Explore in AI Chat

Overview

The PO_RTRN_DTL table is a core transactional data object within the Oracle E-Business Suite Process Manufacturing Logistics (GML) module. It serves as the detailed line-level repository for return transactions, specifically capturing the items being returned against a purchase order. This table is integral to the return-to-vendor process, enabling the detailed tracking of returned quantities, reasons for return, and associated unit of measure conversions. Each record in PO_RTRN_DTL is linked to a parent return header (PO_RTRN_HDR) and typically traces back to the original purchase order line (PO_ORDR_DTL) and corresponding receipt line (PO_RECV_DTL), forming a complete audit trail for procurement returns.

Key Information Stored

The table's structure is defined by its primary and foreign keys, which anchor it within the procurement data model. The primary key, PO_RTRN_DTL_PK, is the LINE_ID column, uniquely identifying each return line. A unique key (PO_RTRN_DTL_UK) also enforces the combination of LINE_ID and RETURN_ID. Critical data columns include RETURN_ID (linking to the header), ITEM_ID (identifying the returned item), and RETURN_CODE (capturing the reason for the return via SY_REAS_CDS). The table also stores transactional quantities and unit of measure details through columns like RETURN_UM1 and RETURN_UM2, which reference SY_UOMS_MST. Foreign key columns such as POLINE_ID, PO_ID, RECVLINE_ID, and RECV_ID establish the essential links to the originating purchase order and receipt documents.

Common Use Cases and Queries

This table is central to reporting and process inquiries related to vendor returns. Common operational use cases include generating detailed return manifests, analyzing return reasons by item or supplier, and reconciling returned quantities against originally received amounts. A typical query would join PO_RTRN_DTL to its related header, item master, and purchase order tables to produce a comprehensive return report. For example, to analyze returns by reason code, one might execute a SQL pattern joining PO_RTRN_DTL to SY_REAS_CDS and IC_ITEM_MST. Data from this table is also critical for inventory and financial adjustments that are triggered by the return process, as it holds the definitive record of what was physically sent back to the supplier.

Related Objects

PO_RTRN_DTL maintains extensive foreign key relationships, positioning it as a nexus within the GML procurement schema. Its primary relationship is with PO_RTRN_HDR via the RETURN_ID column. It is fundamentally connected to the purchase order lifecycle through foreign keys to PO_ORDR_HDR (PO_ID) and PO_ORDR_DTL (POLINE_ID), and to the receipt lifecycle via PO_RECV_HDR (RECV_ID) and PO_RECV_DTL (RECVLINE_ID). Master data is referenced from IC_ITEM_MST_B and IC_ITEM_MST (ITEM_ID) for the item, SY_REAS_CDS and SY_REAS_CDS_B (RETURN_CODE) for the reason, and SY_UOMS_MST (RETURN_UM1, RETURN_UM2) for units of measure. An additional relationship with PO_TEXT_HDR (TEXT_CODE) manages associated textual notes or instructions for the return line.