SAP AUTH_TRACE_GET_USOBX_TRANSP Function Module for









AUTH_TRACE_GET_USOBX_TRANSP is a standard auth trace get usobx transp 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 get usobx transp FM, simply by entering the name AUTH_TRACE_GET_USOBX_TRANSP 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_GET_USOBX_TRANSP 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_GET_USOBX_TRANSP'"
IMPORTING
P_USOBX = "
P_DBCNT = "
.



EXPORTING Parameters details for AUTH_TRACE_GET_USOBX_TRANSP

P_USOBX -

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

P_DBCNT -

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

Copy and paste ABAP code example for AUTH_TRACE_GET_USOBX_TRANSP 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_p_usobx  TYPE USOBX_T, "   
lv_p_dbcnt  TYPE SY-DBCNT. "   

  CALL FUNCTION 'AUTH_TRACE_GET_USOBX_TRANSP'  "
    IMPORTING
         P_USOBX = lv_p_usobx
         P_DBCNT = lv_p_dbcnt
. " AUTH_TRACE_GET_USOBX_TRANSP




ABAP code using 7.40 inline data declarations to call FM AUTH_TRACE_GET_USOBX_TRANSP

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 DBCNT FROM SY INTO @DATA(ld_p_dbcnt).
 


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!