Search Results set_uda_attributes_lines

Overview

PO_EDA_DATATEMPLATE_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Enterprise Data Architecture (EDA) layer for Oracle Purchasing and Oracle Advanced Procurement. Its central role is to construct, filter, and return structured data templates — most often XML fragments — that describe procurement documents such as purchase orders, contracts, and sourcing awards. These data templates feed downstream rendering, printing, and electronic document delivery processes, including Oracle XML Publisher extracts and supplier-facing document generation. The package depends on the PO_EDA_MAPPING table, which stores the mapping metadata that drives field-to-template resolution, and it is documented as an OTHER-classified API rather than a formal public interface. In Oracle EBS 12.1.1 and 12.2.2 the package is shipped in a VALID state and is internally referenced by its own package body logic.

Key Procedures and Functions

The package exposes 47 documented procedures and functions. The most significant are the XML builder routines: GET_CONTACTSXML, GET_ADDRESSXML, GET_SHIPADDRESSXML, GET_MOD_ADDRESSXML, GET_SHIPADDRESSXML_BASE, GET_DRAFTS_CONTACTSXML, and GET_DRAFTS_ADDRESSXML assemble contact and address data for headers, lines, and draft documents. The GET_PROCUREMENTINSTVEHICLE3, GET_PRICINGARRANGEMENTBASE, GET_AWARDFEE, and GET_PERFORMANCEINCENTIVE functions resolve commercial attributes such as procurement vehicles, pricing arrangements, award fees, and performance incentives for inclusion in the template output. Supporting lookups include GET_ADDENDAATTACHED, GET_LINEITEMTYPE, and IS_CONTINGENCYCONTRACT, which determine attachment presence, line type classification, and contingency contract status respectively.

Filtering and mutation logic is handled by DOCFILTER and MODFILTER, while AFTERPFORM provides post-form processing behavior. The UDA-related routines — SET_UDA_ATTRIBUTES_HEADER, SET_UDA_ATTRIBUTES_LINES, and SET_UDA_ATTRS_LINE_LOCATIONS — populate user-defined attribute values at the header, line, and line-location levels of the data template structure.

Tables Accessed

The package reads from several functional areas through APPS synonyms. Purchasing mapping metadata is sourced from PO_EDA_MAPPING. Payment terms data comes from AP_TERMS_LINES. Descriptive flexfield support relies on EGO_FND_DF_COL_USGS_EXT, EGO_FND_DSC_FLX_CTX_EXT, FND_DESCR_FLEX_COLUMN_USAGES, FND_FLEX_VALIDATION_TABLES, FND_FLEX_VALUES, and FND_FLEX_VALUE_SETS, enabling the package to resolve flexfield segments and validation values for UDA processing. Document attachments are handled through FND_DOCUMENTS_SHORT_TEXT and FND_LOBS. Account derivation uses GL_CODE_COMBINATIONS. Contract clause and term content is retrieved from OKC_ARTICLES_ALL, OKC_ARTICLE_VERSIONS, OKC_BUS_DOC_TYPES_B, and OKC_BUS_VARIABLES_B. Together these reads supply the values injected into the generated XML templates.

Usage Notes

PO_EDA_DATATEMPLATE_PKG is not a customer-called public API; it is invoked internally by Oracle Purchasing forms, XML Publisher data templates, and the EDA extraction framework whenever a procurement document must be rendered with full contact, address, commercial, and flexfield detail. Because it is referenced by zero other PL/SQL packages, customizations should not depend on it directly. Where extension is required, the recommended approach is to layer logic through the EDA mapping configuration (PO_EDA_MAPPING) rather than modifying the package. Its status remains VALID in both 12.1.1 and 12.2.2, with no documented signature differences between the releases.