Search Results jg_jgzzarin_xmlp_pkg




Overview
Explore in AI Chat

Overview

JG_JGZZARIN_XMLP_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It is registered as a component of the Oracle Financials for the Americas (JG) localization module and is classified as an XML Publisher (XMLP) report package. The object naming convention—*_XMLP_PKG—identifies it as one of the auto-generated or user-maintained packages that act as the report logic and data-definition layer behind an XML Publisher concurrent program. In the Americas localization context, JG objects support country-specific legal and fiscal reporting, including tax, invoice, and localization-driven financial formats.

The package holds status VALID on both EBS 12.1.1 and 12.2.2. It has no downstream dependents—no other package references it—which confirms that its role is confined to its own report definition and is not consumed programmatically elsewhere. Its only documented dependency is on the SYS.STANDARD package.

Key Procedures and Functions

ETRM documents 62 procedures and functions. The most significant are grouped below.

Tables Accessed

The package reads through APPS synonyms:

  • RA_CUSTOMER_TRX — receivables transactions, the primary data source for invoice-level reporting.
  • ZX_PARTY_TAX_PROFILE — party-level tax registration and configuration data.
  • XLE_ETB_PROFILES — legal entity / establishment profiles used for localization reporting.
  • FND_CURRENCIES — currency codes and precision for formatting amounts.
  • FND_LOOKUP_VALUES — lookup codes used for descriptive and status values.
  • DUAL — single-row utility select.

No documented writes to application tables are recorded; processing is read-oriented with status handling routed through standard concurrent mechanisms.

Usage Notes

This package is invoked indirectly by the XML Publisher concurrent program it supports. Users and developers generally never call it directly. It runs in the context of the concurrent manager, driven by report parameters submitted through the standard Oracle EBS request submission screen. The BEFOREREPORT/AFTERREPORT hooks execute automatically at report boundaries, and the CF_* formulas are referenced by name from the report's data template or RTF layout.

Because the package is VALID and referenced by no other packages, it can be modified or regenerated safely without impacting dependent code, provided the associated concurrent program definition and XML template remain synchronized. In 12.2.2, all APPS-side access continues via synonyms, so the underlying JG schema objects must remain valid for the package to compile and execute.