SAP GET_BM_ATTRIBUT_FOR_KEYDATE Function Module for AFWBM: Find Benchmark Attributes for the Key Date (Interval)
GET_BM_ATTRIBUT_FOR_KEYDATE is a standard get bm attribut for keydate 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: Find Benchmark Attributes for the Key Date (Interval) 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 get bm attribut for keydate FM, simply by entering the name GET_BM_ATTRIBUT_FOR_KEYDATE 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 GET_BM_ATTRIBUT_FOR_KEYDATE 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 'GET_BM_ATTRIBUT_FOR_KEYDATE'"AFWBM: Find Benchmark Attributes for the Key Date (Interval).
EXPORTING
I_BMID = "CFM Benchmarking: Benchmark ID
* I_KEYDATE = "Date: Valid From (Inclusive)
* I_KEYDATE_RANGE = "Key Dates: Ranges
IMPORTING
E_TAB_RANGE_BASIC = "Table Type for Basic Benchmark (for Func GET_BM_ATTRIBUT_FOR_KEYDATE)
E_TAB_RANGE_COMP = "Table Type for Composite Benchmark (for Func GET_BM_ATTRIBUT_FOR_KEYDATE)
E_VALDATE_VALID = "1st Validity Date if History is not Found
EXCEPTIONS
WRONG_PARAM = 1 NOT_FOUND = 2 HIST_NOT_FOUND = 3
IMPORTING Parameters details for GET_BM_ATTRIBUT_FOR_KEYDATE
I_BMID - CFM Benchmarking: Benchmark ID
Data type: AFWBM_BMIDOptional: No
Call by Reference: Yes
I_KEYDATE - Date: Valid From (Inclusive)
Data type: AFW_KEYDATEOptional: Yes
Call by Reference: Yes
I_KEYDATE_RANGE - Key Dates: Ranges
Data type: AFWGO_SO_KEYDATEOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for GET_BM_ATTRIBUT_FOR_KEYDATE
E_TAB_RANGE_BASIC - Table Type for Basic Benchmark (for Func GET_BM_ATTRIBUT_FOR_KEYDATE)
Data type: AFWBM_RANGE_BASIC_TOptional: No
Call by Reference: Yes
E_TAB_RANGE_COMP - Table Type for Composite Benchmark (for Func GET_BM_ATTRIBUT_FOR_KEYDATE)
Data type: AFWBM_RANGE_COMP_TOptional: No
Call by Reference: Yes
E_VALDATE_VALID - 1st Validity Date if History is not Found
Data type: AFW_VALDATEOptional: No
Call by Reference: Yes
EXCEPTIONS details
WRONG_PARAM - Parameter Error
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
Copy and paste ABAP code example for GET_BM_ATTRIBUT_FOR_KEYDATE 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_e_tab_range_basic | TYPE AFWBM_RANGE_BASIC_T, " | |||
| lv_i_keydate | TYPE AFW_KEYDATE, " | |||
| lv_not_found | TYPE AFW_KEYDATE, " | |||
| lv_e_tab_range_comp | TYPE AFWBM_RANGE_COMP_T, " | |||
| lv_hist_not_found | TYPE AFWBM_RANGE_COMP_T, " | |||
| lv_e_valdate_valid | TYPE AFW_VALDATE, " | |||
| lv_i_keydate_range | TYPE AFWGO_SO_KEYDATE. " |
|   CALL FUNCTION 'GET_BM_ATTRIBUT_FOR_KEYDATE' "AFWBM: Find Benchmark Attributes for the Key Date (Interval) |
| EXPORTING | ||
| I_BMID | = lv_i_bmid | |
| I_KEYDATE | = lv_i_keydate | |
| I_KEYDATE_RANGE | = lv_i_keydate_range | |
| IMPORTING | ||
| E_TAB_RANGE_BASIC | = lv_e_tab_range_basic | |
| E_TAB_RANGE_COMP | = lv_e_tab_range_comp | |
| E_VALDATE_VALID | = lv_e_valdate_valid | |
| EXCEPTIONS | ||
| WRONG_PARAM = 1 | ||
| NOT_FOUND = 2 | ||
| HIST_NOT_FOUND = 3 | ||
| . " GET_BM_ATTRIBUT_FOR_KEYDATE | ||
ABAP code using 7.40 inline data declarations to call FM GET_BM_ATTRIBUT_FOR_KEYDATE
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