Results for “psb_parameters_v”
18 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The view PSB_PARAMETERS_V belongs to the Public Sector Budgeting (PSB) product family within Oracle E-Business Suite. In the ETRM 12.2.2 documentation, PSB is explicitly flagged as obsolete, and this particular view is recorded with the implementation note "Not implemented in this database." Consequently, PSB_PARAMETERS_V is a legacy dictionary object that is retained in the data model for backward compatibility and historical reference rather than being an active component of a current 12.1.1 or 12.2.2 installation.
The view presents parameter-type records stored within the PSB entity model. Its purpose in the original PSB design was to expose budgeting parameters—such as automatic increment rules and annual compounding behaviour—for reporting, integration, and concurrent processing. In practice, the view acts as a filtered projection of the underlying entity table, restricting output to rows whose entity type is a parameter. Because PSB budgeting functionality was superseded by later Oracle budgeting and planning solutions, the view is primarily encountered by administrators and technical consultants auditing inherited customizations, reviewing deprecated objects, or migrating historical configuration.
Underlying Base Objects
According to the documented view text, PSB_PARAMETERS_V is defined over a single base table: PSB_ENTITY. The view selects a discrete list of columns from that table and applies a fixed filter, ENTITY_TYPE = 'PARAMETER', so that only parameter records are returned. The view definition references no other documented base objects; the ETRM metadata records "Referenced base objects: none documented" beyond this entity table. Notably, the view text exposes ENTITY_ID and ENTITY_SUBTYPE, whereas the documented column list presents PARAMETER_ID and PARAMETER_TYPE. This naming divergence indicates that the view was aliased or renamed at some point, and that the published column list reflects a later or parallel dictionary representation. The attribute columns, context, and effective-dating columns are inherited directly from the entity table's descriptive-flexfield and date-tracking structure.
Key Columns
ROW_ID/ROWID— The unique row identifier for the parameter record; the view text exposes the database ROWID directly.PARAMETER_ID(ENTITY_ID) — Primary identifier of the parameter entity.PARAMETER_TYPE(ENTITY_SUBTYPE) — Classifies the parameter record within the parameter entity family.PARAMETER_AUTOINC_RULE— Defines the rule governing automatic increment behaviour applied during budget parameter processing. This is the column most frequently associated with the user search term parameter_autoinc_rule.PARAMETER_COMPOUND_ANNUALLY— Indicates whether parameter values compound on an annual basis.SET_OF_BOOKS_IDandBUDGET_GROUP_ID— Establish the ledger and budget group context for the parameter.CURRENCY_CODE— Currency associated with the parameter definition.DATA_EXTRACT_ID— Links the parameter to an associated data extraction process.ATTRIBUTE1–ATTRIBUTE10,CONTEXT— Descriptive flexfield segments and the flexfield context identifier.EFFECTIVE_START_DATE/EFFECTIVE_END_DATE— Date-range control for the parameter's validity.- Audit columns (
LAST_UPDATE_DATE,LAST_UPDATED_BY,CREATION_DATE,CREATED_BY,LAST_UPDATE_LOGIN) — Standard EBS who-columns for change tracking.
Common Use Cases and Queries
Practical usage centers on auditing and historical investigation rather than live budgeting operations, since PSB is obsolete. A typical query retrieves all active parameter definitions for a given ledger:
SELECT parameter_id, parameter_type, name, parameter_autoinc_rule, parameter_compound_annually FROM psb_parameters_v WHERE set_of_books_id = :ledger_id;- Filtering by the increment rule to identify budgets configured for automatic escalation:
... WHERE parameter_autoinc_rule IS NOT NULL; - Reviewing effective-dated parameters as of a specific date:
... WHERE :as_of_date BETWEEN effective_start_date AND effective_end_date; - Extracting flexfield context and attributes for migration analysis:
SELECT context, attribute1, attribute2 FROM psb_parameters_v;
Because the view is documented as not implemented in current databases, these queries should be validated against the specific instance before reliance. Where the object is absent, equivalent parameter data should be sought in the successor budgeting and planning tables.
-
View: PSB_PARAMETERS_V 12.1.1
-
VIEW: APPS.PSB_PARAMETERS_V 12.1.1
-
View: PSB_PARAMETERS_V 12.2.2
Not implemented in this database·Explore PSB module →
-
SYNONYM: APPS.PSB_ENTITY 12.1.1
-
12.1.1 DBA Data 12.1.1
-
PACKAGE: APPS.PSB_WS_POS3 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
eTRM - PSB Tables and Views 12.1.1
User profiles for a worksheet
-
12.1.1 DBA Data 12.1.1
-
eTRM - PSB Tables and Views 12.1.1
User profiles for a worksheet