SAP ISU_DEVCHECK_EXIST_FUBA Function Module for









ISU_DEVCHECK_EXIST_FUBA is a standard isu devcheck exist fuba 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 isu devcheck exist fuba FM, simply by entering the name ISU_DEVCHECK_EXIST_FUBA into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_DEVCHECK_EXIST_FUBA 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 'ISU_DEVCHECK_EXIST_FUBA'"
EXPORTING
X_FINAL_CALL = "
X_FUBANAME = "
X_FKTS_GRUPPE = "

EXCEPTIONS
FUGR_NOT_FOUND = 1 FUBA_NOT_FOUND = 2
.



IMPORTING Parameters details for ISU_DEVCHECK_EXIST_FUBA

X_FINAL_CALL -

Data type: REGEN-KENNZX
Optional: No
Call by Reference: No ( called with pass by value option)

X_FUBANAME -

Data type: EREP_FUBA-FUBA
Optional: No
Call by Reference: No ( called with pass by value option)

X_FKTS_GRUPPE -

Data type: TLIBG-AREA
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

FUGR_NOT_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

FUBA_NOT_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for ISU_DEVCHECK_EXIST_FUBA 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_x_final_call  TYPE REGEN-KENNZX, "   
lv_fugr_not_found  TYPE REGEN, "   
lv_x_fubaname  TYPE EREP_FUBA-FUBA, "   
lv_fuba_not_found  TYPE EREP_FUBA, "   
lv_x_fkts_gruppe  TYPE TLIBG-AREA. "   

  CALL FUNCTION 'ISU_DEVCHECK_EXIST_FUBA'  "
    EXPORTING
         X_FINAL_CALL = lv_x_final_call
         X_FUBANAME = lv_x_fubaname
         X_FKTS_GRUPPE = lv_x_fkts_gruppe
    EXCEPTIONS
        FUGR_NOT_FOUND = 1
        FUBA_NOT_FOUND = 2
. " ISU_DEVCHECK_EXIST_FUBA




ABAP code using 7.40 inline data declarations to call FM ISU_DEVCHECK_EXIST_FUBA

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 KENNZX FROM REGEN INTO @DATA(ld_x_final_call).
 
 
"SELECT single FUBA FROM EREP_FUBA INTO @DATA(ld_x_fubaname).
 
 
"SELECT single AREA FROM TLIBG INTO @DATA(ld_x_fkts_gruppe).
 


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!