Results for “parameter_formula_id”

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

Overview

PSBBV_PARAMETER_FORMULAS is a read-only database view belonging to the Public Sector Budgeting (PSB) module of Oracle E-Business Suite, a product line designated as obsolete in the ETRM reference for releases 12.1.1 and 12.2.2. The view presents the rules that govern how budgeting parameter formulas are evaluated during salary and position budgeting processing. In Public Sector Budgeting, a parameter formula defines the arithmetic logic applied to a budget line—such as applying a prefix or postfix operator, a balance type, a currency, an increment percentage, or a date-range condition for hires and adjustments. PSBBV_PARAMETER_FORMULAS exposes this formula metadata in a denormalized, presentation-ready form so that it can be consumed by concurrent programs, budget worksheets, and custom reporting.

A distinguishing characteristic of this view is its use of message-substitution tokens in the SELECT list. Column aliases such as "_LA:PREFIX_OPERATOR", "_LA:BALANCE_TYPE", "_LA:INCREMENT_TYPE", and "_LA:ASSIGNMENT_TYPE" are not ordinary column names; they instruct the Oracle Application Object Library to substitute a translated lookup meaning from FND_LOOKUPS at runtime. This design supports the multilingual requirements of Public Sector Budgeting without requiring custom join logic in every report. The view is defined WITH READ ONLY, so it can be queried but never used as the target of DML.

Underlying Base Objects

According to the ETRM metadata, no base objects are formally documented for this view. The view text nonetheless reveals its defining query, which selects from three source objects: PSB_PARAMETER_FORMULAS (aliased PF), PSB_BUDGET_YEAR_TYPES (aliased BYT), and PSB_ENTITY (aliased PE). PSB_PARAMETER_FORMULAS is the driving table and supplies nearly every column in the view, including STEP_NUMBER, CONCATENATED_SEGMENTS, AMOUNT, INCREMENT_BY, and ELEMENT_VALUE. PSB_BUDGET_YEAR_TYPES is joined on BUDGET_YEAR_TYPE_ID with an outer join (+) so that formula rows are preserved even when no budget year type is defined. PSB_ENTITY is joined on PARAMETER_ID = ENTITY_ID, an inner join that resolves the owning budget entity. Because the metadata states the view is not implemented in the reference database, DBAs should confirm its presence in the target instance before relying on it.

Key Columns

The column that most directly answers the searched term "increment_by" is INCREMENT_BY, a numeric column holding the value applied to a formula when the associated increment type is evaluated. It is paired with the lookup-substituted "_LA:INCREMENT_TYPE" column, which renders the meaning from the PSB_INCREMENT_TYPE lookup type. Other operation columns follow the same pattern: "_LA:PREFIX_OPERATOR" and "_LA:POSTFIX_OPERATOR" render the PSB_PARAMETER_PREFIX_OPERATOR and PSB_POSTFIX_OPERATOR lookups; "_LA:BALANCE_TYPE" renders PSB_BALANCE_TYPE; "_LA:ASSIGNMENT_TYPE" renders PSB_PARAMETER_ASSIGNMENT_TYPE; and "_LA:ELEMENT_VALUE_TYPE" renders PSB_ELEMENT_VALUE_TYPE. Structural columns include STEP_NUMBER, which orders the evaluation sequence; PARAMETER_FORMULA_ID, the primary identifier; PARAMETER_ID, ATTRIBUTE_ID, PAY_ELEMENT_ID, and PAY_ELEMENT_OPTION_ID, which tie the formula to its budget parameter and payroll element; BUDGET_YEAR_TYPE; GL_ACCOUNT; CONCATENATED_SEGMENTS; CURRENCY_CODE; AMOUNT; GRADE_STEP; ATTRIBUTE_VALUE; and ELEMENT_VALUE. Date-based conditions are exposed through HIREDATE_BETWEEN_FROM, HIREDATE_BETWEEN_TO, ADJDATE_BETWEEN_FROM, and ADJDATE_BETWEEN_TO, while START_EFFECTIVE_DATE and END_EFFECTIVE_DATE provide the standard effective-dating envelope. Audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, and CREATION_DATE close out the projection.

Common Use Cases and Queries

Typical use cases include auditing the increment values configured for a budget parameter, reproducing the formula sequence used to calculate a salary budget line, and validating that lookup-driven operators resolve to expected meanings. A representative query isolates increment logic for a given parameter:

• SELECT parameter_formula_id, step_number, increment_by, "_LA:INCREMENT_TYPE" increment_type, amount, effective_start_date FROM psbbv_parameter_formulas WHERE parameter_id = :p_parameter_id ORDER BY step_number;
• SELECT parameter_formula_id, increment_by, hiredate_between_from, hiredate_between_to FROM psbbv_parameter_formulas WHERE increment_by IS NOT NULL AND effective_end_date IS NULL;
• SELECT parameter_id, COUNT(*) formula_lines, SUM(increment_by) total_increment FROM psbbv_parameter_formulas GROUP BY parameter_id;

Because the lookup token columns are resolved through FND_LOOKUPS, queries should quote the tokenized aliases exactly as shown to retrieve the translated meaning. Any extraction intended for integration should filter on the effective date columns to avoid returning superseded formula versions.