Search Results get_business_group_name

Overview

APPS.PAY_PAYUSRRS_XMLP_PKG is a report-support package body that backs the Oracle Payroll "Payroll User Report" (PAYUSRRS) concurrent program, an XML Publisher–based concurrent report delivered as a PL/SQL package. The package implements the data preparation and formula-callout logic required by the underlying Oracle Reports/XML Publisher definition, resolving user-entered report parameters into descriptive display values and supplying inline formula columns referenced by the report layout. The package header is stored under PAYUSRRSB.pls, and the body carries the header comment $Header: PAYUSRRSB.pls 120.0 2007/12/28 06:47:31 srikrish noship $, indicating it is a non-shipped ("noship") customization-era object retained in the E-Business Suite file system.

Its principal responsibility is the BeforeReport trigger, which converts numeric parameter identifiers into human-readable names and applies a diagnostic trace setting before the report query executes. All parameter resolution occurs inside a single PL/SQL block, and the returned boolean controls whether report execution proceeds.

Key Procedures and Functions

• BEFOREREPORT — The entry point for the report's Before Report trigger. It resolves all descriptive parameter values, sets the derived start and end date globals, optionally enables SQL tracing based on the TRACE action parameter, and returns TRUE to allow the report to run.
• GET_BUSINESS_GROUP_NAME — Returns the business group name corresponding to the business group identifier passed into the report. This is the function most commonly referenced by report formulas and by users searching for the business group retrieval logic; the body delegates the actual lookup to HR_REPORTS.GET_BUSINESS_GROUP and assigns the result to the report's business group name parameter.
• ELEMENT_CATEGORYFORMULA — Formula column that derives the display text for an element information category, resolving category codes to their descriptive meaning.
• GRE_NAMEFORMULA — Formula column that returns the name of the tax reporting unit (GRE) associated with the supplied organization.
• CF_CON_DATEFORMULA — Formula column providing a formatted date value used in the report's header or detail section.
• RVALUEFORMULA — General-purpose formula column that resolves a stored lookup or reference value into its printable form.
• AFTERREPORT and AFTERPFORM — Post-processing triggers; AFTERREPORT executes after the report completes, and AFTERPFORM runs after the report parameter form is submitted, each used to finalize report state.
• C_BUSINESS_GROUP_NAME_P, C_REPORT_SUBTITLE_P, C_PERSON_NAME_P, C_CLASSIFICATION_NAME_P, CP_GRE_NAME_P, CP_ASG_SET_NAME_P — Accessor (getter) functions exposing the package's internal character globals to the report layout, covering business group name, report subtitle, person full name, element classification name, GRE name, and assignment set name respectively.

Tables Accessed

• HR_ASSIGNMENT_SETS — Read to translate the assignment set identifier parameter into its assignment set name (CP_ASG_SET_NAME).
• PAY_ELEMENT_CLASSIFICATIONS — Read to resolve the classification identifier into the classification display name.
• PER_ALL_ASSIGNMENTS_F — Joined with PER_PEOPLE_F to derive the person name when the report is driven by assignment number rather than person identifier.

Additional documented reads not listed in the ETRM table inventory include HR_ORGANIZATION_UNITS (GRE name), PER_PEOPLE_F (person full name), PAY_ACTION_PARAMETERS (TRACE setting), and FND_COMMON_LOOKUPS within ELEMENT_CATEGORYFORMULA.

Usage Notes

The package is invoked exclusively by the PAYUSRRS XML Publisher report as part of the concurrent program execution lifecycle; it is not classified as an API and is referenced by no other documented packages. Custom Report Triggers, formulas, or Data Model groups in the report definition reference these functions and getters directly. Because the BeforeReport block wraps all parameter resolution in an exception handler that suppresses errors, a missing or invalid parameter value simply leaves the corresponding display field null rather than aborting the run. Implementations that require stronger validation should intercept at the report or query level rather than relying on this package.