Search Results pa_ci_supplier_details




Overview

The PA_CI_SUPPLIER_DETAILS table is a core data entity within the Oracle E-Business Suite Projects module (PA), specifically for versions 12.1.1 and 12.2.2. It serves a critical function in the Change Management process by capturing and storing the detailed financial and operational impact of change orders (formally known as Control Items) on external suppliers and related purchase orders. This table enables organizations to systematically track how project changes affect procurement commitments, ensuring that supplier contracts and purchase order values are accurately adjusted and audited in alignment with project modifications.

Key Information Stored

The table acts as a junction entity linking change management transactions to procurement data. While a full column list is not provided in the metadata, the documented foreign key relationships define its essential structure. The table stores identifiers that connect a specific change impact to its associated supplier and purchase document. The primary transactional link is the CI_TRANSACTION_ID, which is part of the table's primary key (PA_CI_SUPPLIER_DETAILS_PK). Other crucial stored attributes, as evidenced by the foreign keys, include CI_TYPE_ID (classifying the change), CI_ID (the Control Item or change order itself), CI_IMPACT_ID (the specific impact record), VENDOR_ID (the supplier), PO_HEADER_ID (the purchase order), and PO_LINE_ID (the specific line item on the purchase order). This structure allows for granular tracking of changes down to the individual PO line.

Common Use Cases and Queries

A primary use case is generating reports on the procurement impact of project changes, which is vital for project controllers and procurement managers. For instance, an organization may need to assess all purchase order adjustments resulting from a specific change order or analyze the total financial impact on a particular supplier across multiple projects. Common SQL queries involve joining this table to the related procurement and projects tables. A typical pattern would be to select change order details alongside impacted purchase order and supplier information.

SELECT pcid.ci_id,
       pci.ci_number,
       pcid.vendor_id,
       pov.vendor_name,
       pcid.po_header_id,
       poh.segment1 po_number,
       pcid.po_line_id,
       pol.line_num
FROM pa.pa_ci_supplier_details pcid
JOIN pa.pa_control_items pci ON pcid.ci_id = pci.ci_id
JOIN ap.po_vendors pov ON pcid.vendor_id = pov.vendor_id
JOIN po.po_headers_all poh ON pcid.po_header_id = poh.po_header_id
JOIN po.po_lines_all pol ON pcid.po_line_id = pol.po_line_id
WHERE pcid.ci_id = :change_order_id;

Related Objects

The PA_CI_SUPPLIER_DETAILS table is centrally connected to several key EBS tables through defined foreign key constraints, as documented in the ETRM metadata. These relationships are fundamental for data integrity and application logic.

  • PA_CI_TYPES_B: Joined via PA_CI_SUPPLIER_DETAILS.CI_TYPE_ID to classify the type of change control item.
  • PA_CONTROL_ITEMS: Joined via PA_CI_SUPPLIER_DETAILS.CI_ID to link to the master change order record.
  • PA_CI_IMPACTS: Joined via PA_CI_SUPPLIER_DETAILS.CI_IMPACT_ID to the specific impact record within the change order.
  • PO_VENDORS: Joined via PA_CI_SUPPLIER_DETAILS.VENDOR_ID to retrieve supplier details from the Purchasing module.
  • PO_HEADERS_ALL: Joined via PA_CI_SUPPLIER_DETAILS.PO_HEADER_ID to access the purchase order header information.
  • PO_LINES_ALL: Joined via PA_CI_SUPPLIER_DETAILS.PO_LINE_ID to access the specific purchase order line item details.