Search Results get_primary_telephone_number




Overview
Explore in AI Chat

Overview

APPS.PQP_HROSS_REPORTS is a PL/SQL package belonging to the Oracle HRMS (People Management) reporting infrastructure within Oracle E-Business Suite. Based on the source header signature pqphrossrpt.pkh 120.5, the package is a public specification intended for use by Oracle's seeded reporting and data-template framework. Its primary business function is to serve as the backend engine that supports configurable, user-driven HR reporting, most notably the "Reports and Processes" style extracts that allow an HR administrator to select a business group, person type, organization, payroll, location, and various personal identifiers, and then produce a filtered, sorted dataset from which a report is generated. The package accumulates a large set of lexical reference variables (for example PERSON_TYPE_WHERE, ORGANNIZATION_NAME_WHERE, and PAYROLL_NAME_WHERE) that are assembled into dynamic WHERE and ORDER BY clauses at runtime — an approach typical of Oracle's data-template wrapper design where SQL predicates are built from user parameter selections rather than being hard-coded.

Key Procedures and Functions

Ten documented program units exist in the specification. Their purpose is as follows:

  • BEFORE_REPORT_TRIGGER — The entry point that fires before report generation. It is the procedure most directly associated with initializing the package state and preparing the parameter set that drives the subsequent extraction; the user search term relates to this unit.
  • GENERATE_REPORT — Assembles the final query and produces the report data, acting as the principal driver of the extraction once initialization is complete.
  • COMPARE_VALUES — Performs a comparison between values, supporting the data-match filtering logic that determines whether a record satisfies the selection criteria.
  • GET_MISMATCH_INDICATOR_FLAG — Returns a flag indicating a data mismatch, used to highlight records that deviate from expected or matched values in the report output.
  • RECORD_FILTER — Applies filtering against a record, enforcing the accumulated WHERE conditions against candidate rows.
  • GET_DATE — Returns a date value, typically formatted for report display or for building date-range predicates.
  • GET_COUNT — Returns a count, used to tally matching records; the specification declares a MATCHING_RECORDS_COUNTER variable consistent with this purpose.
  • GET_PRIMARY_TELEPHONE_NUMBER — Retrieves the primary telephone number for a person from contact point data.
  • GET_SECONDARY_TELEPHONE_NUMBER — Retrieves the corresponding secondary telephone number for a person.

The exact parameter signatures are not reproduced here; only the documented purposes are stated.

Tables Accessed

The package references two tables through APPS synonyms:

  • HZ_CONTACT_POINTS — The Trading Community Architecture table storing phone, email, and related contact mechanisms. It is queried to support the telephone-number retrieval functions, and would be joined to a person or party record to obtain the primary or secondary contact number for each reported individual.
  • DUAL — The standard single-row pseudo-table used for scalar evaluations and lightweight lookups such as the date and count helper functions.

The broader person, assignment, payroll, organization, and location data consumed by the report is obtained through joins assembled in the dynamic SQL built by the wrapper rather than through direct table references within this specification.

Usage Notes

This package is invoked as part of the HRMS data-template reporting flow, which in Oracle EBS 12.1.1 and 12.2.2 is typically triggered from the Reports and Processes form or from an associated concurrent program. The BEFORE_REPORT_TRIGGER procedure is called at the start of that flow to initialize the lexical parameters and package variables, after which GENERATE_REPORT produces the dataset. Because ETRM records no other packages referencing PQP_HROSS_REPORTS, it should be treated as a leaf-level utility rather than a shared API. Customizations should not modify this seeded package; instead, extensions should wrap or clone the calling data template, preserving the package as delivered. Any direct invocation in custom code is discouraged, as the package depends on the internal parameter population performed by the standard report trigger sequence.