Results for “budget_year_type_name”

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

Overview

PSBFV_CONSTRAINT_FORMULAS is a read-only view owned by the APPS schema within the Public Sector Budgeting (PSB) product family of Oracle E-Business Suite. It exposes the individual constraint formula lines that govern how budgetary constraint rules are evaluated during budget formulation and validation. In EBS 12.1.1 and 12.2.2 the object carries a status of VALID and is defined with a WITH READ ONLY clause, meaning it is intended strictly for query and reporting access rather than for DML. The view flattens the normalized relationship between a parent constraint, its constituent formula steps, the applicable budget year type, and — where the formula references a payroll element — the associated pay element and pay element option. This makes it a convenient single-row-per-formula-step source for reporting on constraint logic, for building custom inquiry screens, and for extracting configuration into external budget models or integration layers.

Underlying Base Objects

The view is defined over five APPS tables. PSB_CONSTRAINT_FORMULAS (aliased CF) is the driving table and supplies nearly all exposed columns, including operators, amounts, effective dates, and the foreign keys to constraints, entities, and pay elements. It is joined to PSB_ENTITY (PE) on ENTITY_ID to resolve the constraint name, and to PSB_BUDGET_YEAR_TYPES (BYT) on BUDGET_YEAR_TYPE_ID to resolve the year type name. Two additional outer joins connect the payroll dimension: PSB_PAY_ELEMENTS (PPE) on PAY_ELEMENT_ID and PSB_PAY_ELEMENT_OPTIONS (PEO) on PAY_ELEMENT_OPTION_ID. Both payroll joins use the (+) operator, so constraint formulas that do not reference a pay element or option are still returned, with null values in the payroll columns. The PSB_BUDGET_YEAR_TYPES join is also outer, while the PSB_ENTITY join is inner and therefore mandatory for a row to appear.

Key Columns

• CONSTRAINT_NAME — resolved from PSB_ENTITY via the constraint's ENTITY_ID; identifies the parent constraint.
• STEP_NUMBER — the ordinal position of the formula line within the constraint.
• "_LA:PREFIX_OPERATOR" and "_LA:POSTFIX_OPERATOR" — lookup-encoded operator codes translated through FND_LOOKUPS valuesets PSB_CONSTRAINT_PREFIX_OPERATOR and PSB_POSTFIX_OPERATOR (MEANING).
• "_LA:BALANCE_TYPE" and "_LA:ELEMENT_VALUE_TYPE" — lookup-encoded values from PSB_BALANCE_TYPE and PSB_ELEMENT_VALUE_TYPE.
• BUDGET_YEAR_TYPE_NAME — the budget year type attached to the formula.
• GL_ACCOUNT — the concatenated accounting flexfield segments (CF.CONCATENATED_SEGMENTS) targeted by the formula.
• PAY_ELEMENT_NAME and PAY_ELEMENT_OPTION_NAME — resolved from PSB_PAY_ELEMENTS and PSB_PAY_ELEMENT_OPTIONS; PAY_ELEMENT_OPTION_NAME is the element option referenced by the formula and corresponds to the user's search term "pay_element_option_name."
• ELEMENT_VALUE, CURRENCY_CODE, AMOUNT, ALLOW_MODIFY — the comparison value, currency, monetary amount, and whether the formula line may be modified by the user.
• START_EFFECTIVE_DATE / END_EFFECTIVE_DATE and the standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE).
• CONSTRAINT_FORMULA_ID, CONSTRAINT_ID, BUDGET_YEAR_TYPE_ID, PAY_ELEMENT_ID, PAY_ELEMENT_OPTION_ID — keys for joining back to the base tables.

Common Use Cases and Queries

Typical scenarios include auditing which constraint formulas reference a specific payroll element option, reviewing the operator and amount logic applied against a GL account, and reconciling constraint configuration across budget year types. To find formulas tied to a particular element option:

• SELECT constraint_name, step_number, gl_account, pay_element_name, pay_element_option_name, amount FROM apps.psbfv_constraint_formulas WHERE pay_element_option_name = :p_option_name ORDER BY constraint_name, step_number;
• SELECT constraint_name, step_number, budget_year_type_name, "_LA:PREFIX_OPERATOR", "_LA:BALANCE_TYPE", amount, allow_modify FROM apps.psbfv_constraint_formulas WHERE constraint_id = :p_constraint_id ORDER BY step_number;
• SELECT f.constraint_name, f.gl_account, f.pay_element_option_name FROM apps.psbfv_constraint_formulas f WHERE f.effective_start_date <= SYSDATE AND NVL(f.effective_end_date, SYSDATE) >= SYSDATE;

Because of the WITH READ ONLY restriction, any write operations must target PSB_CONSTRAINT_FORMULAS directly rather than this view.