SAP BM_EVAL_DATA_CHECK Function Module for AFWBM: Check for Dependent Evaluation Data and Composites
BM_EVAL_DATA_CHECK is a standard bm eval data check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for AFWBM: Check for Dependent Evaluation Data and Composites processing and below is the pattern details for this FM, 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 bm eval data check FM, simply by entering the name BM_EVAL_DATA_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: AFWBM_SERVICES
Program Name: SAPLAFWBM_SERVICES
Main Program: SAPLAFWBM_SERVICES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BM_EVAL_DATA_CHECK 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 'BM_EVAL_DATA_CHECK'"AFWBM: Check for Dependent Evaluation Data and Composites.
EXPORTING
I_BMID = "Benchmark ID
I_BMCATEGORY = "Benchmark Category
* I_VALDATE = "Date: Valid From (Inclusive)
* I_MODE_DEL = "X = Check for Deletion
* I_MODE_DISP = "X = Determine Export Indicators Only
IMPORTING
E_FLAG_PH = "' ' = No PH Assignment 'X' = PH Assignment
E_FLAG_COMP = "' ' = No COMPBM assignment; 'X' = COMPBM Assignment
E_TAB_COMP_HIST = "Table Type for Table afwbm_comp
EXCEPTIONS
NO_EVAL_VALDATE = 1 EVAL_VALDATE = 2 EVAL_COMPOSITE = 3 REF_OLD_HISTORY = 4 ASSIGN_TO_ASS_VARI = 5
IMPORTING Parameters details for BM_EVAL_DATA_CHECK
I_BMID - Benchmark ID
Data type: AFWBM_BMIDOptional: No
Call by Reference: Yes
I_BMCATEGORY - Benchmark Category
Data type: AFWBM_CATEGORYOptional: No
Call by Reference: Yes
I_VALDATE - Date: Valid From (Inclusive)
Data type: AFWBM_VALDATEOptional: Yes
Call by Reference: Yes
I_MODE_DEL - X = Check for Deletion
Data type: AFWCH_FLAGOptional: Yes
Call by Reference: Yes
I_MODE_DISP - X = Determine Export Indicators Only
Data type: AFWCH_FLAGOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for BM_EVAL_DATA_CHECK
E_FLAG_PH - ' ' = No PH Assignment 'X' = PH Assignment
Data type: AFWCH_FLAGOptional: No
Call by Reference: Yes
E_FLAG_COMP - ' ' = No COMPBM assignment; 'X' = COMPBM Assignment
Data type: AFWCH_FLAGOptional: No
Call by Reference: Yes
E_TAB_COMP_HIST - Table Type for Table afwbm_comp
Data type: AFWBM_COMP_HIST_TOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_EVAL_VALDATE - Only key figure calculations with a key date outside of validity period exist
Data type:Optional: No
Call by Reference: Yes
EVAL_VALDATE - Key Figure Calculation exists with key date in validity interval
Data type:Optional: No
Call by Reference: Yes
EVAL_COMPOSITE - Component of a Composite Benchmark (No Deletion)
Data type:Optional: No
Call by Reference: Yes
REF_OLD_HISTORY - Component of a Change History
Data type:Optional: No
Call by Reference: Yes
ASSIGN_TO_ASS_VARI - Assignment to an Assignment Variant
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BM_EVAL_DATA_CHECK 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_bmid | TYPE AFWBM_BMID, " | |||
| lv_e_flag_ph | TYPE AFWCH_FLAG, " | |||
| lv_no_eval_valdate | TYPE AFWCH_FLAG, " | |||
| lv_e_flag_comp | TYPE AFWCH_FLAG, " | |||
| lv_eval_valdate | TYPE AFWCH_FLAG, " | |||
| lv_i_bmcategory | TYPE AFWBM_CATEGORY, " | |||
| lv_i_valdate | TYPE AFWBM_VALDATE, " | |||
| lv_eval_composite | TYPE AFWBM_VALDATE, " | |||
| lv_e_tab_comp_hist | TYPE AFWBM_COMP_HIST_T, " | |||
| lv_i_mode_del | TYPE AFWCH_FLAG, " | |||
| lv_ref_old_history | TYPE AFWCH_FLAG, " | |||
| lv_i_mode_disp | TYPE AFWCH_FLAG, " | |||
| lv_assign_to_ass_vari | TYPE AFWCH_FLAG. " |
|   CALL FUNCTION 'BM_EVAL_DATA_CHECK' "AFWBM: Check for Dependent Evaluation Data and Composites |
| EXPORTING | ||
| I_BMID | = lv_i_bmid | |
| I_BMCATEGORY | = lv_i_bmcategory | |
| I_VALDATE | = lv_i_valdate | |
| I_MODE_DEL | = lv_i_mode_del | |
| I_MODE_DISP | = lv_i_mode_disp | |
| IMPORTING | ||
| E_FLAG_PH | = lv_e_flag_ph | |
| E_FLAG_COMP | = lv_e_flag_comp | |
| E_TAB_COMP_HIST | = lv_e_tab_comp_hist | |
| EXCEPTIONS | ||
| NO_EVAL_VALDATE = 1 | ||
| EVAL_VALDATE = 2 | ||
| EVAL_COMPOSITE = 3 | ||
| REF_OLD_HISTORY = 4 | ||
| ASSIGN_TO_ASS_VARI = 5 | ||
| . " BM_EVAL_DATA_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM BM_EVAL_DATA_CHECK
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