SAP JBD_MAP_COLL_GET_LIST Function Module for MAPI: Sicherheiten Stammdaten - Get List
JBD_MAP_COLL_GET_LIST is a standard jbd map coll 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 MAPI: Sicherheiten Stammdaten - Get List 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 coll get list FM, simply by entering the name JBD_MAP_COLL_GET_LIST into the relevant SAP transaction such as SE37 or SE38.
Function Group: JBD_COLL_MAPI
Program Name: SAPLJBD_COLL_MAPI
Main Program: SAPLJBD_COLL_MAPI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function JBD_MAP_COLL_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 'JBD_MAP_COLL_GET_LIST'"MAPI: Sicherheiten Stammdaten - Get List.
EXPORTING
* I_RNG_COLLATERAL_EXT_ID = "
* I_COLLATERAL_CATEGORY = "Ebene der Sicherheit
* I_RNG_PARTNER_EXTERNAL = "
* I_RNG_PARTNER = "Generelle Range Tabelle
* I_COLLATERAL_TYPE = "Sicherheitentyp
* I_ACTIVE_INDICATOR = "Kennzeichen ob Satz aktiv ist oder nicht
* I_MAX_ROWS = "Maximale Trefferanzahl
IMPORTING
E_TAB_COLL_EXT_ID = "Extrene Sicherheiten ID
E_TAB_MESSAGES = "
E_OVERFLOW_FLAG = "
IMPORTING Parameters details for JBD_MAP_COLL_GET_LIST
I_RNG_COLLATERAL_EXT_ID -
Data type: JBD_RNG_GENERALOptional: Yes
Call by Reference: Yes
I_COLLATERAL_CATEGORY - Ebene der Sicherheit
Data type: KLSI01-SITYPOptional: Yes
Call by Reference: Yes
I_RNG_PARTNER_EXTERNAL -
Data type: JBD_RNG_GENERALOptional: Yes
Call by Reference: Yes
I_RNG_PARTNER - Generelle Range Tabelle
Data type: JBD_RNG_GENERALOptional: Yes
Call by Reference: Yes
I_COLLATERAL_TYPE - Sicherheitentyp
Data type: KLSI01-SIARTOptional: Yes
Call by Reference: Yes
I_ACTIVE_INDICATOR - Kennzeichen ob Satz aktiv ist oder nicht
Data type: KLSI01-XAKTOptional: Yes
Call by Reference: Yes
I_MAX_ROWS - Maximale Trefferanzahl
Data type: BAPIMAXROWOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for JBD_MAP_COLL_GET_LIST
E_TAB_COLL_EXT_ID - Extrene Sicherheiten ID
Data type: JBD_TAB_COLL_EXT_ID_MAPOptional: No
Call by Reference: Yes
E_TAB_MESSAGES -
Data type: JBD_TAB_MSGOptional: No
Call by Reference: Yes
E_OVERFLOW_FLAG -
Data type: JBD_DTE_OVERFLOW_FLAGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for JBD_MAP_COLL_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_e_tab_coll_ext_id | TYPE JBD_TAB_COLL_EXT_ID_MAP, " | |||
| lv_i_rng_collateral_ext_id | TYPE JBD_RNG_GENERAL, " | |||
| lv_e_tab_messages | TYPE JBD_TAB_MSG, " | |||
| lv_i_collateral_category | TYPE KLSI01-SITYP, " | |||
| lv_e_overflow_flag | TYPE JBD_DTE_OVERFLOW_FLAG, " | |||
| lv_i_rng_partner_external | TYPE JBD_RNG_GENERAL, " | |||
| lv_i_rng_partner | TYPE JBD_RNG_GENERAL, " | |||
| lv_i_collateral_type | TYPE KLSI01-SIART, " | |||
| lv_i_active_indicator | TYPE KLSI01-XAKT, " | |||
| lv_i_max_rows | TYPE BAPIMAXROW. " |
|   CALL FUNCTION 'JBD_MAP_COLL_GET_LIST' "MAPI: Sicherheiten Stammdaten - Get List |
| EXPORTING | ||
| I_RNG_COLLATERAL_EXT_ID | = lv_i_rng_collateral_ext_id | |
| I_COLLATERAL_CATEGORY | = lv_i_collateral_category | |
| I_RNG_PARTNER_EXTERNAL | = lv_i_rng_partner_external | |
| I_RNG_PARTNER | = lv_i_rng_partner | |
| I_COLLATERAL_TYPE | = lv_i_collateral_type | |
| I_ACTIVE_INDICATOR | = lv_i_active_indicator | |
| I_MAX_ROWS | = lv_i_max_rows | |
| IMPORTING | ||
| E_TAB_COLL_EXT_ID | = lv_e_tab_coll_ext_id | |
| E_TAB_MESSAGES | = lv_e_tab_messages | |
| E_OVERFLOW_FLAG | = lv_e_overflow_flag | |
| . " JBD_MAP_COLL_GET_LIST | ||
ABAP code using 7.40 inline data declarations to call FM JBD_MAP_COLL_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.| "SELECT single SITYP FROM KLSI01 INTO @DATA(ld_i_collateral_category). | ||||
| "SELECT single SIART FROM KLSI01 INTO @DATA(ld_i_collateral_type). | ||||
| "SELECT single XAKT FROM KLSI01 INTO @DATA(ld_i_active_indicator). | ||||
Search for further information about these or an SAP related objects