Results for “okc_rel_obj_po_headers_v”

4 results




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

Overview

OKC_REL_OBJ_PO_HEADERS_V is a reporting view shipped with the Oracle Contracts Core (OKC) module in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the association between a contract and the purchasing document created from it, resolving the generic relationship record held in the Contracts Core relationship table to the corresponding purchasing document header. In functional terms, the view answers the question: "For this contract, which purchase order was created, what is its description, and what is its current authorization status?"

The view is not a base table and carries no stored data of its own. The ETRM metadata records it as "Not implemented in this database," meaning the view is delivered as a database object definition but is populated only at runtime from the underlying purchasing and contracts tables. This is typical of cross-module reporting views in EBS, which act as a stable, denormalized interface over volatile join logic.

Underlying Base Objects

The view is defined over three underlying objects:

  • OKX_PO_HEADERS_V (HDR) — the purchasing document header view, providing the PO number, description, currency code, authorization status, and the internal identifier ID1.
  • OKC_K_REL_OBJS (REL) — the Contracts Core relationship table that links a contract to an external object. The join is restricted to JTOT_OBJECT1_CODE = 'OKX_PO_HEADERS' and RTY_CODE = 'CONTRACTCREATESPO', isolating the "contract creates purchase order" relationship type.
  • FND_LOOKUP_VALUES (OL) — the lookup table supplying the user-facing meaning of the authorization status, joined on LOOKUP_TYPE = 'AUTHORIZATION STATUS' with VIEW_APPLICATION_ID = 201 and a security group and language filter.

The join path is HDR.ID1 = REL.OBJECT1_ID1, and the relationship is further qualified by CHR_ID, the contract header identifier. Because the view spans OKC and PO, it depends on both modules being installed and on the purchasing header view remaining accessible.

Key Columns

  • PO_NUMBER — the purchase order number (HDR.NAME), the primary human-readable identifier of the created document.
  • PO_DESCRIPTION — the free-text description of the purchase order header. This is the column most commonly targeted by users searching for "po_description," as it returns the descriptive text entered against the purchasing document rather than the contract itself.
  • PO_STATUS — the decoded authorization status (OL.MEANING), translating the raw lookup code into a readable value such as Approved, Incomplete, or Cancelled.
  • CURRENCY — the currency code of the purchase order header.
  • OBJECT1_ID1 — the internal identifier of the related purchasing object, used for programmatic joins back to purchasing tables.
  • JTOT_OBJECT1_CODE — the object type code, constant at 'OKX_PO_HEADERS' for rows returned by this view.
  • CHR_ID — the contract header identifier, the key that ties the row back to the source contract.

Common Use Cases and Queries

Typical scenarios include auditing which purchase orders were generated from a given contract, reporting on purchasing documents that remain in an incomplete or unapproved state, and reconciling contract-to-PO relationships during period-end analysis. A representative query retrieving the PO description for a specific contract is:

  • SELECT chr_id, po_number, po_description, po_status, currency FROM okc_rel_obj_po_headers_v WHERE chr_id = :contract_id;

To locate contracts whose generated purchase orders are not yet approved, filter on the decoded status:

  • SELECT po_number, po_description, po_status FROM okc_rel_obj_po_headers_v WHERE po_status <> 'Approved';

Because the view joins the lookup table with a language and security-group filter, results are automatically returned in the session language and respect lookup security. Queries against this view are read-only and should be tuned with a predicate on CHR_ID or PO_NUMBER, as unrestricted scans over the purchasing header view can be costly in high-volume environments.