Results for “max_element_value_type_meaning”

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

Overview

PSB_PAY_ELEMENTS_V is a reporting view historically associated with the Public Sector Budgeting (PSB) module in Oracle E-Business Suite 12.1.1 and 12.2.2. PSB was designed to support budget formulation and salary/position budgeting for public sector organizations, and this view exposes pay element definitions extracted from the budgeting data extraction model. In the schema provided, the object is documented as obsolete and "Not implemented in this database," meaning the underlying tables and the view itself are typically absent in a standard EBS installation unless PSB was licensed and deployed. Where present, the view presents a denormalized, user-facing representation of pay element configuration, resolving raw lookup codes into descriptive meanings.

Its primary role is to support budget data extraction review, reporting, and integration, giving form and report logic a single queryable source for pay element attributes without requiring joins across multiple lookup tables.

Underlying Base Objects

The view is defined over a small set of core tables joined to several instances of FND_LOOKUPS:

• PSB_PAY_ELEMENTS PE — the driving table holding pay element definitions.
• PSB_DATA_EXTRACTS DE — supplies the extraction set name via DATA_EXTRACT_ID.
• PQH_PSB_DFLT_BUDGET_SETS PQH — outer-joined to provide BUDGET_SET_NAME.
• FND_LOOKUPS — joined six times (ELEMENT_VALUE_TYPE, PROCESSING_TYPE, MAX_ELEMENT_VALUE_TYPE, SALARY_TYPE, PERIOD_TYPE, PROCESS_PERIOD_TYPE) to translate codes into meanings.

All FND_LOOKUPS joins are outer joins, so pay elements with unpopulated codes still appear with null meanings.

Key Columns

• PAY_ELEMENT_ID, BUSINESS_GROUP_ID, DATA_EXTRACT_ID, BUDGET_SET_ID — primary keys and foreign keys linking the element to its extraction and budget set.
• NAME, DESCRIPTION, DATA_EXTRACT_NAME, BUDGET_SET_NAME — descriptive identifiers.
• PROCESSING_TYPE — the recurring processing period code; its meaning is drawn from lookup type PSB_RECURRING_PERIOD_TYPE. The corresponding column is commonly surfaced as PROCESSING_TYPE_MEANING, which is the translated text a user sees for the code.
• ELEMENT_VALUE_TYPE_MEANING, MAX_ELEMENT_VALUE_TYPE_MEANING, SALARY_TYPE_MEANING, PERIOD_TYPE_MEANING, PROCESS_PERIOD_TYPE_MEANING — descriptive labels for the respective encoded fields.
• FORMULA_ID, OVERWRITE_FLAG, REQUIRED_FLAG, FOLLOW_SALARY, PAY_BASIS, SALARY_FLAG, OPTION_FLAG — behavioral attributes of the pay element.
• START_DATE, END_DATE — effective dating.
• ATTRIBUTE1–ATTRIBUTE10, ATTRIBUTE_CATEGORY — descriptive flexfield context and segments.
• LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE — audit columns.

Common Use Cases and Queries

Typical scenarios include reviewing configured pay elements within an extraction, verifying which element carries a given processing type, and feeding downstream budget calculations. A representative query returning the processing type meaning follows:

SELECT pay_element_id,
       name,
       data_extract_name,
       processing_type,
       processing_type_meaning
FROM   psb_pay_elements_v
WHERE  processing_type = 'M'
ORDER  BY name;

To locate salary-type attributes across budget sets:

SELECT pe.name, pe.salary_flag, pe.salary_type_meaning
FROM   psb_pay_elements_v pe
WHERE  pe.budget_set_name IS NOT NULL;

Because the object is obsolete and not implemented, queries should be preceded by a check of ALL_VIEWS to confirm existence; alternate extraction or HR pay element views should be used in modern implementations.