Results for “people_group”

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

Overview

PER_ALL_ASSIGNMENTS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, belonging to the PER (Human Resources) product family. The ETRM documentation describes its purpose succinctly: it is "used to support user interface." It is not a transactional table but a presentation-layer construct that flattens and decodes employee assignment data so that Oracle Forms, OAF pages, and reporting tools can retrieve human-readable values without embedding multiple joins against the underlying HR and Payroll tables.

Functionally, the view returns one row per employee assignment, driven by the effective date held in the current FND session (FND_SESSIONS.EFFECTIVE_DATE). Because the driving date comes from the session rather than a bind parameter, the view reflects records that are effective as of the session date chosen by the user in the EBS UI. This makes it well suited to interactive screens, but it requires care when used in batch reporting or integration, since results are implicitly filtered by the active session context. Consistent with Oracle's naming conventions for date-tracked HR entities, the view resolves effective-dated rows automatically through the joins to the _F tables and does not expose the underlying EFFECTIVE_START_DATE or EFFECTIVE_END_DATE columns.

Underlying Base Objects

The view text is defined over a set of base tables and supporting objects, most of which are referenced through synonyms in the APPS schema:

• PER_ALL_ASSIGNMENTS_F and PER_ALL_PEOPLE_F — the core date-tracked assignment and person tables. The join is on PERSON_ID, and the view is restricted to ASSIGNMENT_TYPE = 'E' (employee assignments).
• PAY_PEOPLE_GROUPS — supplies GROUP_NAME, joined by a non-enforced outer join (G.PEOPLE_GROUP_ID (+) = A.PEOPLE_GROUP_ID).
• PER_JOBS_TL and PER_GRADES_TL — translated job and grade names, outer-joined on JOB_ID and GRADE_ID respectively and filtered by USERENV('LANG').
• PAY_ALL_PAYROLLS_F — the effective-dated payroll definition, outer-joined on PAYROLL_ID and constrained to the session effective date.
• PER_PERSON_TYPES and PER_PERSON_TYPES_TL — joined on PERSON_TYPE_ID and language, though the translated column is commented out in favor of a function call.
• FND_SESSIONS — the source of SESSION_ID and EFFECTIVE_DATE, which drive the date-range predicates.
• HR_GENERAL and HR_PERSON_TYPE_USAGE_INFO — PL/SQL packages supplying decode functions (DECODE_ORGANIZATION, DECODE_POSITION_LATEST_NAME, GET_USER_PERSON_TYPE).

Key Columns

The view exposes identity, assignment, and descriptive columns:

• ASSIGNMENT_NUMBER, ASSIGNMENT_ID, PERSON_ID — assignment and person identifiers.
• FULL_NAME, ORDER_NAME, USER_PERSON_TYPE — person name and person-type descriptors.
• PAYROLL_ID, PAYROLL — payroll identifier and resolved name.
• PEOPLE_GROUP_ID, PEOPLE_GROUP — the people group identifier and the resolved GROUP_NAME (the column most relevant to the "people_group" search).
• ORGANIZATION_ID, ORGANIZATION — organization identifier and decoded name.
• POSITION_ID, POSITION, JOB_ID, JOB, GRADE_ID, GRADE, LOCATION_ID — assignment attributes and their resolved labels.
• BUSINESS_GROUP_ID, CURRENT_EMPLOYEE_FLAG — business group context and current-employee indicator.

Common Use Cases and Queries

The view is typically queried to obtain assignment data keyed by people group, payroll, or organization without writing manual joins to the effective-dated tables. A representative query filtering on people group is:

• SELECT person_id, full_name, assignment_number, people_group, payroll, organization FROM per_all_assignments_v WHERE people_group = :group_name;
• Reporting current employees: SELECT assignment_id, full_name, job, position FROM per_all_assignments_v WHERE current_employee_flag = 'Y';
• Joining returned rows to other HR tables via PERSON_ID or ASSIGNMENT_ID.

Because the view depends on FND_SESSIONS, queries executed outside an EBS session (for example, from a generic SQL client) may return no rows unless a valid session context exists. For multi-row date-tracked reporting, direct queries against PER_ALL_ASSIGNMENTS_F with explicit effective-date predicates are generally preferred.