Search Results g_header_out

Overview

PAY_PAYJPSDD_XMLP_PKG is an Oracle Payroll report packaging unit that is generated and maintained by Oracle Reports / Oracle XML Publisher when a report definition is registered and compiled within Oracle E-Business Suite. The naming convention follows the standard EBS pattern in which the package name is derived from the report short name suffixed by _XMLP_PKG. The embedded header comment, $Header: PAYJPSDDS.pls 120.0 2007/12/13 12:07:30 amakrish noship $, indicates that this package supports a report whose source file is PAYJPSDDS.rdf and that it was last revised in late 2007, consistent with the 12.1.1 and 12.2.2 code lines that inherited this object largely unchanged.

The package provides the PL/SQL wrapper that Oracle Reports generates to expose report-level parameters, column values, and formula functions to the report runtime. Its business purpose is therefore tightly bound to the payroll report it underpins — typically a statutory or regulatory output such as a payroll summary, pension or deduction report, or a business-group-scoped statement. The P_* parameter variables carry the runtime inputs supplied at submission (business group, date range, organization, serial number, prepare date, concurrent request ID, and output file name), while the CP_* variables hold computed column/display values for the report layout.

Key Procedures and Functions

The ETRM metadata records no separately documented stored procedures or functions for this package under the 12.2.2 inventory, so descriptions below rely on the source excerpt supplied with the object. The package specification declares the following callable elements:

• BeforeReport — a trigger function returning BOOLEAN, invoked by the Reports engine before report data is fetched; it is used to initialise parameter-derived global state and validate submission inputs.
• AfterReport — a trigger function returning BOOLEAN, invoked after report completion; it handles any post-processing or cleanup logic defined in the report.
• cf_emp_recordformula — a formula column function that computes a per-employee record value, taking total record, assignment, effective date, WP number, and date-of-birth inputs and returning a numeric result.
• CP_*_p accessors — the family of CP_BASIC_PENSION_NUMBER_p, CP_DISQUALIFIED_STATUS_p, CP_DISQUALIFIED_STATUS_CODE_p, CP_WP_STD_MONTHLY_COMP_p, CP_WP_SALARY_p, CP_EMP_FAILURE_ITEM_p, CP_RECORD_NUMBER_p, CP_COUNT_OF_RECORD_p, CP_FD_COUNT_p, CP_FD_SERIAL_NUMBER_p, CP_REPORT_TITLE_p, and CP_MAGFILE_NAME_p. Each returns the current value of its corresponding package-level variable so that the report layout can reference it.

The user's search term, G_HEADER_OUT, identifies a declared global variable of type NUMBER initialised to 0 (line 44). It sits alongside related globals such as G_REC_COUNT, G_COUNT_OF_RECORD, G_FD_COUNT, G_FD_SERIAL_NUMBER, G_MAGFILE_NAME, and the prepare-date component variables, all of which accumulate running totals or carry header-level output data for the report body.

Tables Accessed

No base tables are documented as directly referenced by this package through APPS synonyms in the ETRM 12.2.2 inventory. In the standard EBS Reports model, data retrieval is performed by the query defined inside the .rdf report, not by the generated PL/SQL wrapper. The wrapper package itself is essentially a parameter and state container. Where table access occurs, it is typically indirect — the report query selects from Payroll and HR views such as PER_ALL_PEOPLE_F, PAY_PAYROLL_ACTIONS, PAY_ASSIGNMENT_ACTIONS, and related pay-element or pension structures, depending on the report's specific business rules.

Usage Notes

PAY_PAYJPSDD_XMLP_PKG is not intended to be invoked by application code directly. It is instantiated by the Oracle Reports runtime when the associated concurrent program is launched, or by Oracle XML Publisher when the report is executed in XML mode. The typical flow is: the user submits the report from a Payroll responsibility; the concurrent manager passes the request ID and parameter values; the Reports engine binds those into the P_* package variables; BeforeReport fires; the report query executes; formula columns invoke cf_emp_recordformula; and CP_* accessors supply display values to the layout. The G_HEADER_OUT global, like its sibling globals, is a session-scoped accumulator that exists only for the lifetime of the report run. Customisations should not reference this package directly, as it is automatically regenerated whenever the report is recompiled or migrated, and any manual edits will be overwritten. Teams investigating report output behaviour should instead examine the underlying .rdf definition, the concurrent program registration, and the dependent payroll data, treating this package purely as generated runtime scaffolding.