Search Results to_person_id

Overview

OKX_PO_REQ_LINES_V is a Contracts Integration (OKX) view within Oracle E-Business Suite that exposes purchase requisition line information to the contracts integration layer. It presents one row per requisition line, sourced from the Oracle Purchasing requisition table PO_REQUISITION_LINES_ALL, and is used to translate requisition attributes into the contract authoring and sourcing data model. The view is documented in Oracle EBS 12.1.1 and 12.2.2 references with the note that it is "Not implemented in this database" in the source instance catalogued, meaning it is a shipped view that may only be instantiated or populated within installations that have the OKX integration components deployed. It is not a reporting-only object; its primary purpose is to feed requisition demand data into the contracts integration flows.

Underlying Base Objects

The view text selects directly from requisition line columns, and the documented referenced base objects list is empty, indicating that the definition is a direct projection over the purchasing requisition line entity rather than a join of multiple tables. Functionally the columns map one-to-one to the PO_REQUISITION_LINES_ALL table, with ID1 set to REQUISITION_LINE_ID, ID2 hard-coded to the literal '#', and NAME set to NULL. The surrogate ID1/ID2/NAME trio is a common OKX integration pattern used to provide a uniform key structure for entity mapping. Because no joins or outer tables are documented, the view carries no denormalised descriptive data beyond what exists on the requisition line itself.

Key Columns

• REQUISITION_LINE_ID (aliased ID1) — primary line identifier used as the integration key.
• REQUISITION_HEADER_ID and LINE_NUM — header and line sequencing context.
• PARENT_REQ_LINE_ID — self-referencing pointer from a child requisition line to its parent line, enabling hierarchical display and dependent line processing.
• LINE_TYPE_ID, CATEGORY_ID, ITEM_ID, ITEM_REVISION, ITEM_DESCRIPTION — the requisition line's item and category classification.
• QUANTITY, UNIT_PRICE, CURRENCY_UNIT_PRICE, CURRENCY_CODE, RATE, RATE_TYPE, RATE_DATE — quantity and pricing information with currency conversion.
• NEED_BY_DATE, DELIVER_TO_LOCATION_ID, TO_PERSON_ID, SOURCE_TYPE_CODE — delivery and sourcing attributes.
• SUGGESTED_BUYER_ID, PURCHASING_AGENT_ID, and the SUGGESTED_VENDOR_* columns — buyer and vendor sourcing suggestions, with MUST_USE_SUGG_VENDOR_FLAG enforcing the vendor suggestion.
• SOURCE_ORGANIZATION_ID, SOURCE_SUBINVENTORY, DESTINATION_TYPE_CODE, DESTINATION_ORGANIZATION_ID, DESTINATION_SUBINVENTORY — internal requisition sourcing and destination details.
• QUANTITY_CANCELLED, CANCEL_FLAG, CANCEL_DATE, CANCEL_REASON, CLOSED_CODE — line status and cancellation tracking.
• VENDOR_ID and VENDOR_SITE_ID — the vendor and vendor site associated with the line.

Common Use Cases and Queries

The most frequent application of this view is retrieving requisition lines associated with contract integration, especially where parent-child relationships between lines must be preserved. The parent_req_line_id column supports hierarchical queries that identify dependent lines. A typical query is:

• SELECT id1, requisition_header_id, line_num, parent_req_line_id, item_id, quantity, unit_price FROM okx_po_req_lines_v WHERE requisition_header_id = :header_id ORDER BY line_num;
• SELECT child.id1, child.line_num, parent.id1 AS parent_line FROM okx_po_req_lines_v child, okx_po_req_lines_v parent WHERE child.parent_req_line_id = parent.id1;
• SELECT id1, suggested_buyer_id, must_use_sugg_vendor_flag, vendor_id, vendor_site_id FROM okx_po_req_lines_v WHERE nvl(must_use_sugg_vendor_flag,'N') = 'Y';

These queries are commonly embedded in custom PL/SQL integration routines and in contract sourcing extracts where requisition demand must be matched to contract terms. Because the view reflects PO_REQUISITION_LINES_ALL directly, standard purchasing security and multi-org predicates should be applied by the calling application.