SAP ISCD_BROK_MSG_READ Function Module for









ISCD_BROK_MSG_READ is a standard iscd brok msg read 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 msg read FM, simply by entering the name ISCD_BROK_MSG_READ into the relevant SAP transaction such as SE37 or SE38.

Function Group: IBR02
Program Name: SAPLIBR02
Main Program: SAPLIBR02
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ISCD_BROK_MSG_READ 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_MSG_READ'"
EXPORTING
I_SUBPOSNO = "

IMPORTING
E_MSG = "

EXCEPTIONS
NOT_FOUND = 1
.



IMPORTING Parameters details for ISCD_BROK_MSG_READ

I_SUBPOSNO -

Data type: IBROSTMP-SUBPOSNUMB
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for ISCD_BROK_MSG_READ

E_MSG -

Data type: FIMSG
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISCD_BROK_MSG_READ 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_msg  TYPE FIMSG, "   
lv_not_found  TYPE FIMSG, "   
lv_i_subposno  TYPE IBROSTMP-SUBPOSNUMB. "   

  CALL FUNCTION 'ISCD_BROK_MSG_READ'  "
    EXPORTING
         I_SUBPOSNO = lv_i_subposno
    IMPORTING
         E_MSG = lv_e_msg
    EXCEPTIONS
        NOT_FOUND = 1
. " ISCD_BROK_MSG_READ




ABAP code using 7.40 inline data declarations to call FM ISCD_BROK_MSG_READ

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 SUBPOSNUMB FROM IBROSTMP INTO @DATA(ld_i_subposno).
 


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!