Search Results po_line_num




Overview
Explore in AI Chat

Overview

APPS.PA_CI_SUPPLIER_DETAILS_V is a Projects (PA) module view in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to support the design of user interface screens that display supplier-related change order or control item ("CI") transaction detail. The view joins supplier change data held in PA_CI_SUPPLIER_DETAILS to the parent control item, the purchasing document, and vendor master data, producing a flattened result set suitable for forms, OAF pages, and concurrent report output. Because the object is a view owned by APPS with a status of VALID, it is queried at runtime rather than stored, and it inherits the security and grants applied to its synonyms and base tables.

A distinguishing structural feature is that the view text is a UNION of two branches. The first branch returns populated purchasing document attributes (PO number, PO line number, PO organization) by joining to PO_HEADERS_ALL and PO_LINES_ALL. The second branch handles supplier detail rows where PO_HEADER_ID IS NULL — that is, change records not yet or not ever associated with a purchase order — and substitutes literal NULL for the PO number, 0 for the PO line number, and 0 for the PO organization id. This design guarantees that every supplier detail transaction appears in the result set regardless of procurement linkage.

Underlying Base Objects

The documented base objects referenced by the view are PA_CI_SUPPLIER_DETAILS (synonym), PA_CI_TYPES_VL (view), PA_CONTROL_ITEMS (synonym), PA_RESOURCE_LIST_MEMBERS (synonym), PA_TASKS (synonym), PO_HEADERS_ALL (synonym), PO_LINES_ALL (synonym), and PO_VENDORS (view). Within the published view text, the driving object is PA_CI_SUPPLIER_DETAILS SI, joined to PA_CONTROL_ITEMS CI on CI_ID and to PO_VENDORS POV on VENDOR_ID. The purchasing join to PO_HEADERS_ALL and PO_LINES_ALL is performed on both the header id and the line id, ensuring the PO line belongs to the referenced header. The remaining documented objects — PA_CI_TYPES_VL, PA_RESOURCE_LIST_MEMBERS, and PA_TASKS — support the broader control item and task context available through these relationships and are commonly accessed alongside the view when building the associated UI.

Key Columns

Common Use Cases and Queries

The principal use case is rendering supplier change order lines on a Projects control item screen, showing the supplier, the purchase order and PO line, the change amount, and the approval status. A frequent ad hoc requirement is locating records by purchase order line number, which maps to the PO_LINE_NUM column. The following query returns all supplier change detail for a given PO line number:

SELECT po_number,
       po_line_num,
       vendor_name,
       change_type,
       change_amount,
       currency_code,
       ci_status,
       project_id
  FROM apps.pa_ci_supplier_details_v
 WHERE po_line_num = :p_line_num
   AND po_number   = :p_po_number;

Because the second UNION branch emits PO_LINE_NUM = 0 and PO_NUMBER = NULL for unlinked supplier details, a filter on a real line number naturally excludes those rows. Analysts should therefore treat PO_LINE_NUM = 0 as "no purchase order association" rather than as a genuine line. A second common pattern aggregates change amounts per vendor or project, and a third validates that every supplier detail row resolves to a control item and vendor, since the inner joins require a matching PA_CONTROL_ITEMS and PO_VENDORS record. When reporting across organizations, PO_ORG_ID should be used for operating unit context, remembering that it is returned as 0 for the no-PO branch.