Search Results pay_paykrhcl_xmlp_pkg




Overview
Explore in AI Chat

Overview

PAY_PAYKRHCL_XMLP_PKG is an Oracle EBS XML Publisher (BI Publisher) report package owned by the APPS schema. It supports the Oracle Payroll legislative reports for China (the "KR" and "HCL" tokens in the name correspond to the payroll legislation and report identifier). The package encapsulates the PL/SQL logic embedded in the XML Publisher data template and report definition: it declares the report-level triggers, resolves user entities, builds concatenated or formatted data values, and exposes the computations that produce the report's output columns. Its 22 documented procedures and functions make it a self-contained report driver rather than a reusable business API. The object is classified as OTHER in ETRM and is not referenced by any other database package, confirming that it exists solely to serve its parent concurrent program and template.

Key Procedures and Functions

The documented subprograms fall into several functional groups.

Tables Accessed

  • FF_USER_ENTITIES — source of user-defined entity values, accessed through GET_USER_ENTITY_ID to bind business group or legislative context.
  • FND_CONCURRENT_REQUESTS — provides the concurrent request context (request ID, parameters, and status) used during BEFOREREPORT initialisation.
  • FND_CURRENCIES — supplies currency precision and format information for SET_CURRENCY_FORMAT_MASK and CF_CURRENCY_FORMAT_MASKFORMULA.
  • HR_ORGANIZATION_INFORMATION — resolves organization-level descriptive and statutory attributes, such as business place codes and registration numbers.
  • PAY_PAYROLL_ACTIONS — the primary payroll data source, supplying assignment-level payroll action and run results that feed the CP_HIA_* and CP_HI_* computation columns.

Usage Notes

The package is invoked by the XML Publisher engine when the associated China payroll report concurrent program runs. Users schedule the report from the Payroll responsibility; the concurrent manager spawns the XML Publisher Java process, which calls BEFOREREPORT, executes the data template's SQL against the tables above, evaluates each CF_* and CP_* formula column, and finally invokes AFTERREPORT. There is no form-based entry point and no direct API exposure. Because the package is owned by APPS and depends only on standard, public APIs and synonyms, it is expected to remain valid across both EBS 12.1.1 and 12.2.2. Customisations should avoid modifying the seeded package body; extensions to the Chinese statutory report should instead be implemented through a copy or an additional template, since the package is tightly coupled to its parent report definition.