How To Fix PERFTRAC065 - Execute performance test; reference performance test not unique

PERFTRAC065 - Overview

• Message type: E = Error

• Message class: PERFTRAC - Messages on Global Performance Analysis

• Message number: 065

• Message text: Execute performance test; reference performance test not unique

What causes this issue?

You checked "Reference Performance Test" on another screen. You also
specified that a performance test should be created per test case.
Since all performance tests belong to the same specified log ID, only
one performance test can be a reference performance test. However,
this is not clear from your entry.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Either create only one performance test for all test cases, or reset
the "Reference Performance Test" indicator.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message PERFTRAC065 - Execute performance test; reference performance test not unique ?

  The SAP error message PERFTRAC065 indicates that when trying to execute a performance test, the system has found that the reference performance test is not unique. This typically occurs in the context of performance testing within the SAP system, where the system expects a single reference test to be associated with the execution request, but multiple entries are found.
  
  Cause:
  
  Duplicate Entries: There are multiple performance tests defined in the system that match the criteria for the reference test you are trying to execute.
  
  Configuration Issues: The configuration of the performance tests may not be set up correctly, leading to ambiguity in identifying the correct test.
  Data Integrity Issues: There may be inconsistencies or errors in the underlying data that define the performance tests.
  
  
  Solution:
  
  
  Identify Duplicate Tests:
  
  Go to the transaction code related to performance testing (e.g., ST03N or ST05) and check the list of performance tests.
  Look for tests that have the same name or criteria