SAP BAPI_JBD_MDIR_GET_LIST Function Module for Get-List BAPI
BAPI_JBD_MDIR_GET_LIST is a standard bapi jbd mdir get list 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-List BAPI 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 jbd mdir get list FM, simply by entering the name BAPI_JBD_MDIR_GET_LIST into the relevant SAP transaction such as SE37 or SE38.
Function Group: JBD_MDIR_BAPI
Program Name: SAPLJBD_MDIR_BAPI
Main Program: SAPLJBD_MDIR_BAPI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_JBD_MDIR_GET_LIST 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_JBD_MDIR_GET_LIST'"Get-List BAPI.
EXPORTING
* MAX_ROWS = "Structure for Maximum Number of Rows in Hit List
* PROCESSEXTENSION = "Control Indicator for Executing BAdIs
IMPORTING
OVERFLOW_FLAG = "Flag Showing That Maximum Number of Transactions for Selection Has Been Reached
TABLES
* REFERENCE_RATE = "Selection for Reference Interest Rate
* RATE_DATE = "Selection for Price/Rate Date
* IR_RATES = "Key for Reference Interest Rates
* EXTENSIONIN = "Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
* EXTENSIONOUT = "Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
* RETURN = "Return Parameters
IMPORTING Parameters details for BAPI_JBD_MDIR_GET_LIST
MAX_ROWS - Structure for Maximum Number of Rows in Hit List
Data type: BAPI_JBD_STR_MAX_ROWSOptional: Yes
Call by Reference: No ( called with pass by value option)
PROCESSEXTENSION - Control Indicator for Executing BAdIs
Data type: BAPI_JBD_STR_PROC_EXTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_JBD_MDIR_GET_LIST
OVERFLOW_FLAG - Flag Showing That Maximum Number of Transactions for Selection Has Been Reached
Data type: BAPI_JBD_STR_OVERFLOW_FLAGOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_JBD_MDIR_GET_LIST
REFERENCE_RATE - Selection for Reference Interest Rate
Data type: BAPI_JBD_STR_REFRATE_SELOptional: Yes
Call by Reference: Yes
RATE_DATE - Selection for Price/Rate Date
Data type: BAPI_JBD_STR_RATEDATE_SELOptional: Yes
Call by Reference: No ( called with pass by value option)
IR_RATES - Key for Reference Interest Rates
Data type: BAPI_JBD_STR_MD_IR_KEYOptional: Yes
Call by Reference: Yes
EXTENSIONIN - Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
Data type: BAPIPAREXOptional: Yes
Call by Reference: No ( called with pass by value option)
EXTENSIONOUT - Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
Data type: BAPIPAREXOptional: Yes
Call by Reference: No ( called with pass by value option)
RETURN - Return Parameters
Data type: BAPIRET2Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_JBD_MDIR_GET_LIST 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_max_rows | TYPE BAPI_JBD_STR_MAX_ROWS, " | |||
| lv_overflow_flag | TYPE BAPI_JBD_STR_OVERFLOW_FLAG, " | |||
| lt_reference_rate | TYPE STANDARD TABLE OF BAPI_JBD_STR_REFRATE_SEL, " | |||
| lt_rate_date | TYPE STANDARD TABLE OF BAPI_JBD_STR_RATEDATE_SEL, " | |||
| lv_processextension | TYPE BAPI_JBD_STR_PROC_EXT, " | |||
| lt_ir_rates | TYPE STANDARD TABLE OF BAPI_JBD_STR_MD_IR_KEY, " | |||
| lt_extensionin | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lt_extensionout | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2. " |
|   CALL FUNCTION 'BAPI_JBD_MDIR_GET_LIST' "Get-List BAPI |
| EXPORTING | ||
| MAX_ROWS | = lv_max_rows | |
| PROCESSEXTENSION | = lv_processextension | |
| IMPORTING | ||
| OVERFLOW_FLAG | = lv_overflow_flag | |
| TABLES | ||
| REFERENCE_RATE | = lt_reference_rate | |
| RATE_DATE | = lt_rate_date | |
| IR_RATES | = lt_ir_rates | |
| EXTENSIONIN | = lt_extensionin | |
| EXTENSIONOUT | = lt_extensionout | |
| RETURN | = lt_return | |
| . " BAPI_JBD_MDIR_GET_LIST | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_JBD_MDIR_GET_LIST
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