Search Results gender_code

Overview

The view APPS.HRIFV_US_EMPASGDTL_EMPXASG is a Human Resources Intelligence (HRI) reporting object shipped with Oracle E-Business Suite. It is owned by the APPS schema and carries a VALID status in releases 12.1.1 and 12.2.2. The object is a denormalized reporting view that joins person (employee) records against their assignment records, presenting one row per effective-dated employee/assignment combination. Its stated purpose is to surface workforce analytics data — demographic attributes, personal identifiers, and assignment-level context — in a form suitable for Oracle HRMS Intelligence dashboards, Discoverer workbooks, and ad-hoc HR reporting.

The view text is an outer-projecting SELECT over PER_ALL_PEOPLE_F (aliased PEO) and PER_ASSIGNMENTS_F (aliased ASS), with effective dates collapsed via GREATEST for record start and LEAST for record end. Descriptive values stored as lookup codes are translated into display text through the HR_BIS.BIS_DECODE_LOOKUP package function. The view is therefore the reporting layer that transforms raw HRMS code values into readable attributes.

Underlying Base Objects

The documented base objects reveal the join topology:

• PER_ALL_PEOPLE_F — the primary person record supplying demographic and personal attributes.
• PER_ASSIGNMENTS_F — the effective-dated assignment providing assignment start/end dates.
• PER_BUSINESS_GROUPS — supplies BUSINESS_GROUP_NAME via BGRT.
• PER_PERIODS_OF_SERVICE — service history context.
• PER_ASSIGNMENT_STATUS_TYPES, _TL, PER_ASS_STATUS_TYPE_AMENDS, _TL — assignment status and amendment lookups.
• HR_ALL_ORGANIZATION_UNITS_TL — organization name resolution.
• HR_BIS, HR_GENERAL, HR_SECURITY, FND_DATE — packages for lookup decoding, security predicates, and date handling.

HR_SECURITY is significant: it enforces the security profile applied to the querying user, restricting rows by business group and organization access.

Key Columns

• BUSINESS_GROUP_NAME, EMPLOYEE_NAME, EMPLOYEE_NUMBER — identity and organizational scoping.
• RECORD_START_DATE / RECORD_END_DATE — the intersection of the person and assignment effective ranges.
• GENDER — decoded from PEO.SEX using HR_BIS.BIS_DECODE_LOOKUP('SEX', …); this is the column most commonly targeted when searching for gender_code.
• DATE_OF_BIRTH, MARITAL_STATUS, NATIONALITY, TOWN_OF_BIRTH, COUNTRY_OF_BIRTH — decoded demographic attributes.
• REGISTERED_DISABLED, SECOND_PASSPORT, MAIL_DESTINATION — YES_NO and HOME_OFFICE decodes.
• EMAIL_ADDRESS, NATIONAL_IDENTIFIER, APPLICANT_NUMBER — contact and identification data.
• FTE, WORK_SCHEDULE, OFFICE_NUMBER, MAILSTOP — assignment/work context.

Common Use Cases and Queries

Typical usage includes workforce diversity reporting, headcount demographics, and employee directory extracts. Because GENDER exposes the decoded SEX lookup rather than the raw code, queries seeking gender_code should filter on the decoded value or join to FND_LOOKUP_VALUES directly.

Sample query returning gender distribution by business group:

• SELECT business_group_name, gender, COUNT(*) FROM apps.hrifv_us_empasgdtl_empxasg WHERE record_end_date >= SYSDATE GROUP BY business_group_name, gender;

Employee demographic extract scoped to active records:

• SELECT employee_number, employee_name, gender, date_of_birth, nationality FROM apps.hrifv_us_empasgdtl_empxasg WHERE record_start_date <= SYSDATE AND NVL(record_end_date, SYSDATE) >= SYSDATE;

All access is subject to HR_SECURITY, so results reflect the querying user's security profile across both 12.1.1 and 12.2.2.