Search Results qrm_time_buckets_u1

Overview

QRM.QRM_TIME_BUCKETS is a foundational configuration table within the Oracle E-Business Suite Risk Management (ETRM) module, delivered under the QRM schema. It stores the named sets of time buckets that drive risk analyses performed in Oracle ETRM. Each row represents a distinct bucket set definition, identified by a name and accompanied by a descriptive label. The individual intervals that compose each bucket set — for example, overnight, one-week, one-month, or one-year tenors — are not held here but are persisted separately in QRM_TIME_INTERVALS, which references this table through the TB_NAME column. This separation of the bucket set header from its constituent intervals gives the design a clean parent/child structure suitable for reuse across multiple analyses.

From a dimensional modeling perspective, the metadata suggests a hub-leaning classification. QRM_TIME_BUCKETS behaves as a stable, low-volatility reference entity whose primary key values (TB_NAME) are reused as foreign keys by downstream transactional and configuration tables, which is the characteristic pattern of a Data Vault hub. The WHO audit columns act as a satellite carrying descriptive attributes around that key.

Key Information Stored

The table holds eight documented columns. The most significant are:

• TB_NAME — VARCHAR2(20), mandatory. The business key and primary key component. It names the set of time buckets and is the value propagated to all dependent tables.
• DESCRIPTION — VARCHAR2(50). A human-readable description of the bucket set, presented to users in analysis setup screens and lookup lists.
• ZD_EDITION_NAME — the editioning column introduced by the ETRM 12.2.x edition-based redefinition (EBR) architecture. It participates in the unique index QRM_TIME_BUCKETS_U1 alongside TB_NAME.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns recording creation and last-modification provenance.

The primary key is QRM_TIME_BUCKETS_PK on TB_NAME. The unique index QRM_TIME_BUCKETS_U1 is documented in the 12.2.2 schema as (TB_NAME, ZD_EDITION_NAME), reflecting EBR scoping; in 12.1.1 the same index is defined on TB_NAME alone. The distinction between the surrogate storage key and the business-key candidate is therefore minimal here — TB_NAME is both the logical identifier and the join column throughout the model.

Common Use Cases and Queries

Typical usage includes listing available bucket sets for analysis configuration, validating that a referenced bucket set exists before attaching it to an analysis, and auditing which bucket sets are in active use. A simple lookup pattern is:

• SELECT TB_NAME, DESCRIPTION FROM QRM.QRM_TIME_BUCKETS ORDER BY TB_NAME;
• Join to QRM_TIME_INTERVALS on TB_NAME to expand a bucket set into its constituent intervals for reporting or reconciliation.
• Left-join to QRM_ANALYSIS_SETTINGS on TB_NAME to identify bucket sets that are referenced by one or more analysis configurations.

Because the table is small and static, it is commonly extracted into reporting marts as a reference dimension keyed on TB_NAME.

Related Objects

The following objects depend on or reference QRM_TIME_BUCKETS through the documented key relationships:

• QRM_TIME_INTERVALS — child table; QRM_TIME_INTERVALS.TB_NAME → QRM_TIME_BUCKETS.TB_NAME. Holds the interval definitions for each bucket set.
• QRM_ANALYSIS_SETTINGS — configuration table; QRM_ANALYSIS_SETTINGS.TB_NAME → QRM_TIME_BUCKETS.TB_NAME. Links a bucket set to an analysis definition.
• QRM_TIME_BUCKETS_PK — primary key constraint on TB_NAME.
• QRM_TIME_BUCKETS_U1 — unique index on (TB_NAME, ZD_EDITION_NAME) in 12.2.2, or TB_NAME in 12.1.1.

No database objects are referenced by QRM_TIME_BUCKETS itself, confirming its role as a top-level reference entity within the ETRM schema.