Results for “parameter_set_name”

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

Overview

PSBBV_PARAMETER_SETS is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PSB (Public Sector Budgeting) product family. Despite its name suggesting a broad parameter utility, the view exposes a specialized subset of records from the PSB_ENTITY_SET table: those rows whose ENTITY_TYPE equals the literal value 'PARAMETER'. In this sense, PSBBV_PARAMETER_SETS acts as a filtered, presentation-layer window onto the entity-set infrastructure that Public Sector Budgeting uses to group and manage budgeting parameters.

In EBS Release 12.1.1 and 12.2.2, the view is present with STATUS = VALID in the APPS schema. Its role in reporting and integration is that of a stable, denormalized access point for parameter-set metadata. Rather than requiring consumers to know the ENTITY_TYPE discriminator and join semantics of the underlying table, the view surfaces the parameter-specific subset with renamed columns such as PARAMETER_SET_NAME and PARAMETER_SET_ID. This makes it convenient for custom reports, Oracle Discoverer/BI Publisher data models, and inbound interfaces that need to enumerate the parameter sets defined for a given budgeting configuration. It is important to note that the view is defined WITH READ ONLY, so it cannot be used for DML; all maintenance occurs against the base table through the standard PSB forms and concurrent programs.

Underlying Base Objects

The documented view text defines PSBBV_PARAMETER_SETS strictly over a single base object: PSB_ENTITY_SET (aliased PES). No additional tables, views, or synonyms are documented as referenced objects, and the ETRM 12.2.2 metadata records no other base objects. The definition is a straightforward projection with a predicate:

• SELECT list: PES.NAME, PES.DESCRIPTION, PES.ENTITY_SET_ID, PES.LAST_UPDATE_DATE, PES.LAST_UPDATED_BY, PES.CREATED_BY, PES.CREATION_DATE
• Filter: PES.ENTITY_TYPE = 'PARAMETER'
• Clause: WITH READ ONLY

Because the view is defined directly over PSB_ENTITY_SET without aggregation or outer joins, each row returned corresponds one-to-one with a base row whose entity type is 'PARAMETER'. The relationship is therefore purely restrictive and renaming-oriented; there is no data transformation beyond column aliasing. The last-updated and created audit columns are passed through unchanged, preserving the who/when information maintained by the base table triggers and the EBS audit conventions.

Key Columns

The view exposes seven columns. The original base column name and the exposed view column name differ for the two identifier columns, which is a common EBS technique for presenting entity-specific terminology:

• PARAMETER_SET_NAME — derived from PSB_ENTITY_SET.NAME; the user-facing name of the parameter set. Expect this to be the primary search and display attribute in reports.
• DESCRIPTION — free-text description of the parameter set, passed through directly from the base table.
• PARAMETER_SET_ID — derived from PSB_ENTITY_SET.ENTITY_SET_ID; the surrogate primary key for the parameter set. This is the column referenced by foreign keys in dependent PSB tables and is the typical join key in custom queries.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — standard EBS audit columns indicating when and by which application user the row was created and last modified.

Common Use Cases and Queries

Typical uses include validating a parameter set that a user or interface has supplied, populating LOV-style reports, and auditing when budgeting parameter sets were created or changed. A basic query listing all parameter sets is:

• SELECT parameter_set_id, parameter_set_name, description FROM apps.psbbv_parameter_sets ORDER BY parameter_set_name;
• SELECT parameter_set_id, parameter_set_name, last_update_date, last_updated_by FROM apps.psbbv_parameter_sets WHERE last_update_date >= :p_since;
• SELECT p.parameter_set_id, p.parameter_set_name FROM apps.psbbv_parameter_sets p WHERE p.parameter_set_id = :p_id;

Since the view is read-only and defined over a single table, it can be joined to other PSB objects through PARAMETER_SET_ID without risk of fan-out from the view itself. For performance, note that the underlying predicate ENTITY_TYPE = 'PARAMETER' is applied to PSB_ENTITY_SET; if indexes on that table do not cover ENTITY_TYPE, full scans may occur on large installations. When parameter sets are modified or new ones added through the PSB setup forms, the view reflects the change immediately, as it carries no materialization. Developers should treat PARAMETER_SET_ID as the stable key, since PARAMETER_SET_NAME is editable by users and should not be relied upon as a durable identifier across environments.