SAP Function Modules

BAPI_SEPA_MANDATE_CHANGE1 SAP Function module







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

Associated Function Group: SEPA_MANDATE_BAPIS
Released Date: Not Released
Processing type: Remote-Enabled
remote enabled module settings


Pattern for FM BAPI_SEPA_MANDATE_CHANGE1 - BAPI SEPA MANDATE CHANGE1





CALL FUNCTION 'BAPI_SEPA_MANDATE_CHANGE1' "
  EXPORTING
*   i_application =             " bapi_s_sepa_mandate_id-application
    creditorid =                " bapi_s_sepa_mandate_id-sepa_creditor_id
    mandateid =                 " bapi_s_sepa_mandate_id-sepa_mandate_id
    is_data_to_change =         " bapi_s_sepa_mandate_change
  IMPORTING
    return =                    " bapiret2
    .  "  BAPI_SEPA_MANDATE_CHANGE1

ABAP code example for Function Module BAPI_SEPA_MANDATE_CHANGE1





The ABAP code below is a full code listing to execute function module BAPI_SEPA_MANDATE_CHANGE1 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_return  TYPE BAPIRET2 .


DATA(ld_i_application) = some text here

DATA(ld_creditorid) = some text here

DATA(ld_mandateid) = some text here
DATA(ld_is_data_to_change) = 'Check type of data required'. . CALL FUNCTION 'BAPI_SEPA_MANDATE_CHANGE1' EXPORTING * i_application = ld_i_application creditorid = ld_creditorid mandateid = ld_mandateid is_data_to_change = ld_is_data_to_change IMPORTING return = ld_return . " BAPI_SEPA_MANDATE_CHANGE1
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_return  TYPE BAPIRET2 ,
ld_i_application  TYPE BAPI_S_SEPA_MANDATE_ID-APPLICATION ,
ld_creditorid  TYPE BAPI_S_SEPA_MANDATE_ID-SEPA_CREDITOR_ID ,
ld_mandateid  TYPE BAPI_S_SEPA_MANDATE_ID-SEPA_MANDATE_ID ,
ld_is_data_to_change  TYPE BAPI_S_SEPA_MANDATE_CHANGE .


ld_i_application = some text here

ld_creditorid = some text here

ld_mandateid = some text here
ld_is_data_to_change = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name BAPI_SEPA_MANDATE_CHANGE1 or its description.