SAP MC_CHECK_CONSISTENCY Function Module for Checks the matchcode ID for consistency

Search SAP Function Modules

MC_CHECK_CONSISTENCY is a standard mc check consistency SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Checks the matchcode ID for consistency 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 mc check consistency FM, simply by entering the name MC_CHECK_CONSISTENCY into the relevant SAP transaction such as SE37 or SE38.

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

Function MC_CHECK_CONSISTENCY 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_CHECK_CONSISTENCY'"Checks the matchcode ID for consistency
  EXPORTING
   DD23V_IMP =  "Header of a matchcode ID
*  PRID = 0 "
*  FIELD_LNG_ADAPTION = ' ' "

 IMPORTING
   RC =  "Error structure for export (severity, number)
   UNCOMPLETE_KEY =  "

TABLES
   DD21V_TAB =  "Tables of the matchcode ID
   RSMRL_TAB =  "
   IDTAB_TAB =  "
   DD24V_TAB =  "Fields of a matchcode Id
   DD26V_TAB =  "Tables of the matchcode object
   DD27P_TAB =  "View on fields of a matchcode object
   DD28V_TAB =  "Lines of the selection conditions
   RSMBL_TAB =  "
   RSMFL_TAB =  "
   RSMVL_TAB =  "

.

IMPORTING Parameters details for MC_CHECK_CONSISTENCY

DD23V_IMP - Header of a matchcode ID

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

PRID -

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

FIELD_LNG_ADAPTION -

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

EXPORTING Parameters details for MC_CHECK_CONSISTENCY

RC - Error structure for export (severity, number)

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

UNCOMPLETE_KEY -

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

TABLES Parameters details for MC_CHECK_CONSISTENCY

DD21V_TAB - Tables of the matchcode ID

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

RSMRL_TAB -

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

IDTAB_TAB -

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

DD24V_TAB - Fields of a matchcode Id

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

DD26V_TAB - Tables of the matchcode object

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

DD27P_TAB - View on fields of a matchcode object

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

DD28V_TAB - Lines of the selection conditions

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

RSMBL_TAB -

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

RSMFL_TAB -

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

RSMVL_TAB -

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

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

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