Results for “selected_person_id”

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

Overview

HR_WORKING_PERSON_LISTS is a Human Resources (PER) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, owned by the HR schema. It holds the list of people that constitute a user's current working list, as consumed by the Line Manager Web pages. In practical terms, the table acts as a transient or semi-persistent cache of the rows a manager has accumulated while browsing, selecting, and acting on their direct or indirect reports within self-service line manager transactions. Each row pairs an owning user (expressed as a person) with a selected person, effectively describing a many-to-many, owner-to-selection membership structure.

Regarding Data Vault modeling, the metadata's heuristic classification is standalone, meaning no foreign-key dependencies were mined from the physical structure. Under a Data Vault lens, however, the natural business key (OWNING_PERSON_ID, SELECTED_PERSON_ID, SELECTED_ASSIGNMENT_ID) suggests this table behaves like a link table, resolving the relationship between an owning person and a selected person/assignment pairing, while the descriptive flags (such as CURRENT_SELECTION and MULTIPLE_SELECTION) carry satellite-like attributes. This is a modeling suggestion only; the documented physical structure remains a standalone, denormalized table with no enforced FK relationships.

Key Information Stored

The table comprises seven documented columns. The surrogate primary key and the business-key candidates are distinguished as follows:

• WORKING_PERSON_LIST_ID — surrogate primary key, enforced by HR_WORKING_PERSON_LISTS_PK. Uniquely identifies each list row.
• OWNING_PERSON_ID — identifies the person (typically the line manager) who owns the working list.
• SELECTED_PERSON_ID — the person who has been added to the owner's working list. This column is central to the user's search term and, together with OWNING_PERSON_ID and SELECTED_ASSIGNMENT_ID, forms the unique business key HR_WORKING_PERSON_LISTS_U1.
• SELECTED_ASSIGNMENT_ID — the assignment context for the selected person. Note the schema documents both a misspelled variant (SELECTED_ASSIGNEMENT_ID) and the correctly spelled SELECTED_ASSIGNMENT_ID; both appear in the column list and should be treated as candidates for the same logical attribute.
• CURRENT_SELECTION — flag or indicator marking whether the row represents the owner's currently active selection during line manager navigation.
• MULTIPLE_SELECTION — indicator supporting scenarios where several people are selected simultaneously for a line manager action (for example, a mass transfer or mass assignment update).

The distinction is important for querying: WORKING_PERSON_LIST_ID is a technical surrogate, whereas the U1 index (OWNING_PERSON_ID, SELECTED_PERSON_ID, SELECTED_ASSIGNMENT_ID) represents the meaningful business key that applications and reports should use to identify a list entry consistently.

Common Use Cases and Queries

Typical uses include diagnosing why a manager sees a particular set of people in a line manager page, auditing who has been added to a working list, and cleaning up stale list rows. A representative query to retrieve all selected people for a given owner is:

• SELECT SELECTED_PERSON_ID, SELECTED_ASSIGNMENT_ID, CURRENT_SELECTION, MULTIPLE_SELECTION FROM HR.HR_WORKING_PERSON_LISTS WHERE OWNING_PERSON_ID = :owning_person_id;
• SELECT WORKING_PERSON_LIST_ID FROM HR.HR_WORKING_PERSON_LISTS WHERE OWNING_PERSON_ID = :p AND SELECTED_PERSON_ID = :s AND SELECTED_ASSIGNMENT_ID = :a; (uses the U1 business key)
• Reporting: counting distinct selected persons per owner, or identifying owners with the largest working lists, supports performance and usage analysis of self-service manager pages.

Related Objects

Because the metadata classifies this table as standalone with no mined FKs, relationships are logical rather than enforced. The most significant related objects and join columns are:

• PER_ALL_PEOPLE_F — joined on PERSON_ID = OWNING_PERSON_ID or SELECTED_PERSON_ID to resolve person names and attributes.
• PER_ALL_ASSIGNMENTS_F — joined on ASSIGNMENT_ID = SELECTED_ASSIGNMENT_ID to obtain assignment and organization context.
• FND_USER / PER_PERSON_TYPES — used indirectly to identify the acting user or person type of the owner.
• HR_WORKING_PERSON_LISTS_PK / _U1 — the indexes implementing the primary and unique business keys.
• Line Manager Web page PL/SQL APIs (e.g., HR_LEARNER or manager self-service list handlers) — the consuming application logic for these rows.