SAP ENH_BADI_DEF_CHECK_INTERFACES Function Module for









ENH_BADI_DEF_CHECK_INTERFACES is a standard enh badi def check interfaces 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 enh badi def check interfaces FM, simply by entering the name ENH_BADI_DEF_CHECK_INTERFACES into the relevant SAP transaction such as SE37 or SE38.

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



Function ENH_BADI_DEF_CHECK_INTERFACES 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 'ENH_BADI_DEF_CHECK_INTERFACES'"
EXPORTING
IM_INTERFACE = "

IMPORTING
R_SINGLE_OK = "
.



IMPORTING Parameters details for ENH_BADI_DEF_CHECK_INTERFACES

IM_INTERFACE -

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

EXPORTING Parameters details for ENH_BADI_DEF_CHECK_INTERFACES

R_SINGLE_OK -

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

Copy and paste ABAP code example for ENH_BADI_DEF_CHECK_INTERFACES 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_r_single_ok  TYPE ENHBOOLEAN, "   
lv_im_interface  TYPE SEOCLSKEY. "   

  CALL FUNCTION 'ENH_BADI_DEF_CHECK_INTERFACES'  "
    EXPORTING
         IM_INTERFACE = lv_im_interface
    IMPORTING
         R_SINGLE_OK = lv_r_single_ok
. " ENH_BADI_DEF_CHECK_INTERFACES




ABAP code using 7.40 inline data declarations to call FM ENH_BADI_DEF_CHECK_INTERFACES

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



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!