Evaluating Transaction Correctness

The transactional correctness evaluation consists of two steps. As the transaction correctness tool evaluates performance traces, you have to record a trace of the transaction you want to evaluate, before using the tool.

Note Note

To ensure correct results of the transaction correctness tool, take the following measures:

Record only a single SAP logical unit of work (LUW) in a trace, that is, steps that are to be processed together from a logical point of view, to grant transactional correctness.
While recording the trace, do not use update debugging.
Process inbound queues with a user different from your own user.
To do so, fill the Destination With Logon Data field in the QIN scheduler (transaction SMQR). If the field is empty, the system uses your user to process inbound queue entries you created.

End of the note.

Procedure

Step 1: Recording a Performance Trace

Go to transaction ST05.
Select SQL Trace and Enqueue Trace.
Choose Activate Trace.
Execute the transaction or step that you want to analyze.
Choose Deactivate Trace.

Step 2: Using the Transaction Correctness Tool

Start the transaction correctness tool by calling report /SDF/DCC_TC.
The system displays the selection screen for the trace records that can be evaluated. If you have captured an RFC call in the trace, enter the RFC type under RFC Type for Evaluation:
- NUNI for no RFC or un-identified RFC type
- SRFC for synchronous RFC
- ARFC for asynchronous RFC
- QRFC for queued RFC
Select the performance trance you have recorded, and choose Continue.
The system lists all database changes in your performance trace, with comments indicating where transactional correctness is at risk. For more information, see Displaying Results Of the Transaction Correctness Check.

More Information

For more information, in the SAP NetWeaver documentation at http://help.sap.com/netweaver, search for Performance Trace.