Search Results middle_names

Overview

GMS_EMPLOYEES is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GMS (Grants Accounting) product. Its status is VALID in both Oracle EBS 12.1.1 and 12.2.2. The view presents a denormalized, employee-oriented projection of personnel data used across Grants Accounting functionality, exposing the identity, employment, and vendor-related attributes of employees without requiring the caller to join the underlying HR and Payables constructs directly.

Functionally, GMS_EMPLOYEES is a thin pass-through view defined over PA_EMPLOYEES. Rather than storing data itself, it selects the columns required by Grants Accounting logic and reports, including the person identifier, name components, employee number, effective dating, expense check routing, business group, associated vendor, and an active flag. Because it surfaces employee data through a single, stable object, it supports reporting, integration extracts, and internal joins where grant-related transactions must resolve to the responsible employee.

For users searching on "middle_names," this view is a relevant hit: MIDDLE_NAMES is one of the twelve columns exposed, making GMS_EMPLOYEES a convenient source for employee middle-name data alongside the first and last name components, without navigating the full person-name model in HR.

Underlying Base Objects

GMS_EMPLOYEES is defined over PA_EMPLOYEES, the Projects employee view that underpins the Projects and Grants schemas. The ETRM metadata records the following referenced base objects for the 12.2.2 documented view: HR_GENERAL (PACKAGE), HR_PERSON_NAME (PACKAGE), HR_SECURITY (PACKAGE), and PA_EMPLOYEES (VIEW).

• PA_EMPLOYEES (VIEW): The direct source of all columns exposed by GMS_EMPLOYEES. The Grants view is a straight projection of this object.
• HR_PERSON_NAME (PACKAGE): Supplies and formats person-name components, including the middle-name element, that feed the name columns visible through PA_EMPLOYEES and ultimately GMS_EMPLOYEES.
• HR_GENERAL (PACKAGE): Provides core HR business logic and derived attributes used in constructing employee records.
• HR_SECURITY (PACKAGE): Enforces HR security policies, so row visibility through the underlying chain respects the grants and HR security profile applied to the querying user.

Because the view does not add tables of its own, data access and security behavior are inherited from PA_EMPLOYEES and the HR packages behind it.

Key Columns

The view exposes twelve documented columns:

• PERSON_ID: Primary identifier of the employee/person; the principal join key to HR and other person-based tables.
• FULL_NAME: Concatenated display name of the employee.
• EMPLOYEE_NUMBER: The assigned employee number used for payroll and HR reference.
• LAST_NAME, FIRST_NAME, MIDDLE_NAMES: Individual name components; MIDDLE_NAMES is the element of interest for searches involving middle names.
• EFFECTIVE_START_DATE, EFFECTIVE_END_DATE: Effective-dating bounds describing the validity period of the employee record.
• EXPENSE_CHECK_SEND_TO_ADDRESS: The address to which expense reimbursement checks are directed.
• BUSINESS_GROUP_ID: Identifier of the HR business group to which the employee belongs.
• VENDOR_ID: The supplier/vendor record associated with the employee, typically for expense reimbursement.
• ACTIVE: Indicator of whether the employee record is currently active.

Common Use Cases and Queries

GMS_EMPLOYEES is most often used to list active employees, resolve names for grant-related reporting, and locate employees by name components, including middle names. A typical lookup by middle name is:

SELECT PERSON_ID, FULL_NAME, EMPLOYEE_NUMBER, MIDDLE_NAMES
FROM APPS.GMS_EMPLOYEES
WHERE MIDDLE_NAMES LIKE 'A%' AND ACTIVE = 'Y';

Because EFFECTIVE dates and ACTIVE are exposed, reporting can filter to currently valid records. When VENDOR_ID or EXPENSE_CHECK_SEND_TO_ADDRESS is required for reimbursement analysis, GMS_EMPLOYEES provides those attributes in a single query without joining the underlying HR and Payables structures. Queries execute subject to HR security constraints inherited through PA_EMPLOYEES and the referenced HR packages.