Results for “confirming_order_flag”

50+ results




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

Overview

ITG_PO_HEADER_ARCH_V is an APPS-owned database view within the ITG – Internet Procurement Enterprise Connector product family. It is classified as VALID in the EBS data dictionary and serves a specific integration purpose: it exposes archived purchase order header information in a flattened, XML-friendly shape suitable for mapping at the header level. The view is referenced across Oracle EBS 12.1.1 and 12.2.2 environments where the Internet Procurement Enterprise Connector is deployed to exchange procurement documents between EBS and external systems via XML messaging.

Rather than presenting raw transactional columns, ITG_PO_HEADER_ARCH_V reorganises the header attributes into partner-oriented fields: supplier, buying organisation, bill-to, and buyer details, each with a partner type and one-time flag indicator. This structure aligns with the trading partner model used by the connector, where every document header carries a supplier/sold-to/bill-to triad. Because the view draws from archived PO tables, it supports audit, archival reporting, and outbound message reconstruction where the live PO_HEADERS_ALL row may already have been purged or moved.

Underlying Base Objects

The documented referenced objects span several schemas and include AP_CARDS_ALL, AP_TERMS, FINANCIALS_SYSTEM_PARAMS_ALL, FND_LOOKUP_VALUES_VL, GL_SETS_OF_BOOKS, HR_ALL_ORGANIZATION_UNITS_TL, HR_LOCATIONS_ALL, HR_ORGANIZATION_UNITS_V, PER_ALL_PEOPLE_F, PO_HEADERS_ALL, PO_HEADERS_ARCHIVE_ALL, PO_RELEASES_ARCHIVE_ALL, PO_VENDORS, PO_VENDOR_CONTACTS, and PO_VENDOR_SITES_ALL, together with the packages FND_GLOBAL, HR_API, HR_GENERAL, HR_SECURITY, and POGOT_S.

The view text confirms these relationships: PO_HEADERS_ARCHIVE_ALL supplies the header record (PHA alias), PO_VENDORS provides supplier name, ONE_TIME_FLAG, segment, and payment currency, PO_VENDOR_SITES_ALL supplies supplier address and ECE trading partner location, HR_ALL_ORGANIZATION_UNITS_TL (HOUT) supplies the buying organisation name, HR_LOCATIONS_ALL (HOU_V) supplies buying organisation and bill-to address data, and PER_ALL_PEOPLE_F supplies buyer name and email. The POGOT_S.ECX_GET_TOTAL function computes the order total dynamically from header lines, and HR_GENERAL.GET_WORK_PHONE derives the buyer telephone.

Key Columns

Common Use Cases and Queries

The primary use case is XML payload generation and reconciliation for the Internet Procurement Enterprise Connector. Typical queries select by POID or document number and inspect partner flags, order totals, and buyer contact information for mapping validation or troubleshooting.

  • Retrieve a header snapshot for a specific archived PO:
    SELECT poid, contractb, supp_org_name, supp_otf, order_total FROM apps.itg_po_header_arch_v WHERE contractb = :p_doc_num;
  • Identify one-time suppliers across archived headers:
    SELECT contractb, supp_org_name FROM apps.itg_po_header_arch_v WHERE supp_otf = '1';
  • Report supplier and buying organisation partner identifiers for integration auditing:
    SELECT poid, supplier_partner_id, supplier_partner_id_x, partner_id, partner_id_x FROM apps.itg_po_header_arch_v WHERE creation_date >= :p_from_date;
  • Extract buyer contact data for notification messages:
    SELECT poid, buyer_full_name, buyer_email, buyer_telephone FROM apps.itg_po_header_arch_v WHERE poid = :p_po_header_id;