SAP FMCA_EVENT_5801_SAMPLE Function Module for









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

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



Function FMCA_EVENT_5801_SAMPLE 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_5801_SAMPLE'"
EXPORTING
IS_TRANSFER = "

EXCEPTIONS
TRANSFER_NOT_ALLOWED = 1
.



IMPORTING Parameters details for FMCA_EVENT_5801_SAMPLE

IS_TRANSFER -

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

EXCEPTIONS details

TRANSFER_NOT_ALLOWED -

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

Copy and paste ABAP code example for FMCA_EVENT_5801_SAMPLE 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_is_transfer  TYPE FICA_S_MDT_TREE_TRANSFER, "   
lv_transfer_not_allowed  TYPE FICA_S_MDT_TREE_TRANSFER. "   

  CALL FUNCTION 'FMCA_EVENT_5801_SAMPLE'  "
    EXPORTING
         IS_TRANSFER = lv_is_transfer
    EXCEPTIONS
        TRANSFER_NOT_ALLOWED = 1
. " FMCA_EVENT_5801_SAMPLE




ABAP code using 7.40 inline data declarations to call FM FMCA_EVENT_5801_SAMPLE

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!