Results for “supp_state”

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

Overview

PO_ECX_HEADER_V is a Purchasing (PO) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents purchase order header information in a flattened, partner-oriented layout designed for the Oracle E-Commerce Exchange / XML Gateway (ECX) message infrastructure. Rather than exposing raw transactional columns, the view projects a purchase order header as a set of trading-partner attributes: supplier organization details, buying-organization details, bill-to and sold-to identifiers, buyer contact data, currency information, and monetary totals. The view is intended to supply the header-level payload consumed by outbound XML documents such as purchase order acknowledgements and related supplier-facing messages, and it is also usable for ad hoc reporting on PO trading-partner context.

Underlying Base Objects

The view is defined over a set of PO and HR objects joined to derive partner and organizational attributes. Documented base objects in ETRM 12.2.2 include PO_HEADERS_ARCHIVE_ALL and PO_RELEASES_ARCHIVE_ALL (synonyms supplying the header/release records), PO_VENDORS and PO_VENDOR_SITES_ALL (views supplying supplier name, payment currency, VAT number, and supplier site address components), HR_ALL_ORGANIZATION_UNITS_TL, HR_ORGANIZATION_UNITS_V, HR_LOCATIONS_ALL, HR_GENERAL, HR_API, and HR_SECURITY (used to resolve buying-organization names, addresses, telephone numbers, and work phone lookups), PER_ALL_PEOPLE_F (buyer full name and e-mail), FND_GLOBAL (session and org context), AP_TERMS and FINANCIALS_SYSTEM_PARAMS_ALL (terms and financials setup), and PO_LOOKUP_CODES (decoded lookup meanings). The packaged function POGOT_S.ECX_GET_TOTAL is invoked to compute the ORDER_TOTAL column, and several HR packages and PO function calls provide derived partner attributes. The joins are largely outer/NVL-guarded, allowing the view to return header rows even when supplier site or org location data is incomplete.

Key Columns

• POID — the PO_HEADER_ID, the primary key of the purchase order header.
• CONTRACTB / TYPE_LOOKUP_CODE — the order number (SEGMENT1) and document type.
• ORDER_TOTAL — computed by POGOT_S.ECX_GET_TOTAL('H', PO_HEADER_ID, CURRENCY_CODE); this is the column referenced by the search term "order_total" and represents the header-level monetary total of the purchase order.
• PO_CURRENCY / SUPP_CURRENCY / BUYING_ORG_CURRENCY / BILLTO_ORG_CURRENCY / BILLTO_ORG_CURRENCY — the document currency and the respective partner currencies (e.g., VENDOR payment currency, financials system parameters).
• SUPPLIER_PARTNER_ID / SUPPLIER_PARTNER_ID_X / SUPP_ORG_NAME / SUPP_OTF / SUPP_PARTNER_TYPE — supplier identifier, ECE location code, vendor name, one-time flag, and the constant 'SUPPLIER' partner role.
• SUPP_ADDR_LINE1..3, SUPP_CITY, SUPP_STATE, SUPP_ZIP, SUPP_COUNTRY, SUPP_PHONE — supplier site address components and concatenated phone.
• BUYING_ORG_NAME / BUYING_ORG_ADDR_LINE1..3 / BUYING_ORG_CITY / BUYING_ORG_COUNTRY / BUYING_ORG_ZIP / BUYING_ORG_PHONE1..3 — buying organization identity and address (role 'SOLDTO').
• BILLTO_ORG_NAME / BILLTO_ORG_ADDR_LINE1..2 / BILLTO_PARTNER_TYPE — bill-to organization identity (role 'BILLTO').
• BUYER_ID / BUYER_FULL_NAME / BUYER_EMAIL / BUYER_TELEPHONE — the agent (buyer) on the header and contact details.
• CREATION_DATE, ACCEPTANCE_REQUIRED_FLAG, ACCEPTANCE_DUE_DATE, SUPPLIER_ORDER_NUM — order metadata carried through for message formatting.

Common Use Cases and Queries

The view is most commonly queried to obtain header-level totals and partner context for XML Gateway messages, or to reconcile PO totals with supplier-facing documents. Because ORDER_TOTAL is derived through POGOT_S, queries should filter by header ID or org rather than aggregating across the whole view. A typical query retrieves the total and currency for a specific order:

SELECT poid, contractb, order_total, po_currency, supp_org_name, buying_org_name FROM apps.po_ecx_header_v WHERE poid = :p_po_header_id;

For reporting on orders by buying organization, restrict by the appropriate partner columns and order number:

SELECT contractb, order_total, po_currency, supplier_order_num FROM apps.po_ecx_header_v WHERE buying_org_name = :p_org AND creation_date >= :p_from_date;

Because the view references archive synonyms and HR security packages, access is subject to HR security profiles and the MO/operating-unit context of the session; results may therefore vary by responsibility and org. It is best suited for point lookups and message population rather than large set-based reporting, where querying PO_HEADERS_ALL directly is generally more efficient.