Results for “pay_people_groups”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PAY_PEOPLE_GROUPS is a Payroll (PAY) module table owned by the HR schema in Oracle EBS 12.1.1 and 12.2.2. It stores people group flexfield information, functioning as the definitional master for People Groups — reusable groupings of assignments, applicants, or employees that drive eligibility, element linking, benefits participation, and payroll processing rules. Because People Groups are defined through a key flexfield, each physical row in PAY_PEOPLE_GROUPS represents one flexfield combination together with the descriptive segments that make it uniquely identifiable.

From a modeling perspective, ETRM's heuristic Data Vault classification for this table is hub-leaning. This designation reflects the table's role as a durable, low-volatility repository of business keys observed and referenced by numerous dependent objects. Analysts designing a warehouse layer over EBS may treat PAY_PEOPLE_GROUPS as the anchor hub for People Group identity, with the referencing tables described below as link and satellite candidates.

The table is central to payroll configuration: any process that must target or exclude a defined population — element eligibility, assignment grouping, benefits plan participation, or vacancy management — resolves through this table.

Key Information Stored

The documented physical schema contains 42 columns. The most significant are:

• PEOPLE_GROUP_ID — the surrogate primary key, enforced by the unique index PAY_PEOPLE_GROUPS_PK. All foreign key relationships point to this column.
• GROUP_NAME — the user-visible name of the people group, commonly the primary display identifier in forms and reports.
• ID_FLEX_NUM — identifies the flexfield structure (key flexfield definition) against which the segment values are validated. This column governs how the SEGMENTn columns are interpreted.
• SEGMENT1 through SEGMENT30 — the flexfield segment values that constitute the people group combination. In practice only a subset is populated, depending on the configured flexfield structure.
• SUMMARY_FLAG — indicates whether the row is a summary (parent) combination or a detail combination.
• ENABLED_FLAG — controls whether the people group is active and selectable for new assignments, eligibility, or element links.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the effective date range during which the people group may be used.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE — standard WHO audit columns.

The surrogate key (PEOPLE_GROUP_ID) should be distinguished from business-key candidates: the flexfield combination formed by ID_FLEX_NUM plus the populated SEGMENT values, and the human-readable GROUP_NAME, are typical natural identifiers used in reporting and integration. The only documented unique index, however, is PAY_PEOPLE_GROUPS_PK on PEOPLE_GROUP_ID.

Common Use Cases and Queries

Typical reporting scenarios include: identifying active people groups for a given date, resolving a People Group ID to its descriptive name for a report, auditing all assignments or element links that reference a specific group, and reconciling eligible populations across payroll and benefits configurations.

List currently active people groups:

• SELECT people_group_id, group_name, enabled_flag, start_date_active, end_date_active FROM pay_people_groups WHERE enabled_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, TRUNC(SYSDATE) + 1);

Resolve the people group for each assignment, joining on the documented FK:

• SELECT a.assignment_id, a.people_group_id, g.group_name FROM per_all_assignments_f a, pay_people_groups g WHERE a.people_group_id = g.people_group_id AND TRUNC(SYSDATE) BETWEEN a.effective_start_date AND a.effective_end_date;

Identify element links targeted at a people group:

• SELECT el.element_link_id, el.people_group_id, g.group_name FROM pay_element_links_f el, pay_people_groups g WHERE el.people_group_id = g.people_group_id;

Because the key flexfield combination is validated, queries that filter on specific SEGMENT values should also constrain ID_FLEX_NUM to the correct structure.

Related Objects

The following objects reference PAY_PEOPLE_GROUPS through documented foreign keys on PEOPLE_GROUP_ID:

• PER_ALL_ASSIGNMENTS_F — links each assignment (or applicant assignment) to a people group; the most frequently joined consumer.
• PAY_ELEMENT_LINKS_F — element eligibility links that may be scoped to a people group.
• BEN_ELIG_PPL_GRP_PRTE_F and BEN_PPL_GRP_RT_F — benefits eligibility and rate configurations keyed to people groups.
• PER_ALL_VACANCIES — vacancy definitions that assign a people group.
• PSP_EFFORT_REPORT_TEMPLATES and PSP_PAYROLL_SUB_LINES — public-sector effort reporting objects referencing people groups.
• PAY_BATCH_ELEMENT_LINKS and PAY_GB_YEAR_END_ASSIGNMENTS — payroll batch and UK year-end processing references.
• HR_PERSON_DEPLOYMENTS, HR_EDW_WRK_ACTVTY_F, and EDW_HR_ASGN_ASSGNMNT_LSTG — HR deployment and E-Business Suite warehouse extracts.
• BEN_CWB_PERSON_INFO and BEN_PL_EXTRACT_IDENTIFIER_F — compensation workbench and plan extraction objects.

Functionally, people group definitions are maintained through the People Groups (key flexfield) window, and the table is consumed indirectly by Payroll, Benefits, and OTL processing flows that resolve populations via PEOPLE_GROUP_ID.