Search Results get_addressxml

Overview

APPS.ICX_DATATEMPLATE_PKG is a server-side PL/SQL package in Oracle E-Business Suite that supplies XML and CLOB data templates for Oracle iProcurement and related Internet Computing Architecture (ICX) purchasing flows. It is defined with AUTHID CURRENT_USER, meaning its unqualified references resolve against the schema of the invoking session rather than the APPS schema owner. The package assembles structured document fragments — addresses, contacts, authorizing officers, funds data, and user-defined attribute (UDA) metadata — that are consumed by data templates and XML publishers used in requisition and purchase-order rendering. It also provides helper logic for descriptive flexfield context and column usage definitions, functions for appropriation and spending-limit derivation, and utilities tied to DD448 (DD Form 448, Military Interdepartmental Purchase Request, or MIPR) templates. The package is therefore part of the document-generation and template-population layer rather than a transactional business API. Its most directly relevant member for the search term "get_addressxml" is the function GET_ADDRESSXML, which returns address content as a CLOB for embedding in generated XML documents.

Key Procedures and Functions

• AFTERPFORM — a form-level trigger function (note the case-insensitive naming of AfterPForm) that returns a Boolean, typically used to initialize package state, including the reqHeaderId global, after a form is entered.
• GET_UDA_ATTR_DESC_SQL — builds a SQL fragment describing a user-defined attribute for a given document type, data type, attribute group, attribute ID, and application/end-user column names; the UDA descriptor is returned as a VARCHAR2.
• GET_UDA_HEADER_XML — returns the UDA header information as an XMLType document.
• GET_ADDRESSXML — returns address information as a CLOB, the function most commonly located through searches for address XML generation in iProcurement/ICX data templates.
• GET_CONTACTSXML — returns contact information as a CLOB for inclusion in generated documents.
• GET_AUTH_OFFICER_XML — returns authorizing officer details as a CLOB.
• GET_APPROPRIATION — derives an appropriation value from a charge account passed as VARCHAR2.
• GET_LIMITSH — derives a spending-limit indicator from a charge account, returning VARCHAR2.
• GET_ADDRESS_FROM_LOCATION — resolves an address from a location identifier supplied as a number.
• GET_FUNDSDATAXML — returns funds data as a CLOB.
• GET_MIPR_ACC_ATTRIBUTES — returns MIPR accounting attributes as a CLOB.
• GET_TEMPLATES_FOR_DD448 and GET_TEMPLATES_FOR_DD448_2 — output the face page template, continuation page template, and data definition values needed for DD448/MIPR document generation via NOCOPY OUT parameters.
• GET_ADDRESS_FROM_UDA_ATTR — resolves an address from a UDA attribute based on requisition header ID, address type, and column name.
• GET_MIPR_ACCEPTANCE_STATUS — returns the MIPR acceptance status for a given requisition header ID.

Tables Accessed

The package reads and writes through APPS synonyms. Requisition and header data come from PO_REQUISITION_LINES_ALL and PO_REQ_HEADERS_EXT_B, which supply line and header context for template rendering. User-defined attribute metadata is drawn from PO_UDA_AG_TEMPLATES and PO_UDA_AG_TEMPLATE_USAGES, while descriptive flexfield structures are read from FND_DESCR_FLEX_COLUMN_USAGES, EGO_FND_DSC_FLX_CTX_EXT, and EGO_FND_DF_COL_USGS_EXT. DUAL supports simple single-row expression evaluation, DBMS_LOB provides large-object manipulation for the CLOB-returning functions, and XMLTYPE provides the XML document type used by GET_UDA_HEADER_XML.

Usage Notes

ICX_DATATEMPLATE_PKG is invoked from Oracle Forms and from XML/data-template generation flows in the ICX and iProcurement stack rather than being called directly by end users. The documented metadata notes it is referenced by one other package and does not itself expose a public API classification. Customizations should treat GET_ADDRESSXML and its companion CLOB/XML functions as read-oriented providers and avoid modifying package state; because the package uses AUTHID CURRENT_USER, callers must ensure appropriate synonyms and privileges are visible in the invoking schema. Package state such as reqHeaderId is set during form initialization via AFTERPFORM.