Search Results operamt_extended




Overview
Explore in AI Chat

Overview

APPS.ITG_SP_REL_HEADERS_V is a validity-confirmed database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is registered in FND Design Data under the identifier ITG.ITG_SP_REL_HEADERS_V. Its documented purpose is to generate XML at the Purchase Order release header level for the Sync PO Release XML interface, an integration mechanism that exports release header data from EBS to an external or downstream system. The view therefore sits at the integration boundary rather than in the transactional core: it flattens and renames data drawn from Purchasing base objects into a structure aligned to an XML payload contract. Notably, the view is not referenced by any other database object, which confirms it is a terminal, read-only presentation object consumed by external interface programs rather than by other database logic.

Underlying Base Objects

The documented dependencies identify the base objects over which the view is defined. Transactional sourcing comes from PO_RELEASES_ALL and PO_HEADERS_ALL, respectively the release header and the parent purchase order header. Employee and organizational context is supplied by PER_PEOPLE_F and the HR_PERSON_NAME package for the buyer identity, HR_LOCATIONS_ALL for delivery location details, and HR_SECURITY for access control. HR_GENERAL provides utility lookups, while ITG_X_UTILS is a custom package that supplies the Sync PO Release XML specific derivation and formatting logic. The presence of HR_SECURITY, HR_LOCATIONS_ALL, and PER_PEOPLE_F indicates the view enforces HR organization-level security and resolves the buyer and deliver-to values at query time rather than storing denormalized copies.

Key Columns

The view exposes nineteen columns. The join keys PO_HEADER_ID and PO_RELEASE_ID, together with the numeric PORELEASE, uniquely identify each release line at header level. DATETIME_DOCUMENT carries the document date used in the XML output. OPERAMT_EXTENDED and OPERAMT_CURRENCY together express the extended release amount and its operating currency, the currency attribute that users search for when tracing release-level monetary values in the interface. OPERAMT_CURRENCY is a VARCHAR2(15) field. POID and BUYERID provide the human-readable purchase order number and buyer identifier, while DELIVERTO, POENTITY, POSTATUS, and POTYPE supply the delivery destination, operating entity, document status, and document type used by the receiving system. TAXWHEXMPT indicates tax withholding exemption status. The remaining columns — TO_PO_INTERNAL, TO_MISC, TO_APPROVER, TO_BUYER, TO_PAYABLES, TO_RECEIVER, and TO_SUPPLIER — are routing or distribution attributes populated for the XML message.

Common Use Cases and Queries

Typical usage is diagnostic and integration-oriented: validating the XML payload produced for a release, reconciling currency and extended amounts before transmission, or confirming that HR security filters return the expected buyer records. The canonical query follows the documented column list.

  • SELECT PO_HEADER_ID, PO_RELEASE_ID, OPERAMT_EXTENDED, OPERAMT_CURRENCY, POID, BUYERID, POSTATUS FROM APPS.ITG_SP_REL_HEADERS_V;
  • Filter or aggregate by OPERAMT_CURRENCY to validate multi-currency release populations prior to XML generation.
  • Join the returned PO_HEADER_ID and PO_RELEASE_ID back to PO_HEADERS_ALL and PO_RELEASES_ALL for drill-down into transactional detail.

Because the view depends on HR_SECURITY and other HR objects, results are constrained by the querying user's HR security profile.