SAP BAPI_SEPAMANDAT_CHANGE Function Module for









BAPI_SEPAMANDAT_CHANGE is a standard bapi sepamandat change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for bapi sepamandat change FM, simply by entering the name BAPI_SEPAMANDAT_CHANGE into the relevant SAP transaction such as SE37 or SE38.

Function Group: SEPA_MANDATE_ALE
Program Name: SAPLSEPA_MANDATE_ALE
Main Program: SAPLSEPA_MANDATE_ALE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_SEPAMANDAT_CHANGE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'BAPI_SEPAMANDAT_CHANGE'"
EXPORTING
IS_MANDATE_IDS = "
* IS_COMMON_DATA = "
* I_NO_DISTRIBUTION = "

IMPORTING
RETURN = "

TABLES
* IT_APPEND_DATA = "
.



IMPORTING Parameters details for BAPI_SEPAMANDAT_CHANGE

IS_MANDATE_IDS -

Data type: BAPI_S_SEPA_MANDATE_ID
Optional: No
Call by Reference: No ( called with pass by value option)

IS_COMMON_DATA -

Data type: BAPI_S_SEPA_MANDATE_COMMON
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_NO_DISTRIBUTION -

Data type: BAPI_S_BF_FLAG
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BAPI_SEPAMANDAT_CHANGE

RETURN -

Data type: BAPIRET2
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BAPI_SEPAMANDAT_CHANGE

IT_APPEND_DATA -

Data type: BAPI_S_SEPA_MANDATE_APPEND
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for BAPI_SEPAMANDAT_CHANGE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_return  TYPE BAPIRET2, "   
lv_is_mandate_ids  TYPE BAPI_S_SEPA_MANDATE_ID, "   
lt_it_append_data  TYPE STANDARD TABLE OF BAPI_S_SEPA_MANDATE_APPEND, "   
lv_is_common_data  TYPE BAPI_S_SEPA_MANDATE_COMMON, "   
lv_i_no_distribution  TYPE BAPI_S_BF_FLAG. "   

  CALL FUNCTION 'BAPI_SEPAMANDAT_CHANGE'  "
    EXPORTING
         IS_MANDATE_IDS = lv_is_mandate_ids
         IS_COMMON_DATA = lv_is_common_data
         I_NO_DISTRIBUTION = lv_i_no_distribution
    IMPORTING
         RETURN = lv_return
    TABLES
         IT_APPEND_DATA = lt_it_append_data
. " BAPI_SEPAMANDAT_CHANGE




ABAP code using 7.40 inline data declarations to call FM BAPI_SEPAMANDAT_CHANGE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!