SAP JBD_MAP_MDVOSE_GET_DET_MULT Function Module for get detail mult MAPI
JBD_MAP_MDVOSE_GET_DET_MULT is a standard jbd map mdvose get det mult SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for get detail mult MAPI 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 jbd map mdvose get det mult FM, simply by entering the name JBD_MAP_MDVOSE_GET_DET_MULT into the relevant SAP transaction such as SE37 or SE38.
Function Group: JBD_MD_MAPI
Program Name: SAPLJBD_MD_MAPI
Main Program: SAPLJBD_MD_MAPI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function JBD_MAP_MDVOSE_GET_DET_MULT 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 'JBD_MAP_MDVOSE_GET_DET_MULT'"get detail mult MAPI.
EXPORTING
I_TAB_MD_VOLRATES = "Tabelle Schlüssel Wertpapiervolatilitäten
IMPORTING
E_TAB_ATTRIBUTES = "Tabelle Wertpapiervolatilitäten
E_TAB_MESSAGES = "Fehlermeldungen
IMPORTING Parameters details for JBD_MAP_MDVOSE_GET_DET_MULT
I_TAB_MD_VOLRATES - Tabelle Schlüssel Wertpapiervolatilitäten
Data type: JBD_TAB_MD_VOSE_KEYOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for JBD_MAP_MDVOSE_GET_DET_MULT
E_TAB_ATTRIBUTES - Tabelle Wertpapiervolatilitäten
Data type: JBD_TAB_MD_VOSE_ATOptional: No
Call by Reference: No ( called with pass by value option)
E_TAB_MESSAGES - Fehlermeldungen
Data type: JBD_TAB_MSGOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for JBD_MAP_MDVOSE_GET_DET_MULT 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_e_tab_attributes | TYPE JBD_TAB_MD_VOSE_AT, " | |||
| lv_i_tab_md_volrates | TYPE JBD_TAB_MD_VOSE_KEY, " | |||
| lv_e_tab_messages | TYPE JBD_TAB_MSG. " |
|   CALL FUNCTION 'JBD_MAP_MDVOSE_GET_DET_MULT' "get detail mult MAPI |
| EXPORTING | ||
| I_TAB_MD_VOLRATES | = lv_i_tab_md_volrates | |
| IMPORTING | ||
| E_TAB_ATTRIBUTES | = lv_e_tab_attributes | |
| E_TAB_MESSAGES | = lv_e_tab_messages | |
| . " JBD_MAP_MDVOSE_GET_DET_MULT | ||
ABAP code using 7.40 inline data declarations to call FM JBD_MAP_MDVOSE_GET_DET_MULT
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