Results for “client_info”

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

Overview

APPS.ICX_EDM_PURCHASE_ORDER_V is a reporting view in the Oracle E-Business Suite Procurement module that exposes a denormalized, presentation-ready picture of purchase orders and purchase agreements. The name prefix ICX indicates its use by the Oracle iProcurement and Internet Procurement (ICX) layer, while EDM refers to the Enterprise Data Model interface used to feed sourcing and procurement dashboards. The view consolidates header-level purchasing attributes, supplier and supplier contact details, buyer identity, currency-formatted order totals, project and task references, and lookup-driven descriptive fields such as authorization status, FOB, freight terms, and closure status into a single row per purchase order distribution.

Its principal role is to support procurement analytics, supplier-facing reporting, and integration payloads where a flat structure is required. Because several descriptive values are resolved through PL/SQL service packages and lookup views rather than stored as plain text, the view shields consumers from the underlying ID-based model and returns display-ready values, which makes it well suited to OBIEE, XML Publisher, and custom concurrent program output.

Underlying Base Objects

The view is defined over transaction tables and supporting lookup and party objects. Core purchasing data originates from PO_HEADERS_ALL (joined as POH), with purchase order distributions drawn from PO_DISTRIBUTIONS_ALL (DIST) and document type classification from PO_DOCUMENT_TYPES_ALL (PDT). PO_RELEASES_ALL is referenced in the metadata, reflecting the view's participation in the release numbering model; the view text returns PO_RELEASE_NUMBER and PO_RELEASE_ID as TO_NUMBER(NULL), confirming that this specific definition is scoped to standard purchase orders and agreements rather than blanket releases.

• Supplier master data: PO_VENDORS (V), PO_VENDOR_SITES_ALL (VS), PO_VENDOR_CONTACTS (VC), and AP_TERMS (AT).
• Location data: HR_LOCATIONS (HRL1 for ship-to, HRL2 for bill-to), resolved through the HR_GENERAL package.
• Lookups and descriptive values: PO_LOOKUP_CODES (POLC, POLC2, POLC3, POLC4) supply AUTHORIZATION_STATUS, FOB, FREIGHT_TERMS, and CLOSURE_STATUS from the displayed_field column.
• Service and utility packages: PO_TOTALS_PO_SV.GET_PO_TOTAL formats the order amount, FND_CURRENCY.SAFE_GET_FORMAT_MASK supplies the currency format mask, PO_INQ_SV.GET_PERSON_NAME returns the buyer name, MRP_GET_PROJECT resolves project and task names, and FND_GLOBAL supplies session context.

The joins are largely equi-joins with one outer join on PO_VENDOR_CONTACTS, allowing orders without a designated supplier contact to still be returned.

Key Columns

• PO_NUM, PO_HEADER_ID, ORDER_DATE, PRINTED_DATE, REVISION_NUM, REVISED_DATE — purchase order identification and lifecycle dates.
• TYPE_NAME — document type (for example Standard Purchase Order or Purchase Agreement), sourced from PO_DOCUMENT_TYPES_ALL.
• AUTHORIZATION_STATUS, CLOSURE_STATUS, FOB, FREIGHT_TERMS — decoded descriptive values from PO_LOOKUP_CODES.
• AMOUNT and CURRENCY_CODE — total order value returned by PO_TOTALS_PO_SV with a currency-aware format mask.
• BUYER_NAME and BUYER_ID — buyer identity resolved via PO_INQ_SV.
• SUPPLIER_NAME, SUPPLIER_ID, SUPPLIER_URL, SUPPLIER_CONTACT_NAME, VENDOR_SITE_ID, VENDOR_SITE_CODE — supplier and site details.
• SHIP_TO_LOCATION, BILL_TO_LOCATION, TERMS_NAME, SHIP_VIA_LOOKUP_CODE — logistics and payment terms.
• PROJECT_ID, TASK_ID and their resolved names — project accounting context from distributions.

Common Use Cases and Queries

Typical usage includes purchasing dashboards, supplier scorecards, open-order extracts, and integration feeds to external procurement systems.

• Listing active purchase orders by supplier with formatted totals.
• Reporting orders by authorization or closure status.
• Extracting project-charged purchase lines for cost analysis.

A representative query is:

SELECT po_num, order_date, type_name, supplier_name, buyer_name, amount, currency_code, authorization_status, closure_status FROM apps.icx_edm_purchase_order_v WHERE order_date >= SYSDATE - 30 ORDER BY order_date DESC;

Because the view aggregates distribution-level rows with DISTINCT, and because it invokes PL/SQL functions in its SELECT list, query performance benefits from filtering on PO_NUM, ORDER_DATE, or SUPPLIER_ID rather than scanning the full result set. The view is read-only and intended for inquiry and reporting, not transactional updates.