Search Results salary_flag




Overview
Explore in AI Chat

Overview

APPS.PSB_POSITION_ASSIGN_ELEMENT_V is a supplementary Oracle E-Business Suite view owned by the APPS schema and registered under the FND design data reference PSB.PSB_POSITION_ASSIGN_ELEMENT_V. It presents pay element assignments linked to position-based assignment records used by the PSB (Public Sector/Position Budgeting) product family, exposing the intersection of position assignment data and payroll element configuration. The view carries a VALID status and is classified as a supplementary view whose stated purpose is to simplify forms coding within the application. Oracle explicitly warns that this object is not intended to be queried or used to alter data directly, and that its structure may change substantially across minor or major releases. Because of this, the view should be treated as an internal implementation artifact rather than a stable public interface.

For the user search term "salary_flag," the view is directly relevant: SALARY_FLAG is one of the 32 columns exposed, alongside related salary attributes such as SALARY_TYPE, ELEMENT_VALUE_TYPE, PAY_BASIS, and GRADE_STEP.

Underlying Base Objects

The ETRM metadata documents no referenced base objects for this view, and the dependency section is truncated. Based on the column set and the APPS.PSB_ prefix, the view is built over PSB position assignment element tables and joined to payroll element definition tables (such as PAY_ELEMENT_TYPES_F and PAY_ELEMENT_OPTIONS, from which ELEMENT_NAME and OPTION_NAME are derived), plus assignment/position tables providing POSITION_ID and EMPLOYEE_ID. The ROW_ID column confirms a ROWID-based key, typical of a view constructed with a form-block identifier. Common keys threading the view together include POSITION_ASSIGNMENT_ID, DATA_EXTRACT_ID, WORKSHEET_ID, PAY_ELEMENT_ID, PAY_ELEMENT_OPTION_ID, PAY_ELEMENT_RATE_ID, and ASSIGNMENT_DEFAULT_RULE_ID, which are the foreign keys linking it back to those base tables.

Key Columns

Common Use Cases and Queries

Typical use cases include salary-element analysis for a position assignment, verification of defaulting rules, and reconciliation of element values across worksheets. A representative query filtering on the searched attribute is:

SELECT POSITION_ASSIGNMENT_ID, POSITION_ID, EMPLOYEE_ID,
       ELEMENT_NAME, OPTION_NAME, ELEMENT_VALUE,
       SALARY_FLAG, SALARY_TYPE, PAY_BASIS, CURRENCY_CODE
FROM   APPS.PSB_POSITION_ASSIGN_ELEMENT_V
WHERE  SALARY_FLAG = 'Y'
AND    TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE;

Because Oracle advises against direct reliance on this view, production reporting should preferentially use the underlying payroll elements and PSB base tables. Where the view must be used, queries should always apply effective-date filtering and should be re-validated after any EBS patch or upgrade, since column semantics and availability can change between releases.