Search Results d_sex




Overview
Explore in AI Chat

Overview

GHR_PERSON_SUMMARY_V is an Oracle E-Business Suite view owned by the APPS schema that presents a consolidated, session-aware snapshot of person and primary assignment information. It is a reporting and integration object rather than a base table, and it is defined in the ETRM metadata for both 12.1.1 and 12.2.2. The view joins person records to their primary assignment, resolves the person's sex code to its descriptive meaning, and filters everything against the effective date of the current user session. Because it returns exactly one primary assignment row per person for the session's effective date, it is well suited to point-in-time headcount, roster, and directory-style reporting.

The name prefix "GHR" reflects its orientation toward global human resources reporting. The view is read-only and inherits the security characteristics of the underlying PER objects, meaning row visibility is ultimately governed by the person security profile and related HR security packages.

Underlying Base Objects

The view is defined over five principal sources joined in its SELECT text:

  • PER_PEOPLE_F (VIEW) — the effective-dated person record, aliased PER.
  • PER_ASSIGNMENTS_F (VIEW) — the effective-dated assignment record, aliased ASG, restricted to primary assignments.
  • PER_ASSIGNMENT_STATUS_TYPES (SYNONYM) — resolves the assignment's status type, aliased AST.
  • HR_LOOKUPS (VIEW) — supplied as HL_SEX to translate the SEX lookup code into a meaning.
  • FND_SESSIONS (SYNONYM) — joined via USERENV('sessionid') to obtain the session effective date.

The ETRM metadata additionally lists HR_API, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY as referenced base objects, reflecting the standard HR API and security infrastructure the view depends on. The join to HR_LOOKUPS is an outer join (denoted by the (+) operator) on LOOKUP_TYPE = 'SEX', so a person is still returned if no lookup meaning exists. Effective dating is enforced on both the person and assignment by comparing SES.EFFECTIVE_DATE against the start and end dates of each record.

Key Columns

Common Use Cases and Queries

The view is typically used for current headcount, roster, and directory reports that need person details paired with the active primary assignment. The filter on PER_SYSTEM_STATUS limits results to ACTIVE_ASSIGN, SUSP_ASSIGN, and ACTIVE_CWK, and the assignment flags restrict rows to primary employee ('E') or contingent worker ('C') assignments, so results represent the primary working relationship for the session date. A representative query returning name, sex description, and job is:

  • SELECT person_id, full_name, d_sex, employee_number, job_id, position_id, location_id FROM apps.ghr_person_summary_v;
  • SELECT full_name, employee_number, d_sex FROM apps.ghr_person_summary_v WHERE business_group_id = :p_bg_id ORDER BY full_name;
  • SELECT COUNT(*) FROM apps.ghr_person_summary_v WHERE per_system_status = 'ACTIVE_ASSIGN';

Because effective dating is anchored to the current FND session, the view returns data "as of" the session effective date and should not be relied upon for historical point-in-time comparisons unless the session date is controlled. Row-level security from HR_SECURITY applies, so accessible rows depend on the user's security profile.