SAP BAPI_MDDATASET_SELECT_DATA Function Module for Executes the MDX Command









BAPI_MDDATASET_SELECT_DATA is a standard bapi mddataset select data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Executes the MDX Command 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 mddataset select data FM, simply by entering the name BAPI_MDDATASET_SELECT_DATA into the relevant SAP transaction such as SE37 or SE38.

Function Group: RSOB
Program Name: SAPLRSOB
Main Program: SAPLRSOB
Appliation area: B
Release date: 12-Nov-1999
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_MDDATASET_SELECT_DATA 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_MDDATASET_SELECT_DATA'"Executes the MDX Command
EXPORTING
DATASETID = "MD_COMMAND Object Handle
* SUPPRESS_EMPTY_CELLS = ' ' "Suppress Empty Cells in Cell Data Table
* USE_SCALING_FACTORS = ' ' "Use BW-Specific Scaling Factors
* EXPLAINABLE = ' ' "Internal Use Only
* XML = "XML

IMPORTING
RETURN = "BAPI Return Parameter
STATISTIC = "BI Statistics

TABLES
* CMD = "Parser Bytecode (for ODBO Provider)
* CMD_PARAMS = "Parser Parameter (for ODBO Provider)
* TRACE = "Parser Debug Info. (for ODBO Provider)
.



IMPORTING Parameters details for BAPI_MDDATASET_SELECT_DATA

DATASETID - MD_COMMAND Object Handle

Data type: BAPI6111GEN-OBJ_HANDLE
Optional: No
Call by Reference: No ( called with pass by value option)

SUPPRESS_EMPTY_CELLS - Suppress Empty Cells in Cell Data Table

Data type: RS_BOOL
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

USE_SCALING_FACTORS - Use BW-Specific Scaling Factors

Data type: RS_BOOL
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPLAINABLE - Internal Use Only

Data type: RS_BOOL
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

XML - XML

Data type: XSTRING
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BAPI_MDDATASET_SELECT_DATA

RETURN - BAPI Return Parameter

Data type: BAPIRET2
Optional: No
Call by Reference: No ( called with pass by value option)

STATISTIC - BI Statistics

Data type: BAPI6111STT
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BAPI_MDDATASET_SELECT_DATA

CMD - Parser Bytecode (for ODBO Provider)

Data type: BAPI6111CMD
Optional: Yes
Call by Reference: No ( called with pass by value option)

CMD_PARAMS - Parser Parameter (for ODBO Provider)

Data type: BAPI6111CP
Optional: Yes
Call by Reference: No ( called with pass by value option)

TRACE - Parser Debug Info. (for ODBO Provider)

Data type: BAPI6111TR
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for BAPI_MDDATASET_SELECT_DATA 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:
lt_cmd  TYPE STANDARD TABLE OF BAPI6111CMD, "   
lv_return  TYPE BAPIRET2, "   
lv_datasetid  TYPE BAPI6111GEN-OBJ_HANDLE, "   
lv_statistic  TYPE BAPI6111STT, "   
lt_cmd_params  TYPE STANDARD TABLE OF BAPI6111CP, "   
lv_suppress_empty_cells  TYPE RS_BOOL, "   SPACE
lt_trace  TYPE STANDARD TABLE OF BAPI6111TR, "   
lv_use_scaling_factors  TYPE RS_BOOL, "   SPACE
lv_explainable  TYPE RS_BOOL, "   SPACE
lv_xml  TYPE XSTRING. "   

  CALL FUNCTION 'BAPI_MDDATASET_SELECT_DATA'  "Executes the MDX Command
    EXPORTING
         DATASETID = lv_datasetid
         SUPPRESS_EMPTY_CELLS = lv_suppress_empty_cells
         USE_SCALING_FACTORS = lv_use_scaling_factors
         EXPLAINABLE = lv_explainable
         XML = lv_xml
    IMPORTING
         RETURN = lv_return
         STATISTIC = lv_statistic
    TABLES
         CMD = lt_cmd
         CMD_PARAMS = lt_cmd_params
         TRACE = lt_trace
. " BAPI_MDDATASET_SELECT_DATA




ABAP code using 7.40 inline data declarations to call FM BAPI_MDDATASET_SELECT_DATA

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 OBJ_HANDLE FROM BAPI6111GEN INTO @DATA(ld_datasetid).
 
 
 
DATA(ld_suppress_empty_cells) = ' '.
 
 
DATA(ld_use_scaling_factors) = ' '.
 
DATA(ld_explainable) = ' '.
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!