Results for “element_value_type_meaning”

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

Overview

The view PSB_DEFAULT_ASSIGNMENTS_V belongs to the PSB – Public Sector Budgeting product family within Oracle E-Business Suite, a module that is designated Obsolete in ETRM 12.2.2. The view is a denormalized, read-oriented presentation layer over the PSB default assignment configuration tables. It exposes the rules by which default payroll element assignments, attribute values, and pay-basis defaults are resolved for budgeting positions and assignments. In practice, the view provides a single flattened row for each combination of default assignment, attribute, and pay element configuration, joining lookup translations and element/option definitions so that consumers do not need to perform the joins themselves.

For reporting and integration purposes, the view is the most direct source for the "salary_type" attribute once the underlying pay element has been configured with SALARY_FLAG set. Because the join to PSB_PAY_ELEMENTS is an outer join, the SALARY_TYPE column will be null where a default assignment row is driven purely by attribute logic rather than by a pay element. The ETRM record explicitly notes "Not implemented in this database," meaning no live instance of the view existed in the documented environment and no base objects were inventoried; the view's definition is therefore the authoritative reference for its behavior.

Underlying Base Objects

The view text documents the following base objects, each joined through the PSB_DEFAULT_ASSIGNMENTS driving table:

• PSB_DEFAULT_ASSIGNMENTS (DA) – the primary table holding default assignment rules, their assignment type, pay basis, element value, and audit columns.
• PSB_ATTRIBUTES (PAT) – outer-joined on ATTRIBUTE_ID to supply the attribute name.
• PSB_ATTRIBUTE_VALUES (PATV) – outer-joined on ATTRIBUTE_VALUE_ID to resolve coded attribute values.
• PSB_PAY_ELEMENTS (PE) – outer-joined on PAY_ELEMENT_ID to supply element name, overwrite flag, salary flag, salary type, and option flag.
• PSB_PAY_ELEMENT_OPTIONS (PEO) – outer-joined on PAY_ELEMENT_OPTION_ID for option name and grade step.
• FND_LOOKUPS (EV) – outer-joined on lookup type PSB_ELEMENT_VALUE_TYPE and lookup code ELEMENT_VALUE_TYPE to translate the element value type.

Note that although ETRM 12.2.2 lists no referenced base objects, the ETRM excerpt for this view enumerates these six tables explicitly.

Key Columns

• DEFAULT_ASSIGNMENT_ID / DEFAULT_RULE_ID – primary key and the parent rule identifier.
• ASSIGNMENT_TYPE – classifies the assignment (for example attribute-driven versus element-driven).
• ATTRIBUTE_ID / ATTRIBUTE_NAME / ATTRIBUTE_VALUE_ID / ATTRIBUTE_VALUE – the attribute and its resolved value; DISPLAY_ATTRIBUTE_VALUE applies a DECODE so that coded values fall back to the literal value.
• PAY_ELEMENT_ID / ELEMENT_NAME – the defaulted pay element.
• SALARY_FLAG / SALARY_TYPE – indicate whether the element is salary-bearing and its salary classification; these are the columns targeted by a "salary_type" search.
• OVERWRITE_FLAG / OPTION_FLAG / GRADE_STEP – control whether existing values are overwritten and which pay element option applies.
• PAY_BASIS, ELEMENT_VALUE_TYPE, ELEMENT_VALUE_TYPE_MEANING, ELEMENT_VALUE, CURRENCY_CODE – the defaulted amount and its basis.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – standard audit columns.

Common Use Cases and Queries

Typical queries validate which defaults carry salary elements, or trace the source of a salary type on a position default rule.

• Listing salary-bearing defaults: SELECT default_assignment_id, element_name, salary_type, pay_basis FROM psb_default_assignments_v WHERE salary_flag = 'Y';
• Resolving attribute-driven defaults: SELECT default_rule_id, attribute_name, display_attribute_value, element_name FROM psb_default_assignments_v;
• Auditing recently changed rules: SELECT default_assignment_id, salary_type, last_update_date, last_updated_by FROM psb_default_assignments_v ORDER BY last_update_date DESC;

Because PSB is obsolete, these queries are relevant mainly for historical data migration, reconciliation, or upgrade analysis rather than ongoing budgeting operations.