Search Results po_req_creates_k

Overview

The view OKC_REL_OBJ_PO_REQ_HEADERS_V is a Contracts Core (OKC) reporting view that exposes the association between Oracle Purchasing requisition headers and the contract relationship objects maintained by Oracle Contract Terms and ETRM. It is one of several relationship-denormalization views (related to the OKC_K_REL_OBJS entity) that publish cross-module object links in a flattened, business-friendly shape. The view answers a specific question: which purchasing requisition header is bound to a contract repository record, and through which relationship type?

The ETRM 12.2.2 metadata classifies this view as not implemented in this database, meaning it ships as part of the product definition but is not deployed or populated in the documentation environment from which the metadata was extracted. Administrators should therefore validate availability before relying on it in custom reports or integrations. The user search term "okx_po_req_headers_v" refers to the underlying Purchasing requisition view (OKX_PO_REQ_HEADERS_V) that this OKC view joins against.

Underlying Base Objects

Per the documented view text, OKC_REL_OBJ_PO_REQ_HEADERS_V is defined over exactly two sources:

• OKX_PO_REQ_HEADERS_V RHDV — the Purchasing requisition header view, supplying requisition number, description, authorization status, and the internal requisition header ID (ID1).
• OKC_K_REL_OBJS ROBJ — the Contracts relationship object table, supplying the relationship type code, joined object type code, contract line / contract header identifiers (CLE_ID, CHR_ID), object version, audit columns, and security group.

The join is driven by two predicates: ROBJ.OBJECT1_ID1 = RHDV.ID1 equates the relationship object's first object identifier with the requisition header's internal ID, and two constant filters restrict the result set to contract-to-requisition links only — ROBJ.JTOT_OBJECT1_CODE = 'OKX_PO_REQ_HDR' and ROBJ.RTY_CODE = 'PO_REQ_CREATES_K'. The relationship type PO_REQ_CREATES_K denotes the "requisition creates contract" linkage captured when a contract is authored from a purchasing requisition.

Key Columns

• REQUISITION_NUMBER (RHDV.SEGMENT1) — the user-visible requisition document number.
• NAME (RHDV.DESCRIPTION) — the requisition description, useful as a display label.
• REQUISITION_HEADER_ID (RHDV.ID1) — the internal primary key of the requisition header.
• ID, CLE_ID, CHR_ID — the relationship object's primary key, contract line ID, and contract header ID respectively, linking back into OKC contract records.
• RTY_CODE — the relationship type; always PO_REQ_CREATES_K for rows returned by this view.
• JTOT_OBJECT1_CODE — the joined object type, always OKX_PO_REQ_HDR.
• AUTHORIZATION_STATUS — the requisition approval state, carried through from the Purchasing view.
• OBJECT1_ID2, OBJECT_VERSION_NUMBER — secondary object identifier and optimistic-locking version number for the relationship row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — standard EBS audit columns.
• SECURITY_GROUP_ID — the multi-org/multi-tenant security grouping used by ETRM objects.

Common Use Cases and Queries

Typical usage includes: tracing a contract back to the requisition that originated it; reconciling requisition approval status against contract creation; and feeding downstream reporting on procurement-to-contract traceability.

SELECT r.requisition_number,
       r.name,
       r.authorization_status,
       r.chr_id,
       r.cle_id
FROM   okc_rel_obj_po_req_headers_v r
WHERE  r.requisition_number = :req_num;

To list all contracts generated from approved requisitions:

SELECT r.requisition_number,
       r.chr_id,
       r.creation_date
FROM   okc_rel_obj_po_req_headers_v r
WHERE  r.authorization_status = 'APPROVED'
ORDER  BY r.creation_date DESC;

Because the view is documented as not implemented, confirm its presence with SELECT * FROM all_views WHERE view_name = 'OKC_REL_OBJ_PO_REQ_HEADERS_V' before deploying dependent queries, and prefer the base relationship table for any customization that must survive patching.