Search Results primary_employee_flag




Overview

APPS.PSB_POSITION_ASSIGN_EMP_V is a supplementary Oracle EBS view owned by the APPS schema and registered under FND Design Data as PSB.PSB_POSITION_ASSIGN_EMP_V. It belongs to the PSB (Public Sector Budgeting / Position Budgeting) product family and is documented in ETRM for both 12.1.1 and 12.2.2. The view consolidates position assignment records with employee identification attributes, exposing position assignments joined to employee details in a single flattened result set. Its documented purpose is to simplify Oracle Forms coding within the Public Sector Budgeting module; Oracle explicitly warns that the view is not intended for direct customer queries or data modification, and that its definition may change significantly in subsequent minor or major releases.

In practice, the view serves reporting and integration needs where budget analysts, position control officers, or downstream extracts require a denormalized view of which employees occupy which budgeted positions, along with the flag identifying the primary employee on a given position assignment. Because it is a supplementary (Forms-support) view, it should be treated as a read-only convenience interface rather than a stable public API.

Underlying Base Objects

The ETRM dependency documentation states that APPS.PSB_POSITION_ASSIGN_EMP_V references two base tables: PSB_POSITION_ASSIGNMENTS and PSB_EMPLOYEES. The join is driven by the position assignment header, which supplies the assignment identifiers (POSITION_ASSIGNMENT_ID, POSITION_ID, WORKSHEET_ID, DATA_EXTRACT_ID) and effective dating, while PSB_EMPLOYEES supplies the person-level attributes (EMPLOYEE_ID, EMPLOYEE_NUMBER, FULL_NAME, PRIMARY_EMPLOYEE_FLAG). The view is not referenced by any other database object, confirming it is a terminal, Forms-oriented interface rather than a building block for further views.

Key Columns

  • ROW_ID — ROWID of the underlying row, useful for Forms block coordination.
  • POSITION_ASSIGNMENT_ID — Primary identifier of the position assignment record.
  • POSITION_ID — The budgeted position to which the employee is assigned.
  • WORKSHEET_ID and DATA_EXTRACT_ID — Budget worksheet and extract context that scope the assignment.
  • EMPLOYEE_ID, EMPLOYEE_NUMBER, FULL_NAME — Employee identity attributes carried from PSB_EMPLOYEES.
  • PRIMARY_EMPLOYEE_FLAG — The column most commonly searched; indicates whether the employee is the primary occupant of the position assignment.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date-effective range of the assignment.
  • Audit columnsLAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE.

Common Use Cases and Queries

Typical uses include validating that each position has exactly one primary employee, producing roster extracts by worksheet, and reconciling position budgets against staffed assignments.

SELECT position_id, position_assignment_id,
       employee_number, full_name, primary_employee_flag
FROM   apps.psb_position_assign_emp_v
WHERE  primary_employee_flag = 'Y'
AND    SYSDATE BETWEEN effective_start_date
                   AND NVL(effective_end_date, SYSDATE + 1);

Because the object is a Forms supplementary view, any production use should be validated after patching and never subjected to DML.