Show TOC

Procedure documentationEvaluating Transactional Correctness Using SAP Solution Manager

 

You can evaluate the transactional correctness of one of your managed systems, from SAP Solution Manager. You can call it from the Data Consistency Management tile on the Fiori launchpad.

Procedure

Step 1: Start and Stop Traces

  1. On the ST05 tab page, choose the RFC destination of the managed system for which you want to check the transactional correctness.

  2. Enter the user who is to execute the program you want to analyze.

  3. Under Tables, the list contains tables that are to be excluded from the transactional correctness analysis.

    The tables listed by default should be excluded, since they are not relevant for the analysis, and might jeopardize the analysis if they are included. Review this list before each analysis.

    Choose Insert Row or Append Row, to add tables. Choose Delete Row to remove a table from the list.

  4. Choose Start Trace to start the database performance trace in the managed system.

  5. Choose Stop Trace to finish the trace in the managed system.

Step 2: Select Traces

  1. Under Trace Restrictions, enter the RFC destination of the managed system containing the program you want to analyze.

  2. Enter the ID of the user who executed the program you want to analyze. This should be the user that has been traced.

  3. The Date and Time fields are pre-filled by the system, with the start date and time and end date and time of the last trace. You can change the contents of these fields, if required.

  4. If the trace records are to be distinguished by the extended passport root ID, the extended passport connection ID, the extended passport connection counter, or the TransGUID, you can enter the required data.

  5. Under Data for Evaluation, if the program you traced used an RFC, you can either choose the RFC type or “Unknown RFC Type” if an un-identified RFC was used. You can also leave this field blank.

  6. Choose Load Trace.

    The system displays the trace records based on the selection criteria specified.

    Field

    Description

    Server Name

    Name of application server the database trace record was read from

    Trace Rec. Number

    Number of the evaluated database trace record

    Client

    Client of the managed system in which the database was traced

    Date

    Time stamp (date) of the recorded trace

    Time

    Time stamp (time) of the recorded trace

    Object Name

    Table the statement was performed on

    Statement

    Analyzed statement

    Note Note

    The tool only analyzes and lists INSERT, UPDATE, UPSERT, and DELETE statements, and COMMITs and ROLLBACKs.

    End of the note.

    Work Process no.

    The number of the work process in which the SQL statement was executed in the managed system.

    Executed Operation

    The SQL operation related to the trace record.

    Note Note

    The tool only analyzes and lists REEXEC, EXECSTA, and EXCUSED statements. For the analysis of enqueues and dequeues, ENQUEUE, DEQUEUE, and DEQUEUE ALL statements are also considered.

    End of the note.

    Program Name

    Program that was executed and traced in the managed system

    Process Type

    Work process type in which the action was executed in the managed system

    Executed Transaction

    Transaction the trace was executed from (in the managed system)

    User Name

    User ID that was traced in the managed system

    TransGUID

    Transaction GUID of the captured trace record

    Extended Passport Root ID

    Extended Passport Root ID of the captured trace record

    Extended Passport Connection ID

    Extended Passport Connection ID of the captured trace record

    Extended Passport Connection Counter

    Extended Passport Connection Counter of the captured trace record

  7. Choose Upload/Download to download the results.

  8. Select all trace records that are to be analyzed. Ideally, select all trace records that belong to the same SAP logical unit of work (SAP LUW), so that affected data belongs together logically, and should be posted to the database together or not at all.

Step 3: Display Result

  1. Choose the Commit Structure tab page to display the check results of the commit structure of the analyzed program, based on the selected trace records.

    The system evaluates how many change blocks are contained in the trace (a “change block” is ended by a COMMIT statement) and whether there is a risk to the transactional correctness of the program. The Description for TC check result line column contains a warning message, if transactional correctness is at risk.

    For more information, see Handling Transaction Correctness Warning Messages.

  2. Choose the Enqueues tab page to display the result of the enqueue/dequeue structure check of the analyzed program, based on the selected records.

    They system evaluates whether correct and complete enqueues and dequeues are set, and whether they match the captured database changes. The Description for TC check result line column contains a warning message if transactional correctness is at risk.

    For more information, see Handling Transaction Correctness Warning Messages.