SAP MCS_INFO_STATUS_GET Function Module for NOTRANSL: Ermittelt den Status einer Info-Struktur (siehe Parameter E_MCST
MCS_INFO_STATUS_GET is a standard mcs info status get 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: Ermittelt den Status einer Info-Struktur (siehe Parameter E_MCST 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 status get FM, simply by entering the name MCS_INFO_STATUS_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: MCSA
Program Name: SAPLMCSA
Main Program: SAPLMCSA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MCS_INFO_STATUS_GET 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_STATUS_GET'"NOTRANSL: Ermittelt den Status einer Info-Struktur (siehe Parameter E_MCST.
EXPORTING
* I_FROM_TMC4_IF_POSSIBLE = ' ' "Do not determine status, if one exists
I_GSTRU = "Generated database table
I_MCINF = "Info structure
* I_CLIENT = ' ' "Client for checking data (SAPCE: all)
* I_NO_CHECK_DATA = ' ' "
IMPORTING
E_FLG_DATA = "Already updated?
E_MCSTI = "Info structure status
IMPORTING Parameters details for MCS_INFO_STATUS_GET
I_FROM_TMC4_IF_POSSIBLE - Do not determine status, if one exists
Data type: XFLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_GSTRU - Generated database table
Data type: TMC4-GSTRUOptional: No
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_CLIENT - Client for checking data (SAPCE: all)
Data type: T000-MANDTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_NO_CHECK_DATA -
Data type: XFLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MCS_INFO_STATUS_GET
E_FLG_DATA - Already updated?
Data type: XFLAGOptional: No
Call by Reference: No ( called with pass by value option)
E_MCSTI - Info structure status
Data type: TMC4-MCSTIOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MCS_INFO_STATUS_GET 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_e_flg_data | TYPE XFLAG, " | |||
| lv_i_from_tmc4_if_possible | TYPE XFLAG, " SPACE | |||
| lv_e_mcsti | TYPE TMC4-MCSTI, " | |||
| lv_i_gstru | TYPE TMC4-GSTRU, " | |||
| lv_i_mcinf | TYPE TMC4-MCINF, " | |||
| lv_i_client | TYPE T000-MANDT, " SPACE | |||
| lv_i_no_check_data | TYPE XFLAG. " SPACE |
|   CALL FUNCTION 'MCS_INFO_STATUS_GET' "NOTRANSL: Ermittelt den Status einer Info-Struktur (siehe Parameter E_MCST |
| EXPORTING | ||
| I_FROM_TMC4_IF_POSSIBLE | = lv_i_from_tmc4_if_possible | |
| I_GSTRU | = lv_i_gstru | |
| I_MCINF | = lv_i_mcinf | |
| I_CLIENT | = lv_i_client | |
| I_NO_CHECK_DATA | = lv_i_no_check_data | |
| IMPORTING | ||
| E_FLG_DATA | = lv_e_flg_data | |
| E_MCSTI | = lv_e_mcsti | |
| . " MCS_INFO_STATUS_GET | ||
ABAP code using 7.40 inline data declarations to call FM MCS_INFO_STATUS_GET
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_from_tmc4_if_possible) | = ' '. | |||
| "SELECT single MCSTI FROM TMC4 INTO @DATA(ld_e_mcsti). | ||||
| "SELECT single GSTRU FROM TMC4 INTO @DATA(ld_i_gstru). | ||||
| "SELECT single MCINF FROM TMC4 INTO @DATA(ld_i_mcinf). | ||||
| "SELECT single MANDT FROM T000 INTO @DATA(ld_i_client). | ||||
| DATA(ld_i_client) | = ' '. | |||
| DATA(ld_i_no_check_data) | = ' '. | |||
Search for further information about these or an SAP related objects