Show TOC

Simulating and Debugging DTP RequestsLocate this document in the navigation structure

Use

Simulating the data update and debugging a data transfer process request (DTP request) help you to analyze an incorrect DTP request.

In this way you can also simulate a transformation prior to the actual data transfer if you would like to check whether it provides the desired results.

Procedure

Simple Simulation and Debugging

  1. If you want to execute a standard DTP in debug mode, choose Serially in the Dialog Process (for Debugging) as the processing mode on the Execute tab page in the DTP maintenance.
  2. In the overview for program execution, define breakpoints for debugging by choosing Change Breakpoints.
  3. Choose Simulate.

    The simulation request is started. The request is processed synchronously in a dialog process. If you defined breakpoints, you go to the ABAP Debugger.If you defined a breakpoint for the transformation, you can jump directly to the corresponding data in the ABAP source code from the Data section.

    The result of the simulation is displayed in the DTP monitor.

Simulation and Debugging in Expert Mode

In addition to setting breakpoints, expert mode enables you to specify selections for simulating the request and for defining the substep after which you want to write to temporary store during the simulation.

  1. You can perform the simulation of a request in expert mode from the DTP maintenance or the DTP monitor.
    1. In the DTP maintenance, select the processing mode Serially in the Dialog Process (for Debugging) on the Execute tab page, set the indicator Expert Mode, and choose Simulate.
    2. In the DTP monitor, choose Debugging.

    The Debug Request screen appears.

  2. Make the settings on the Filter tab page.

    When you call the simulation from the DTP monitor, the filter settings that are displayed as initial are copied from the request displayed in the monitor. When you call it from the DTP maintenance, the filter settings displayed as initial are copied from the next "real" request of the DTP.

    • You can change the filter in order to restrict the data for the analysis. In addition to the selection with the fields of the source, you can also restrict the request ID (REQUID), data package ID (DATAPKID), and data record number (RECORD) with the technical fields. You should restrict the data in order to prevent the simulation from running for a long time, for example, if you loaded a large amount of data. Selections are also recommended if the fields refer to certain data records in the source or to a certain selection of data in the source.
    • With Save as Variant you can store the selections in the database for later use.
    • With Load Variant you can call a selection variant stored for this request.
    • With Technical Field Name / Description you can switch between displaying the technical field name and the description.
    • With Change Selection you can change the list of fields displayed in the selection screen.
  3. Make your settings on the Temporary Storage and Breakpoints tab page.

    You can define if and when to write data to temporary storage during processing and set breakpoints at different times.

  4. Choose Execute.

    The simulation request is started. The request is processed synchronously in a dialog process. If you defined breakpoints, you go to the ABAP Debugger.If you defined a breakpoint for the transformation, you can jump directly to the corresponding data in the ABAP source code from the Data section.

    The result of the simulation is displayed in the monitor and can be analyzed.