SAP TH_PREPARE_EXT_DEBUGGING2 Function Module for









TH_PREPARE_EXT_DEBUGGING2 is a standard th prepare ext debugging2 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for th prepare ext debugging2 FM, simply by entering the name TH_PREPARE_EXT_DEBUGGING2 into the relevant SAP transaction such as SE37 or SE38.

Function Group: THFB2
Program Name: SAPLTHFB2
Main Program: SAPLTHFB2
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function TH_PREPARE_EXT_DEBUGGING2 pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'TH_PREPARE_EXT_DEBUGGING2'"
IMPORTING
CONTEXT_ID = "
ID_LEN = "
REMOTE_DEBUG_KEY = "
REMOTE_DEBUG_KEY_LEN = "

EXCEPTIONS
NO_DEBUGGING_POSSIBLE = 1
.



EXPORTING Parameters details for TH_PREPARE_EXT_DEBUGGING2

CONTEXT_ID -

Data type: THFB_CONTEXT_ID
Optional: No
Call by Reference: No ( called with pass by value option)

ID_LEN -

Data type: I
Optional: No
Call by Reference: No ( called with pass by value option)

REMOTE_DEBUG_KEY -

Data type: USER_KEY_HEX
Optional: No
Call by Reference: No ( called with pass by value option)

REMOTE_DEBUG_KEY_LEN -

Data type: I
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NO_DEBUGGING_POSSIBLE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TH_PREPARE_EXT_DEBUGGING2 Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

DATA:
lv_context_id  TYPE THFB_CONTEXT_ID, "   
lv_no_debugging_possible  TYPE THFB_CONTEXT_ID, "   
lv_id_len  TYPE I, "   
lv_remote_debug_key  TYPE USER_KEY_HEX, "   
lv_remote_debug_key_len  TYPE I. "   

  CALL FUNCTION 'TH_PREPARE_EXT_DEBUGGING2'  "
    IMPORTING
         CONTEXT_ID = lv_context_id
         ID_LEN = lv_id_len
         REMOTE_DEBUG_KEY = lv_remote_debug_key
         REMOTE_DEBUG_KEY_LEN = lv_remote_debug_key_len
    EXCEPTIONS
        NO_DEBUGGING_POSSIBLE = 1
. " TH_PREPARE_EXT_DEBUGGING2




ABAP code using 7.40 inline data declarations to call FM TH_PREPARE_EXT_DEBUGGING2

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!