Results for “pay_element_option_id”

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

Overview

PSBBV_CONSTRAINT_FORMULAS is a read-only Oracle EBS view owned by the APPS schema in the Public Sector Budgeting (PSB) product. In both EBS 12.1.1 and 12.2.2 it presents the budget constraint formulas that govern how budget organizations, revenue and expenditure elements, and pay elements are validated against defined budget constraints. Each row represents a single formula step, so a given constraint is typically composed of several rows sequenced by STEP_NUMBER.

The view translates coded values into descriptive meanings for end users and integrations. Prefix and postfix operators, balance type, and element value type are exposed through FND lookups (PSB_CONSTRAINT_PREFIX_OPERATOR, PSB_POSTFIX_OPERATOR, PSB_BALANCE_TYPE, PSB_ELEMENT_VALUE_TYPE) rather than raw codes, making it suitable for reporting, data extraction, and interface work without additional lookup joins.

Underlying Base Objects

The view text selects from PSB_CONSTRAINT_FORMULAS (aliased CF), joined to PSB_ENTITY (PE) and outer-joined to PSB_BUDGET_YEAR_TYPES (BYT). The join conditions are CF.CONSTRAINT_ID = PE.ENTITY_ID and CF.BUDGET_YEAR_TYPE_ID = BYT.BUDGET_YEAR_TYPE_ID(+). The outer join on budget year type allows formula rows that are not tied to a specific year type to remain visible. The view is defined WITH READ ONLY, so DML against it is not permitted; maintenance must be performed against the base tables or through the PSB application forms.

The columns STEP_NUMBER, CONCATENATED_SEGMENTS, ELEMENT_VALUE, CURRENCY_CODE, AMOUNT, PAY_ELEMENT_ID, PAY_ELEMENT_OPTION_ID, ALLOW_MODIFY and the descriptive lookup columns are drawn from PSB_CONSTRAINT_FORMULAS. Note that the column name ALLOW_MODIFY is the source of the user's search term; it appears as an actual column in the view, not as a lookup, and indicates whether the generated formula is editable by the user.

Key Columns

• STEP_NUMBER – Ordinal position of the formula row within its parent constraint.
• "_LA:PREFIX_OPERATOR" / "_LA:POSTFIX_OPERATOR" – Lookup meanings for the operators placed before and after the element in the formula expression.
• "_LA:BALANCE_TYPE" – Lookup meaning for the balance class (for example, budget or actual) against which the formula evaluates.
• GL_ACCOUNT – Concatenated accounting flexfield segments (aliased from CONCATENATED_SEGMENTS in the base table).
• "_LA:ELEMENT_VALUE_TYPE" / ELEMENT_VALUE – Type and literal value of the budget element used in the step.
• CURRENCY_CODE and AMOUNT – Currency and threshold amount applied by the step.
• PAY_ELEMENT_ID / PAY_ELEMENT_OPTION_ID – Payroll element and option references where the formula applies to pay elements.
• ALLOW_MODIFY – Flag indicating whether the constraint formula may be modified by the user.
• START_EFFECTIVE_DATE / END_EFFECTIVE_DATE – Effective dating of the formula row.
• CONSTRAINT_FORMULA_ID / CONSTRAINT_ID – Primary key of the formula row and its parent constraint (matching PE.ENTITY_ID).
• BUDGET_YEAR_TYPE_ID, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE – Foreign key and audit columns.

Common Use Cases and Queries

Typical uses include auditing which formulas are user-modifiable, reconciling constraint definitions against entities, and extracting formula detail for migration or interface testing. A representative query listing editable steps for a constraint:

SELECT step_number, constraint_id, "_LA:BALANCE_TYPE", gl_account,
  "_LA:ELEMENT_VALUE_TYPE", element_value, amount, allow_modify
 FROM apps.psbbv_constraint_formulas
 WHERE constraint_id = :p_constraint_id
 ORDER BY step_number;

To identify all formulas open to user modification:

SELECT constraint_id, constraint_formula_id, step_number, allow_modify
 FROM apps.psbbv_constraint_formulas
 WHERE allow_modify = 'Y'
 AND SYSDATE BETWEEN start_effective_date AND NVL(end_effective_date, SYSDATE);