Search Results default_ags_from_usage_object




Overview
Explore in AI Chat

Overview

PON_UDA_PKG is a PL/SQL package body owned by the APPS schema and classified under the ETRM "OTHER" API category. It encapsulates user-defined attribute (UDA) handling for Oracle Purchasing and the Oracle Sourcing (PON) module in Oracle E-Business Suite releases 12.1.1 and 12.2.2. The package provides server-side logic for retrieving and populating descriptive and user-defined attribute content associated with sourcing documents, auction lines, address definitions, and inventory item descriptions. It also supplies import and validation utilities that allow UDA values to be loaded in bulk — typically from Microsoft Excel workbooks — and validated before they are persisted against auction or purchasing records.

The header comment ($Header: PON_UDA_PKG.plb 120.16.12020000.2 2013/05/30) confirms that the package was last versioned in the 12.2 line, and the body is delivered as a wrapped (.plb) deployment artifact, consistent with Oracle's practice for internal APIs. A private constant, g_module_prefix, is defined at the top of the body and is used to build FND_LOG debug messages, indicating that the package is instrumented for diagnostic logging via the FND logging framework.

Key Procedures and Functions

The ETRM metadata documents eight callable units within APPS.PON_UDA_PKG:

  • COMPETITIVE_INFO_XDE — Returns competitive information values, including set-aside status and set-aside percentage. In the visible source these are returned as fixed constants ('SET_ASIDE' and '100'), making this a stub or placeholder procedure.
  • PON_ADD_ITEM_INFO_XLE — Retrieves the extended description (LONG_DESCRIPTION) for a given inventory item and organization, and returns the standard FND_API return status, error code, message count, and message data. It is wrapped in FND_LOG diagnostic logging and uses fnd_msg_pub.Add_Exc_Msg for exception handling.
  • PON_ADDRESSDEF — Handles address definition data, accepting and returning address type, location, address code, contact, and address details. This is the object associated with the "pon_addressdef" search term.
  • PON_ADDRESSES_XPD — Supports the address definition/display path for sourcing and purchasing documents.
  • DELETE_UDA — Removes user-defined attribute records for a given entity.
  • DEFAULT_NON_RENDER_UDA — Applies default values to user-defined attributes that are not rendered on the user interface but must still be populated.
  • IMPORT_EXCEL_UDA — Bulk-loads user-defined attribute values supplied in an Excel workbook format.
  • VALIDATE_UDA — Performs validation of user-defined attribute values prior to save or import.

Tables Accessed

The package references the following tables through APPS synonyms:

  • MTL_SYSTEM_ITEMS_TL — Source of the translated long description used by PON_ADD_ITEM_INFO_XLE.
  • PON_AUCTION_HEADERS_ALL — Stores auction (sourcing) header records whose user-defined attributes are managed by this package.
  • PON_AUCTION_HEADERS_EXT_B — The extension table holding UDA column values for auction headers; populated by IMPORT_EXCEL_UDA and DEFAULT_NON_RENDER_UDA.
  • PON_BID_ITEM_PRICES_EXT_B — Extension table for bid item price UDA content on auction lines.
  • PLITBLM — A PL/SQL index-by table type used as an internal associative array structure for holding collections of UDA values during processing.

Usage Notes

PON_UDA_PKG is an internal Oracle Sourcing/Purchasing API rather than a public, documented interface. It is typically invoked from Oracle Forms client code, from other PL/SQL packages within the PON schema, and from concurrent-program or customization code that needs to read or write UDA content for auctions and sourcing documents. The ETRM metadata records that the package is referenced by one other package, indicating it participates in a dependency chain and should not be modified without assessing upstream impact.

Because the body is shipped wrapped, changes must be made through Oracle-supplied patches or by recompiling an unwrapped custom copy; direct modification is not supported. The inclusion of FND_LOG calls means debug output can be enabled through the standard FND logging profile options during troubleshooting. When calling PON_ADD_ITEM_INFO_XLE or PON_ADDRESSDEF, callers must always inspect the returned x_return_status and message stack, since errors are surfaced through the FND API message framework (G_RET_STS_SUCCESS, G_RET_STS_UNEXP_ERROR) rather than raised exceptions. As with all ETRM-documented PON objects, behavior should be validated against the specific patch level of 12.1.1 or 12.2.2 in use, because procedure signatures and UDA extension table structures vary between releases.