Results for “research_agent_id”

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

Overview

PO_REQ_LINES_GT is a global temporary table (GTT) owned by the PO schema in Oracle E-Business Suite Purchasing. It is derived structurally from PO_REQUISITION_LINES_ALL, the base transactional table that stores requisition line detail. The table is documented as For Internal Use Only: it exists to support the internal processing of data required by PO Approval Submission Checks, meaning the rows it holds are transient working sets consumed by the approval submission validation logic rather than persistent application data.

Because it is a global temporary table, its contents are scoped to a session or transaction depending on the ON COMMIT clause defined at creation. Rows are populated at runtime by the approval submission check program, validated, and then discarded; no permanent business record is retained. In ETRM 12.2.2 the table is documented with 140 columns and is classified as VALID. From a data-vault modeling perspective, the heuristic classification is standalone — the table does not participate in a hub, link, or satellite pattern because it is a transient staging structure, not an integrated subject area entity. Any attempt to model it as a persistent source should be discouraged; it is a processing artifact.

Key Information Stored

The column set mirrors PO_REQUISITION_LINES_ALL, extended to carry approval-relevant attributes. The following columns are the most operationally significant:

• REQUISITION_LINE_ID — the business-key candidate, enforced by the unique index PO_REQ_LINES_GT_U1. It identifies the requisition line being processed.
• REQUISITION_HEADER_ID — links the line back to its requisition header for header-level approval checks.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrent program context identifying which request populated the temporary rows.
• LINE_NUM, LINE_TYPE_ID, CATEGORY_ID, ITEM_ID, ITEM_DESCRIPTION — line identification and item/category attributes used in validation rules.
• QUANTITY, UNIT_PRICE, AMOUNT, CURRENCY_CODE, CURRENCY_UNIT_PRICE — monetary and quantity fields evaluated for approval thresholds.
• ORG_ID — the operating unit context, critical where multi-org approval routing applies.
• DESTINATION_TYPE_CODE, DESTINATION_ORGANIZATION_ID, DESTINATION_SUBINVENTORY, DELIVER_TO_LOCATION_ID, TO_PERSON_ID — destination and requester routing information.
• CANCEL_FLAG, CLOSED_CODE, CLOSED_REASON, CLOSED_DATE — status indicators that determine whether a line remains eligible for approval submission.
• QUANTITY_RECEIVED, QUANTITY_DELIVERED, QUANTITY_CANCELLED — cumulative settlement quantities checked during submission.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

There is no surrogate primary key in the conventional sense; the unique index on REQUISITION_LINE_ID functions as the identifying key for the working set.

Common Use Cases and Queries

Direct querying of PO_REQ_LINES_GT outside a debugging context is unusual and generally unrewarding, because rows only exist within the session or transaction that populated them. The practical scenarios are:

• Troubleshooting approval submission failures. A developer or DBA reproduces the approval submission check within a single session and inspects the rows that the checking logic populated to determine which line failed a rule.
• Diagnosing concurrent program behavior. Filtering by REQUEST_ID correlates the temporary rows to the specific concurrent request that generated them, isolating a failed run.
• Validation of approval thresholds. Aggregating AMOUNT or CURRENCY_UNIT_PRICE by ORG_ID or REQUISITION_HEADER_ID confirms the totals the approval engine evaluated.

A representative session-scoped query pattern is:

SELECT requisition_line_id, requisition_header_id, line_num, amount, currency_code
FROM po.po_req_lines_gt
WHERE request_id = :request_id
ORDER BY requisition_header_id, line_num;

Because the table is session- or transaction-scoped, this query returns data only when executed from the owning session; querying from a separate session returns an empty set. This behavior is frequently mistaken for a data problem and should be confirmed before escalating.

Related Objects

The FK metadata reveals several reference relationships, though on a GTT these are documented relationships rather than persistently enforced constraints in the normal transactional sense. The most significant related objects are:

• PO_REQUISITION_LINES_ALL — the base table from which the structure is derived, joined on REQUISITION_LINE_ID.
• PO_REQUISITION_HEADERS_ALL — joined on REQUISITION_HEADER_ID for header-level context.
• PO_LINE_TYPES_B — joined via LINE_TYPE_ID for line type validation.
• PO_HAZARD_CLASSES_B — joined via HAZARD_CLASS_ID.
• PO_UN_NUMBERS_B — joined via UN_NUMBER_ID for hazardous material classification.
• MTL_KANBAN_CARDS — joined via KANBAN_CARD_ID for kanban-sourced lines.
• MTL_MANUFACTURERS — joined via MANUFACTURER_ID.
• ICX_POR_ITEM_SOURCES — joined via ITEM_SOURCE_ID for catalog source resolution.
• PON_AUCTION_HEADERS_ALL — joined via AUCTION_HEADER_ID for auction-sourced requisitions.

These references confirm the table's role as a consolidated validation snapshot spanning purchasing, inventory, and sourcing contexts, assembled on demand by the approval submission check and discarded once processing completes.