Search Results get_release_total

Overview

PO_TOTALS_PO_SV is a server-side PL/SQL specification package owned by the APPS schema in Oracle E-Business Suite. It is classified in the ETRM metadata as an OTHER API, meaning it is not an externally supported public interface but rather an internal utility package used by Purchasing and related modules to compute monetary totals for purchase orders and releases. Its four documented functions return numeric totals derived from transactional and archived purchasing tables, resolving amounts across header, release, and line location levels. The package is declared with AUTHID CURRENT_USER, so all unqualified object references resolve against the privileges of the calling session rather than the package owner.

A recurring design characteristic of PO_TOTALS_PO_SV is the use of PRAGMA RESTRICT_REFERENCES. Each of the four functions carries the WNDS, RNPS, and WNPS constraints, which guarantees that the functions write no database state and read no package or session state. This makes them callable from SQL statements, including SELECT and WHERE clauses, a requirement for reporting views and forms-based queries that must compute totals inline.

Key Procedures and Functions

• GET_PO_TOTAL — Returns the total monetary value of a purchase order identified by its header. It consolidates the amounts associated with the order at the header level.
• GET_RELEASE_TOTAL — Returns the total monetary value of a release (or blanket agreement release) identified by its release identifier. This function is the subject of the common search term get_release_archive_total-related lookups, since it is the non-archive counterpart to the archive variant below.
• GET_PO_ARCHIVE_TOTAL — Returns the total monetary value of an archived purchase order revision. It accepts a header and a revision number and reads the corresponding archived revision rather than the live order.
• GET_RELEASE_ARCHIVE_TOTAL — Returns the total monetary value of an archived release revision. It accepts the release identifier and revision number and resolves the amount from the archived release records. This is the function users frequently reference alongside the get_release_archive_total search term when auditing historical release amounts.

Tables Accessed

The package reads from tables exposed through APPS synonyms. For live data it references PO_HEADERS (order header amounts), PO_LINE_LOCATIONS (shipment and distribution level amounts), and PO_RELEASES (release amounts). For historical and audit contexts it references PO_HEADERS_ARCHIVE, PO_LINE_LOCATIONS_ARCHIVE, and PO_RELEASES_ARCHIVE, which store prior revisions of the live records. FND_CURRENCIES is referenced to support currency-aware computation and rounding so that totals are meaningful across multi-currency purchasing environments. All access is read-only, consistent with the RESTRICT_REFERENCES declarations.

Usage Notes

PO_TOTALS_PO_SV is invoked internally by Purchasing forms, by concurrent programs that generate purchasing reports and audit extracts, and by the eight documented packages that reference it. Because the functions are pure (no side effects) and AUTHID CURRENT_USER, custom code can call them from SQL or PL/SQL provided the caller has the necessary object privileges. Typical use cases include purchase order and release total validation, archived revision comparison for audit trails, and populating report columns where a stored aggregate is not otherwise available.

Consumers should treat the package as internal. If signature changes occur between 12.1.1 and 12.2.2, dependent custom code may fail to compile, so customizations should be validated against each release. When computing archived release values, callers must supply the correct revision number; supplying an invalid revision returns no meaningful total. Because of the WNDS/RNPS/WNPS pragmas, the functions may be embedded directly in SQL without inducing mutating-table or consistency errors.