Search Results validate_uda




Overview
Explore in AI Chat

Overview

APPS.PON_UDA_PKG is a PL/SQL package in the Oracle E-Business Suite APPS schema that supports the Sourcing and Negotiations modules, specifically the handling of user-defined attributes (UDAs) on auction and negotiation documents. User-defined attributes allow organizations to extend the standard sourcing data model with customer-specific fields. The package provides the runtime plumbing used by Sourcing to import, validate, store, and delete UDA values associated with negotiation headers, items, and bids. In ETRM 12.2.2 the package carries a status of VALID and is classified as an OTHER API rather than a public, supported interface. Within the dependency chain, PON_UDA_PKG sits beneath the negotiation service layer: the Oracle Sourcing UI layer calls PON_UDA_PKG through PO_NEGOTIATIONS_SV1, and the package in turn relies on the Extensibility Framework (EGO) attribute table types such as EGO_USER_ATTR_ROW_TABLE, EGO_USER_ATTR_DATA_TABLE, and EGO_COL_NAME_VALUE_PAIR_TABLE to pass attribute rows and column/value pairs between Sourcing and the extensibility engine.

Key Procedures and Functions

The ETRM documentation lists the following eight procedures and functions in APPS.PON_UDA_PKG:

  • COMPETITIVE_INFO_XDE — Handles competitive-information attribute extraction or export within the UDA processing flow, particularly for attribute values exchanged with external or dependent processes.
  • PON_ADD_ITEM_INFO_XLE — Adds item-level attribute information, translating Sourcing item data into the extensibility structures used for UDA storage.
  • PON_ADDRESSDEF — Manages address-related attribute definitions, allowing address fields to be treated as user-defined attributes on negotiation documents.
  • PON_ADDRESSES_XPD — Processes or populates address attribute data for the negotiation, working with the address definitions resolved by PON_ADDRESSDEF.
  • DELETE_UDA — Removes UDA values, typically invoked when attribute assignments are cleared, changed, or when a negotiation is reset.
  • DEFAULT_NON_RENDER_UDA — Applies default values to UDAs that are not rendered (displayed) on the current page, ensuring non-visible attributes still receive appropriate values.
  • IMPORT_EXCEL_UDA — Supports importing UDA values supplied through an Excel-based upload, mapping spreadsheet columns to attribute definitions.
  • VALIDATE_UDA — Validates attribute values against defined attribute rules and data types before persistence, returning validation outcomes to the calling layer.

Tables Accessed

Through APPS synonyms the package reads and writes several core Sourcing and inventory tables. PON_AUCTION_HEADERS_ALL is the base table for auction and negotiation headers, where header-level attributes are stored. PON_AUCTION_HEADERS_EXT_B and PON_BID_ITEM_PRICES_EXT_B are the extension tables holding header-level and bid-item-price-level UDA values respectively, consistent with the EBS extensibility pattern of separating attribute columns into "_EXT_B" entities. MTL_SYSTEM_ITEMS_TL supplies translated item descriptions and attributes when item-level UDA information is assembled. PLITBLM is a Sourcing internal temporary or lookup table used in the attribute processing path. The package also references the EGO extensibility table types noted above, which are PL/SQL collection types representing user attribute rows, data, and name/value pairs.

Usage Notes

PON_UDA_PKG is not intended for direct customer invocation. It is invoked primarily through the Oracle Sourcing negotiation flow, reached from PO_NEGOTIATIONS_SV1, which serves as the calling service layer for the Sourcing forms and pages. The Excel import path confirms that IMPORT_EXCEL_UDA is exercised from the Sourcing user interface when users upload attribute data. Because the package is documented as an OTHER API, its signatures are not guaranteed by Oracle's public API policy, and customizations should avoid calling it directly; instead, extensions should use the supported Sourcing and extensibility APIs. The package depends on the APPS EGO attribute infrastructure and the STANDARD package, so it requires the Sourcing and Extensibility Framework products to be installed. Any validation or defaulting behavior occurs in the context of the Sourcing transaction, and deletions through DELETE_UDA follow the negotiation lifecycle.