SAP Function Modules

comments icon Comments

SEPA_MANDATES_API_CHANGE SAP Function module







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

Associated Function Group: SEPA_MANDATE_SERVICES
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM SEPA_MANDATES_API_CHANGE - SEPA MANDATES API CHANGE 





CALL FUNCTION 'SEPA_MANDATES_API_CHANGE' "
  EXPORTING
*   i_authority_check = 'X'     " boolean
*   i_update_task = 'X'         " boolean
*   i_buffer_only = SPACE       " boolean
    i_tab_data_mandate_chng =   " sepa_tab_data_mandate_chng
*   i_only_1_change_version_in_luw = SPACE  " boolean
*   i_already_checked = SPACE   " xfeld
*   i_proceed_by_warning = 'X'  " xfeld
*   i_force_new_version =       " xfeld
*   i_clear_use_data =          " xfeld
*   i_no_distribution =         " xfeld
  IMPORTING
    et_mandates_failed =        " sepa_tab_mandate_key_external
    et_messages =               " bapiret1_list
    et_messages2 =              " bapirettab
    .  "  SEPA_MANDATES_API_CHANGE

ABAP code example for Function Module SEPA_MANDATES_API_CHANGE





The ABAP code below is a full code listing to execute function module SEPA_MANDATES_API_CHANGE 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_et_mandates_failed    TYPE SEPA_TAB_MANDATE_KEY_EXTERNAL
,
ld_et_messages    TYPE BAPIRET1_LIST
,
ld_et_messages2    TYPE BAPIRETTAB
.




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

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

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

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

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

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

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

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

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

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

CALL FUNCTION 'SEPA_MANDATES_API_CHANGE'
  EXPORTING
*   i_authority_check =          ld_i_authority_check
*   i_update_task =              ld_i_update_task
*   i_buffer_only =              ld_i_buffer_only
    i_tab_data_mandate_chng =    ld_i_tab_data_mandate_chng
*   i_only_1_change_version_in_luw =    ld_i_only_1_change_version_in_luw
*   i_already_checked =          ld_i_already_checked
*   i_proceed_by_warning =       ld_i_proceed_by_warning
*   i_force_new_version =        ld_i_force_new_version
*   i_clear_use_data =           ld_i_clear_use_data
*   i_no_distribution =          ld_i_no_distribution
  IMPORTING
    et_mandates_failed =         ld_et_mandates_failed
    et_messages =                ld_et_messages
    et_messages2 =               ld_et_messages2
    .  "  SEPA_MANDATES_API_CHANGE

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_et_mandates_failed  TYPE SEPA_TAB_MANDATE_KEY_EXTERNAL ,
ld_i_authority_check  TYPE BOOLEAN ,
ld_et_messages  TYPE BAPIRET1_LIST ,
ld_i_update_task  TYPE BOOLEAN ,
ld_et_messages2  TYPE BAPIRETTAB ,
ld_i_buffer_only  TYPE BOOLEAN ,
ld_i_tab_data_mandate_chng  TYPE SEPA_TAB_DATA_MANDATE_CHNG ,
ld_i_only_1_change_version_in_luw  TYPE BOOLEAN ,
ld_i_already_checked  TYPE XFELD ,
ld_i_proceed_by_warning  TYPE XFELD ,
ld_i_force_new_version  TYPE XFELD ,
ld_i_clear_use_data  TYPE XFELD ,
ld_i_no_distribution  TYPE XFELD .




ld_i_authority_check = 'Check type of data required'.
ld_i_update_task = 'Check type of data required'.
ld_i_buffer_only = 'Check type of data required'.
ld_i_tab_data_mandate_chng = 'Check type of data required'.
ld_i_only_1_change_version_in_luw = 'Check type of data required'.
ld_i_already_checked = 'Check type of data required'.
ld_i_proceed_by_warning = 'Check type of data required'.
ld_i_force_new_version = 'Check type of data required'.
ld_i_clear_use_data = 'Check type of data required'.
ld_i_no_distribution = '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 SEPA_MANDATES_API_CHANGE or its description.


   
 

SEPA_MANDATES_API_CHANGE - 
SEPA_MANDATES_API_CANCEL - 
SEPA_MANDATES_API_ADD_USAGE - 
SEPA_GET_MANDAT_IBAN_ALL_ANWD - 
SEPA_GET_MANDAT_BY_UCI_ALL - 
SEPA_GET_MANDAT_BY_UCI -