Search Results execute_import_uda_function




Overview
Explore in AI Chat

Overview

APPS.PO_UDA_IMPORT_PKG is a PL/SQL package in Oracle E-Business Suite that supports the importing of User Defined Attributes (UDA) for Purchasing documents. User Defined Attributes extend standard Purchasing entities such as headers, lines, and distributions with customer-configured descriptive flexfield segments and attribute groups. The package provides the programmatic machinery to read attribute definitions from Oracle's attribute-group and action framework, populate the required flexfield structures, and transfer and persist imported UDA values against Purchasing documents. It is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the APPS schema. The package belongs to the Purchasing (PO) product family and is tightly coupled with the EGO extensibility framework and the FND descriptive flexfield APIs.

Key Procedures and Functions

  • POPULATE_STRUCTURES — Builds the internal attribute structures for a given attribute group and transaction context. It accepts a transaction identifier, attribute group type, and primary key values, and returns the base object name, key column/name-value pairs, attribute name-value pairs, attribute row table, and class code name-value pairs, along with standard return status and message outputs.
  • POPULATE_REMAINING_ATTRIBUTES — Completes the attribute name-value and attribute row tables by populating any remaining attributes not yet resolved, ensuring the full attribute set is available for import.
  • POPULATE_EMPTY_AGS — Generates empty attribute groups for a template, accepting the template identifier, key column pairs, external attribute value pairs, and an optional address lookup type, returning usage objects, attribute values, and attribute rows.
  • EXECUTE_IMPORT_UDA_FUNCTION — The central entry point for executing a UDA import for a given template and event. It receives the template identifier and event name and returns the external attribute value pairs, delegating the underlying import, error handling, and status updates.
  • IMPORT_UDA_ATTRS — Performs the actual import of the collected UDA attribute values into the target Purchasing data structures.
  • HANDLE_ERROR — Centralizes error processing, populating the standard return status, message count, and message data outputs.
  • UPDATE_STATUS — Records or refreshes the processing status of the import operation.
  • TRANSFER_UDA_DATA — Moves the imported UDA data into the final destination structures for persistence.

Tables Accessed

The package reads and writes through APPS synonyms. It references EGO_ACTIONS_B, EGO_ACTION_DISPLAYS_B, EGO_DATA_LEVEL_B, EGO_EXTFWK_S, and EGO_FND_DSC_FLX_CTX_EXT to resolve attribute-group definitions, actions, display metadata, and the descriptive flexfield context extension mapping. FND_DESCR_FLEX_COLUMN_USAGES, FND_LANGUAGES, and FND_LOOKUP_VALUES supply flexfield column definitions, language information, and lookup validations. PO_UDA_AG_TEMPLATE_USAGES links attribute-group templates to their usages. The Purchasing layer is represented by PO_HEADERS_DRAFT_ALL, PO_LINES_DRAFT_ALL, PO_LINE_LOCATIONS_DRAFT_ALL, PO_DISTRIBUTIONS_DRAFT_ALL, and the external attribute columns PO_LINES_ALL_EXT_B and PO_LINES_ALL_EXT_TL. Draft tables hold the imported data prior to validation, while the EXT tables store the persisted user-defined attribute values.

Usage Notes

PO_UDA_IMPORT_PKG is an internal implementation package rather than a public API, and is documented as referenced by nine other packages, indicating that it is called principally from higher-level Purchasing and extensibility packages. EXECUTE_IMPORT_UDA_FUNCTION is normally invoked in response to an attribute-group event, such as an import or apply action, triggered from the extensibility framework or a Purchasing form session. Because the package operates on draft Purchasing tables, callers are expected to run the import within a controlled transaction that subsequently validates and commits the affected documents. Custom integrations that need to load UDA values for requisitions and purchase orders generally reach this package indirectly; direct invocation requires fully populated EGO attribute collections and correct template identifiers, and callers must inspect the returned status and message outputs to detect failures.