SAP FMCA_ECMD_EVENT Function Module for









FMCA_ECMD_EVENT is a standard fmca ecmd event 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 fmca ecmd event FM, simply by entering the name FMCA_ECMD_EVENT into the relevant SAP transaction such as SE37 or SE38.

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



Function FMCA_ECMD_EVENT 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_ECMD_EVENT'"
  EXPORTING
*  IV_BUT000 =  "BP: General Data I
*  IT_FKKVKP =  "Table Type for FKKVKP
*  IT_DPSOB =  "Contract Object Table in IS-PS-CA
*  IT_DPSOB_BP_ACC =  "Table: Contract Object and Contract Object Cat. for Partner
*  IV_ADDR2_ADD =  "Table Type for SZA7_D0400
   IX_COMMIT =  "
   IV_EVENT =  "Data Element for FMCA_ECMD Events
*  IT_FACTS =  "Table Type for BAPI_CTRACPSOBJECT_FACTS
*  IX_WD_MODE = ' ' "
*  IX_CHANGE_ON_BP = 'X' "
*  IT_BUT0BK =  "Table of Bank Details
*  IT_BUT0CC =  "Table Type for Payment Cards
*  IT_BUT0ID =  "SAP BP: Table Type for Transferring Identification Data
*  IV_ADRC =  "Addresses (Business Address Services)
*  IV_TEL =  "BAPI Structure for Telephone Numbers (Business Address Services)
*  IV_FAX =  "BAPI Structure for Fax Numbers (Business Address Services)
*  IV_SMTP =  "BAPI Structure for E-Mail Addresses (Business Address Services)
*  IT_FKKVK =  "Table Type for Contract Account Header

 IMPORTING
   ET_RETURN =  "Return Table

CHANGING
   CT_STRUCTURE =  "Table Type for Structure of Simplified Master Data Creation
.



IMPORTING Parameters details for FMCA_ECMD_EVENT

IV_BUT000 - BP: General Data I

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

IT_FKKVKP - Table Type for FKKVKP

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

IT_DPSOB - Contract Object Table in IS-PS-CA

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

IT_DPSOB_BP_ACC - Table: Contract Object and Contract Object Cat. for Partner

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

IV_ADDR2_ADD - Table Type for SZA7_D0400

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

IX_COMMIT -

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

IV_EVENT - Data Element for FMCA_ECMD Events

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

IT_FACTS - Table Type for BAPI_CTRACPSOBJECT_FACTS

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

IX_WD_MODE -

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

IX_CHANGE_ON_BP -

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

IT_BUT0BK - Table of Bank Details

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

IT_BUT0CC - Table Type for Payment Cards

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

IT_BUT0ID - SAP BP: Table Type for Transferring Identification Data

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

IV_ADRC - Addresses (Business Address Services)

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

IV_TEL - BAPI Structure for Telephone Numbers (Business Address Services)

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

IV_FAX - BAPI Structure for Fax Numbers (Business Address Services)

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

IV_SMTP - BAPI Structure for E-Mail Addresses (Business Address Services)

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

IT_FKKVK - Table Type for Contract Account Header

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

EXPORTING Parameters details for FMCA_ECMD_EVENT

ET_RETURN - Return Table

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

CHANGING Parameters details for FMCA_ECMD_EVENT

CT_STRUCTURE - Table Type for Structure of Simplified Master Data Creation

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

Copy and paste ABAP code example for FMCA_ECMD_EVENT 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_et_return  TYPE BAPIRET2_T, "   
lv_iv_but000  TYPE BUT000, "   
lv_ct_structure  TYPE FMCA_ECMD_ENTRY_T, "   
lv_it_fkkvkp  TYPE FKKVKP_T, "   
lv_it_dpsob  TYPE DPSOB_T, "   
lv_it_dpsob_bp_acc  TYPE DPSOB_BP_ACC_T, "   
lv_iv_addr2_add  TYPE FMCA_ADDR2_ADD_T, "   
lv_ix_commit  TYPE BOOLE-BOOLE, "   
lv_iv_event  TYPE FMCA_ECMD_EVENT_PS, "   
lv_it_facts  TYPE BAPI_CTRACPSOBJECT_FACTS_T, "   
lv_ix_wd_mode  TYPE XFELD, "   SPACE
lv_ix_change_on_bp  TYPE XFELD, "   'X'
lv_it_but0bk  TYPE BUT0BK_T, "   
lv_it_but0cc  TYPE FMCA_BUT0CC_T, "   
lv_it_but0id  TYPE TTY_BUT0ID, "   
lv_iv_adrc  TYPE ADRC, "   
lv_iv_tel  TYPE BAPIADTEL, "   
lv_iv_fax  TYPE BAPIADFAX, "   
lv_iv_smtp  TYPE BAPIADSMTP, "   
lv_it_fkkvk  TYPE FKKVK_T. "   

  CALL FUNCTION 'FMCA_ECMD_EVENT'  "
    EXPORTING
         IV_BUT000 = lv_iv_but000
         IT_FKKVKP = lv_it_fkkvkp
         IT_DPSOB = lv_it_dpsob
         IT_DPSOB_BP_ACC = lv_it_dpsob_bp_acc
         IV_ADDR2_ADD = lv_iv_addr2_add
         IX_COMMIT = lv_ix_commit
         IV_EVENT = lv_iv_event
         IT_FACTS = lv_it_facts
         IX_WD_MODE = lv_ix_wd_mode
         IX_CHANGE_ON_BP = lv_ix_change_on_bp
         IT_BUT0BK = lv_it_but0bk
         IT_BUT0CC = lv_it_but0cc
         IT_BUT0ID = lv_it_but0id
         IV_ADRC = lv_iv_adrc
         IV_TEL = lv_iv_tel
         IV_FAX = lv_iv_fax
         IV_SMTP = lv_iv_smtp
         IT_FKKVK = lv_it_fkkvk
    IMPORTING
         ET_RETURN = lv_et_return
    CHANGING
         CT_STRUCTURE = lv_ct_structure
. " FMCA_ECMD_EVENT




ABAP code using 7.40 inline data declarations to call FM FMCA_ECMD_EVENT

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 BOOLE FROM BOOLE INTO @DATA(ld_ix_commit).
 
 
 
DATA(ld_ix_wd_mode) = ' '.
 
DATA(ld_ix_change_on_bp) = 'X'.
 
 
 
 
 
 
 
 
 


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!