SAP DD_F4_GET_TRIGGER_BODY Function Module for

Search SAP Function Modules

DD_F4_GET_TRIGGER_BODY is a standard dd f4 get trigger body 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 dd f4 get trigger body FM, simply by entering the name DD_F4_GET_TRIGGER_BODY into the relevant SAP transaction such as SE37 or SE38.

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

Function DD_F4_GET_TRIGGER_BODY 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 'DD_F4_GET_TRIGGER_BODY'"
  EXPORTING
   OBJECTNAME =  "Trigger name

TABLES
   TRIGGERCODE =  "

.

IMPORTING Parameters details for DD_F4_GET_TRIGGER_BODY

OBJECTNAME - Trigger name

Data type: DDTRIGNAME
Optional: No
Call by Reference: Yes

TABLES Parameters details for DD_F4_GET_TRIGGER_BODY

TRIGGERCODE -

Data type:
Optional: No
Call by Reference: Yes

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

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