SAP MCS_FUNCTION_MODULES_SEARCH Function Module for NOTRANSL: Verwendungungsnachweis für Kommunikationsstrukturen in Ereigniss

Search SAP Function Modules

MCS_FUNCTION_MODULES_SEARCH is a standard mcs function modules search SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Verwendungungsnachweis für Kommunikationsstrukturen in Ereigniss 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 mcs function modules search FM, simply by entering the name MCS_FUNCTION_MODULES_SEARCH into the relevant SAP transaction such as SE37 or SE38.

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

Function MCS_FUNCTION_MODULES_SEARCH 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 'MCS_FUNCTION_MODULES_SEARCH'"NOTRANSL: Verwendungungsnachweis für Kommunikationsstrukturen in Ereigniss
  EXPORTING
*  I_CSTRU =  "Information structure for which determination is to take place
*  I_FUNCTION = 'ENTRY' "Check if Cstru only exists once

 IMPORTING
   E_FNAME =  "Name of inbound function module
   E_INCLUDE =  "Not used !!! Report name of the Include
   E_FBIDOC =  "Name of IDoc function module

CHANGING
*  C_ZEITP =  "Event for which determination to take place!

EXCEPTIONS
   NO_EVENT_TO_CSTRUCTURE = 1    SEVERAL_EVENTS_AVAILABLE = 2    NO_INPUT_PARAMETERS = 3    FUNCTIONTYPE_NOT_IN_TMCE = 4    FUNCTION_MODULE_NOT_FOUND = 5 

.

IMPORTING Parameters details for MCS_FUNCTION_MODULES_SEARCH

I_CSTRU - Information structure for which determination is to take place

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

I_FUNCTION - Check if Cstru only exists once

Data type: TMCE-SUBID
Default: 'ENTRY'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for MCS_FUNCTION_MODULES_SEARCH

E_FNAME - Name of inbound function module

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

E_INCLUDE - Not used !!! Report name of the Include

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

E_FBIDOC - Name of IDoc function module

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

CHANGING Parameters details for MCS_FUNCTION_MODULES_SEARCH

C_ZEITP - Event for which determination to take place!

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

EXCEPTIONS details

NO_EVENT_TO_CSTRUCTURE - No event for communication structure!

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

SEVERAL_EVENTS_AVAILABLE - MOre than one event for communication structure!

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

NO_INPUT_PARAMETERS - Neither I_CSTRU nor C_ZEITP is filled!

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

FUNCTIONTYPE_NOT_IN_TMCE - The function type you are looking for is not in table TMCE!

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

FUNCTION_MODULE_NOT_FOUND - Function module not found!

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

Copy and paste ABAP code example for MCS_FUNCTION_MODULES_SEARCH 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.

ABAP code using 7.40 inline data declarations to call FM MCS_FUNCTION_MODULES_SEARCH

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