Results for “max_element_value”

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

Overview

PSBBV_PAY_ELEMENTS is a read-only view owned by the APPS schema in Oracle E-Business Suite, registered as VALID and associated with the PSB – Public Sector Budgeting product family. It exposes the pay element definitions used by the budgeting engine, presenting each pay element together with its descriptive, behavioral, and effective-dating attributes. The view is defined WITH READ ONLY, so it is intended strictly for query, reporting, and integration consumption rather than for DML.

A distinctive characteristic of this view is its use of Oracle Application Object Library descriptive flexfield token syntax. Several columns are not stored values but tokenized references of the form "_LA:PE.<COLUMN>:FND_LOOKUPS:<LOOKUP_TYPE>:MEANING", which instruct the EBS framework to substitute the meaning of the corresponding lookup code at runtime. This design allows report and form layers to render human-readable values (for example, processing type or period type) without hard-coding lookup joins. For users investigating the overwrite_flag attribute, the view is the primary reporting surface through which PSB_PAY_ELEMENTS.OVERWRITE_FLAG becomes visible alongside the element name, value type, required flag, and salary-related flags.

Underlying Base Objects

The view text is defined over two tables joined on DATA_EXTRACT_ID:

• PSB_PAY_ELEMENTS PE — the driving table that supplies all substantive columns, including NAME, DESCRIPTION, OVERWRITE_FLAG, REQUIRED_FLAG, FOLLOW_SALARY, START_DATE, END_DATE, MAX_ELEMENT_VALUE, SALARY_FLAG, OPTION_FLAG, and the audit columns.
• PSB_DATA_EXTRACTS DE — joined via PE.DATA_EXTRACT_ID = DE.DATA_EXTRACT_ID, scoping each pay element to its parent data extract.

The join is an inner equijoin, meaning pay elements that are not associated with a valid data extract row are not returned. Although PSB_DATA_EXTRACTS contributes no projected columns, its presence in the FROM clause and WHERE clause constrains the result set. Beyond these two documented base objects, the ETRM metadata lists no further referenced objects; the lookup meanings referenced by the "_LA:" tokens are resolved by the runtime framework rather than by additional joins in the view definition itself.

Key Columns

• NAME / DESCRIPTION — the pay element identifier and its user-facing description.
• OVERWRITE_FLAG — indicates whether the pay element value may be overwritten during processing or budget regeneration; this is the attribute most frequently searched against this view.
• REQUIRED_FLAG — marks whether a value must be supplied for the element.
• FOLLOW_SALARY / SALARY_FLAG / "_LA:SALARY_TYPE" — govern salary-driven derivation of element values and the associated salary type meaning.
• START_DATE / END_DATE — effective dating for the element definition.
• "_LA:ELEMENT_VALUE_TYPE", "_LA:PROCESSING_TYPE", "_LA:PERIOD_TYPE", "_LA:PROCESS_PERIOD_TYPE", "_LA:MAX_ELEMENT_VALUE_TYPE" — tokenized lookups resolving against PSB_ELEMENT_VALUE_TYPE, PSB_PROCESSING_TYPE, PSB_PERIOD_TYPE, PSB_PROCESS_PERIOD_TYPE, and PSB_MAX_ELEMENT_VALUE_TYPE respectively.
• MAX_ELEMENT_VALUE — the ceiling applied to the element value where a maximum is enforced.
• OPTION_FLAG — behavioral option indicator for the element.
• PAY_ELEMENT_ID / DATA_EXTRACT_ID — primary and foreign key identifiers linking to the pay element definition and its parent extract.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY — standard audit columns.

Common Use Cases and Queries

Typical scenarios include auditing which pay elements are configured as overwritable, reconciling element definitions across data extracts, and feeding element metadata into downstream budget interfaces.

• List all elements and their overwrite behavior for a given extract:

  SELECT name, overwrite_flag, required_flag, salary_flag
  FROM   apps.psbbv_pay_elements
  WHERE  data_extract_id = :p_extract_id;

• Identify elements that are both required and overwritable:

  SELECT name, overwrite_flag, required_flag
  FROM   apps.psbbv_pay_elements
  WHERE  overwrite_flag = 'Y'
  AND    required_flag  = 'Y';

• Review effective-dated elements active on a reference date:

  SELECT name, start_date, end_date, option_flag
  FROM   apps.psbbv_pay_elements
  WHERE  :p_ref_date BETWEEN start_date AND NVL(end_date, :p_ref_date);

• Inspect salary-linked elements:

  SELECT name, salary_flag, follow_salary, "_LA:SALARY_TYPE"
  FROM   apps.psbbv_pay_elements
  WHERE  salary_flag = 'Y';

Because the view is read-only, all access should be through SELECT statements, and the "_LA:" columns should be queried with their quoted aliases exactly as exposed.