Results for “po_req_lines_trx_v”

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

Overview

PO_REQ_LINES_TRX_V is an APPS-owned, VALID view within the Oracle E-Business Suite Purchasing (PO) module. It is documented as the "Requisition Lines View" and exposes requisition line detail in a flattened, transaction-oriented form. The view is defined over PO_REQUISITION_LINES (accessed through a synonym) and references the PO_CLM_INTG_GRP package, placing it at the intersection of core requisition data and the supplier-sourcing/contract-lifecycle integration layer used by Purchasing.

Functionally, the view presents one row per requisition line (keyed by REQUISITION_LINE_ID) with the header linkage preserved through REQUISITION_HEADER_ID. Because it surfaces sourcing-related flags and suggested-vendor attributes alongside standard line attributes, it is commonly used in reporting, requisition-to-order progression analysis, and inbound/outbound integration where consumers require a read-only requisition line representation rather than the base table itself.

Underlying Base Objects

Per the ETRM metadata, PO_REQ_LINES_TRX_V is defined over two documented referenced objects:

• PO_REQUISITION_LINES (SYNONYM) — the primary base object supplying the requisition line columns. The synonym resolves to the underlying APPS requisition lines table, from which all projected columns (REQUISITION_LINE_ID, QUANTITY, NEED_BY_DATE, and so on) originate.
• PO_CLM_INTG_GRP (PACKAGE) — a Purchasing package linked to the contract lifecycle management / sourcing integration group. Its presence indicates that the view participates in integrated sourcing and contract workflows rather than exposing purely static requisition data.

The view selects directly from the requisition line source, applying NVL logic on LINE_NUM (NVL(PRL.LINE_NUM_DISPLAY, TO_CHAR(PRL.LINE_NUM))), which confirms it is a straightforward projection view rather than a join-heavy construct. In practice it behaves as a stable read interface layered over POSYN/PO requisition line storage.

Key Columns

The view projects a broad set of requisition line attributes. Notable groups include:

• Identity and linkage: REQUISITION_LINE_ID, REQUISITION_HEADER_ID, LINE_NUM, LINE_TYPE_ID, PARENT_REQ_LINE_ID.
• Item and category: ITEM_ID, ITEM_REVISION, CATEGORY_ID, ITEM_DESCRIPTION, UNIT_MEAS_LOOKUP_CODE, QUANTITY, UNIT_PRICE.
• Sourcing and supplier: SOURCE_TYPE_CODE, SUGGESTED_BUYER_ID, SUGGESTED_VENDOR_NAME, SUGGESTED_VENDOR_LOCATION, MUST_USE_SUGG_VENDOR_FLAG, VENDOR_ID, VENDOR_SITE_ID, RESEARCH_AGENT_ID, ON_LINE_FLAG, ON_RFQ_FLAG, RFQ_REQUIRED_FLAG. These columns, together with the PO_CLM_INTG_GRP reference, support the sourcing flags commonly targeted by searches such as the "at_sourcing_flag" term.
• Processing status: ENCUMBERED_FLAG, CANCEL_FLAG, CLOSED_CODE, QUANTITY_DELIVERED, QUANTITY_CANCELLED, MODIFIED_BY_AGENT_FLAG.
• Financial and currency: CURRENCY_CODE, RATE_TYPE, RATE_DATE, RATE, CURRENCY_UNIT_PRICE.
• Planning and destination: NEED_BY_DATE, DESTINATION_TYPE_CODE, DESTINATION_ORGANIZATION_ID, DESTINATION_SUBINVENTORY, SOURCE_ORGANIZATION_ID, WIP_ENTITY_ID and associated WIP columns.
• Descriptive flexfields: ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE6.

Common Use Cases and Queries

The view is typically queried for requisition line reporting, exposure through interfaces, and analysis of sourcing readiness. A representative query returning open, unencumbered lines awaiting action:

• SELECT requisition_line_id, requisition_header_id, line_num, item_description, quantity, need_by_date, suggested_vendor_name FROM po_req_lines_trx_v WHERE encumbered_flag = 'N' AND cancel_flag = 'N';
• Joining to PO_REQUISITION_HEADERS to obtain requisition number, preparer, and org context.
• Filtering on SOURCE_TYPE_CODE or suggested-vendor columns to identify lines relevant to sourcing and supplier selection workflows.

Because the view is read-only and VALID in both 12.1.1 and 12.2.2, it is safe for custom reports and integration extracts, provided consumers account for its dependency on the requisition line source and the PO_CLM_INTG_GRP integration package.