SAP Function Modules

LTR_TRACE_GET_TRACE SAP Function module - LTR: Get Trace Data







LTR_TRACE_GET_TRACE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name LTR_TRACE_GET_TRACE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SLTR_TRACE_TOOLS
Released Date: Not Released
Processing type: Remote-Enabled
remote enabled module settings


Pattern for FM LTR_TRACE_GET_TRACE - LTR TRACE GET TRACE





CALL FUNCTION 'LTR_TRACE_GET_TRACE' "LTR: Get Trace Data
  EXPORTING
    iv_pcl_package_id =         " cnv_mbt_packid  Package Number of Transformation / Analysis Package
    iv_bob_guid =               " ltr_business_object_guid  LTR: Business Object GUID
    iv_tabname =                " tabname       Table Name
  IMPORTING
    et_trace =                  " ltr_t_delim_rlt_t  .
  EXCEPTIONS
    NO_AUTHORITY = 1            "
    .  "  LTR_TRACE_GET_TRACE

ABAP code example for Function Module LTR_TRACE_GET_TRACE





The ABAP code below is a full code listing to execute function module LTR_TRACE_GET_TRACE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_et_trace  TYPE LTR_T_DELIM_RLT_T .

DATA(ld_iv_pcl_package_id) = 'Check type of data required'.
DATA(ld_iv_bob_guid) = 'Check type of data required'.
DATA(ld_iv_tabname) = 'Check type of data required'. . CALL FUNCTION 'LTR_TRACE_GET_TRACE' EXPORTING iv_pcl_package_id = ld_iv_pcl_package_id iv_bob_guid = ld_iv_bob_guid iv_tabname = ld_iv_tabname IMPORTING et_trace = ld_et_trace EXCEPTIONS NO_AUTHORITY = 1 . " LTR_TRACE_GET_TRACE
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_et_trace  TYPE LTR_T_DELIM_RLT_T ,
ld_iv_pcl_package_id  TYPE CNV_MBT_PACKID ,
ld_iv_bob_guid  TYPE LTR_BUSINESS_OBJECT_GUID ,
ld_iv_tabname  TYPE TABNAME .

ld_iv_pcl_package_id = 'Check type of data required'.
ld_iv_bob_guid = 'Check type of data required'.
ld_iv_tabname = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name LTR_TRACE_GET_TRACE or its description.