Search Results qrm_time_buckets




Overview
Explore in AI Chat

Overview

QRM_TIME_BUCKETS is a header table in the Oracle E-Business Suite Risk Management (QRM) module, which forms the technical foundation of Oracle's Enterprise Treasury Risk Management (ETRM) product. The table stores the definition of time buckets — discrete, ordered date or tenor ranges such as "Overnight," "1M," "3M," or "1Y" — that risk engines use to aggregate cash flows, exposures, and market risk sensitivities into a manageable grid for reporting and analysis.

Each row represents one named bucket set (a "time bucket header") that groups downstream interval definitions into a coherent, reusable tenor framework. Rather than defining buckets inline per analysis, the Risk Management engine references a named bucket set, allowing standardization across analyses, portfolios, and regulatory reports. This design makes QRM_TIME_BUCKETS a reference/master data table rather than a transactional table.

Based on the foreign key structure — two child tables (QRM_ANALYSIS_SETTINGS and QRM_TIME_INTERVALS) referencing QRM_TIME_BUCKETS via TB_NAME — the metadata heuristic classifies this object as hub-leaning in a Data Vault model. This is a modeling suggestion: the table behaves like a business-key hub, with TB_NAME as the natural business key and its children acting as satellites or links.

Key Information Stored

The table contains 8 documented columns. The most significant are:

  • TB_NAME — the natural/business key identifying the time bucket set. It is the single column of the primary key QRM_TIME_BUCKETS_PK and the join column for all foreign key relationships. Application logic keys on this value rather than a numeric surrogate.
  • DESCRIPTION — a user-facing description of the bucket set, used for selection in setup and reporting UIs.
  • ZD_EDITION_NAME — the editioning column enabling Oracle EBS online patching (available in 12.2.x). It participates with TB_NAME in the unique index QRM_TIME_BUCKETS_U1 (TB_NAME, ZD_EDITION_NAME), which is the actual business-key candidate when editioning is active.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns recording row creation and last modification metadata.

The primary key is a business-key primary key on TB_NAME rather than a generated surrogate; in 12.2.2 deployments, the unique index QRM_TIME_BUCKETS_U1 extends this key with ZD_EDITION_NAME to support editioned data.

Common Use Cases and Queries

Typical usage includes setup verification, dependency analysis before deleting or renaming a bucket set, and reporting on which analyses reference which tenor framework.

  • List all defined bucket sets: 
    SELECT tb_name, description FROM qrm.qrm_time_buckets
ORDER BY tb_name;
  • Find analyses depending on a bucket set: 
    SELECT a.* FROM qrm.qrm_analysis_settings a
WHERE a.tb_name = :bucket_name;
  • Retrieve the intervals belonging to a bucket set: 
    SELECT i.* FROM qrm.qrm_time_intervals i
WHERE i.tb_name = :bucket_name;
  • Detect orphaned headers (no intervals defined): 
    SELECT b.tb_name FROM qrm.qrm_time_buckets b
WHERE NOT EXISTS (SELECT 1 FROM qrm.qrm_time_intervals i
                  WHERE i.tb_name = b.tb_name);

In 12.2.x, add ZD_EDITION_NAME = 'SET1' (or the appropriate edition) to queries to avoid reading across edition ranges.

Related Objects

  • QRM_TIME_INTERVALS — child table; QRM_TIME_INTERVALS.TB_NAME references QRM_TIME_BUCKETS.TB_NAME. Holds the individual interval definitions within each bucket set.
  • QRM_ANALYSIS_SETTINGS — child table; QRM_ANALYSIS_SETTINGS.TB_NAME references QRM_TIME_BUCKETS.TB_NAME. Links analysis configurations to a chosen bucket set.
  • QRM_TIME_BUCKETS_PK — primary key constraint on TB_NAME.
  • QRM_TIME_BUCKETS_U1 — unique index on (TB_NAME, ZD_EDITION_NAME), the editioning-aware business key.
  • Related QRM risk-engine and analysis views/APIs that resolve tenor grids consume the header and its intervals together.