SAP BM_CONSISTENCY_CHECK Function Module for AFWBM: Consistency Check for a BMID
BM_CONSISTENCY_CHECK is a standard bm consistency 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: Consistency Check for a BMID 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 consistency check FM, simply by entering the name BM_CONSISTENCY_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_CONSISTENCY_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_CONSISTENCY_CHECK'"AFWBM: Consistency Check for a BMID.
EXPORTING
* I_BMID = "CFM Benchmarking: Benchmark ID
* I_VALDATE = "Date: Valid From (Inclusive)
* I_STR_AFWBM = "Auxiliary Structure for Transaction AFWBM
* I_TAB_AFWBM_COMP = "Table Type for Table Parameters for Composite Benchmark
* I_FLAG_UPDATE_STATE = "X = Update status flag if data is inconsistent
* I_FLAG_STATIC = '' "X= Do not reset static table
EXCEPTIONS
WRONG_PARAM = 1 BM_NOK = 2 NOT_FOUND = 3 HIST_NOT_FOUND = 4 ERROR_MODIFY = 5
IMPORTING Parameters details for BM_CONSISTENCY_CHECK
I_BMID - CFM Benchmarking: Benchmark ID
Data type: AFWBM_BMIDOptional: Yes
Call by Reference: Yes
I_VALDATE - Date: Valid From (Inclusive)
Data type: AFWBM_VALDATEOptional: Yes
Call by Reference: Yes
I_STR_AFWBM - Auxiliary Structure for Transaction AFWBM
Data type: AFWBM_STROptional: Yes
Call by Reference: Yes
I_TAB_AFWBM_COMP - Table Type for Table Parameters for Composite Benchmark
Data type: AFWBM_COMP_TOptional: Yes
Call by Reference: Yes
I_FLAG_UPDATE_STATE - X = Update status flag if data is inconsistent
Data type: AFWCH_FLAGOptional: Yes
Call by Reference: Yes
I_FLAG_STATIC - X= Do not reset static table
Data type: AFWCH_FLAGDefault: ''
Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
WRONG_PARAM - Incorrect Parameter
Data type:Optional: No
Call by Reference: Yes
BM_NOK - Error in the attributes
Data type:Optional: No
Call by Reference: Yes
NOT_FOUND - Benchmark does not exist
Data type:Optional: No
Call by Reference: Yes
HIST_NOT_FOUND - Unable to find history
Data type:Optional: No
Call by Reference: Yes
ERROR_MODIFY - Error during update of status flag
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BM_CONSISTENCY_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_wrong_param | TYPE AFWBM_BMID, " | |||
| lv_bm_nok | TYPE AFWBM_BMID, " | |||
| lv_i_valdate | TYPE AFWBM_VALDATE, " | |||
| lv_not_found | TYPE AFWBM_VALDATE, " | |||
| lv_i_str_afwbm | TYPE AFWBM_STR, " | |||
| lv_hist_not_found | TYPE AFWBM_STR, " | |||
| lv_i_tab_afwbm_comp | TYPE AFWBM_COMP_T, " | |||
| lv_error_modify | TYPE AFWBM_COMP_T, " | |||
| lv_i_flag_update_state | TYPE AFWCH_FLAG, " | |||
| lv_i_flag_static | TYPE AFWCH_FLAG. " '' |
|   CALL FUNCTION 'BM_CONSISTENCY_CHECK' "AFWBM: Consistency Check for a BMID |
| EXPORTING | ||
| I_BMID | = lv_i_bmid | |
| I_VALDATE | = lv_i_valdate | |
| I_STR_AFWBM | = lv_i_str_afwbm | |
| I_TAB_AFWBM_COMP | = lv_i_tab_afwbm_comp | |
| I_FLAG_UPDATE_STATE | = lv_i_flag_update_state | |
| I_FLAG_STATIC | = lv_i_flag_static | |
| EXCEPTIONS | ||
| WRONG_PARAM = 1 | ||
| BM_NOK = 2 | ||
| NOT_FOUND = 3 | ||
| HIST_NOT_FOUND = 4 | ||
| ERROR_MODIFY = 5 | ||
| . " BM_CONSISTENCY_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM BM_CONSISTENCY_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.| DATA(ld_i_flag_static) | = ''. | |||
Search for further information about these or an SAP related objects