SAP FMCA_EVENT_0600 Function Module for Payment - Payment Data from DPSOB and Additional Grouping Characteristic
FMCA_EVENT_0600 is a standard fmca event 0600 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Payment - Payment Data from DPSOB and Additional Grouping Characteristic processing and below is the pattern details for this FM, 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 fmca event 0600 FM, simply by entering the name FMCA_EVENT_0600 into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMCA_PAY
Program Name: SAPLFMCA_PAY
Main Program: SAPLFMCA_PAY
Appliation area: F
Release date: 04-Mar-2005
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMCA_EVENT_0600 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 'FMCA_EVENT_0600'"Payment - Payment Data from DPSOB and Additional Grouping Characteristic.
EXPORTING
* I_DPAYC = "Administrative Data for Payment Run
* I_PAYING_PARTNER = "Business Partner Number
* I_PAYING_ACCOUNT = "Contract Account Number
* I_PARA = "Payment Program - Parameters
* I_BASICS = "Mass Activities: Global Values for All Mass Activities
TABLES
T_0600 = "Items and changable fields (*_0600)
* T_MESSA = "Messages for the Job Log
* T_MESSA_KK = "FI-CA: Messages with Log Class from Application Log
IMPORTING Parameters details for FMCA_EVENT_0600
I_DPAYC - Administrative Data for Payment Run
Data type: DPAYCOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PAYING_PARTNER - Business Partner Number
Data type: FKKOP-GPARTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PAYING_ACCOUNT - Contract Account Number
Data type: FKKOP-VKONTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PARA - Payment Program - Parameters
Data type: FKKPY_PARAOptional: Yes
Call by Reference: No ( called with pass by value option)
I_BASICS - Mass Activities: Global Values for All Mass Activities
Data type: FKK_MAD_BASICSOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FMCA_EVENT_0600
T_0600 - Items and changable fields (*_0600)
Data type: FKKPY_0600Optional: No
Call by Reference: Yes
T_MESSA - Messages for the Job Log
Data type: MESSAOptional: Yes
Call by Reference: Yes
T_MESSA_KK - FI-CA: Messages with Log Class from Application Log
Data type: MESSA_KKOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for FMCA_EVENT_0600 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: | ||||
| lt_t_0600 | TYPE STANDARD TABLE OF FKKPY_0600, " | |||
| lv_i_dpayc | TYPE DPAYC, " | |||
| lt_t_messa | TYPE STANDARD TABLE OF MESSA, " | |||
| lv_i_paying_partner | TYPE FKKOP-GPART, " | |||
| lt_t_messa_kk | TYPE STANDARD TABLE OF MESSA_KK, " | |||
| lv_i_paying_account | TYPE FKKOP-VKONT, " | |||
| lv_i_para | TYPE FKKPY_PARA, " | |||
| lv_i_basics | TYPE FKK_MAD_BASICS. " |
|   CALL FUNCTION 'FMCA_EVENT_0600' "Payment - Payment Data from DPSOB and Additional Grouping Characteristic |
| EXPORTING | ||
| I_DPAYC | = lv_i_dpayc | |
| I_PAYING_PARTNER | = lv_i_paying_partner | |
| I_PAYING_ACCOUNT | = lv_i_paying_account | |
| I_PARA | = lv_i_para | |
| I_BASICS | = lv_i_basics | |
| TABLES | ||
| T_0600 | = lt_t_0600 | |
| T_MESSA | = lt_t_messa | |
| T_MESSA_KK | = lt_t_messa_kk | |
| . " FMCA_EVENT_0600 | ||
ABAP code using 7.40 inline data declarations to call FM FMCA_EVENT_0600
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.| "SELECT single GPART FROM FKKOP INTO @DATA(ld_i_paying_partner). | ||||
| "SELECT single VKONT FROM FKKOP INTO @DATA(ld_i_paying_account). | ||||
Search for further information about these or an SAP related objects