Search Results qrm_time_intervals_u1




Overview
Explore in AI Chat

Overview

QRM.QRM_TIME_INTERVALS is a reference table within the Oracle E-Business Suite Quality and Risk Management (QRM) module, specifically supporting the Enterprise Treasury and Risk Management (ETRM) functionality. The table stores the individual time intervals that collectively define a set of time buckets used in financial instrument valuation, interest rate curve construction, and cash flow projection. Each row represents a discrete time interval tied to a parent time bucket definition in QRM_TIME_BUCKETS.

From a Data Vault modeling perspective, the mined relationship structure suggests a satellite-leaning classification. The table carries descriptive attributes (INTERVAL_LENGTH, INTERVAL_TYPE, LABEL) that describe a parent business entity (time buckets), which is characteristic of satellite behavior. This classification is a heuristic modeling suggestion based on FK structure and should not be interpreted as a formal Data Vault design.

Key Information Stored

The table's physical schema documents 11 columns in Oracle EBS 12.2.2. The most significant columns are:

  • TB_NAME (VARCHAR2, 20) — Identifies the parent time bucket definition; part of the composite primary key and the foreign key to QRM_TIME_BUCKETS.
  • SEQUENCE_NUMBER (NUMBER) — Defines the ordering of the time interval within its parent bucket; also part of the composite primary key.
  • INTERVAL_LENGTH (NUMBER) — Numeric value specifying the duration of the interval.
  • INTERVAL_TYPE (VARCHAR2) — The unit of measure for the interval length, derived from the FND Lookup Type QRM_PERIOD_LENGTH (e.g., days, months, years).
  • LABEL (VARCHAR2, 20) — Descriptive label for the time interval.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking row creation and modification.

The primary key is QRM_TIME_INTERVALS_PK on (SEQUENCE_NUMBER, TB_NAME). Two unique indexes are documented: QRM_TIME_INTERVALS_N1 on (TB_NAME, SEQUENCE_NUMBER, ZD_EDITION_NAME) and QRM_TIME_INTERVALS_U1 on (SEQUENCE_NUMBER, TB_NAME, ZD_EDITION_NAME). The N1 index, referenced in the user's search query, serves as a business-key candidate and supports efficient lookups by time bucket name. The ZD_EDITION_NAME column appears in the 12.2.2 documented schema, reflecting edition-based redefinition support.

Common Use Cases and Queries

This table is queried when developers or analysts need to enumerate the intervals that make up a given time bucket, typically for curve construction, gap analysis, or reporting on bucket configurations. A typical query pattern joining the child intervals to their parent buckets is:

  • Retrieve all intervals for a specific bucket: SELECT sequence_number, interval_length, interval_type, label FROM qrm.qrm_time_intervals WHERE tb_name = :bucket_name ORDER BY sequence_number;
  • List buckets and interval counts: SELECT tb_name, COUNT(*) FROM qrm.qrm_time_intervals GROUP BY tb_name;
  • Reverse-lookup interval type lookups: join to FND_LOOKUP_VALUES where lookup_type = 'QRM_PERIOD_LENGTH' to translate INTERVAL_TYPE codes into descriptions.

Reporting use cases include validating bucket configuration completeness, auditing changes to interval definitions via the WHO columns, and supporting migration or setup validation during 12.1.1 to 12.2.2 upgrades.

Related Objects

The most significant related objects are:

  • QRM.QRM_TIME_BUCKETS — Parent table; joined on TB_NAME. QRM_TIME_INTERVALS.TB_NAME is a foreign key to this table, defining the bucket to which each interval belongs.
  • QRM_TIME_INTERVALS (APPS synonym) — Public synonym exposing the QRM table to the APPS schema.
  • FND_LOOKUP_VALUES — Provides the valid values for INTERVAL_TYPE via lookup type QRM_PERIOD_LENGTH.
  • FND_APPLICATION / FND_TABLES — Metadata views registering the object within the EBS data dictionary.
  • ZD_EDITION_NAME-dependent editioning views — In 12.2.2, edition-based redefinition views wrap this table for online patching.

No upstream database objects are referenced beyond QRM_TIME_BUCKETS, confirming the table's role as a descriptive satellite within the QRM time-bucket domain.