Search Results tbl_v1

Overview

PON_PO_INTEGRATION_GRP is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified in the E-Business Technical Reference Manual (ETRM) as a Group ("GRP") API. It is declared with AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking user rather than the definer. The package header carries the revision marker $Header: PONGPOIS.pls 120.0 2005/06/01, indicating it belongs to the Procurement (PON) product family and has been stable across the 12.1.1 and 12.2.2 releases.

The package provides the business logic required to validate and execute the purge of Oracle Purchasing documents that originate from or are integrated with sourcing and auction flows. In practice it answers two questions for the calling application: is it permissible to purge a given purchasing document, and if so, perform the purge. It does not expose document creation or update APIs; its scope is limited to the removal and pre-removal validation of Purchasing records linked to sourcing integration.

Key Procedures and Functions

The ETRM metadata documents two procedures.

• VALIDATE_PO_PURGE — Accepts the standard PL/SQL API argument set (API version, initialization of the message list, commit flag) together with an input record of type PURGE_IN_RECTYPE, and returns a PURGE_OUT_RECTYPE output record. Its purpose is to determine, for each submitted entity, whether purging is permitted. The result is exposed through the purge_allowed table of flags inside the output record.
• PO_PURGE — Uses the same entry parameters and input record but returns no output record. It performs the actual purge of the purchasing entities identified in the input. Standard x_return_status, x_msg_count, and x_msg_data are returned so the caller can inspect success or failure through the FND message stack.

The custom record types PURGE_IN_RECTYPE and PURGE_OUT_RECTYPE, along with the collection types TBL_NUM and TBL_V1, form the interface contract. PURGE_IN_RECTYPE contains an entity_name plus a numeric collection of entity_ids, allowing a caller to submit a set of document identifiers for a named entity type in a single call. The output record contains a parallel collection of single-character flags indicating the purge eligibility of each submitted identifier.

Tables Accessed

The package accesses the following tables through APPS synonyms:

• PON_AUCTION_HEADERS_ALL — auction header records that are subject to sourcing purge logic.
• PON_BID_HEADERS — bid header records associated with the sourcing documents being validated or removed.
• PON_BACKING_REQUISITIONS — the requisitions that back purchasing documents created through the sourcing integration.
• DUAL — used for single-row PL/SQL evaluation within the package body.
• PLITBLM — the standard PL/SQL table used for message handling, supporting the FND_MSG_PUB message stack accessed via the x_msg_count and x_msg_data outputs.

Usage Notes

The package is a server-side API intended for programmatic invocation. It is typically called from concurrent programs, from form-level logic that implements a purge action, or from custom PL/SQL that needs to validate and then remove integrated purchasing documents. Documented references indicate one other package depends on it, so callers should treat the header signature as a stable interface.

Because the package is AUTHID CURRENT_USER, the invoking session must hold the necessary privileges on the underlying PON tables directly. A caller should invoke VALIDATE_PO_PURGE first, inspect purge_allowed for each entity, and only then call PO_PURGE for the identifiers that were approved. Both procedures return standard message-stack data, so the caller is responsible for reading the message list when x_return_status indicates an error, and for clearing the message stack before the next call.