SAP CY_GET_MCOBJ Function Module for Determines the matchcode object for a field from CYFI1
CY_GET_MCOBJ is a standard cy get mcobj SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determines the matchcode object for a field from CYFI1 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 cy get mcobj FM, simply by entering the name CY_GET_MCOBJ into the relevant SAP transaction such as SE37 or SE38.
Function Group: CYCP
Program Name: SAPLCYCP
Main Program: SAPLCYCP
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CY_GET_MCOBJ 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 'CY_GET_MCOBJ'"Determines the matchcode object for a field from CYFI1.
EXPORTING
FIELDNAME = "The name of the field
IMPORTING
MCOBJ = "
EXCEPTIONS
NO_MATCHCODE = 1
IMPORTING Parameters details for CY_GET_MCOBJ
FIELDNAME - The name of the field
Data type: FIELDNAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CY_GET_MCOBJ
MCOBJ -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_MATCHCODE - There is no matchcode for the field
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CY_GET_MCOBJ 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_mcobj | TYPE C, " | |||
| lv_fieldname | TYPE FIELDNAME, " | |||
| lv_no_matchcode | TYPE FIELDNAME. " |
|   CALL FUNCTION 'CY_GET_MCOBJ' "Determines the matchcode object for a field from CYFI1 |
| EXPORTING | ||
| FIELDNAME | = lv_fieldname | |
| IMPORTING | ||
| MCOBJ | = lv_mcobj | |
| EXCEPTIONS | ||
| NO_MATCHCODE = 1 | ||
| . " CY_GET_MCOBJ | ||
ABAP code using 7.40 inline data declarations to call FM CY_GET_MCOBJ
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