Search Results csr_timers_b




Overview
Explore in AI Chat

Overview

CSR_TIMERS_B is a table in the CSR (Scheduler) product schema of Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. Per the ETRM repository metadata, it stores timing data temporarily for the current test run. The "B" suffix follows the standard EBS convention for the base table of a table/view pair, indicating that CSR_TIMERS_B holds the physical rows while a corresponding translation or reporting view exposes them. In practice, CSR_TIMERS_B acts as a short-lived diagnostic and instrumentation structure: scheduler processes write elapsed-time measurements and task milestones here during execution so that performance can be observed and analyzed before the data is purged or superseded by the next run.

The documented physical schema in 12.2.2 comprises fourteen columns owned by the CSR schema. From a Data Vault modeling perspective, the ETRM heuristic classification for this object is standalone, meaning it has no child tables depending on it and participates in no hub-to-link chains. A modeler would therefore treat CSR_TIMERS_B as a satellite-like structure (a descriptive, keyed attribute set) rather than a hub or link, since its purpose is measurement capture rather than master-data or relationship resolution.

Key Information Stored

The table carries the full complement of EBS standard WHO columns plus a small set of business attributes. The most significant columns are:

  • SEQ — the sequence identifier and the primary key candidate for each timing record. Because the metadata describes it as a standalone table with no dependent foreign keys, SEQ effectively serves as the surrogate key for this structure.
  • NAME — the identity of the timer, counter, or measurement point being recorded during the test run. This is the principal business-key candidate when combined with SEQ.
  • VALUE — the numeric or textual timing value captured for the named timer, typically elapsed duration or a counter total.
  • MEANING and DESCRIPTION — human-readable context describing what the timer measures and how it should be interpreted.
  • TRIP_POSITION and TRIP_TASKS — positional and task-related attributes that tie the timing measurement to a specific point within a scheduler trip or task sequence.
  • SECURITY_GROUP_ID — the multi-tenant / data-security grouping column, which is the table's only documented foreign key (see below).
  • OBJECT_VERSION_NUMBER — the optimistic locking column used by the EBS framework to detect concurrent updates.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — the standard WHO audit columns tracking insert and update accountability.

No unique index beyond the sequence-keyed structure is documented, so NAME alone should not be assumed to be unique; a query filter on NAME and the run's creation timestamps is the safe approach.

Common Use Cases and Queries

The primary use case is performance analysis of the scheduler's test runs: developers and DBAs query the table to identify slow timer entries and understand where execution time is spent. A typical pattern selects the slowest recorded timers for a run window:

  • SELECT name, value, meaning, creation_date FROM csr.csr_timers_b WHERE creation_date >= :run_start ORDER BY value DESC;
  • Filtering by NAME to trend a single metric across successive test runs: SELECT seq, value, creation_date FROM csr.csr_timers_b WHERE name = :timer_name ORDER BY creation_date;
  • Joining to the security grouping to respect data access: SELECT t.name, t.value FROM csr.csr_timers_b t WHERE t.security_group_id = :sgid;

Because the data is transient, reporting is normally ad hoc and diagnostic rather than historical; extract rows to a staging table before the next run overwrites them if longer retention is required.

Related Objects

The documented relationship data is limited, identifying a single foreign key dependency:

  • FND_SECURITY_GROUPS — joined on CSR_TIMERS_B.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID; this is the only documented foreign key and the primary means of scoping access to timing rows.
  • FND_OBJECTS / FND_APPLICATION — indirectly relevant because the CSR schema and its menu entries are registered there.
  • CSR_TIMERS_TL / CSR_TIMERS_V (or the corresponding translation view) — the base/translation or base/view partner implied by the "_B" suffix convention.
  • FND_CONCURRENT_REQUESTS and FND_LOG_MESSAGES — frequently correlated with timing data to tie measurements to the concurrent program invocation and its log.
  • FND_USER — joined on CREATED_BY and LAST_UPDATED_BY to attribute timing records to the responsible user.

Given the standalone classification and the single documented foreign key, dependency analysis for this table is straightforward, and its impact radius on the wider EBS data model is minimal.