SAMPLE_PROCESS_00103035 SAP Function module - RFFMINTCALC: Call Form

SAMPLE_PROCESS_00103035 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 SAMPLE_PROCESS_00103035 into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM SAMPLE_PROCESS_00103035 - SAMPLE PROCESS 00103035

CALL FUNCTION 'SAMPLE_PROCESS_00103035' "RFFMINTCALC: Call Form
  EXPORTING
    u_test_run =                " boole-boole   Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
    u_t_bsid =                  " fm_bsid_tab   Table Type for BSAD
    u_t_bsec =                  " fm_bsec_tab   Table Type for BSAD
    u_t_bsad =                  " fm_bsad_tab   Table Type for BSAD
    u_t_mhnd =                  " fm_mhnd_print_tab  MHND Collector: Dunning Data (used for printing)
    u_t_mhnk =                  " fm_mhnk_print_tab  MHNK Collector - Dunning Data (account entries)
    u_notify_date =             " fm_notify_date  Notification Date
    .  "  SAMPLE_PROCESS_00103035

ABAP code example for Function Module SAMPLE_PROCESS_00103035

The ABAP code below is a full code listing to execute function module SAMPLE_PROCESS_00103035 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(ld_u_test_run) = some text here

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

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

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

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

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

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

CALL FUNCTION 'SAMPLE_PROCESS_00103035'
  EXPORTING
    u_test_run =                 ld_u_test_run
    u_t_bsid =                   ld_u_t_bsid
    u_t_bsec =                   ld_u_t_bsec
    u_t_bsad =                   ld_u_t_bsad
    u_t_mhnd =                   ld_u_t_mhnd
    u_t_mhnk =                   ld_u_t_mhnk
    u_notify_date =              ld_u_notify_date
    .  "  SAMPLE_PROCESS_00103035

IF SY-SUBRC EQ 0.
  "All OK
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_u_test_run
 
 TYPE BOOLE-BOOLE ,
ld_u_t_bsid
 
 TYPE FM_BSID_TAB ,
ld_u_t_bsec
 
 TYPE FM_BSEC_TAB ,
ld_u_t_bsad
 
 TYPE FM_BSAD_TAB ,
ld_u_t_mhnd
 
 TYPE FM_MHND_PRINT_TAB ,
ld_u_t_mhnk
 
 TYPE FM_MHNK_PRINT_TAB ,
ld_u_notify_date
 
 TYPE FM_NOTIFY_DATE .



ld_u_test_run = some text here
ld_u_t_bsid = 'Check type of data required'.
ld_u_t_bsec = 'Check type of data required'.
ld_u_t_bsad = 'Check type of data required'.
ld_u_t_mhnd = 'Check type of data required'.
ld_u_t_mhnk = 'Check type of data required'.
ld_u_notify_date = 'Check type of data required'.