Results for “return_code”

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

Overview

PO_RTRN_DTL is the return-line detail table within the GML (Process Manufacturing Logistics) product family of Oracle E-Business Suite. As the name implies, it stores the individual line-level records that make up a return transaction, where goods previously received against a purchase order are sent back to a supplier or otherwise reversed. Each row in PO_RTRN_DTL represents one return line and is linked to a parent header row in PO_RTRN_HDR through the RETURN_ID column. The table is owned by the GML schema and is documented as VALID in both EBS 12.1.1 and 12.2.2, with a documented physical schema of 53 columns in the 12.2.2 ETRM repository.

The primary key is defined by the index PO_RTRN_DTL_PK on the surrogate column LINE_ID. A second unique index, PO_RTRN_DTL_UK (the object the user searched for), is also defined on the LINE_ID column in the documented metadata. From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is link: the table's identity is dominated by relationships to header, order, receipt, item, and code-reference tables rather than by descriptive attributes. In practical terms, it operates as a transaction detail table sitting between a return header and the source purchasing and receiving documents.

Key Information Stored

The most significant columns are those that identify the line and connect it to the surrounding transaction chain:

• LINE_ID — Surrogate primary key and sole column of the unique index PO_RTRN_DTL_PK (and PO_RTRN_DTL_UK).
• RETURN_ID — Foreign key to PO_RTRN_HDR; identifies the parent return.
• LINE_NO — Line sequence number within the return.
• PO_ID and POLINE_ID — Foreign keys to PO_ORDR_HDR and PO_ORDR_DTL, tying the return to the original purchase order and line.
• RECV_ID and RECVLINE_ID — Foreign keys to PO_RECV_HDR and PO_RECV_DTL, linking the return to the originating receipt.
• ITEM_ID — Foreign key to IC_ITEM_MST / IC_ITEM_MST_B; the returned item.
• RETURN_QTY1, RETURN_QTY2, RETURN_UM1, RETURN_UM2 — Returned quantities in the primary and secondary units of measure; the UM columns reference SY_UOMS_MST.
• RMA — Return merchandise authorization reference.
• RETURN_CODE — Reason code, foreign key to SY_REAS_CDS_B / SY_REAS_CDS.
• TEXT_CODE — Foreign key to PO_TEXT_HDR for line notes.
• REORDER_IND and TRANS_CNT — Flags and counters for return processing.
• Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) and the ATTRIBUTE_CATEGORY / ATTRIBUTE1–ATTRIBUTE30 descriptive flexfield columns.

Common Use Cases and Queries

Typical reporting scenarios include tracing returns back to their purchase order and receipt, analyzing return volumes by item or supplier, and reconciling return quantities by reason code. A representative join query is:

• Return header/detail listing: join PO_RTRN_DTL to PO_RTRN_HDR on RETURN_ID to obtain header and line information.
• Source-document traceability: join to PO_ORDR_DTL on POLINE_ID and to PO_RECV_DTL on RECVLINE_ID to relate each return line to the order line and receipt line that generated it.
• Reason-code analysis: join to SY_REAS_CDS on RETURN_CODE to summarize return quantities by reason.
• Item enrichment: join to IC_ITEM_MST on ITEM_ID to report returned items by description or category.

Related Objects

• PO_RTRN_HDR — Parent return header, joined on RETURN_ID.
• PO_ORDR_HDR / PO_ORDR_DTL — Original purchase order header and line, joined on PO_ID and POLINE_ID.
• PO_RECV_HDR / PO_RECV_DTL — Originating receipt header and line, joined on RECV_ID and RECVLINE_ID.
• IC_ITEM_MST / IC_ITEM_MST_B — Item master, joined on ITEM_ID.
• SY_REAS_CDS / SY_REAS_CDS_B — Reason codes, joined on RETURN_CODE.
• SY_UOMS_MST — Units of measure, joined on RETURN_UM1 and RETURN_UM2.
• PO_TEXT_HDR — Text headers for line notes, joined on TEXT_CODE.