SAP SEPA_MANDATE_UI_CHG_STATUS_GET Function Module for









SEPA_MANDATE_UI_CHG_STATUS_GET is a standard sepa mandate ui chg status get 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 mandate ui chg status get FM, simply by entering the name SEPA_MANDATE_UI_CHG_STATUS_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function SEPA_MANDATE_UI_CHG_STATUS_GET 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_MANDATE_UI_CHG_STATUS_GET'"
  EXPORTING
   I_ANWND =  "
   I_ORIGIN_REC_CRDID =  "
   I_ORIGIN_MNDID =  "
*  I_CHG_TYPE =  "

 IMPORTING
   E_CHANGED =  "
.



IMPORTING Parameters details for SEPA_MANDATE_UI_CHG_STATUS_GET

I_ANWND -

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

I_ORIGIN_REC_CRDID -

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

I_ORIGIN_MNDID -

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

I_CHG_TYPE -

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

EXPORTING Parameters details for SEPA_MANDATE_UI_CHG_STATUS_GET

E_CHANGED -

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

Copy and paste ABAP code example for SEPA_MANDATE_UI_CHG_STATUS_GET 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_i_anwnd  TYPE SEPA_ANWND, "   
lv_e_changed  TYPE XFELD, "   
lv_i_origin_rec_crdid  TYPE SEPA_CRDID_ORIGIN, "   
lv_i_origin_mndid  TYPE SEPA_MNDID_ORIGIN, "   
lv_i_chg_type  TYPE C. "   

  CALL FUNCTION 'SEPA_MANDATE_UI_CHG_STATUS_GET'  "
    EXPORTING
         I_ANWND = lv_i_anwnd
         I_ORIGIN_REC_CRDID = lv_i_origin_rec_crdid
         I_ORIGIN_MNDID = lv_i_origin_mndid
         I_CHG_TYPE = lv_i_chg_type
    IMPORTING
         E_CHANGED = lv_e_changed
. " SEPA_MANDATE_UI_CHG_STATUS_GET




ABAP code using 7.40 inline data declarations to call FM SEPA_MANDATE_UI_CHG_STATUS_GET

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!