Search Results psb_position_assign_element_v

Overview

The PSB_POSITION_ASSIGN_ELEMENT_V view is a reporting and integration object within the Public Sector Budgeting (PSB) module of Oracle E-Business Suite, defined in the APPS schema. It presents position assignment records that specifically relate to pay elements — the compensation building blocks (such as salary, allowances, and rates) attached to a position's assignment. By restricting its driving query to ASSIGNMENT_TYPE = 'ELEMENT', the view isolates the element-driven component of position assignments, distinguishing it from other assignment types such as distribution lines or account-based assignments.

In the context of ETRM 12.1.1 and 12.2.2, this view serves as the primary read interface through which budget planners, reports, and downstream integrations examine how pay elements are configured against positions within a worksheet. The inclusion of the ELEMENT_VALUE_TYPE column makes the view particularly relevant for searches concerning how an element's value is characterized — for example whether it is expressed as a rate, a percentage, a fixed amount, or an override — and how that type governs subsequent budget calculation logic.

Underlying Base Objects

The view is defined over three PSB objects using an outer-join construction:

• PSB_POSITION_ASSIGNMENTS_V (aliased PAS) — the primary driving object, supplying all core assignment, position, worksheet, date-range, and element-value attributes. The view pre-filters this source on ASSIGNMENT_TYPE = 'ELEMENT'.
• PSB_PAY_ELEMENTS (aliased PE) — joined with an outer join (+) on PAY_ELEMENT_ID, contributing element-level metadata such as OVERWRITE_FLAG, SALARY_TYPE, OPTION_FLAG, NAME, and SALARY_FLAG.
• PSB_PAY_ELEMENT_OPTIONS (aliased PEO) — outer-joined on PAY_ELEMENT_OPTION_ID, supplying grade step, option name, and sequence information.

Because both pay element joins are outer joins, assignments that reference no matching pay element or option still return rows, with a NULL element name in the affected columns. The view exposes the underlying ROWID from the assignment source, which permits positional updates where the view is not read-only.

Key Columns

• ELEMENT_VALUE_TYPE — classifies the nature of the element value, driving the meaning of the ELEMENT_VALUE field.
• ELEMENT_VALUE, PAY_BASIS, CURRENCY_CODE — the numeric value, pay basis (for example annual or hourly), and currency applicable to the assignment element.
• POSITION_ASSIGNMENT_ID, POSITION_ID, WORKSHEET_ID, DATA_EXTRACT_ID — identifiers linking the assignment to its position, budget worksheet, and data extraction run.
• PAY_ELEMENT_ID, PAY_ELEMENT_OPTION_ID, PAY_ELEMENT_RATE_ID — foreign keys to the pay element, option, and rate definitions.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date range over which the assignment element is valid.
• GLOBAL_DEFAULT_FLAG, ASSIGNMENT_DEFAULT_RULE_ID, MODIFY_FLAG — flags and rules governing defaulting and whether the value may be modified.
• NAME and the PEO NAME (exposed as ELEMENT_NAME and OPTION_NAME), plus GRADE_STEP, SALARY_TYPE, SALARY_FLAG, SEQUENCE_NUMBER — descriptive attributes of the element and its option.
• Standard WHO columns (LAST_UPDATE_DATE, CREATED_BY, and related audit fields).

Common Use Cases and Queries

A frequent scenario is reviewing how element values are typed across all position assignments in a worksheet:

• Audit by value type: SELECT POSITION_ID, PAY_ELEMENT_ID, ELEMENT_VALUE_TYPE, ELEMENT_VALUE FROM PSB_POSITION_ASSIGN_ELEMENT_V WHERE WORKSHEET_ID = :worksheet_id ORDER BY POSITION_ID;
• Element-level roll-up: group by PAY_ELEMENT_ID and ELEMENT_VALUE_TYPE to aggregate budgeted element values by worksheet.
• Currency and pay-basis analysis: filter on PAY_BASIS and CURRENCY_CODE to compare element configuration across positions.
• Defaulting and override review: inspect GLOBAL_DEFAULT_FLAG, MODIFY_FLAG, and ASSIGNMENT_DEFAULT_RULE_ID to confirm which element assignments were system-defaulted versus manually overridden.

The view is typically consumed read-only for reporting and data extraction rather than direct DML, since it draws from a view-based source. Queries should be bounded by worksheet or position identifiers to limit scan volume.