Results for “po_requisition_lines_all”

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

Overview

PO_REQUISITION_LINES_ALL is the core transactional table in the Oracle E-Business Suite Purchasing (PO) module that stores the individual line-level details of every purchase requisition. A requisition represents an internal request to procure goods or services; the header information (requester, preparation date, authorization status) resides in PO_REQUISITION_HEADERS_ALL, while each item, quantity, price, and delivery attribute requested on that requisition is captured as a row in PO_REQUISITION_LINES_ALL. The table is owned by the PO schema and is present in both 12.1.1 and 12.2.2, with the documented 12.2.2 physical schema containing 222 columns.

Because the table is the central point from which requisition data fans out to sourcing, purchasing, receiving, inventory, and payables, a Data Vault classification heuristic suggests treating it as a hub. Its surrogate identity is stable and it is referenced by a very large number of downstream foreign keys, which is characteristic of a hub entity anchoring many links and satellites.

Key Information Stored

The surrogate primary key is REQUISITION_LINE_ID (constraint PO_REQUISITION_LINES_PK). Two unique indexes are documented: PO_REQUISITION_LINES_U1 on REQUISITION_LINE_ID and PO_REQUISITION_LINES_U2 on (REQUISITION_HEADER_ID, CREATION_DATE, LINE_NUM), the latter identifying the natural business key of a line within its requisition.

• REQUISITION_HEADER_ID — foreign key to the parent requisition in PO_REQUISITION_HEADERS_ALL.
• LINE_NUM — the line number within the requisition.
• LINE_TYPE_ID — references PO_LINE_TYPES_B, distinguishing goods, services, and other line categories.
• ITEM_ID, ITEM_DESCRIPTION, ITEM_REVISION — the requested item and its description.
• QUANTITY, UNIT_PRICE, UNIT_MEAS_LOOKUP_CODE — requested amount, price basis, and UOM.
• CATEGORY_ID — purchasing category, referencing MTL_CATEGORIES_B.
• NEED_BY_DATE, DELIVER_TO_LOCATION_ID, TO_PERSON_ID — delivery requirements.
• SUGGESTED_BUYER_ID / PURCHASING_AGENT_ID — the buyer associated with the line (buyer role references PO_AGENTS).
• CURRENCY_CODE, RATE_TYPE, RATE, CURRENCY_UNIT_PRICE — currency and conversion detail (references FND_CURRENCIES and GL_DAILY_CONVERSION_TYPES).
• VENDOR_ID, VENDOR_SITE_ID, VENDOR_CONTACT_ID, SUGGESTED_VENDOR_NAME — suggested source information.
• SOURCE_TYPE_CODE, DOCUMENT_TYPE_CODE, BLANKET_PO_HEADER_ID — sourcing/document context, including blanket references to PO_HEADERS_ALL.
• CANCEL_FLAG, CANCEL_DATE, CANCEL_REASON, CLOSED_CODE, CLOSED_DATE — lifecycle and closure status.
• PARENT_REQ_LINE_ID — self-referencing foreign key supporting line hierarchies.
• ORG_ID — operating unit, enforcing multi-org security.

Numerous optional columns support WIP references (WIP_ENTITY_ID, WIP_LINE_ID, WIP_REPETITIVE_SCHEDULE_ID, BOM_RESOURCE_ID), documentation, professional services/contractor lines, tax (TAX_CODE_ID), and kanban sourcing.

Common Use Cases and Queries

Typical reporting includes open requisition listings, requisition-to-PO tracking, buyer workload, and encumbrance analysis. A representative join to the header is:

• SELECT l.requisition_line_id, l.line_num, l.item_description, l.quantity, l.unit_price, h.preparer_id, h.authorization_status FROM po_requisition_lines_all l, po_requisition_headers_all h WHERE l.requisition_header_id = h.requisition_header_id AND l.org_id = :org_id;
• Open-line reporting filters on CLOSED_CODE, CANCEL_FLAG, and NEED_BY_DATE.
• Distribution-level spend analysis joins PO_REQ_DISTRIBUTIONS_ALL on REQUISITION_LINE_ID.
• Receiving reconciliation joins RCV_SHIPMENT_LINES and RCV_TRANSACTIONS on REQUISITION_LINE_ID.

Because the table carries multi-org (ORG_ID) and multiple attribute/global-attribute (flexfield) columns, queries should always be scoped by operating unit and, where relevant, by descriptive flexfield context.

Related Objects

• PO_REQUISITION_HEADERS_ALL — parent requisition; join on REQUISITION_HEADER_ID.
• PO_REQ_DISTRIBUTIONS_ALL — charge distributions per line; references REQUISITION_LINE_ID.
• PO_REQUISITION_LINES_ALL (self) — parent/child line hierarchy via PARENT_REQ_LINE_ID.
• PO_REQUISITIONS_INTERFACE_ALL — inbound interface carrying requisition lines for import.
• RCV_SHIPMENT_LINES / RCV_TRANSACTIONS — receiving activity tied to requisition lines.
• PO_HEADERS_ALL / PO_AGENTS / MTL_CATEGORIES_B — blanket references, buyer, and category lookups.
• MTL_SUPPLY — supply/demand planning reference to requisition lines.
• OE_DROP_SHIP_SOURCES / SO_DROP_SHIP_SOURCES — drop-shipment linkage to order management.
• PO_LINE_LOCATIONS_ALL — schedules referenced through LINE_LOCATION_ID.