SAP ISCD_BROK_ACTIVITY_SAMPLE Function Module for









ISCD_BROK_ACTIVITY_SAMPLE is a standard iscd brok activity sample 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 activity sample FM, simply by entering the name ISCD_BROK_ACTIVITY_SAMPLE 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_ACTIVITY_SAMPLE 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_ACTIVITY_SAMPLE'"
EXPORTING
I_ACT_DATA = "
I_BRO_STMH = "
I_BRO_STMP = "
* I_BRO_STMP_ADD = "ISCD: Broker Report - Item Data
* I_FAST_ENTRY = "Broker Collections - Screen Fields Fast Entry
* IX_CALL_FROM_FAST_ENTRY = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

IMPORTING
E_XCFC_CREATED = "

TABLES
* T_BRO_STMS = "
* IT_BRO_STMS_ADD = "ISCD: Broker Report - Selected Items Related to an Item

EXCEPTIONS
ACTIV_EXEC_ERROR = 1
.



IMPORTING Parameters details for ISCD_BROK_ACTIVITY_SAMPLE

I_ACT_DATA -

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

I_BRO_STMH -

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

I_BRO_STMP -

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

I_BRO_STMP_ADD - ISCD: Broker Report - Item Data

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

I_FAST_ENTRY - Broker Collections - Screen Fields Fast Entry

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

IX_CALL_FROM_FAST_ENTRY - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

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

EXPORTING Parameters details for ISCD_BROK_ACTIVITY_SAMPLE

E_XCFC_CREATED -

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

TABLES Parameters details for ISCD_BROK_ACTIVITY_SAMPLE

T_BRO_STMS -

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

IT_BRO_STMS_ADD - ISCD: Broker Report - Selected Items Related to an Item

Data type: IBROSTMS
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

ACTIV_EXEC_ERROR -

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

Copy and paste ABAP code example for ISCD_BROK_ACTIVITY_SAMPLE 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_i_act_data  TYPE TIBRACTIVITY, "   
lt_t_bro_stms  TYPE STANDARD TABLE OF IBROSTMS, "   
lv_e_xcfc_created  TYPE BOOLE-BOOLE, "   
lv_activ_exec_error  TYPE BOOLE, "   
lv_i_bro_stmh  TYPE IBROSTMH, "   
lt_it_bro_stms_add  TYPE STANDARD TABLE OF IBROSTMS, "   
lv_i_bro_stmp  TYPE IBROSTMP, "   
lv_i_bro_stmp_add  TYPE IBROSTMP, "   
lv_i_fast_entry  TYPE SIBRQENTRY, "   
lv_ix_call_from_fast_entry  TYPE BOOLE-BOOLE. "   

  CALL FUNCTION 'ISCD_BROK_ACTIVITY_SAMPLE'  "
    EXPORTING
         I_ACT_DATA = lv_i_act_data
         I_BRO_STMH = lv_i_bro_stmh
         I_BRO_STMP = lv_i_bro_stmp
         I_BRO_STMP_ADD = lv_i_bro_stmp_add
         I_FAST_ENTRY = lv_i_fast_entry
         IX_CALL_FROM_FAST_ENTRY = lv_ix_call_from_fast_entry
    IMPORTING
         E_XCFC_CREATED = lv_e_xcfc_created
    TABLES
         T_BRO_STMS = lt_t_bro_stms
         IT_BRO_STMS_ADD = lt_it_bro_stms_add
    EXCEPTIONS
        ACTIV_EXEC_ERROR = 1
. " ISCD_BROK_ACTIVITY_SAMPLE




ABAP code using 7.40 inline data declarations to call FM ISCD_BROK_ACTIVITY_SAMPLE

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 BOOLE FROM BOOLE INTO @DATA(ld_e_xcfc_created).
 
 
 
 
 
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_ix_call_from_fast_entry).
 


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!