Results for “okc_rel_obj_po_req_lines_v”
4 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OKC_REL_OBJ_PO_REQ_LINES_V is a Contracts Core (OKC) view that exposes the relationship between Oracle Purchasing requisition lines and Oracle Contracts. It surfaces the association records created when a purchasing requisition line is linked to a contract through the relationship type PO_REQ_CREATES_K, while enriching those links with requisition line detail and item description attributes drawn from Oracle Purchasing and inventory item views. The view is the contracts-side representation of the "requisition creates contract" linkage and answers the practical business question of which contract line is sourced from which requisition line, along with quantity, price, and amount.
In Oracle EBS 12.1.1 and 12.2.2, the object is documented in the ETRM repository as an OKC Contracts Core view. The user search term "okx_po_req_lines_v" reflects the underlying base view named in the FROM clause, OKX_PO_REQ_LINES_V, which is the Oracle Sourcing/Purchasing contract-requisition integration view. OKC_REL_OBJ_PO_REQ_LINES_V joins that sourcing view to the OKC relationship table, so it is primarily used for reporting and integration rather than as a transactional entry point.
Underlying Base Objects
The view text is defined over three objects: OKX_PO_REQ_LINES_V (aliased RLIN), OKX_SYSTEM_ITEMS_V (aliased ITMS), and OKC_K_REL_OBJS (aliased ROBJ). The join conditions are:
- ROBJ.OBJECT1_ID1 = RLIN.ID1 — links the relationship object record to the requisition line.
- RLIN.ITEM_ID = ITMS.ID1 AND RLIN.ORG_ID = ITMS.ID2 — links the requisition line to the item description.
- ROBJ.JTOT_OBJECT1_CODE = 'OKX_PO_REQ_LINE' — restricts the relationship object to requisition line objects.
- ROBJ.RTY_CODE = 'PO_REQ_CREATES_K' — restricts to the relationship type representing requisition-to-contract creation.
OKC_K_REL_OBJS is the OKC Contracts Core relationship object table that stores generic links between contracts and external business objects; the RTY_CODE and JTOT_OBJECT1_CODE columns determine the nature of the linked object. The view is documented as not implemented in the reference database, and base objects beyond those named in the view text are not separately catalogued. Note also that the OKX_ objects are sourcing-related views rather than base tables, so the requisition data itself ultimately derives from PO_REQUISITION_LINES_ALL and PO_REQUISITION_HEADERS_ALL.
Key Columns
- ID — the relationship object identifier (ROBJ.ID) representing the specific contract-to-requisition line link.
- CLE_ID, CHR_ID — contract line and contract header identifiers from the OKC relationship record.
- RTY_CODE — relationship type code, constant value 'PO_REQ_CREATES_K'.
- JTOT_OBJECT1_CODE — the linked object code, constant value 'OKX_PO_REQ_LINE'.
- REQUISITION_LINE_ID / REQUISITION_HEADER_ID — the purchasing requisition line and header identifiers.
- LINE_NUM — the requisition line number.
- ITEM_ID, ITEM_NAME, DESCRIPTION — item identifier, item description, and the requisition line item description.
- UOM_CODE, UNIT_PRICE, QUANTITY, AMOUNT — unit of measure, price, quantity, and computed amount (UNIT_PRICE * QUANTITY).
- NEED_BY_DATE, CURRENCY_CODE — required-by date and transaction currency.
- OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, SECURITY_GROUP_ID — standard OKC audit and multi-org security columns.
Note that ROW_ID is RLIN.ROWID, and that LAST_UPDATE_LOGIN is sourced from ROBJ.LAST_UPDATE_DATE in the documented view text.
Common Use Cases and Queries
Typical scenarios include auditing which requisition lines were created against or linked to contracts, reconciling contract committed amounts against requisition quantities, and reporting on sourcing activity by contract. A sample query joining the view to contract information is:
SELECT ID, CLE_ID, CHR_ID, REQUISITION_LINE_ID, REQUISITION_HEADER_ID, LINE_NUM, ITEM_NAME, QUANTITY, UNIT_PRICE, AMOUNT, NEED_BY_DATE FROM OKC_REL_OBJ_PO_REQ_LINES_V;- To filter for a specific contract line: add
WHERE CLE_ID = :cle_id. - To report by item: add
WHERE ITEM_ID = :item_id. - To trend by need-by date: add
WHERE NEED_BY_DATE BETWEEN :start_date AND :end_date ORDER BY NEED_BY_DATE.
Because the view is read-only and defined over sourcing and OKC relationship views, it is appropriate for reporting and integration extracts rather than DML. Performance-sensitive queries should filter on CLE_ID or REQUISITION_LINE_ID to constrain access to the underlying OKC_K_REL_OBJS relationship table.
-
Not implemented in this database·Explore OKC module →
-
Not implemented in this database·Explore OKC module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2