SAP MCS_INFO_STRUCTURE_CONSISTENT Function Module for NOTRANSL: Prüft, ob Tabellen zu einer Info-Struktur und Datenbanktabelle p
MCS_INFO_STRUCTURE_CONSISTENT is a standard mcs info structure consistent 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: Prüft, ob Tabellen zu einer Info-Struktur und Datenbanktabelle p 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 info structure consistent FM, simply by entering the name MCS_INFO_STRUCTURE_CONSISTENT into the relevant SAP transaction such as SE37 or SE38.
Function Group: MCSA
Program Name: SAPLMCSA
Main Program: SAPLMCSA
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MCS_INFO_STRUCTURE_CONSISTENT 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_INFO_STRUCTURE_CONSISTENT'"NOTRANSL: Prüft, ob Tabellen zu einer Info-Struktur und Datenbanktabelle p.
EXPORTING
* I_FLG_NO_PROT = ' ' "No log should be written
* I_FLG_TEST = ' ' "= 'X' => The log is reset
I_MCINF = "Info structure
* I_MANDT = SY-MANDT "Client
* I_FLG_UPDATEGENER = ' ' "
IMPORTING
E_FLG_DOM_FAULT = "Inconsistency at domain level
E_FLG_DTEL_FAULT = "Inconsistency at data element level
E_FLG_FIELD_FAULT = "Inconsistency at field level
E_FLG_UNIT_FAULT = "Inconsistency at unit level
TABLES
* T_TMC1D = "Key Figures
* T_TMC1K = "Characteristics
EXCEPTIONS
MCINF_NOT_DEFINED = 1 TABLE_NOT_ACTIVE = 2
IMPORTING Parameters details for MCS_INFO_STRUCTURE_CONSISTENT
I_FLG_NO_PROT - No log should be written
Data type: XFLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_TEST - = 'X' => The log is reset
Data type: XFLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MCINF - Info structure
Data type: TMC4-MCINFOptional: No
Call by Reference: No ( called with pass by value option)
I_MANDT - Client
Data type: SY-MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_UPDATEGENER -
Data type: XFLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MCS_INFO_STRUCTURE_CONSISTENT
E_FLG_DOM_FAULT - Inconsistency at domain level
Data type: XFLAGOptional: No
Call by Reference: No ( called with pass by value option)
E_FLG_DTEL_FAULT - Inconsistency at data element level
Data type: XFLAGOptional: No
Call by Reference: No ( called with pass by value option)
E_FLG_FIELD_FAULT - Inconsistency at field level
Data type: XFLAGOptional: No
Call by Reference: No ( called with pass by value option)
E_FLG_UNIT_FAULT - Inconsistency at unit level
Data type: XFLAGOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MCS_INFO_STRUCTURE_CONSISTENT
T_TMC1D - Key Figures
Data type: TMC1DOptional: Yes
Call by Reference: No ( called with pass by value option)
T_TMC1K - Characteristics
Data type: TMC1KOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
MCINF_NOT_DEFINED - Info structure does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLE_NOT_ACTIVE - Generated table is not available or active
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MCS_INFO_STRUCTURE_CONSISTENT 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: | ||||
| lt_t_tmc1d | TYPE STANDARD TABLE OF TMC1D, " | |||
| lv_i_flg_no_prot | TYPE XFLAG, " SPACE | |||
| lv_e_flg_dom_fault | TYPE XFLAG, " | |||
| lv_mcinf_not_defined | TYPE XFLAG, " | |||
| lt_t_tmc1k | TYPE STANDARD TABLE OF TMC1K, " | |||
| lv_i_flg_test | TYPE XFLAG, " SPACE | |||
| lv_e_flg_dtel_fault | TYPE XFLAG, " | |||
| lv_table_not_active | TYPE XFLAG, " | |||
| lv_i_mcinf | TYPE TMC4-MCINF, " | |||
| lv_e_flg_field_fault | TYPE XFLAG, " | |||
| lv_i_mandt | TYPE SY-MANDT, " SY-MANDT | |||
| lv_e_flg_unit_fault | TYPE XFLAG, " | |||
| lv_i_flg_updategener | TYPE XFLAG. " SPACE |
|   CALL FUNCTION 'MCS_INFO_STRUCTURE_CONSISTENT' "NOTRANSL: Prüft, ob Tabellen zu einer Info-Struktur und Datenbanktabelle p |
| EXPORTING | ||
| I_FLG_NO_PROT | = lv_i_flg_no_prot | |
| I_FLG_TEST | = lv_i_flg_test | |
| I_MCINF | = lv_i_mcinf | |
| I_MANDT | = lv_i_mandt | |
| I_FLG_UPDATEGENER | = lv_i_flg_updategener | |
| IMPORTING | ||
| E_FLG_DOM_FAULT | = lv_e_flg_dom_fault | |
| E_FLG_DTEL_FAULT | = lv_e_flg_dtel_fault | |
| E_FLG_FIELD_FAULT | = lv_e_flg_field_fault | |
| E_FLG_UNIT_FAULT | = lv_e_flg_unit_fault | |
| TABLES | ||
| T_TMC1D | = lt_t_tmc1d | |
| T_TMC1K | = lt_t_tmc1k | |
| EXCEPTIONS | ||
| MCINF_NOT_DEFINED = 1 | ||
| TABLE_NOT_ACTIVE = 2 | ||
| . " MCS_INFO_STRUCTURE_CONSISTENT | ||
ABAP code using 7.40 inline data declarations to call FM MCS_INFO_STRUCTURE_CONSISTENT
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.| DATA(ld_i_flg_no_prot) | = ' '. | |||
| DATA(ld_i_flg_test) | = ' '. | |||
| "SELECT single MCINF FROM TMC4 INTO @DATA(ld_i_mcinf). | ||||
| "SELECT single MANDT FROM SY INTO @DATA(ld_i_mandt). | ||||
| DATA(ld_i_mandt) | = SY-MANDT. | |||
| DATA(ld_i_flg_updategener) | = ' '. | |||
Search for further information about these or an SAP related objects