Search Results ja_jainprrg_xmlp_pkg




Overview
Explore in AI Chat

Overview

The APPS.JA_JAINPRRG_XMLP_PKG package is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. Its naming convention follows the standard Oracle XML Publisher (BI Publisher) report integration pattern: the _XMLP_PKG suffix identifies a package generated to support a concurrent program whose output is rendered through an XML Publisher template. The JA_ prefix indicates that the parent report belongs to the Oracle Japan (JA) localization product family, and the JAINPRRG mnemonic corresponds to a Japanese localization report, most likely a printed invoice, purchasing, or payment-related register report.

The package is classified in ETRM documentation with an API classification of OTHER and the dependency extract confirms its status as VALID in the APPS schema. It depends only on SYS.STANDARD and is referenced by no other packages, confirming it is a leaf-level report package rather than a shared library. Its sole inbound reference is to itself, reflecting the standard XML Publisher package/body pattern where the specification and body call one another. The package encapsulates the data retrieval logic, formula computations, and report lifecycle event handlers required to produce the XML data stream consumed by the associated RTF or eText template.

Key Procedures and Functions

ETRM documents ten program units within this package. They fall into three functional groupings.

  • BEFOREREPORT — Standard XML Publisher before-report trigger; initializes package-level state and session context before the main data query executes.
  • AFTERPFORM — Before-formula trigger invoked after the report's data groups are populated but before template formulas are evaluated; typically used to seed computed values.
  • AFTERREPORT — Standard after-report trigger; performs post-processing, cleanup, or final outputs once all groups have been fetched.
  • CF_PO_NUM_N_RELEASEFORMULA — A column formula that concatenates or formats the purchase order number with its release number for display on the report output.
  • CF_TOTAL_AMOUNTFORMULA — A column formula computing the total amount value printed on the report, aggregating or deriving the figure from retrieved line values.
  • CF_VENDOR_NAMEFORMULA — A column formula that resolves and formats the supplier name for presentation.
  • CF_VENDOR_SITE_CODEFORMULA — A column formula that resolves the supplier site code associated with the transaction and formats it for output.
  • P_ORG_ADDR1VALIDTRIGGER — A validation trigger associated with the organization address line; validates the address element during report processing.
  • G_INVOICEGROUPFILTER — A package-level global variable used as a filter criterion to restrict the report to a specific invoice group.
  • CP_SERIAL_P — A serial-number or sequence parameter/utility used to identify or order report output.

Tables Accessed

Documented references are made through APPS synonyms:

  • FND_CONCURRENT_PROGRAMS — Read to obtain the concurrent program definition, enabling the package to resolve program-level attributes at runtime.
  • FND_CONCURRENT_REQUESTS — Read to capture the current request ID and associated runtime parameters for the executing report.
  • V$DATABASE — Read to capture database identity information for the report header or audit purposes.
  • V$SESSION — Read to obtain the current session identifier and user environment.
  • V$PROCESS — Read to capture operating-system process information for the executing session.

The V$ views and FND concurrent tables are commonly combined in XML Publisher report packages to print database instance, session, and concurrent request identification in the report header or footer, supporting auditability and troubleshooting.

Usage Notes

This package is not intended for direct invocation from forms or custom PL/SQL. It is registered as the data-definition package behind the JAINPRRG XML Publisher concurrent program. At runtime, the concurrent manager executes the program; the generated XML is merged with the report template, and the BEFOREREPORT, AFTERPFORM, and AFTERREPORT triggers fire at their respective lifecycle points. The CF_* formula functions are bound to template data fields, and G_INVOICEGROUPFILTER and CP_SERIAL_P are populated from program parameters. Because no other package references it, changes are isolated to the report itself.