SAP FKK_SAMPLE_0572 Function Module for









FKK_SAMPLE_0572 is a standard fkk sample 0572 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 fkk sample 0572 FM, simply by entering the name FKK_SAMPLE_0572 into the relevant SAP transaction such as SE37 or SE38.

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



Function FKK_SAMPLE_0572 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 'FKK_SAMPLE_0572'"
EXPORTING
* I_SND_ID = "
* I_REC_ID = "
* I_WA = "SEPA Mandate
* I_FIX_DATA = "SEPA Mandate
* I_REF_ID = "SEPA Mandate: ID of Referenced Object
* I_APPLK = "Application Area

IMPORTING
E_SND_DATA = "
E_REC_DATA = "
E_ADMIN_DATA = "
E_REC_ID = "
E_REF_DATA = "SEPA Mandate: Data of Referenced Object
E_SND_ID = "
.



IMPORTING Parameters details for FKK_SAMPLE_0572

I_SND_ID -

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

I_REC_ID -

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

I_WA - SEPA Mandate

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

I_FIX_DATA - SEPA Mandate

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

I_REF_ID - SEPA Mandate: ID of Referenced Object

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

I_APPLK - Application Area

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

EXPORTING Parameters details for FKK_SAMPLE_0572

E_SND_DATA -

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

E_REC_DATA -

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

E_ADMIN_DATA -

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

E_REC_ID -

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

E_REF_DATA - SEPA Mandate: Data of Referenced Object

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

E_SND_ID -

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

Copy and paste ABAP code example for FKK_SAMPLE_0572 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_snd_id  TYPE SEPA_S_SENDER_ID, "   
lv_e_snd_data  TYPE SEPA_S_SENDER_DATA, "   
lv_i_rec_id  TYPE SEPA_S_RECEIVER_ID, "   
lv_e_rec_data  TYPE SEPA_S_RECEIVER_DATA, "   
lv_i_wa  TYPE SEPA_MANDATE, "   
lv_e_admin_data  TYPE SEPA_S_ADMIN_EXT, "   
lv_e_rec_id  TYPE SEPA_S_RECEIVER_ID, "   
lv_i_fix_data  TYPE SEPA_MANDATE, "   
lv_i_ref_id  TYPE FKK_SEPA_REFERENCE_ID, "   
lv_e_ref_data  TYPE FKK_SEPA_REFERENCE_DATA, "   
lv_i_applk  TYPE APPLK_KK, "   
lv_e_snd_id  TYPE SEPA_S_SENDER_ID. "   

  CALL FUNCTION 'FKK_SAMPLE_0572'  "
    EXPORTING
         I_SND_ID = lv_i_snd_id
         I_REC_ID = lv_i_rec_id
         I_WA = lv_i_wa
         I_FIX_DATA = lv_i_fix_data
         I_REF_ID = lv_i_ref_id
         I_APPLK = lv_i_applk
    IMPORTING
         E_SND_DATA = lv_e_snd_data
         E_REC_DATA = lv_e_rec_data
         E_ADMIN_DATA = lv_e_admin_data
         E_REC_ID = lv_e_rec_id
         E_REF_DATA = lv_e_ref_data
         E_SND_ID = lv_e_snd_id
. " FKK_SAMPLE_0572




ABAP code using 7.40 inline data declarations to call FM FKK_SAMPLE_0572

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!