Search Results p_data_mismatch_flag




Overview
Explore in AI Chat

Overview

APPS.PQP_HROSS_REPORTS is a PL/SQL package body shipped as part of the Oracle HRMS (Human Resources Management System) self-service reporting layer. In Oracle EBS 12.1.1 and 12.2.2, its principal business function is to provide the server-side logic that supports HR self-service report outputs generated through Oracle Reports. The package encapsulates the trigger logic executed at report run time and a small set of helper routines used to format, filter, and validate the data presented to end users. Its header signature (pqphrossrpt.pkb 120.6) indicates a long-lived component that has remained stable across releases, and the embedded Hr_utility.set_location instrumentation reflects the standard HRMS diagnostic conventions for tracing package execution.

Key Procedures and Functions

The ETRM metadata documents ten public and private program units. The principal routines are described below.

  • BEFORE_REPORT_TRIGGER — Executed before report output is produced. It establishes the runtime context for the report, including date formatting and report-level session state, so that subsequent formatting and filtering logic operates against a consistent environment.
  • GENERATE_REPORT — The primary driver that assembles and returns report content. It orchestrates the invocation of the supporting functions and ensures that output reflects the caller's parameters and filters.
  • COMPARE_VALUES — A comparison function that determines whether two string parameters are equivalent. It normalises inputs by stripping embedded blank spaces before comparison and returns a status indicator ('=' or '<>'). When a mismatch is detected it sets the package-level P_DATA_MISMATCH_FLAG, which downstream logic uses to control report behaviour.
  • GET_MISMATCH_INDICATOR_FLAG — Returns the current value of the mismatch flag set by COMPARE_VALUES, allowing callers to act on detected discrepancies.
  • RECORD_FILTER — Applies record-level filtering, restricting the rows eligible for inclusion in the report based on supplied criteria.
  • GET_DATE — Returns a formatted date value for use in report output.
  • GET_COUNT — Returns a numeric count, typically used to populate summary or aggregate sections of the report.
  • GET_PRIMARY_TELEPHONE_NUMBER and GET_SECONDARY_TELEPHONE_NUMBER — Retrieve the respective telephone numbers associated with a contact, sourcing them from the contact point data described below.

In addition to the named units, the body declares the package-global variable g_debug and the constant g_pkg, used to prefix set_location trace messages.

Tables Accessed

The package references two objects through APPS synonyms. DUAL is used solely as a computational vehicle — the COMPARE_VALUES routine performs REPLACE ... FROM DUAL selections to strip blank characters from the incoming parameters prior to comparison. HZ_CONTACT_POINTS, part of the Trading Community Architecture (TCA) contact model, provides the telephone number data returned by GET_PRIMARY_TELEPHONE_NUMBER and GET_SECONDARY_TELEPHONE_NUMBER. No other base tables are documented as being touched directly, consistent with a package whose role is presentation-oriented rather than transactional.

Usage Notes

Because the ETRM record shows no other packages referencing PQP_HROSS_REPORTS, it is not a shared internal API. It is invoked instead as the PL/SQL library backing HR self-service report definitions executed through Oracle Reports, with BEFORE_REPORT_TRIGGER firing in the report's Before Report trigger and GENERATE_REPORT supplying the report payload. The package is not registered as a concurrent program in its own right. The search term payroll_name_where reflects the operational reality that HR self-service reports frequently require a payroll name or payroll identifier as a filtering predicate; such predicates are applied through RECORD_FILTER and can be validated by COMPARE_VALUES when value matching is required. Administrators inspecting a report's SQL or PL/SQL library will find this package referenced where payroll-scoped selection and contact detail output are needed. Customisations should avoid modifying the seeded body; extensions are better placed in a separate package that calls these routines.