SAP BAPI_MPRO_GETDETAIL Function Module for Reads Details for a MultiProvider
BAPI_MPRO_GETDETAIL is a standard bapi mpro getdetail SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Reads Details for a MultiProvider 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 bapi mpro getdetail FM, simply by entering the name BAPI_MPRO_GETDETAIL into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSAB_MPRO
Program Name: SAPLRSAB_MPRO
Main Program: SAPLRSAB_MPRO
Appliation area: B
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_MPRO_GETDETAIL 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 'BAPI_MPRO_GETDETAIL'"Reads Details for a MultiProvider.
EXPORTING
* OBJVERS = RS_C_OBJVERS-ACTIVE "Object Version
INFOPROV = "Name of MultiProvider
IMPORTING
DETAILS = "MultiProvider (Detail)
RETURN = "BAPI Return Parameter
TABLES
* DIMENSIONS = "MultiProvider - Dimensions
* INFOOBJECTS = "MultiProvider - InfoObjects
* DIMENSIONINFOOBJECTS = "MultiProvider - InfoObjects in the Dimensions
* PARTINFOPROVS = "MultiProvider - InfoProvider Involved
* PARTINFOOBJECTSIDENT = "MultiProvider - InfoObject Identification
IMPORTING Parameters details for BAPI_MPRO_GETDETAIL
OBJVERS - Object Version
Data type: BAPI6117-OBJVERSDefault: RS_C_OBJVERS-ACTIVE
Optional: Yes
Call by Reference: No ( called with pass by value option)
INFOPROV - Name of MultiProvider
Data type: BAPI6117-INFOPROVOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_MPRO_GETDETAIL
DETAILS - MultiProvider (Detail)
Data type: BAPI6117Optional: No
Call by Reference: No ( called with pass by value option)
RETURN - BAPI Return Parameter
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_MPRO_GETDETAIL
DIMENSIONS - MultiProvider - Dimensions
Data type: BAPI6117DIOptional: Yes
Call by Reference: Yes
INFOOBJECTS - MultiProvider - InfoObjects
Data type: BAPI6117IOOptional: Yes
Call by Reference: Yes
DIMENSIONINFOOBJECTS - MultiProvider - InfoObjects in the Dimensions
Data type: BAPI6117DIOOptional: Yes
Call by Reference: Yes
PARTINFOPROVS - MultiProvider - InfoProvider Involved
Data type: BAPI6117PIOptional: Yes
Call by Reference: Yes
PARTINFOOBJECTSIDENT - MultiProvider - InfoObject Identification
Data type: BAPI6117PIOOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_MPRO_GETDETAIL 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_details | TYPE BAPI6117, " | |||
| lv_objvers | TYPE BAPI6117-OBJVERS, " RS_C_OBJVERS-ACTIVE | |||
| lt_dimensions | TYPE STANDARD TABLE OF BAPI6117DI, " | |||
| lv_return | TYPE BAPIRET2, " | |||
| lv_infoprov | TYPE BAPI6117-INFOPROV, " | |||
| lt_infoobjects | TYPE STANDARD TABLE OF BAPI6117IO, " | |||
| lt_dimensioninfoobjects | TYPE STANDARD TABLE OF BAPI6117DIO, " | |||
| lt_partinfoprovs | TYPE STANDARD TABLE OF BAPI6117PI, " | |||
| lt_partinfoobjectsident | TYPE STANDARD TABLE OF BAPI6117PIO. " |
|   CALL FUNCTION 'BAPI_MPRO_GETDETAIL' "Reads Details for a MultiProvider |
| EXPORTING | ||
| OBJVERS | = lv_objvers | |
| INFOPROV | = lv_infoprov | |
| IMPORTING | ||
| DETAILS | = lv_details | |
| RETURN | = lv_return | |
| TABLES | ||
| DIMENSIONS | = lt_dimensions | |
| INFOOBJECTS | = lt_infoobjects | |
| DIMENSIONINFOOBJECTS | = lt_dimensioninfoobjects | |
| PARTINFOPROVS | = lt_partinfoprovs | |
| PARTINFOOBJECTSIDENT | = lt_partinfoobjectsident | |
| . " BAPI_MPRO_GETDETAIL | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_MPRO_GETDETAIL
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 OBJVERS FROM BAPI6117 INTO @DATA(ld_objvers). | ||||
| DATA(ld_objvers) | = RS_C_OBJVERS-ACTIVE. | |||
| "SELECT single INFOPROV FROM BAPI6117 INTO @DATA(ld_infoprov). | ||||
Search for further information about these or an SAP related objects