Search Results pon_uda_import_pkg




Overview
Explore in AI Chat

Overview

APPS.PON_UDA_IMPORT_PKG is a PL/SQL package owned by the APPS schema that supports the import of User-Defined Attributes (UDAs) into Oracle E-Business Suite Purchasing. In EBS 12.1.1 and 12.2.2, UDAs extend standard purchasing documents — purchase orders, agreements, and related entities — through the Oracle EGO (Enterprise Governance Object) attribute framework. The package is registered with an API classification of OTHER and is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the definer. Its principal role is to bridge the interface staging tables (the PO_UDA_INTERFACE family) with the EGO attribute template and structure metadata, populating name/value pairs, attribute row tables, and primary key structures that the EGO framework requires to persist imported attribute data.

Key Procedures and Functions

The package exposes 18 documented procedures and functions. The following are documented in the ETRM excerpt and metadata:

  • POPULATE_STRUCTURES — Core routine that assembles the base object name, primary key column/value pairs, attribute name/value pairs, attribute row table, and class code pairs for a given attribute group type and PK values. It drives the structural scaffolding used by downstream EGO processing.
  • POPULATE_REMAINING_ATTRIBUTES — Completes population of attribute name/value pairs and row tables, typically invoked after POPULATE_STRUCTURES to fill attributes not resolved in the initial pass.
  • POPULATE_EMPTY_AGS — Populates empty attribute groups given a template ID, PK pairs, external attribute values, and an optional address lookup type; returns a PO UDA usage object array.
  • EXECUTE_IMPORT_UDA_FUNCTION — Executes the UDA import logic for a specified template and event, exchanging external attribute value pairs and PK column pairs.
  • IMPORT_UDA_ATTRS — Performs the import of UDA attributes themselves.
  • CONSTRUCT_PK_OBJECT — The object most frequently referenced in searches, this routine constructs the primary key object used to identify the target entity during import; it underpins how PK values are assembled and passed through the structure-population routines.
  • HANDLE_ERROR and UPDATE_STATUS — Error handling and status maintenance utilities that manage return status, message counts, and interface status transitions.
  • SET_EXT_ATTR_NAME_VALUE_PAIR and GET_EXT_ATTR_NAME_VALUE_PAIR — Accessor routines for reading and writing external attribute name/value pairs.
  • DEBUG — Diagnostic logging utility.

Tables Accessed

The package references several APPS synonyms. The primary staging tables are PO_UDA_INTERFACE, PO_UDA_INTERFACE_ROW_ID_S, and PO_UDA_INTERFACE_USER_ROW_ID_S, which hold records awaiting import and their surrogate row identifiers. Template configuration is read from PO_UDA_AG_TEMPLATES and PO_UDA_AG_TEMPLATE_USAGES. Attribute and action metadata come from EGO_ACTIONS_B, EGO_ACTION_DISPLAYS_B, and EGO_DATA_LEVEL_B. Descriptive flexfield context information is sourced from FND_DESCR_FLEX_CONTEXTS, FND_DESCR_FLEX_CONTEXTS_TL, FND_DESCR_FLEX_COLUMN_USAGES, and EGO_FND_DSC_FLX_CTX_EXT, with lookup validation via FND_LOOKUP_VALUES. DBMS_SQL and DUAL are used for dynamic SQL and constant evaluation respectively.

Usage Notes

This package is an internal integration and programmatic-interface component. It is typically invoked from purchasing UDA import concurrent programs, from the UDA setup and maintenance forms when users submit attribute imports, or from custom PL/SQL extensions that need to migrate UDA values into the EGO framework. Because it is AUTHID CURRENT_USER and depends on EGO and PO staging structures, it must be called from a session with APPS-level access and appropriate interface records loaded. The presence of NOCOPY OUT parameters on large array types (EGO_COL_NAME_VALUE_PAIR_ARRAY, EGO_USER_ATTR_DATA_TABLE, PO_UDA_USAGE_OBJECT_ARRAY) reflects the bulk nature of the import, and callers should expect return status, error code, message count, and message data conventions on every documented routine. One dependent package references PON_UDA_IMPORT_PKG, confirming its role as a reusable import service rather than a standalone application entry point.