Search Results get_contactxml

Overview

APPS.PON_DATATEMPLATE_PKG is a PL/SQL package within the Oracle E-Business Suite sourcing and procurement modules (PON — Sourcing). It is defined with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the invoking user rather than the package owner. The package serves as a data template and XML assembly layer for Oracle Sourcing (both Classic and the deeper ETRM integration points), generating structured XML fragments and formatted descriptive values that are consumed by the sourcing user interface, notifications, and printable or exportable documents.

Its central role is to construct XML payloads representing header and line level data, addresses, and contacts, so that downstream consumers (such as Oracle XML Publisher templates, the sourcing negotiation UI, and integration extracts) can render consistent documents. In Oracle EBS 12.1.1 and 12.2.2, this package operates alongside the sourcing negotiation and auction tables, bridging transactional sourcing data with presentation-layer XML.

Key Procedures and Functions

• GET_UDA_HEADER_XML — Returns an XMLTYPE document containing User Defined Attribute (UDA) header information for a negotiation or auction context.
• GET_UDA_LINES_XML — Returns an XMLTYPE document containing line-level UDA information, parameterized by a line identifier.
• GET_ADDRESSXML — Returns a CLOB containing address XML, typically for the negotiation's primary or default address context.
• GET_CONTACTXML — Returns a CLOB of contact XML, providing contact details for document rendering.
• GET_AMD_CONTACTXML — Returns contact XML for amendment scenarios, allowing amended contact data to be represented distinctly.
• GET_AMD_ADDRESSXML — Returns address XML for amendment scenarios, complementing the amended contact function.
• GET_SHIPADDRESSXML — Returns a CLOB of ship-to address XML for a given line, which is the function referenced by the search term "get_shipaddressxml". It resolves the shipping address associated with a specific document line for inclusion in the assembled output.
• GET_FPFOBCODEDES — Returns a VARCHAR2 describing the FOB (Free On Board) code, providing a formatted textual value used in document templates.

The package also exposes a set of package-level variables (auction header identifier, client and server time zones, date format, user view type, trading partner and requested supplier identifiers and names, vendor site identifier, SGD inclusion flag, document amendment flag, and exhibit number) that carry session and document context across these functions.

Tables Accessed

• PON_AUCTION_HEADERS_ALL, PON_AUCTION_HEADERS_EXT_B — Header-level auction and negotiation data, including descriptive flexfield extensions.
• PON_AUCTION_ITEM_PRICES_ALL, PON_AUCTION_ITEM_PRICES_EXT_B — Line and item price data used when assembling line-level XML.
• PO_UDA_AG_TEMPLATES, PO_UDA_AG_TEMPLATE_USAGES — User Defined Attribute template definitions and their usage mappings, driving the UDA XML output.
• EGO_FND_DF_COL_USGS_EXT, EGO_FND_DSC_FLX_CTX_EXT, FND_DESCR_FLEX_COLUMN_USAGES — Descriptive flexfield context and column usage metadata, used to resolve attribute structure and labels.
• DUAL, DBMS_LOB, XMLTYPE — Utility references for singleton queries and for CLOB/XML construction and manipulation.

Usage Notes

PON_DATATEMPLATE_PKG is typically invoked by the Oracle Sourcing negotiation and auction pages, by concurrent programs that generate negotiation documents, and by XML Publisher (BI Publisher) templates that require pre-assembled address, contact, UDA, and line XML. Custom extensions commonly call the individual getter functions directly to retrieve address or contact XML for their own document templates.

Because the package is documented as referenced by zero other packages, it functions as a terminal utility layer called from forms, OAF pages, or custom code rather than as a shared library. Its AUTHID CURRENT_USER declaration means callers must have appropriate privileges on the underlying sourcing tables and EGO/FND flexfield views. The amendment-specific functions (GET_AMD_CONTACTXML, GET_AMD_ADDRESSXML) and the amendment flag variable indicate that the package supports both original and amended document rendering. Functions returning CLOB are intended for large address and contact payloads, while XMLTYPE-returning functions support more structured UDA processing.