SAP EU_BEFORE_TADIR_CHANGED Function Module for
EU_BEFORE_TADIR_CHANGED is a standard eu before tadir changed 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 eu before tadir changed FM, simply by entering the name EU_BEFORE_TADIR_CHANGED into the relevant SAP transaction such as SE37 or SE38.
Function Group: EU_BADI_CALLS
Program Name: SAPLEU_BADI_CALLS
Main Program: SAPLEU_BADI_CALLS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EU_BEFORE_TADIR_CHANGED 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 'EU_BEFORE_TADIR_CHANGED'".
EXPORTING
IM_TROBJTYPE = "
IM_SOBJ_NAME = "
IMPORTING
EX_OBJECT_IS_SWITCHABLE = "
IMPORTING Parameters details for EU_BEFORE_TADIR_CHANGED
IM_TROBJTYPE -
Data type: TROBJTYPEOptional: No
Call by Reference: Yes
IM_SOBJ_NAME -
Data type: SOBJ_NAMEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for EU_BEFORE_TADIR_CHANGED
EX_OBJECT_IS_SWITCHABLE -
Data type: FLAGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for EU_BEFORE_TADIR_CHANGED 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_im_trobjtype | TYPE TROBJTYPE, " | |||
| lv_ex_object_is_switchable | TYPE FLAG, " | |||
| lv_im_sobj_name | TYPE SOBJ_NAME. " |
|   CALL FUNCTION 'EU_BEFORE_TADIR_CHANGED' " |
| EXPORTING | ||
| IM_TROBJTYPE | = lv_im_trobjtype | |
| IM_SOBJ_NAME | = lv_im_sobj_name | |
| IMPORTING | ||
| EX_OBJECT_IS_SWITCHABLE | = lv_ex_object_is_switchable | |
| . " EU_BEFORE_TADIR_CHANGED | ||
ABAP code using 7.40 inline data declarations to call FM EU_BEFORE_TADIR_CHANGED
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