SAP ISCD_BROK_MASTERDAT_COMPLETE Function Module for
ISCD_BROK_MASTERDAT_COMPLETE is a standard iscd brok masterdat complete SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 iscd brok masterdat complete FM, simply by entering the name ISCD_BROK_MASTERDAT_COMPLETE into the relevant SAP transaction such as SE37 or SE38.
Function Group: IBR02
Program Name: SAPLIBR02
Main Program: SAPLIBR02
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISCD_BROK_MASTERDAT_COMPLETE 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 'ISCD_BROK_MASTERDAT_COMPLETE'".
EXPORTING
* I_PARTNER = "
* I_ACCOUNT = "
* I_INSOBJ = "
* IX_SINGLE_CHECK = ' ' "
IMPORTING
E_PARTNER = "
E_ACCOUNT = "
E_INSOBJ = "
TABLES
* ET_DIMAIOBPAR = "Insurance Object-Partner Relationship in FS-CD
EXCEPTIONS
ERR_PARAM = 1 NOT_FOUND = 2 SINGLE_VALUE_WRONG = 3
IMPORTING Parameters details for ISCD_BROK_MASTERDAT_COMPLETE
I_PARTNER -
Data type: BUT000-PARTNEROptional: Yes
Call by Reference: No ( called with pass by value option)
I_ACCOUNT -
Data type: FKKVK-VKONTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_INSOBJ -
Data type: DIMAIOB-INSOBJECTOptional: Yes
Call by Reference: No ( called with pass by value option)
IX_SINGLE_CHECK -
Data type: BOOLE-BOOLEDefault: ' '
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ISCD_BROK_MASTERDAT_COMPLETE
E_PARTNER -
Data type: BUT000-PARTNEROptional: No
Call by Reference: No ( called with pass by value option)
E_ACCOUNT -
Data type: FKKVK-VKONTOptional: No
Call by Reference: No ( called with pass by value option)
E_INSOBJ -
Data type: DIMAIOB-INSOBJECTOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISCD_BROK_MASTERDAT_COMPLETE
ET_DIMAIOBPAR - Insurance Object-Partner Relationship in FS-CD
Data type: DIMAIOBPAROptional: Yes
Call by Reference: Yes
EXCEPTIONS details
ERR_PARAM -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SINGLE_VALUE_WRONG -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISCD_BROK_MASTERDAT_COMPLETE 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_err_param | TYPE STRING, " | |||
| lv_e_partner | TYPE BUT000-PARTNER, " | |||
| lv_i_partner | TYPE BUT000-PARTNER, " | |||
| lt_et_dimaiobpar | TYPE STANDARD TABLE OF DIMAIOBPAR, " | |||
| lv_e_account | TYPE FKKVK-VKONT, " | |||
| lv_i_account | TYPE FKKVK-VKONT, " | |||
| lv_not_found | TYPE FKKVK, " | |||
| lv_e_insobj | TYPE DIMAIOB-INSOBJECT, " | |||
| lv_i_insobj | TYPE DIMAIOB-INSOBJECT, " | |||
| lv_single_value_wrong | TYPE DIMAIOB, " | |||
| lv_ix_single_check | TYPE BOOLE-BOOLE. " ' ' |
|   CALL FUNCTION 'ISCD_BROK_MASTERDAT_COMPLETE' " |
| EXPORTING | ||
| I_PARTNER | = lv_i_partner | |
| I_ACCOUNT | = lv_i_account | |
| I_INSOBJ | = lv_i_insobj | |
| IX_SINGLE_CHECK | = lv_ix_single_check | |
| IMPORTING | ||
| E_PARTNER | = lv_e_partner | |
| E_ACCOUNT | = lv_e_account | |
| E_INSOBJ | = lv_e_insobj | |
| TABLES | ||
| ET_DIMAIOBPAR | = lt_et_dimaiobpar | |
| EXCEPTIONS | ||
| ERR_PARAM = 1 | ||
| NOT_FOUND = 2 | ||
| SINGLE_VALUE_WRONG = 3 | ||
| . " ISCD_BROK_MASTERDAT_COMPLETE | ||
ABAP code using 7.40 inline data declarations to call FM ISCD_BROK_MASTERDAT_COMPLETE
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 PARTNER FROM BUT000 INTO @DATA(ld_e_partner). | ||||
| "SELECT single PARTNER FROM BUT000 INTO @DATA(ld_i_partner). | ||||
| "SELECT single VKONT FROM FKKVK INTO @DATA(ld_e_account). | ||||
| "SELECT single VKONT FROM FKKVK INTO @DATA(ld_i_account). | ||||
| "SELECT single INSOBJECT FROM DIMAIOB INTO @DATA(ld_e_insobj). | ||||
| "SELECT single INSOBJECT FROM DIMAIOB INTO @DATA(ld_i_insobj). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_ix_single_check). | ||||
| DATA(ld_ix_single_check) | = ' '. | |||
Search for further information about these or an SAP related objects