Search Results pogot_s




Overview
Explore in AI Chat

Overview

POGOT_S is an Oracle Purchasing utility package owned by the APPS schema. Its purpose is narrow and well defined: it calculates the monetary total of a given Purchasing or iProcurement object. The package exposes a single general-purpose computation entry point, GET_TOTAL, together with a supplementary function, ECX_GET_TOTAL, which is tailored to the e-commerce extension (ECX) integration layer used by iProcurement and related self-service flows. The "_S" suffix and the AUTHID CURRENT_USER declaration indicate a shared, invoker-rights utility package rather than a business-event API. The package does not own transactional data; it derives aggregate values from existing Purchasing tables at runtime and returns a numeric result to the caller. Because totals are computed interpretation of header, line, distribution, and currency data rather than stored values, POGOT_S provides a consistent, centralized calculation path that avoids duplicating summation logic across forms, workflows, and integration programs.

Key Procedures and Functions

  • GET_TOTAL — Returns the total value of a specified Purchasing or requisitioning object. The caller supplies an object type code, an object identifier, and a flag requesting whether the result should be expressed in the base (functional) currency. Documented object type codes cover PO Header ('H'), PO Line ('L'), PO Blanket ('B'), PO Planned ('P'), Requisition Header ('E'), Requisition Line ('I'), Contract ('C'), and Release ('R'). The function resolves the appropriate source records for the nominated object and returns the summed amount. When base-currency output is requested, the result is converted from the document currency rather than returned in the transaction currency.
  • ECX_GET_TOTAL — Returns the total for an object in the context of an explicitly supplied PO currency. This variant supports the ECX integration path, where the calling interface already knows the document currency and requires the total expressed accordingly. It parallels the behavior of GET_TOTAL but accepts currency as an input rather than deriving it internally.

The package header additionally documents the object-type-to-ID parameter convention and the boolean base-currency switch, confirming that a single function signature serves all supported document categories rather than separate functions per object type.

Tables Accessed

POGOT_S reads from the core Purchasing and requisitioning base tables through APPS synonyms. PO_HEADERS and PO_HEADERS_ALL supply document-level context, including currency and document type. PO_LINES and PO_LINES_ALL provide line amounts, while PO_LINE_LOCATIONS and PO_LINE_LOCATIONS_ALL contribute shipment-level quantities and pricing relevant to line and release totals. PO_DISTRIBUTIONS and PO_DISTRIBUTIONS_ALL supply accounting distributions used when aggregating amounts attributable to an object. PO_RELEASES and PO_RELEASES_ALL support release-level totals against blanket agreements and contracts. PO_REQUISITION_LINES and PO_REQUISITION_LINES_ALL serve the requisition header ('E') and requisition line ('I') object types. FND_CURRENCIES and FINANCIALS_SYSTEM_PARAMETERS support currency resolution and base-currency conversion, since the calculation must determine the functional currency and any applicable rounding conventions before returning a result.

Usage Notes

POGOT_S is referenced by five other packages, indicating it is invoked as a shared calculation service rather than called directly by end users. Typical invocation occurs from Purchasing and iProcurement forms, from workflow and notification logic that must display a document total, and from custom or extension code that requires an authoritative sum for a PO, release, contract, or requisition. The ECX_GET_TOTAL variant is used where the ECX layer already holds the document currency. Because the package declares AUTHID CURRENT_USER, callers must have the underlying SELECT privileges on the referenced Purchasing tables in their own right. When extending Purchasing logic, developers should call GET_TOTAL rather than replicating summation queries, thereby preserving consistency in currency handling, distribution inclusion, and object-type interpretation across the application.