ISU_BI_SMDATA_DOWN_CUST_TAB SAP Function module - User Exit: Download for Customer Tables

ISU_BI_SMDATA_DOWN_CUST_TAB is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name ISU_BI_SMDATA_DOWN_CUST_TAB into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: ERATE_TRANS
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM ISU_BI_SMDATA_DOWN_CUST_TAB - ISU BI SMDATA DOWN CUST TAB

CALL FUNCTION 'ISU_BI_SMDATA_DOWN_CUST_TAB' "User Exit: Download for Customer Tables
* EXPORTING
*   xr_sparte =                 " isu_ranges_sparte  Selection criteria table: Division
*   xr_aklasse =                " isu_ranges_aklasse  Selection criteria table: Billing class
*   xt_tariftyp =               " isu_tariftyp_htab  Hashed table of rate category keys
*   xt_schemanr =               " isu_schemanr_htab  Hashed table of billing schema keys
*   xt_tarifnr =                " isu_tarifnr_htab  Hashed table of rate keys
  TABLES
    yt_tab =                    "
  EXCEPTIONS
    GENERAL_FAULT = 1           "
    .  "  ISU_BI_SMDATA_DOWN_CUST_TAB

ABAP code example for Function Module ISU_BI_SMDATA_DOWN_CUST_TAB

The ABAP code below is a full code listing to execute function module ISU_BI_SMDATA_DOWN_CUST_TAB including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
it_yt_tab  
 
 TYPE STANDARD TABLE OF STRING,"TABLES PARAM
wa_yt_tab
 
 LIKE LINE OF it_yt_tab
.


DATA(ld_xr_sparte) = 'Check type of data required'.

DATA(ld_xr_aklasse) = 'Check type of data required'.

DATA(ld_xt_tariftyp) = 'Check type of data required'.

DATA(ld_xt_schemanr) = 'Check type of data required'.

DATA(ld_xt_tarifnr) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_yt_tab to it_yt_tab.
.

CALL FUNCTION 'ISU_BI_SMDATA_DOWN_CUST_TAB'
* EXPORTING
*   xr_sparte =                  ld_xr_sparte
*   xr_aklasse =                 ld_xr_aklasse
*   xt_tariftyp =                ld_xt_tariftyp
*   xt_schemanr =                ld_xt_schemanr
*   xt_tarifnr =                 ld_xt_tarifnr
  TABLES
    yt_tab =                     it_yt_tab
  EXCEPTIONS
    GENERAL_FAULT =              1
    .  "  ISU_BI_SMDATA_DOWN_CUST_TAB

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_xr_sparte
 
 TYPE ISU_RANGES_SPARTE ,
it_yt_tab
 
 TYPE STANDARD TABLE OF STRING ,
wa_yt_tab
 
 LIKE LINE OF it_yt_tab,
ld_xr_aklasse
 
 TYPE ISU_RANGES_AKLASSE ,
ld_xt_tariftyp
 
 TYPE ISU_TARIFTYP_HTAB ,
ld_xt_schemanr
 
 TYPE ISU_SCHEMANR_HTAB ,
ld_xt_tarifnr
 
 TYPE ISU_TARIFNR_HTAB .


ld_xr_sparte = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_yt_tab to it_yt_tab.
ld_xr_aklasse = 'Check type of data required'.
ld_xt_tariftyp = 'Check type of data required'.
ld_xt_schemanr = 'Check type of data required'.
ld_xt_tarifnr = 'Check type of data required'.