Results for “fnd_performance_tests”

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

Overview

FND_PERFORMANCE_TESTS is a table in the APPLSYS schema owned by the FND — Application Object Library product within Oracle E-Business Suite. As its description indicates, it stores data generated by performance tests executed against the EBS environment, capturing the parameters, run characteristics, and metadata for each test invocation. The table has a status of VALID in both the 12.1.1 and 12.2.2 documentation sets referenced by the ETRM, and its documented schema spans 15 columns. It functions as the parent or header record for individual test executions, with a child table recording the measured results.

From a Data Vault modeling perspective, the mined relationship structure suggests this object leans toward a hub. The single-column primary key, TEST_ID, is a surrogate identifier that anchors each distinct performance test record, while the child table FND_PERFORMANCE_RESULTS carries the descriptive and measurable attributes that would typically reside in a satellite. Analysts designing a dimensional or Data Vault representation should treat FND_PERFORMANCE_TESTS as the business key hub and FND_PERFORMANCE_RESULTS as its dependent satellite.

Key Information Stored

The table is organized around the surrogate primary key TEST_ID, enforced by the constraint FND_PERFORMANCE_TESTS_PK. A unique index, FND_PERFORMANCE_TESTS_U1, is defined over the combination of TEST_ID and ZD_EDITION_NAME, indicating that the edition name participates in business-key uniqueness and reflects the edition-based redefinition support present in EBS 12.2. The presence of ZD_EDITION_NAME as a documented column is consistent with the 12.2.2 online patching architecture, while 12.1.1 predates that mechanism.

The most significant columns include: TEST_ID, the primary key; TEST_DATE, recording when the test was executed; BATCH, identifying the batch grouping to which the test belongs; DATA_SIZE, indicating the volume of data processed during the run; LATENCY_TRIALS, LATENCY_ITERATIONS, BANDWIDTH_TRIALS, and BANDWIDTH_ITERATIONS, which capture the trial and iteration counts used for latency and bandwidth measurements respectively; and NOTES, a free-text field for annotations. Standard audit columns complete the structure: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN, plus ZD_EDITION_NAME for edition tracking. These attributes describe the test configuration rather than the outcome; the outcome data is held in the related results table.

Common Use Cases and Queries

Typical use cases center on benchmarking and capacity analysis. DBAs and performance engineers query this table to correlate test configurations with observed results, compare batch runs over time, or identify trends in data size versus measured throughput. A representative query joining the header to its results might read:

• Joining headers to results: SELECT t.TEST_ID, t.TEST_DATE, t.BATCH, t.DATA_SIZE, r.* FROM APPLSYS.FND_PERFORMANCE_TESTS t, APPLSYS.FND_PERFORMANCE_RESULTS r WHERE t.TEST_ID = r.TEST_ID.
• Filtering by date range to isolate a benchmarking window: WHERE t.TEST_DATE BETWEEN :start_date AND :end_date.
• Grouping by BATCH to compare aggregate behavior across batches: GROUP BY t.BATCH.
• Reviewing annotation history via the NOTES column to understand prior test intent.

These patterns support regression testing, upgrade validation, and performance tuning exercises.

Related Objects

The dominant relationship is with FND_PERFORMANCE_RESULTS, which references FND_PERFORMANCE_TESTS through the foreign key column TEST_ID. This child table holds the measured latency and bandwidth outcomes for each test header and is the primary object joined to this table in reporting. The relationship is a one-to-many parent-child association: one header row in FND_PERFORMANCE_TESTS can correspond to multiple result rows. Together these two objects form a self-contained performance-testing data model within the FND module. No other foreign-key dependencies involving FND_PERFORMANCE_TESTS are documented in the ETRM metadata, so the significant related object set is limited to the results table and the primary/unique index structures that enforce integrity on the header itself.