SAP FSCD_GET_CUSTOMER_FOR_BROKER Function Module for









FSCD_GET_CUSTOMER_FOR_BROKER is a standard fscd get customer for broker 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 fscd get customer for broker FM, simply by entering the name FSCD_GET_CUSTOMER_FOR_BROKER into the relevant SAP transaction such as SE37 or SE38.

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



Function FSCD_GET_CUSTOMER_FOR_BROKER 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 'FSCD_GET_CUSTOMER_FOR_BROKER'"
  EXPORTING
*  IX_MDAT = 'X' "
*  IX_COLLECT = 'X' "
*  I_DATE_FROM =  "
*  I_DATE_TO =  "
*  IX_DOCU = ' ' "
*  IX_CLEARED_ITEMS = ' ' "
*  I_FAEDN_FROM =  "
*  I_FAEDN_TO =  "

TABLES
*  IT_BROKER =  "
*  IT_BROKER_CONTR =  "
*  ET_DIMAPARBROK =  "
*  ET_FKKCL =  "
.



IMPORTING Parameters details for FSCD_GET_CUSTOMER_FOR_BROKER

IX_MDAT -

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IX_COLLECT -

Data type: XONLYCOLL_BRO
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_DATE_FROM -

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

I_DATE_TO -

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

IX_DOCU -

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

IX_CLEARED_ITEMS -

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

I_FAEDN_FROM -

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

I_FAEDN_TO -

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

TABLES Parameters details for FSCD_GET_CUSTOMER_FOR_BROKER

IT_BROKER -

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

IT_BROKER_CONTR -

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

ET_DIMAPARBROK -

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

ET_FKKCL -

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

Copy and paste ABAP code example for FSCD_GET_CUSTOMER_FOR_BROKER 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_ix_mdat  TYPE XFELD, "   'X'
lt_it_broker  TYPE STANDARD TABLE OF FKKR_GPART, "   
lv_ix_collect  TYPE XONLYCOLL_BRO, "   'X'
lt_it_broker_contr  TYPE STANDARD TABLE OF FKKR_VTREF, "   
lv_i_date_from  TYPE DIMAPARBROK-DATE_FROM, "   
lt_et_dimaparbrok  TYPE STANDARD TABLE OF DIMAPARBROK, "   
lt_et_fkkcl  TYPE STANDARD TABLE OF FKKCL, "   
lv_i_date_to  TYPE DIMAPARBROK-DATE_TO, "   
lv_ix_docu  TYPE XFELD, "   ' '
lv_ix_cleared_items  TYPE XFELD, "   ' '
lv_i_faedn_from  TYPE FAEDN_KK, "   
lv_i_faedn_to  TYPE FAEDN_KK. "   

  CALL FUNCTION 'FSCD_GET_CUSTOMER_FOR_BROKER'  "
    EXPORTING
         IX_MDAT = lv_ix_mdat
         IX_COLLECT = lv_ix_collect
         I_DATE_FROM = lv_i_date_from
         I_DATE_TO = lv_i_date_to
         IX_DOCU = lv_ix_docu
         IX_CLEARED_ITEMS = lv_ix_cleared_items
         I_FAEDN_FROM = lv_i_faedn_from
         I_FAEDN_TO = lv_i_faedn_to
    TABLES
         IT_BROKER = lt_it_broker
         IT_BROKER_CONTR = lt_it_broker_contr
         ET_DIMAPARBROK = lt_et_dimaparbrok
         ET_FKKCL = lt_et_fkkcl
. " FSCD_GET_CUSTOMER_FOR_BROKER




ABAP code using 7.40 inline data declarations to call FM FSCD_GET_CUSTOMER_FOR_BROKER

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.

DATA(ld_ix_mdat) = 'X'.
 
 
DATA(ld_ix_collect) = 'X'.
 
 
"SELECT single DATE_FROM FROM DIMAPARBROK INTO @DATA(ld_i_date_from).
 
 
 
"SELECT single DATE_TO FROM DIMAPARBROK INTO @DATA(ld_i_date_to).
 
DATA(ld_ix_docu) = ' '.
 
DATA(ld_ix_cleared_items) = ' '.
 
 
 


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!