SAP FAA_DC_SHOW_TRACE_CUSTOMER Function Module for









FAA_DC_SHOW_TRACE_CUSTOMER is a standard faa dc show trace customer 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 faa dc show trace customer FM, simply by entering the name FAA_DC_SHOW_TRACE_CUSTOMER into the relevant SAP transaction such as SE37 or SE38.

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



Function FAA_DC_SHOW_TRACE_CUSTOMER 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 'FAA_DC_SHOW_TRACE_CUSTOMER'"
EXPORTING
* ID_LEADOBJ_VALUE = "
* ID_LEADOBJ_TYPE = "
* ID_ANLN1 = "
* ID_ANLN2 = "
.



IMPORTING Parameters details for FAA_DC_SHOW_TRACE_CUSTOMER

ID_LEADOBJ_VALUE -

Data type: ANLA-BUKRS
Optional: Yes
Call by Reference: Yes

ID_LEADOBJ_TYPE -

Data type: STRING
Optional: Yes
Call by Reference: Yes

ID_ANLN1 -

Data type: ANLA-ANLN1
Optional: Yes
Call by Reference: Yes

ID_ANLN2 -

Data type: ANLA-ANLN2
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for FAA_DC_SHOW_TRACE_CUSTOMER 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_id_leadobj_value  TYPE ANLA-BUKRS, "   
lv_id_leadobj_type  TYPE STRING, "   
lv_id_anln1  TYPE ANLA-ANLN1, "   
lv_id_anln2  TYPE ANLA-ANLN2. "   

  CALL FUNCTION 'FAA_DC_SHOW_TRACE_CUSTOMER'  "
    EXPORTING
         ID_LEADOBJ_VALUE = lv_id_leadobj_value
         ID_LEADOBJ_TYPE = lv_id_leadobj_type
         ID_ANLN1 = lv_id_anln1
         ID_ANLN2 = lv_id_anln2
. " FAA_DC_SHOW_TRACE_CUSTOMER




ABAP code using 7.40 inline data declarations to call FM FAA_DC_SHOW_TRACE_CUSTOMER

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 BUKRS FROM ANLA INTO @DATA(ld_id_leadobj_value).
 
 
"SELECT single ANLN1 FROM ANLA INTO @DATA(ld_id_anln1).
 
"SELECT single ANLN2 FROM ANLA INTO @DATA(ld_id_anln2).
 


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!