FKK_BWP2P_EVENT SAP Function module - Mass Activity: Update Delta Queue for Promise to Pay

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

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

Pattern for FM FKK_BWP2P_EVENT - FKK BWP2P EVENT

CALL FUNCTION 'FKK_BWP2P_EVENT' "Mass Activity: Update Delta Queue for Promise to Pay
  EXPORTING
    i_low =                     " keypp_kk      Lower Interval Limit
    i_high =                    " keypp_kk      Upper Interval Limit
*   i_basics =                  " fkk_mad_basics  Mass Activities: Global Values for All Mass Activities
  CHANGING
    c_pp_test_num =             " i             tested promise to pay header
    c_pp_success_num =          " i             successful promise to pay header
    c_ppd_test_num =            " i             tested Amount Due Per Payment Date
    c_ppd_success_num =         " i             successful Amount Due Per Payment Date
    .  "  FKK_BWP2P_EVENT

ABAP code example for Function Module FKK_BWP2P_EVENT

The ABAP code below is a full code listing to execute function module FKK_BWP2P_EVENT 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_c_pp_test_num) = 'Check type of data required'.

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

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

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

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

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

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

CALL FUNCTION 'FKK_BWP2P_EVENT'
  EXPORTING
    i_low =                      ld_i_low
    i_high =                     ld_i_high
*   i_basics =                   ld_i_basics
  CHANGING
    c_pp_test_num =              ld_c_pp_test_num
    c_pp_success_num =           ld_c_pp_success_num
    c_ppd_test_num =             ld_c_ppd_test_num
    c_ppd_success_num =          ld_c_ppd_success_num
    .  "  FKK_BWP2P_EVENT

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_c_pp_test_num
 
 TYPE I ,
ld_i_low
 
 TYPE KEYPP_KK ,
ld_c_pp_success_num
 
 TYPE I ,
ld_i_high
 
 TYPE KEYPP_KK ,
ld_c_ppd_test_num
 
 TYPE I ,
ld_i_basics
 
 TYPE FKK_MAD_BASICS ,
ld_c_ppd_success_num
 
 TYPE I .


ld_c_pp_test_num = 'Check type of data required'.
ld_i_low = 'Check type of data required'.
ld_c_pp_success_num = 'Check type of data required'.
ld_i_high = 'Check type of data required'.
ld_c_ppd_test_num = 'Check type of data required'.
ld_i_basics = 'Check type of data required'.
ld_c_ppd_success_num = 'Check type of data required'.