SAP MC_CRE_CHECK_UTILITY Function Module for
MC_CRE_CHECK_UTILITY is a standard mc cre check utility 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 mc cre check utility FM, simply by entering the name MC_CRE_CHECK_UTILITY into the relevant SAP transaction such as SE37 or SE38.
Function Group: SMC0
Program Name: SAPLSMC0
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MC_CRE_CHECK_UTILITY 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 'MC_CRE_CHECK_UTILITY'".
EXPORTING
FUNC = "function for MCO maintenance to be
MCONAME = "MCO name
EXCEPTIONS
FCT_NOT_FOUND = 1
IMPORTING Parameters details for MC_CRE_CHECK_UTILITY
FUNC - function for MCO maintenance to be
Data type: MCMACO-FKT_Optional: No
Call by Reference: No ( called with pass by value option)
MCONAME - MCO name
Data type: DD20L-MCONAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FCT_NOT_FOUND - required function module is not av
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MC_CRE_CHECK_UTILITY 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_func | TYPE MCMACO-FKT_, " | |||
| lv_fct_not_found | TYPE MCMACO, " | |||
| lv_mconame | TYPE DD20L-MCONAME. " |
|   CALL FUNCTION 'MC_CRE_CHECK_UTILITY' " |
| EXPORTING | ||
| FUNC | = lv_func | |
| MCONAME | = lv_mconame | |
| EXCEPTIONS | ||
| FCT_NOT_FOUND = 1 | ||
| . " MC_CRE_CHECK_UTILITY | ||
ABAP code using 7.40 inline data declarations to call FM MC_CRE_CHECK_UTILITY
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 FKT_ FROM MCMACO INTO @DATA(ld_func). | ||||
| "SELECT single MCONAME FROM DD20L INTO @DATA(ld_mconame). | ||||
Search for further information about these or an SAP related objects