Search Results pay_payjpnui_xmlp_pkg




Overview
Explore in AI Chat

Overview

APPS.PAY_PAYJPNUI_XMLP_PKG is a PL/SQL package that supports the Oracle Payroll Japanese localization report known as PAYJPNUI, whose internal header identifier is PAYJPNUIS.pls (version 120.0, dated 2007/12/13). The package is defined with AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the invoking session rather than the definer, which is the standard pattern for Oracle E-Business Suite XML Publisher (BI Publisher) report packages generated from concurrent program definitions. Its role is to hold the global variables, substitution values, and formula functions that an XML Publisher report template requires at runtime, and to provide the report-level hooks that the Oracle Reports-to-XML Publisher bridge invokes during execution. In EBS 12.1.1 and 12.2.2 it remains an APPS-owned object classified as OTHER in the ETRM metadata, and it is referenced by no other packages, confirming that it functions as a leaf-level report support unit rather than shared infrastructure.

Key Procedures and Functions

The package declares twelve documented procedures and functions, supported by a set of global package variables. The principal entry points are the report event hooks:

  • BEFOREREPORT — the standard XML Publisher before-report trigger, used to initialize report state and evaluate any parameters required before data retrieval.
  • AFTERPFORM — the after-parameter-form trigger, which runs once the concurrent program's parameter form values have been captured so defaults and derived values can be set.
  • AFTERREPORT — the after-report trigger, used to perform any final cleanup or post-processing after the report data set is produced.
  • CF_DETAILS_DUMMYFORMULA — a dummy formula function that returns a numeric value; such functions exist to satisfy report template placeholders or to drive conditional formatting without affecting output data.

The remaining functions are getter accessors that expose the package's global substitution values to the report template. CP_UI_NUMBER_P, CP_TARGET_DATE_P, CP_DATE_OF_BIRTH_P, CP_QUALIFIED_DATE_P, CP_OUTPUT_DATE_GLOBAL_P, CP_REPORT_TITLE_P, CP_TARGET_DATE_TITLE_P, and CP_NOTE_TITLE_P each return a VARCHAR2 value corresponding to a like-named package variable such as CP_UI_NUMBER, CP_NOTE_TITLE, or CP_OUTPUT_DATE_GLOBAL. The user's search term cp_note_title_p maps directly to the CP_NOTE_TITLE_P getter and its backing variable CP_NOTE_TITLE.

Tables Accessed

The ETRM metadata records no tables referenced through APPS synonyms for this package. Its variables and functions are parameter and formatting oriented; any database access performed on behalf of the report is directed through the XML Publisher query associated with the PAYJPNUI concurrent program rather than being hard-coded in this package body. The numeric identifier globals G_UI_NUMBER_IV_ID and G_QUALIFIED_DATE_IV_ID suggest that lookup values are resolved at runtime through the concurrent program's value sets, not through direct table DML in this unit.

Usage Notes

The package is invoked indirectly whenever the PAYJPNUI Japanese payroll concurrent program is executed. Oracle's report generation framework calls BEFOREREPORT, AFTERPFORM, and AFTERREPORT at the appropriate lifecycle points, then uses the CP_*_P accessor functions to populate template substitution fields. Because the getters carry no parameters and simply return package state, they are safe to call from XML Publisher template expressions. Customizations should avoid modifying this package directly, since it is an Oracle-shipped, header-versioned artifact; extensions should be implemented in a separate custom package or by copying the concurrent program. The package has no inbound dependencies from other packages, so changes to it carry no ripple effect on other EBS code.