SAP SEPA_MANDATES_API_ADD_USAGE Function Module for

Search SAP Function Modules

SEPA_MANDATES_API_ADD_USAGE is a standard sepa mandates api add usage 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 sepa mandates api add usage FM, simply by entering the name SEPA_MANDATES_API_ADD_USAGE into the relevant SAP transaction such as SE37 or SE38.

Function Group: SEPA_MANDATE_SERVICES
Program Name: SAPLSEPA_MANDATE_SERVICES
Main Program: SAPLSEPA_MANDATE_SERVICES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SEPA_MANDATES_API_ADD_USAGE 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 'SEPA_MANDATES_API_ADD_USAGE'"
  EXPORTING
   I_TAB_USE_EXT =  "
*  I_UPDATE_TASK = 'X' "
*  I_AUTHORITY_CHECK = 'X' "
*  I_BUFFER_ONLY = ' ' "
*  I_LAST_USE = ' ' "
*  I_FIRSTUSE_PAYRUN = ' ' "

 IMPORTING
   ET_MANDATES_FAILED =  "
   ET_MESSAGES =  "

.

IMPORTING Parameters details for SEPA_MANDATES_API_ADD_USAGE

I_TAB_USE_EXT -

Data type: SEPA_TAB_USE_EXT
Optional: No
Call by Reference: Yes

I_UPDATE_TASK -

Data type: BOOLEAN
Default: 'X'
Optional: No
Call by Reference: No ( called with pass by value option)

I_AUTHORITY_CHECK -

Data type: BOOLEAN
Default: 'X'
Optional: No
Call by Reference: No ( called with pass by value option)

I_BUFFER_ONLY -

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

I_LAST_USE -

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

I_FIRSTUSE_PAYRUN -

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

EXPORTING Parameters details for SEPA_MANDATES_API_ADD_USAGE

ET_MANDATES_FAILED -

Data type: SEPA_TAB_MANDATE_KEY_EXTERNAL
Optional: No
Call by Reference: Yes

ET_MESSAGES -

Data type: BAPIRET1_LIST
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SEPA_MANDATES_API_ADD_USAGE 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.

ABAP code using 7.40 inline data declarations to call FM SEPA_MANDATES_API_ADD_USAGE

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