Results for “supplier_site_code”

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

Overview

OKE_DTS_PURCHASING_V is an APPS-owned, VALID database view within the OKC/OKE — Project Contracts product family of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. Its purpose, as documented in the ETRM repository, is to present purchasing data related to contract deliverables. In the Project Contracts data model, deliverables represent the tangible or intangible items a contractor commits to provide under a contract; when those deliverables are fulfilled through procurement activity, the linkage between the deliverable and the associated purchase order must be visible for reporting and integration purposes.

This view bridges that gap. It joins the contracts-side deliverable identifiers (contract header, contract line, deliverable, project, and task) to the purchasing-side documents (purchase order header, line, and shipment) that satisfy them. Quantities ordered, delivered, and cancelled are carried alongside the PO number, line number, shipment number, buyer, need-by date, authorization status, unit of measure, and receiving location. For a procurement manager or contracts analyst, the view answers the operational question: which purchase orders, with which quantities and statuses, are supporting a given contract deliverable?

Because it is a reporting view rather than a transactional table, it is read-only, non-updatable in any meaningful sense, and should be queried rather than manipulated. It also depends on the FND_GLOBAL package for session context and on the PO purchasing synonyms for its row sources.

Underlying Base Objects

The documented base objects fall into three groups:

• Purchasing transaction tables: PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, and PO_DISTRIBUTIONS_ALL. The view drives from PO_DISTRIBUTIONS_ALL (aliased D) and joins upward through PO_LINE_LOCATIONS_ALL (LL), PO_LINES_ALL (L), and PO_HEADERS_ALL (H). The distribution record supplies the deliverable linkage and quantity columns; the header supplies the PO number, authorization status, and agent (buyer); the line and shipment supply line and shipment numbering.
• Reference and HR objects: FND_LOOKUP_VALUES_VL supplies the authorized-status meaning from the 'AUTHORIZATION STATUS' lookup type (view application 201), HR_LOCATIONS_ALL supplies the receiving location code via an outer join on SHIP_TO_LOCATION_ID, and PER_ALL_PEOPLE_F supplies the buyer's full name, constrained to the currently effective person record using date-range logic against SYSDATE.
• Package and additional views: FND_GLOBAL is referenced for session context, while PO_VENDORS and PO_VENDOR_SITES_ALL are listed as referenced objects available to consumers of the view's subject area.

The contracts-side identifiers returned — OKE_CONTRACT_HEADER_ID, OKE_CONTRACT_LINE_ID, and OKE_CONTRACT_DELIVERABLE_ID — originate from the OKC contract tables and are surfaced here through the purchasing distribution linkage.

Key Columns

The view exposes twenty columns, with descriptive names that differ slightly from the underlying expressions:

• K_HEADER_ID, K_LINE_ID, DELIVERABLE_ID — the contract header, contract line, and deliverable identifiers, corresponding to L.OKE_CONTRACT_HEADER_ID, D.OKE_CONTRACT_LINE_ID, and D.OKE_CONTRACT_DELIVERABLE_ID.
• PROJECT_ID, TASK_ID — the project and task to which the deliverable is attributed.
• PO_HEADER_ID, PO_LINE_ID, PO_LINE_LOCATION_ID — surrogate keys for the purchasing document, line, and shipment.
• PO_NUMBER, PO_LINE_NUMBER, PO_SHIPMENT_NUMBER — the human-readable document, line, and shipment references (H.SEGMENT1, L.LINE_NUM, LL.SHIPMENT_NUM).
• QUANTITY_ORDERED, QUANTITY_DELIVERED, QUANTITY_CANCELLED — the core procurement quantities from the distribution.
• UOM — unit of measure lookup code for the ordered quantity.
• BUYER — full name of the purchasing agent from PER_ALL_PEOPLE_F.
• PO_NEED_BY_DATE — the shipment need-by date.
• STATUS — the PO authorization status meaning; where the header status is null, the view defaults the lookup code to 'INCOMPLETE'.
• RECEIVING_LOCATION — the ship-to location code, returned via outer join and therefore potentially null.

Common Use Cases and Queries

Typical uses include deliverable fulfilment tracking, contract-to-PO reconciliation, and buyer workload reporting. The following query lists all POs supporting a specific contract deliverable:

SELECT po_number, po_line_number, po_shipment_number, quantity_ordered, quantity_delivered, quantity_cancelled, uom, status, buyer, po_need_by_date
FROM apps.oke_dts_purchasing_v
WHERE deliverable_id = :p_deliverable_id
ORDER BY po_number, po_line_number, po_shipment_number;

A second pattern aggregates ordered versus delivered quantities by contract header and status, useful for open-commitment analysis:

SELECT k_header_id, status, SUM(quantity_ordered) ordered_qty, SUM(quantity_delivered) delivered_qty
FROM apps.oke_dts_purchasing_v
GROUP BY k_header_id, status;

Because the view restricts the buyer join to currently effective person records, queries should not be used to reconstruct historical buyer assignments. For pipeline or commitment reports, filter on STATUS to exclude incomplete or cancelled authorization states, and apply NVL handling to RECEIVING_LOCATION where shipments may not specify a ship-to location.