Search Results p_output_new_hire_null

Overview

APPS.PER_PERUSHIR_XMLP_PKG is the generated PL/SQL package body that backs the Oracle HRMS "New Hire Report" (PERUSHIR) concurrent program. As with all XML Publisher report packages in Oracle E-Business Suite, the package is produced automatically by the XML Publisher (BI Publisher) concurrent program definition when the report is registered and compiled. Its primary responsibility is to satisfy the data model contract expected by the XML Publisher engine: a BEFORE REPORT trigger, a set of formula columns invoked during row rendering, group filters applied to repeating data groups, and AFTER REPORT/AFTER FORM triggers that perform any final cleanup or status updates.

The package is documented with an API classification of OTHER and is owned by APPS. It references standard HRMS base tables via the APPS synonyms, and is not referenced by any other package (0 dependents), confirming its role as a top-level, report-specific artifact rather than a shared utility. The report is used to produce a listing of newly hired employees, typically for regulatory or compliance reporting (for example, new hire state reporting where different states impose different data requirements).

Key Procedures and Functions

The documented 30 program units include the standard XML Publisher report lifecycle entry points and per-column formula functions:

• BEFOREREPORT — the pre-report trigger. It resolves business group name, medical availability flag, tax unit organization name, and state name into package-level globals, normalizes the report mode, sets a report date, and evaluates state codes to set internal flags used to conditionally display sections of the report.
• AFTERREPORT and AFTERPFORM — post-processing triggers invoked after the report data model completes and after the report form is run.
• BETWEENPAGE — formatting logic applied between report pages.
• C_EMPLOYEE_ADDRESSFORMULA — returns a formatted employee address for a given person.
• C_CONTACT_NAMEFORMULA, C_CONTACT_TITLEFORMULA, C_CONTACT_PHONEFORMULA — resolve the name, title, and phone of a new hire contact.
• C_SALARYFORMULA — formats the salary value presented for the new hire.
• C_TAX_UNIT_ADDRESSFORMULA — returns the address of the tax unit organization.
• G_TAX_UNIT_HEADERGROUPFILTER and G_NEW_HIRESGROUPFILTER — group filters that control which rows are emitted for the tax unit header and new hire data groups.
• P_UPDATE_STATUS — updates the report status, typically for audit or re-run tracking.
• P_OUTPUT_NEW_HIRE_NULL — controls output when no new hire records are found, driving the "no data" condition of the report.
• Getter functions C_BUSINESS_GROUP_NAME_P, C_REPORT_SUBTITLE_P, C_TAX_UNIT_P, C_STATE_NAME_P, C_MEDICAL_AVAIL_P, and C_END_OF_TIME_P expose package globals set in BEFOREREPORT to the XML template.

Tables Accessed

The package reads from standard HRMS tables resolved through APPS synonyms, including HR_LOCATIONS_ALL (employee and tax unit addresses), HR_SOFT_CODING_KEYFLEX (key flexfield values used in assignment coding), PER_ALL_ASSIGNMENTS_F and PER_ALL_PEOPLE_F (the current effective assignments and person records for new hires), PER_JOBS (job information), and PER_PERIODS_OF_SERVICE (hire and period dates). All access is read-oriented, supporting the report data model; the only write activity is the status update performed by P_UPDATE_STATUS.

Usage Notes

The package is invoked exclusively by the XML Publisher/BI Publisher runtime when the PERUSHIR concurrent program is submitted; it is not designed to be called directly by application forms or custom PL/SQL. Because it is regenerated whenever the report definition is updated in the XML Publisher administrator or when the concurrent program is recompiled, customizations should not be applied directly to the package body. Any behavior change, such as suppressing output when no new hires exist (via P_OUTPUT_NEW_HIRE_NULL) or altering state-specific logic in BEFOREREPORT, should instead be implemented by redefining the report data template/query or by wrapping the report in a custom concurrent program. The absence of dependents confirms that modifications here are isolated to PERUSHIR itself.