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

Function CHECK_MINIAPP_START 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 'CHECK_MINIAPP_START'".
EXPORTING
* USER_NAME = SY-UNAME "
MINIAPP = "MiniApp Name
EXCEPTIONS
NOT_AUTHORIZED = 1
IMPORTING Parameters details for CHECK_MINIAPP_START
USER_NAME -
Data type: SY-UNAMEDefault: SY-UNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)
MINIAPP - MiniApp Name
Data type: AGR_MAPP-APPNAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_AUTHORIZED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CHECK_MINIAPP_START 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_user_name | TYPE SY-UNAME, " SY-UNAME | |||
| lv_not_authorized | TYPE SY, " | |||
| lv_miniapp | TYPE AGR_MAPP-APPNAME. " |
|   CALL FUNCTION 'CHECK_MINIAPP_START' " |
| EXPORTING | ||
| USER_NAME | = lv_user_name | |
| MINIAPP | = lv_miniapp | |
| EXCEPTIONS | ||
| NOT_AUTHORIZED = 1 | ||
| . " CHECK_MINIAPP_START | ||
ABAP code using 7.40 inline data declarations to call FM CHECK_MINIAPP_START
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 UNAME FROM SY INTO @DATA(ld_user_name). | ||||
| DATA(ld_user_name) | = SY-UNAME. | |||
| "SELECT single APPNAME FROM AGR_MAPP INTO @DATA(ld_miniapp). | ||||
Search for further information about these or an SAP related objects