SAP FM_BUD_CHECK_COMPONENT Function Module for









FM_BUD_CHECK_COMPONENT is a standard fm bud check component 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 fm bud check component FM, simply by entering the name FM_BUD_CHECK_COMPONENT into the relevant SAP transaction such as SE37 or SE38.

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



Function FM_BUD_CHECK_COMPONENT 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 'FM_BUD_CHECK_COMPONENT'"
EXPORTING
* I_FIKRS = "
* I_STANDARD_ENV = "
* I_KOM_ENV = "
* I_EU_ENV = "
* I_NO_HIERARCHY_ENV = "
.



IMPORTING Parameters details for FM_BUD_CHECK_COMPONENT

I_FIKRS -

Data type: FM01-FIKRS
Optional: Yes
Call by Reference: Yes

I_STANDARD_ENV -

Data type: XFELD
Optional: Yes
Call by Reference: Yes

I_KOM_ENV -

Data type: XFELD
Optional: Yes
Call by Reference: Yes

I_EU_ENV -

Data type: XFELD
Optional: Yes
Call by Reference: Yes

I_NO_HIERARCHY_ENV -

Data type: XFELD
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for FM_BUD_CHECK_COMPONENT 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_i_fikrs  TYPE FM01-FIKRS, "   
lv_i_standard_env  TYPE XFELD, "   
lv_i_kom_env  TYPE XFELD, "   
lv_i_eu_env  TYPE XFELD, "   
lv_i_no_hierarchy_env  TYPE XFELD. "   

  CALL FUNCTION 'FM_BUD_CHECK_COMPONENT'  "
    EXPORTING
         I_FIKRS = lv_i_fikrs
         I_STANDARD_ENV = lv_i_standard_env
         I_KOM_ENV = lv_i_kom_env
         I_EU_ENV = lv_i_eu_env
         I_NO_HIERARCHY_ENV = lv_i_no_hierarchy_env
. " FM_BUD_CHECK_COMPONENT




ABAP code using 7.40 inline data declarations to call FM FM_BUD_CHECK_COMPONENT

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 FIKRS FROM FM01 INTO @DATA(ld_i_fikrs).
 
 
 
 
 


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!