Search Results pon_forms_util_pvt




Overview
Explore in AI Chat

Overview

PON_FORMS_UTIL_PVT is a private (PVT) PL/SQL package in the Oracle E-Business Suite APPS schema that provides the shared utility layer for the Oracle Sourcing (PON) module's form and XML infrastructure. Its header carries the revision marker $Header: PONFMUTS.pls 120.3 2006/03/14, indicating that the package has been stable across the 12.1.1 and 12.2.2 releases. The package exists to support the Oracle Sourcing buyer and negotiation forms, XML publishing of negotiation data, and the retrieval of flexfield, system, and freight-related values that those forms require.

The 12.2.2 ETRM metadata documents 43 procedures and functions within this package. This summary covers the documented metadata items; the user search term "get_freight" corresponds to the documented GET_FREIGHT function, which is included in the package's public interface.

Key Procedures and Functions

  • PRINT_ERROR_LOG / PRINT_DEBUG_LOG — Diagnostic utilities that write error and debug messages, respectively, to the Oracle Sourcing logging framework. They accept a module identifier and a message string.
  • GETSYSTEMDATE / GETSYSTEMNUMBER / GETSYSTEMCHAR — Typed accessors that retrieve system-defined field values (date, number, and character respectively) for a given field code and identifier. These support form field defaulting.
  • GETFLEXINDENDENTVALUE / GETFLEXTBLVALUE / GETFLEXVALUE — Flexfield value resolution helpers. GETFLEXINDENDENTVALUE resolves a value against a named value set; GETFLEXTBLVALUE and GETFLEXVALUE resolve flexfield and mapping-column values for a field code or form field identifier.
  • GENERATE_XMLQUERY / GENERATE_XMLSCHEMA / GENERATE_XML — The XML publishing core. GENERATE_XMLQUERY builds the query statement for a form; GENERATE_XMLSCHEMA produces the XML schema and query; GENERATE_XML produces the XML document for an entity code and primary key, returning the applicable XDO stylesheet code.
  • COMPILE_FORM / GENERATE_FORM_DETAILS — Form metadata management routines that compile form definitions and generate associated detail records.
  • GETDATAENTRYREGIONNAME / GETREADONLYREGIONNAME — Return the region names used for data-entry and read-only display of a given form.
  • GETVALSETQUERYIDORDER — Returns the query statement, order-by clause, and ID-column-existence flag for a named value set, supporting LOV construction.
  • PUBLISHABSTRACT / PERFORMPOSTSAVECHANGES / DELETEFORMFIELDVALUES — Lifecycle utilities covering abstract publishing, post-save processing, and cleanup of form field values.
  • GET_FREIGHT — The documented freight retrieval function, the object matching this search. It is part of the package's utility surface and draws on the freight-related tables listed below.

Tables Accessed

The package reads and writes through APPS synonyms. Freight data is sourced from ORG_FREIGHT_TL (the freight-charge translation table), which supports GET_FREIGHT. Flexfield resolution relies on FND_FLEX_VALUE_SETS, FND_FLEX_VALUES, FND_FLEX_VALUES_TL, FND_FLEX_VALIDATION_TABLES, and EGO_FND_DSC_FLX_CTX_EXT. System and organizational context come from FINANCIALS_SYSTEM_PARAMS_ALL, HR_ALL_ORGANIZATION_UNITS_TL, FND_LANGUAGES, and FND_LOOKUP_VALUES. Sourcing-specific negotiation and auction data reside in PON_AUCTION_HEADERS_ALL, PON_AUCTION_ITEM_PRICES_ALL, PON_AUC_DOCTYPES, PON_AUC_DOCTYPES_TL, and PON_FBO_POSTS. These are read or written to populate form fields, generate XML, and resolve values during negotiation processing.

Usage Notes

PON_FORMS_UTIL_PVT is a private package and is referenced by five other packages, meaning it is normally invoked indirectly through Oracle Sourcing's forms and public APIs rather than called directly by customers. Its XML generation and form compilation routines are most active when negotiation abstracts are published and when XML documents are produced for an auction or negotiation entity. Because the package carries no public API designation, Oracle does not guarantee its signature across releases; customizations should avoid direct invocation. Any custom code that must retrieve freight values should preferably use a supported public API rather than GET_FREIGHT. Diagnostics produced by PRINT_ERROR_LOG and PRINT_DEBUG_LOG appear in the standard Sourcing debug output when logging is enabled.