Search Results cf_count_trigger_nameformula




Overview
Explore in AI Chat

Overview

APPS.PAY_PAYRPHTS_XMLP_PKG is a PL/SQL package that serves as the XML Publisher (BI Publisher) report definition package associated with an Oracle Payroll concurrent program. The XMLP_PKG naming convention identifies packages that are automatically generated by Oracle E-Business Suite when a concurrent program is registered against an XML Publisher data template and template file. In this case the package name and the source header reference to PAYRPHTSS.pls indicate that it underpins a Payroll report — most likely a "Payroll Action/HT S" style report — whose report triggers must be evaluated at runtime.

The package declares a set of public package-level variables that map directly to the report's parameters and to internal control values, and it exposes two report lifecycle functions (BeforeReport and AfterReport) together with two formula functions and two parameter accessor functions. Because the package is declared AUTHID CURRENT_USER, it executes with the privileges of the invoking session rather than the definer, which is standard for generated XML Publisher report packages in the EBS 12.1.1 and 12.2.2 code lines.

Key Procedures and Functions

  • BeforeReport — A function that returns a boolean. It is the standard XML Publisher report trigger invoked immediately before report data is fetched, and is used by the generated package to initialize report-level state and validate execution context.
  • AfterReport — A function returning boolean, invoked after the report output has been produced. It conventionally releases any resources or performs end-of-run cleanup and completion logic for the report.
  • CF_ENABLED_FLAGFormula — A formula function returning a Char value. It supplies the computed value for an "enabled flag" column or control in the report layout, letting the report display a derived status derived from query data.
  • CF_COUNT_TRIGGER_NAMEFormula — A formula function accepting a CS_COUNT_TRIGGER_NAME input and returning a number. This is the specific object referenced by the user search term "cf_count_trigger_nameformula"; it computes a numeric value relating to counting or matching trigger names for the report's action/payroll trigger logic.
  • CP_COUNT_TRIGGER_NAME_p — An accessor function that returns the current value of the package variable CP_COUNT_TRIGGER_NAME (number), used by the report to expose that control value to the data model or layout.
  • CP_STATUS_P — An accessor function returning the CP_STATUS package varchar2 value, exposing the report's status control to the report engine.

Tables Accessed

The only table documented as referenced through APPS synonyms is FND_SESSIONS. This is the Oracle Application Object Library table that tracks active user sessions in an EBS instance. The package reads FND_SESSIONS in connection with its BeforeReport and AfterReport trigger logic, typically to identify or validate the concurrent request's session context and to correlate the report run with the originating EBS session. No payroll or HR transactional tables are documented as direct references for this package; the substantive payroll data is retrieved by the underlying report SQL and XML data template rather than by the PL/SQL wrapper itself.

Usage Notes

PAY_PAYRPHTS_XMLP_PKG is not intended to be called directly from custom forms, concurrent programs, or ad hoc code. It is invoked implicitly by the Oracle XML Publisher engine whenever the associated Payroll concurrent program runs. As the report request executes, the engine calls BeforeReport, evaluates the formula functions and parameter accessor functions as it renders the data template, then calls AfterReport on completion.

The package is documented as referenced by zero other packages, confirming that it sits at the leaf of the dependency chain and acts purely as the report-side wrapper. Customization should not be performed against this generated package body, because it is regenerated whenever the concurrent program definition or XML template is modified; any bespoke logic belongs in a separate custom package or in the underlying report query.