Results for “return_date”

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

Overview

PO_RTRN_HDR is the return header table in the Oracle EBS Process Manufacturing Logistics (GML) module. It stores the top-level record for a vendor return transaction, capturing who is returning goods, from which organization, to which vendor, on what date, and through which shipper. Each row represents one return document, identified by the primary key RETURN_ID and enumerated to users through the business-facing RETURN_NO. The table serves as the parent of the return detail table PO_RTRN_DTL, which holds the specific items, lots, and quantities being returned.

From a dimensional modeling perspective, the foreign key structure suggests PO_RTRN_HDR behaves as a satellite-leaning entity: it carries descriptive and transactional attributes (return date, shipper, vendor, address, text reference) that qualify a business process event, while most of its dependencies point outward to master and reference tables. This classification is a heuristic derived from the documented FK topology rather than a declared design intent, and should be treated as a modeling suggestion when building downstream marts or integration layers.

Key Information Stored

The table is documented with 46 columns. The most operationally significant are:

• RETURN_ID — surrogate primary key, enforced by unique index PO_RTRN_HDR_PK. This is the sole documented unique index and therefore the definitive join key.
• RETURN_NO — user-visible return document number; the natural business identifier, though not backed by a documented unique constraint.
• ORGN_CODE — organization (warehouse/plant) originating the return; FK to SY_ORGN_MST and SY_ORGN_MST_B.
• RETURN_VENDOR_ID — the vendor receiving the return; FK to PO_VEND_MST.
• RTRNADDR_ID — ship-to or return address; FK to SY_ADDR_MST.
• RETURN_DATE — date the return is raised.
• SHIPPER_CODE — carrier/shipper used for the return; FK to OP_SHIP_MST.
• TEXT_CODE — reference into the text/long-description framework; FK to PO_TEXT_HDR.
• IN_USE — record-level usage/status flag.
• DELETE_MARK — logical delete indicator; standard in GML/OPM tables and must be filtered in queries.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — the DFF/value-set flex columns used for client-specific extensions.

Common Use Cases and Queries

Typical use cases include return reporting by vendor or organization, reconciliation of return headers to their detail lines and lots, and extraction of return activity for analytics or third-party logistics feeds. Because DELETE_MARK is present, every query should filter on it. Example patterns:

• Return headers for a given organization and date range: SELECT return_id, return_no, return_date, return_vendor_id FROM po_rtrn_hdr WHERE orgn_code = :orgn AND return_date BETWEEN :from_dt AND :to_dt AND NVL(delete_mark,0) = 0;
• Header-to-line drill-down: SELECT h.return_no, d.* FROM po_rtrn_hdr h JOIN po_rtrn_dtl d ON d.return_id = h.return_id WHERE h.return_no = :ret_no;
• Enrichment with vendor and address: join RETURN_VENDOR_ID to PO_VEND_MST and RTRNADDR_ID to SY_ADDR_MST.
• Carrier analysis: group returns by SHIPPER_CODE joined to OP_SHIP_MST.

Reporting typically exposes RETURN_NO rather than RETURN_ID, and DFF attributes are read only where the ATTRIBUTE_CATEGORY is populated.

Related Objects

• PO_RTRN_DTL — child lines linked via RETURN_ID.
• PO_VEND_MST — vendor master joined on RETURN_VENDOR_ID.
• SY_ORGN_MST and SY_ORGN_MST_B — organization master joined on ORGN_CODE.
• SY_ADDR_MST — address master joined on RTRNADDR_ID.
• OP_SHIP_MST — shipper master joined on SHIPPER_CODE.
• PO_TEXT_HDR — text header joined on TEXT_CODE for extended descriptions.

These six dependencies plus the child detail table constitute the documented relationship footprint of PO_RTRN_HDR; no additional views or APIs are enumerated in the source metadata.