SAP AUTH_TRACE_SET_TADIR Function Module for









AUTH_TRACE_SET_TADIR is a standard auth trace set tadir 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 auth trace set tadir FM, simply by entering the name AUTH_TRACE_SET_TADIR into the relevant SAP transaction such as SE37 or SE38.

Function Group: SAUTHTRACE
Program Name: SAPLSAUTHTRACE
Main Program: SAPLSAUTHTRACE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function AUTH_TRACE_SET_TADIR 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 'AUTH_TRACE_SET_TADIR'"
EXPORTING
PGMID = "Program ID in requests and tasks
OBJECT = "Object Type
OBJ_NAME = "Object Name in Object Directory

EXCEPTIONS
INVALID_OBJECT = 1 INTERNAL_ERROR = 2
.



IMPORTING Parameters details for AUTH_TRACE_SET_TADIR

PGMID - Program ID in requests and tasks

Data type: USOBHASH-PGMID
Optional: No
Call by Reference: No ( called with pass by value option)

OBJECT - Object Type

Data type: USOBHASH-OBJECT
Optional: No
Call by Reference: No ( called with pass by value option)

OBJ_NAME - Object Name in Object Directory

Data type: USOBHASH-OBJ_NAME
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

INVALID_OBJECT -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR - An internal error has occurred

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for AUTH_TRACE_SET_TADIR 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_pgmid  TYPE USOBHASH-PGMID, "   
lv_invalid_object  TYPE USOBHASH, "   
lv_object  TYPE USOBHASH-OBJECT, "   
lv_internal_error  TYPE USOBHASH, "   
lv_obj_name  TYPE USOBHASH-OBJ_NAME. "   

  CALL FUNCTION 'AUTH_TRACE_SET_TADIR'  "
    EXPORTING
         PGMID = lv_pgmid
         OBJECT = lv_object
         OBJ_NAME = lv_obj_name
    EXCEPTIONS
        INVALID_OBJECT = 1
        INTERNAL_ERROR = 2
. " AUTH_TRACE_SET_TADIR




ABAP code using 7.40 inline data declarations to call FM AUTH_TRACE_SET_TADIR

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.

"SELECT single PGMID FROM USOBHASH INTO @DATA(ld_pgmid).
 
 
"SELECT single OBJECT FROM USOBHASH INTO @DATA(ld_object).
 
 
"SELECT single OBJ_NAME FROM USOBHASH INTO @DATA(ld_obj_name).
 


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!