Search Results max_element_value

Overview

PSBFV_PAY_ELEMENTS is an Oracle E-Business Suite business intelligence (BI) system view owned by the APPS schema and registered under the FND Design Data application PSB. Its object type is VIEW and its documented status is VALID. As the name implies, the view presents definitional information about pay elements — the configurable building blocks that drive earnings, deductions, and other compensation components processed by Oracle Payroll and Oracle Human Resources. In the ETRM metadata the view is characterized as a Business Intelligence System view, indicating that it is intended primarily for reporting, extraction, and downstream integration rather than for transactional data entry.

The view exposes the descriptive and controlling attributes of each pay element, including its name, description, value type, processing behavior, effective dating, salary linkage, and maximum value constraints. Because the view is a flattened, read-oriented projection, it allows report authors and integration developers to query pay element metadata without navigating the more normalized base tables directly. In EBS 12.1.1 and 12.2.2, the view is commonly consumed by BI Publisher reports, discoverer worksheets, and custom PL/SQL extraction routines that need to reconcile element definitions across business groups. The search term "max_element_value" maps directly to the MAX_ELEMENT_VALUE column documented in this view, which is the numeric ceiling associated with an element.

Underlying Base Objects

The ETRM documentation for this object does not list any referenced base objects; the section "Referenced base objects" is recorded as "none documented." The FND Design Data reference PSB.PSBFV_PAY_ELEMENTS confirms the view is delivered as part of the PSB application design. In practice, a view of this name and structure is defined over the core pay element definition table, commonly PAY_ELEMENT_TYPES_F and its associated translation and lookup structures, joined to produce the friendly _LA (lookup meaning) columns shown in the metadata. Because the authoritative base object list is not supplied, consumers should treat the view as a stable reporting interface and should not assume any particular join path or dependency in custom code. The presence of the view in the APPS schema means it is accessible to any responsibility or concurrent program with the necessary APPS privileges.

Key Columns

• PAY_ELEMENT_ID — Numeric unique identifier for the pay element; the primary join key to other payroll objects.
• NAME / DESCRIPTION — The element name (30 characters) and its descriptive text (240 characters).
• DATA_EXTRACT_NAME / DATA_EXTRACT_ID — Identifier and name used to associate the element with a data extract.
• _LA:ELEMENT_VALUE_TYPE — Element value type: A (Amount), P (Percent), PI (Percent Increase), or PS (Percent of Salary).
• _LA:MAX_ELEMENT_VALUE_TYPE — Value type for the maximum: A (Amount) or P (Percent).
• MAX_ELEMENT_VALUE — Number (20) giving the maximum value associated with the element; this is the column of interest for the "max_element_value" search.
• OVERWRITE_FLAG — Indicates whether the element value can be overwritten.
• REQUIRED_FLAG — Indicates whether the element is required.
• FOLLOW_SALARY — Indicates whether the element follows salary distribution.
• START_EFFECTIVE_DATE / END_EFFECTIVE_DATE — Effective date range for the element definition.
• _LA:PROCESSING_TYPE — N (Non-Recurring) or R (Recurring).
• _LA:PERIOD_TYPE / _LA:PROCESS_PERIOD_TYPE — HRMS period type and the calculation period to which cost is charged (First or Last).
• SALARY_FLAG / _LA:SALARY_TYPE — Whether the element is a salary element and whether the salary type is Rate or Step.
• OPTION_FLAG — Indicates whether the element has options.
• BUSINESS_GROUP_ID — Business group identifier for multitenant filtering.
• LAST_UPDATED_BY / LAST_UPDATE_DATE — Standard WHO audit columns.

Common Use Cases and Queries

Typical uses include validating element configuration before a payroll run, auditing maximum value thresholds, and feeding element metadata into external compensation systems. The following query retrieves all amount-type elements with a defined maximum, filtered by business group.

SELECT name, description, max_element_value, _LA:MAX_ELEMENT_VALUE_TYPE
FROM apps.psbfv_pay_elements
WHERE business_group_id = :p_business_group_id
AND max_element_value IS NOT NULL
ORDER BY name;

To enumerate salary elements and their value types, a report author might use:

SELECT name, _LA:ELEMENT_VALUE_TYPE, salary_flag
FROM apps.psbfv_pay_elements
WHERE salary_flag = 'Y';

Because the view is read-only and conformed to the APPS schema, it can be safely referenced from concurrent programs, BI Publisher data models, and OBIEE or Discoverer layers. As the base object mapping is not documented, integration code should reference only the exposed columns and should not depend on underlying table structures.