Search Results c_employee_name

Overview

The APPS.PER_PERUSCNL_XMLP_PKG package body is the generated PL/SQL library that supports the Oracle HRMS concurrent report PERUSCNL. In Oracle EBS 12.1.1 and 12.2.2, this report is the "US Canadian Employee Report," used to produce a per-employee output for a selected business group and effective date. The package is a classic Oracle Reports 6i XML Publisher (XMLP) integration unit: its role is not to implement business logic in the transactional sense, but to prepare the report's global/placeholder variables, format user-entered parameters, and expose report placeholders to the calling Oracle Reports engine. The single source header comment ($Header: PERUSCNLB.pls 120.1 2008/03/12 ... $) confirms that the file is generated from an Oracle Reports PL/SQL library and shipped under the APPS schema.

Key Procedures and Functions

The ETRM metadata documents 5 callable units in the package body:

• BeforeReport — The Oracle Reports "BeforeReport" trigger function. It transforms the user's session date into the display format 'DD-MON-YYYY', derives the business group name from HR_REPORTS.GET_BUSINESS_GROUP, derives the employee name through HR_REPORTS.GET_PERSON_NAME (populating C_EMPLOYEE_NAME), and conditionally formats the qualifying date parameter into C_QUALIFYING_DATE. This is the unit that answers the user search term c_employee_name.
• AfterReport — A no-op placeholder function that returns TRUE. It exists to satisfy the Oracle Reports "AfterReport" trigger contract; the original calls to HR_STANDARD.EVENT are commented out.
• C_BUSINESS_GROUP_NAME_p — A getter function for the report placeholder C_BUSINESS_GROUP_NAME.
• C_EMPLOYEE_NAME_p — A getter function for the report placeholder C_EMPLOYEE_NAME, the variable the user searched for. It simply returns the value set during BeforeReport.
• C_QUALIFYING_DATE_p — A getter function for the report placeholder C_QUALIFYING_DATE.

These three _p functions are "placeholder accessors" generated by the Oracle Reports XMLP converter so that the report's data model and layout templates can reference the PL/SQL globals by a legal function call.

Tables Accessed

The documented ETRM metadata lists no directly referenced tables via APPS synonyms. All data access is indirect: HR_REPORTS.GET_BUSINESS_GROUP and HR_REPORTS.GET_PERSON_NAME are Oracle HRMS report utility functions that internally resolve the business group and person identifiers against HR core objects (for example PER_BUSINESS_GROUPS, PER_ALL_PEOPLE_F, and their date-tracked equivalents). Because the package itself performs no DML, it carries no insert/update/delete footprint; the driving SQL belongs to the report definition rather than to this package body.

Usage Notes

PER_PERUSCNL_XMLP_PKG is invoked automatically by Oracle Reports when the PERUSCNL concurrent program is run from the Submit Requests form or scheduled by the concurrent manager. There is no documented public API surface and no other package references it (Referenced by 0 other packages), so it should be treated as report-private. Customization should target the report definition or a wrapper concurrent program rather than editing the seeded package body, since the package is regenerated by HRMS patch application and the header revision is version-controlled. In 12.2.2 the same package family continues to ship under the APPS schema with the online patching editioning model applied to the synonym layer, but the package source itself is unchanged from the 12.1.1 revision documented here.