Search Results itg_sp_rel_headers_v




Overview
Explore in AI Chat

Overview

The ITG_SP_REL_HEADERS_V view is a read-only database object owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the ITG — Internet Procurement Enterprise Connector product, the integration layer that synchronizes procurement documents between E-Business Suite and external sourcing or requisitioning systems. As documented in the ETRM repository, the view exists to generate XML at the PO release header level for the "Sync PO Release XML" interface. In practical terms, it flattens one row per purchasing document release, combining header attributes from PO_HEADERS_ALL with release-specific attributes from PO_RELEASES_ALL, and decorating the result with buyer, delivery location, computed release amount, and attachment references. Because the object is a view and not a table, it holds no data of its own; all values are derived at query time from the referenced base objects and from PL/SQL utility functions in the ITG_X_UTILS package.

Underlying Base Objects

The view's defining query joins four principal sources. PO_HEADERS_ALL supplies the header-level context — operating unit, currency, document type, buyer, ship-to location, segment, and free-text comments — while PO_RELEASES_ALL supplies the release number, approval status, approval date, and release identifier. PER_PEOPLE_F (a synonym resolving to the HR person view) is outer-joined on AGENT_ID to resolve the buyer name, and HR_LOCATIONS_ALL is outer-joined on SHIP_TO_LOCATION_ID to resolve the delivery location code. The ETRM metadata additionally lists HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY as referenced packages, which are invoked indirectly through the PER_PEOPLE_F view, and ITG_X_UTILS, which supplies the SUMPOLINELOCS and GETATTACHMENTS functions used in the select list. The join between PO_HEADERS_ALL and PO_RELEASES_ALL is an inner join on PO_HEADER_ID, so only headers that have at least one release are represented. The effective-dated filter NVL(PER.EFFECTIVE_END_DATE, SYSDATE+1) > SYSDATE restricts the person record to the currently active row.

Key Columns

  • PO_HEADER_ID / PO_RELEASE_ID — the primary and foreign key identifiers linking the row back to the purchasing header and release records.
  • PORELEASE — the human-readable release number (PRA.RELEASE_NUM) that identifies the release within the document.
  • POID — the document number (PHA.SEGMENT1), the value users recognize as the purchase order number.
  • POSTATUS — the release authorization status, drawn from PRA.AUTHORIZATION_STATUS.
  • POTYPE — the document type lookup code (PHA.TYPE_LOOKUP_CODE), such as STANDARD or BLANKET.
  • DATETIME_DOCUMENT — the release approved date, used as the document timestamp in the outbound XML.
  • OPERAMT_EXTENDED / OPERAMT_CURRENCY — the release amount calculated by ITG_X_UTILS.SUMPOLINELOCS, paired with the header currency code.
  • BUYERID, DELIVERTO, POENTITY — buyer full name, ship-to location code, and the string form of the operating unit (ORG_ID).
  • TO_PO_INTERNAL, TO_MISC, TO_APPROVER, TO_BUYER, TO_PAYABLES, TO_RECEIVER, TO_SUPPLIER — attachment payloads returned by ITG_X_UTILS.GETATTACHMENTS, keyed to the 'PO_RELEASES' entity type for each attachment category.
  • NOTES and TAXWHEXMPT — free-text header comments and a reserved, currently NULL tax exemption placeholder.

Common Use Cases and Queries

The principal consumer is the Sync PO Release XML concurrent process, which selects from this view to build release header payloads for transmission to the external procurement system. Developers and support analysts also query it directly to audit release status, verify attachment routing, or reconcile calculated release amounts against line-level totals. A typical diagnostic query lists releases for a given document:

SELECT porelease, poid, postatus, datetime_document, operamt_extended, operamt_currency
FROM apps.itg_sp_rel_headers_v
WHERE poid = :p_po_number
ORDER BY porelease;

To review attachments associated with releases in a date range:

SELECT poid, porelease, to_supplier, to_approver, to_receiver
FROM apps.itg_sp_rel_headers_v
WHERE datetime_document BETWEEN :p_from AND :p_to;

Because the select list invokes PL/SQL functions, queries that touch OPERAMT_EXTENDED or any TO_* attachment column execute procedural code per row and should be filtered tightly. Note also that the GETATTACHMENTS calls hard-code the entity name 'PO_RELEASES'; the data returned therefore reflects FND attachment records filed against releases, not against the parent header.