Results for “correction_time”

8 results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_PERFORMANCE_RESULTS is a table in the APPLSYS schema of the Oracle E-Business Suite Application Object Library (FND) product. As documented in the ETRM repository, it stores the results of network performance tests executed by the EBS environment. In EBS 12.1.1 and 12.2.2, this table forms part of the infrastructure used by the Oracle Applications Manager (OAM) and related diagnostics utilities to capture timing and latency measurements between client tiers, application servers, and database nodes. The data supports troubleshooting of slow forms response, network bottleneck analysis, and capacity assessments for globally distributed deployments.

From a Data Vault modeling perspective, the heuristic classification provided in the metadata is satellite-leaning. This suggests the table behaves primarily as a descriptive satellite attached to a parent test definition, capturing measured attributes at a point in time rather than acting as a standalone hub or an associative link. The parent relationship is established through TEST_ID, which references the FND_PERFORMANCE_TESTS table, positioning FND_PERFORMANCE_RESULTS as the measurement companion to the test definition.

Key Information Stored

The documented physical schema contains thirteen columns. The most operationally significant are listed below.

  • TEST_ID — Identifies the performance test that produced this result row. It is a foreign key to FND_PERFORMANCE_TESTS and forms the first component of the composite primary key.
  • TYPE — Classifies the kind of measurement recorded, distinguishing categories of network or response-time tests.
  • TRIAL_ID — Distinguishes individual repetitions of a test, allowing throughput and variance analysis across multiple runs.
  • ELAPSED_TIME — The measured duration, in the unit defined by the test, representing the core performance metric.
  • START_TIME and END_TIME — The wall-clock boundaries of the test execution, enabling correlation with concurrent system activity or user-reported incidents.
  • CORRECTION_TIME — An adjustment applied to the raw elapsed measurement, typically for clock skew or latency compensation between nodes.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who inserted and last modified each row.
  • ZD_EDITION_NAME — The editioning column introduced by the EBS 12.2 online patching architecture, identifying the edition under which the row was created.

The surrogate primary key is FND_PERFORMANCE_RESULTS_PK, defined on (TEST_ID, TYPE, TRIAL_ID). A unique index, FND_PERFORMANCE_RESULTS_U1, extends this business key with ZD_EDITION_NAME, reflecting the edition-aware uniqueness enforced in 12.2.2.

Common Use Cases and Queries

Typical uses include diagnosing intermittent slowness, validating network links after infrastructure changes, and building historical baselines for response-time SLAs. A representative query joins the parent definition to inspect the slowest trials:

  • Analyzing high-latency results: SELECT r.TEST_ID, r.TRIAL_ID, r.ELAPSED_TIME, r.START_TIME FROM FND_PERFORMANCE_RESULTS r WHERE r.ELAPSED_TIME > :threshold ORDER BY r.ELAPSED_TIME DESC;
  • Trending elapsed time across trials: aggregate AVG, MIN, and MAX of ELAPSED_TIME grouped by TEST_ID and TYPE.
  • Auditing rows in the current edition by filtering on ZD_EDITION_NAME in 12.2.2.

Because the table can grow with each test cycle, reports should always filter by TEST_ID and a date range rather than scanning the full table.

Related Objects

  • FND_PERFORMANCE_TESTS — The parent table referenced by FND_PERFORMANCE_RESULTS.TEST_ID; it defines each test executed.
  • FND_PERFORMANCE_RESULTS_PK — Primary key constraint on (TEST_ID, TYPE, TRIAL_ID).
  • FND_PERFORMANCE_RESULTS_U1 — Unique index on (TEST_ID, TYPE, TRIAL_ID, ZD_EDITION_NAME).
  • FND_CONCURRENT_REQUESTS — Frequently correlated when performance diagnostics are run as concurrent programs.
  • Oracle Applications Manager (OAM) diagnostics pages and the FND diagnostic framework consume this table for monitoring dashboards.