Results for “date_of_birth”

50+ results




Overview
Explore in AI Chat

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

Overview

PER_ASSIGNMENTS_V11 is a VALID Oracle E-Business Suite view owned by the APPS schema and registered under the PER (Human Resources) product family within ETRM 12.2.2. Its documented description states it is "Used to support user interface," identifying it as a UI-oriented construct rather than a general-purpose reporting interface. The view consolidates person and assignment data from the core HR tables — PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, and PER_PERSON_TYPES — and joins them against FND_SESSIONS so that the effective date of the current user session governs the date-tracked rows returned. This design makes the view self-filtering and session-aware: the caller receives the person and assignment records that are effective on the session's effective date rather than a full history. Because the view surfaces APPLICANT_NUMBER, EMPLOYEE_NUMBER, and NPW_NUMBER alongside name and date of birth, it supports forms and self-service pages that must identify a worker regardless of whether that person is recorded as an applicant, an employee, or a non-person worker. All access is read-only, and the object is not a base table for data entry.

Underlying Base Objects

The documented referenced base objects are:

The view text is a UNION of two branches, both restricted to assignment types 'E' (employee) and 'C' (contingent worker) and to rows where POSITION_ID is not null. The first branch excludes assignments whose immediately preceding assignment row already carried the same assignment type and position, preventing duplicate contiguous segments; the second branch applies the package-derived date functions to reconstruct start and end dates.

Key Columns

  • POSITION_ID — the position to which the assignment is attached; only non-null positions qualify.
  • ASSIGNMENT_ID and ASSIGNMENT_TYPE — the assignment identifier and its type, limited to 'E' and 'C'.
  • PERSON_ID, FULL_NAME, BUSINESS_GROUP_ID — core person identification attributes.
  • APPLICANT_NUMBER — the applicant identifier carried on the person record, the attribute prompted by the user's search term.
  • EMPLOYEE_NUMBER and NPW_NUMBER — the employee and non-person-worker numbers for the same person.
  • DATE_OF_BIRTH — birth date from the person record.
  • START_DATE and END_DATE — assignment/position effective dates, the latter computed by PER_GET_ASG_POS.END_DATE.
  • SYSTEM_PERSON_TYPE and USER_PERSON_TYPE — the seeded person type and the session-resolved user person type.

Common Use Cases and Queries

The view is appropriate when a form or concurrent process needs session-effective assignment and position data. To retrieve records by applicant number:

  • SELECT person_id, full_name, applicant_number, employee_number, assignment_id, position_id, start_date, end_date FROM apps.per_assignments_v11 WHERE applicant_number = :applicant_number;
  • SELECT person_id, applicant_number, assignment_id, position_id, user_person_type FROM apps.per_assignments_v11 WHERE business_group_id = :bg_id AND assignment_type = 'E';
  • SELECT COUNT(*) FROM apps.per_assignments_v11 WHERE employee_number = :employee_number AND sysdate BETWEEN start_date AND end_date;

Because results depend on FND_SESSIONS and USERENV('SESSIONID'), queries executed outside an EBS session context may return no rows. For historical or set-based reporting, querying PER_ALL_PEOPLE_F and PER_ALL_ASSIGNMENTS_F directly is generally preferred.