Search Results po_common_xmlp_pkg




Overview
Explore in AI Chat

Overview

PO_COMMON_XMLP_PKG is a small utility package in the APPS schema that provides shared helper logic used by Oracle Purchasing XML Publisher (XMLP) report definitions. The package was authored by DWKRISHN and first created on 26-June-2006, with the source header indicating a last revision of 120.2 dated 03-January-2008 under the "noship" designation. Its documented purpose, as reflected in the source comment block, is simply to expose common declarations consumed by the concurrent programs, report templates, and related PL/SQL packages that make up the Purchasing XML Publisher family.

In the Oracle E-Business Suite 12.1.1 and 12.2.2 architecture, XML Publisher concurrent programs frequently rely on a small compiled package that exposes helper routines callable from within the report's PL/SQL group or from the data template logic. PO_COMMON_XMLP_PKG serves precisely this role for the Purchasing module: it centralizes formatting logic that would otherwise be duplicated across the various PO XMLP report definitions, ensuring consistent output formatting across reports such as purchasing documents, purchase order acknowledgements, and related transactional outputs.

Key Procedures and Functions

The package exposes a single documented public routine, declared as a function returning VARCHAR2. Per the ETRM metadata, no parameter list beyond the documented quantity-precision input is invented here; only the name and purpose are asserted.

  • GET_PRECISION — a function that accepts a quantity precision value and returns a character representation. Its role is to translate a numeric quantity precision into the display format expected by Purchasing XML Publisher output, allowing report templates to consistently render quantity values with the correct number of decimal places. This is a formatting utility rather than a business transaction; it performs no data manipulation and is intended to be called from within report logic.

The absence of additional documented procedures indicates that the package is deliberately minimal. Its value lies in providing a stable, centrally maintained entry point for quantity-precision formatting that the wider Purchasing XMLP code base can depend upon without embedding the same logic in every report.

Tables Accessed

No tables are referenced by this package through APPS synonyms, according to the documented metadata. This is consistent with its role as a pure formatting helper: GET_PRECISION operates on values passed into it by the calling report or package and does not query or update any base or interface table. Consequently, PO_COMMON_XMLP_PKG introduces no SQL dependency of its own and cannot be a source of table-level locking or read consistency issues within the Purchasing XMLP flow.

Usage Notes

PO_COMMON_XMLP_PKG is referenced by 31 other packages in the E-Business Suite, which underscores its role as a widely consumed utility within the Purchasing XML Publisher framework. It is not intended for direct end-user invocation from a form or as a standalone concurrent program; instead, it is compiled into the APPS schema and called programmatically by the XML Publisher reports and supporting packages that need its formatting behaviour.

From a customisation and support perspective, the package should generally be treated as Oracle-owned and not modified. Because so many dependent packages reference it, changes could propagate widely across the Purchasing reporting suite. Administrators investigating report formatting discrepancies — particularly where quantity decimal precision appears inconsistent between PO reports — may find the compiled version and status of PO_COMMON_XMLP_PKG in DBA_OBJECTS relevant, and the package's invalid state after patching is a common cause of XML Publisher program failure. It is version-dependent and is superseded only by Oracle patches, not by customer extension.