SAP STOP_IFI_DB_TRACE Function Module for STOP_IFI_DB_TRACE

Search SAP Function Modules

STOP_IFI_DB_TRACE is a standard stop ifi db trace SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for STOP_IFI_DB_TRACE processing and below is the pattern details for this FM, 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 stop ifi db trace FM, simply by entering the name STOP_IFI_DB_TRACE into the relevant SAP transaction such as SE37 or SE38.

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

Function STOP_IFI_DB_TRACE 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 'STOP_IFI_DB_TRACE'"STOP_IFI_DB_TRACE
 IMPORTING
   TRCSTAT =  "Status of  IFI DB Trace
   TRCSTATTXT =  "Status of  IFI DB Trace Text

EXCEPTIONS
   REQUEST_TO_OLD = 1    IFI_ERROR = 10    NO_BUFFER_SPACE_IN_SHM = 2    UNVALID_REQUEST_ID = 3    ANSWER_IS_NOT_YET_AVAILABLE = 4    COMMUNICATION_ERROR = 5    ANSWER_NOT_POSSIBLE = 6    COMMUNICATION_BUFFER_TO_SMALL = 7    UNKNOWN_ERROR = 8    ILLEGAL_PARAMETER = 9 

.

EXPORTING Parameters details for STOP_IFI_DB_TRACE

TRCSTAT - Status of IFI DB Trace

Data type: DB2IFIDBTR-TRCSTAT
Optional: No
Call by Reference: Yes

TRCSTATTXT - Status of IFI DB Trace Text

Data type: DB2IFIDBTR-TRCSTATTXT
Optional: No
Call by Reference: Yes

EXCEPTIONS details

REQUEST_TO_OLD -

Data type:
Optional: No
Call by Reference: Yes

IFI_ERROR -

Data type:
Optional: No
Call by Reference: Yes

NO_BUFFER_SPACE_IN_SHM -

Data type:
Optional: No
Call by Reference: Yes

UNVALID_REQUEST_ID -

Data type:
Optional: No
Call by Reference: Yes

ANSWER_IS_NOT_YET_AVAILABLE -

Data type:
Optional: No
Call by Reference: Yes

COMMUNICATION_ERROR -

Data type:
Optional: No
Call by Reference: Yes

ANSWER_NOT_POSSIBLE -

Data type:
Optional: No
Call by Reference: Yes

COMMUNICATION_BUFFER_TO_SMALL -

Data type:
Optional: No
Call by Reference: Yes

UNKNOWN_ERROR -

Data type:
Optional: No
Call by Reference: Yes

ILLEGAL_PARAMETER -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for STOP_IFI_DB_TRACE 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.

ABAP code using 7.40 inline data declarations to call FM STOP_IFI_DB_TRACE

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