Show TOC

Defining Debug PointsLocate this document in the navigation structure

Prerequisites

You can find information on the prerequisites in the Debugging in the IDoc Inbox/Outbox.

Context

Using transaction WEADM or report RBDCONFIG you can easily create, change, and delete control entries for the debugging function.

Procedure

  1. Open the transaction WEADM or start report RBDCONFIG.

    The saved debug settings overview appears. Detailed information is displayed by double-clicking on an entry. The overview starts by default in the display mode. The entries that were saved last are displayed in the list. If you have not yet made any settings, the list is empty.

    The following debug points are defined in the graphic below: File inbox, HTTP inbox, and tRFC 3.x inbox.

  2. To create new entries, switch to the editing mode.
  3. Choose Create Entry.

    The list of debug types is displayed. This list only contains the debug types for which debug points have not yet been defined since only one active setting is supported for each inbox type and a global entry for the output.

    If you would like to change a definition for a debug point that has already been created, you can either delete the relevant entry from the list and create it again or change an existing ectry, for example, reactivate the same entry with an updated time entry.

  4. Select the required debug type. After selecting a row and the following confirmation, the detailed information is examined.

    There is specific data that is the same for all debug types. This is included in the Control Information field:

    Input Field

    Description

    Start time

    Adjusts itself according to the system time and determines the point in time from when debugging is to be active.

    Duration

    Time period for how long the debugging is to be active in seconds as of the time of activation (999 seconds maximum).

    Number

    Maximum number of processes that can be debugged.

    User name

    This can optionally be restricted to users so that only contexts that are created externally with this user are placed into the loop.

    Data is also requested that is dependent on the debug type:

    Debug Type

    Data Class

    Outbox (A)

    Message Type

    File Inbox (D) and XML File Inbox (X)

    Sender Port

    File Inbox (D)

    In the file inbox you can also specify when the debugging is to be started.

    • At the first statement of the function

    • At the event start

    • At every new IDoc

    tRFC 3.x Inbox (3) and tRFC 4.x Inbox (4),

    • Message Type

    • Sender Parameter Number/Type/Role (Optional)

    • Sender Port (Optional)

    HTTP Inbox (H) and SOAP Inbox (S)

    IDoc Type or Enhancement Type:

    If the inbox is to be debugged for an enhancement type then the enhancement type must be entered. If the inbox is to be debugged for a non-enhanced IDoc type then the name of the IDoc type must be specified.
  5. Confirm your entries and save the list.

Results

You have defined a debug point. If the related processes are put in a loop, you can start the debugging for these processes from the SM50.

If you want to delete a debug entry, you can do this from the debug points overview described above. Simply select an entry and then the wastebasket icon.