SAP FMCA_EVENT_1702 Function Module for Create Interval Module Invoices









FMCA_EVENT_1702 is a standard fmca event 1702 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create Interval Module Invoices 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 1702 FM, simply by entering the name FMCA_EVENT_1702 into the relevant SAP transaction such as SE37 or SE38.

Function Group: FMCA_MASS_P004
Program Name: SAPLFMCA_MASS_P004
Main Program: SAPLFMCA_MASS_P004
Appliation area: F
Release date: 26-Nov-2001
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FMCA_EVENT_1702 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_1702'"Create Interval Module Invoices
  EXPORTING
   I_LOW =  "
   I_HIGH =  "
*  I_FKKCOCC =  "
*  I_FKK_PROT =  "
*  I_BASICS =  "

CHANGING
   C_TEST_NUM =  "
   C_SUCCESS_NUM =  "

TABLES
*  T_FIMSG =  "
*  T_BUKRS =  "
*  T_GPART =  "
*  T_VKONT =  "
*  T_FKKCOINFO =  "
*  T_PROT_GPART =  "
*  T_PROT_VKONT =  "
.



IMPORTING Parameters details for FMCA_EVENT_1702

I_LOW -

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

I_HIGH -

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

I_FKKCOCC -

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

I_FKK_PROT -

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

I_BASICS -

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

CHANGING Parameters details for FMCA_EVENT_1702

C_TEST_NUM -

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

C_SUCCESS_NUM -

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

TABLES Parameters details for FMCA_EVENT_1702

T_FIMSG -

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

T_BUKRS -

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

T_GPART -

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

T_VKONT -

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

T_FKKCOINFO -

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

T_PROT_GPART -

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

T_PROT_VKONT -

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

Copy and paste ABAP code example for FMCA_EVENT_1702 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_low  TYPE C, "   
lt_t_fimsg  TYPE STANDARD TABLE OF FIMSG, "   
lv_c_test_num  TYPE I, "   
lv_i_high  TYPE C, "   
lt_t_bukrs  TYPE STANDARD TABLE OF FKKR_BUKRS, "   
lv_c_success_num  TYPE I, "   
lt_t_gpart  TYPE STANDARD TABLE OF FKKR_GPART, "   
lv_i_fkkcocc  TYPE FKKCOCC, "   
lt_t_vkont  TYPE STANDARD TABLE OF FKKR_VKONT, "   
lv_i_fkk_prot  TYPE FKKPROT, "   
lv_i_basics  TYPE FKK_MAD_BASICS, "   
lt_t_fkkcoinfo  TYPE STANDARD TABLE OF FKKCOINFO, "   
lt_t_prot_gpart  TYPE STANDARD TABLE OF FKKR_GPART, "   
lt_t_prot_vkont  TYPE STANDARD TABLE OF FKKR_VKONT. "   

  CALL FUNCTION 'FMCA_EVENT_1702'  "Create Interval Module Invoices
    EXPORTING
         I_LOW = lv_i_low
         I_HIGH = lv_i_high
         I_FKKCOCC = lv_i_fkkcocc
         I_FKK_PROT = lv_i_fkk_prot
         I_BASICS = lv_i_basics
    CHANGING
         C_TEST_NUM = lv_c_test_num
         C_SUCCESS_NUM = lv_c_success_num
    TABLES
         T_FIMSG = lt_t_fimsg
         T_BUKRS = lt_t_bukrs
         T_GPART = lt_t_gpart
         T_VKONT = lt_t_vkont
         T_FKKCOINFO = lt_t_fkkcoinfo
         T_PROT_GPART = lt_t_prot_gpart
         T_PROT_VKONT = lt_t_prot_vkont
. " FMCA_EVENT_1702




ABAP code using 7.40 inline data declarations to call FM FMCA_EVENT_1702

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!