SAP RECA_GUI_BUSOBJ_APPL Function Module for Start Application
RECA_GUI_BUSOBJ_APPL is a standard reca gui busobj appl SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Start Application 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 reca gui busobj appl FM, simply by entering the name RECA_GUI_BUSOBJ_APPL into the relevant SAP transaction such as SE37 or SE38.
Function Group: RECA_GUI_BUSOBJ_APPL
Program Name: SAPLRECA_GUI_BUSOBJ_APPL
Main Program: SAPLRECA_GUI_BUSOBJ_APPL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RECA_GUI_BUSOBJ_APPL 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 'RECA_GUI_BUSOBJ_APPL'"Start Application.
EXPORTING
* ID_ACTIVITY = '03' "Activity
* ID_OBJTYPE = "Object Type (Only Required in Create Mode)
* ID_INTRENO = "
* ID_OBJNR = "CO Object Number
* IF_LEAVE_CURRENT = ABAP_FALSE "'X' = LEAVE TRANSACTION
* IF_NEW_EXTERNAL_MODE = ABAP_FALSE "Open New Window?
* IF_NEW_INTERNAL_MODE = ABAP_FALSE "New Internal Mode (CALL TRANSACTION)?
* IS_NAVIGATION_DATA = "Possible Navigation Information
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for RECA_GUI_BUSOBJ_APPL
ID_ACTIVITY - Activity
Data type: RECA1_ACTIVITYDefault: '03'
Optional: No
Call by Reference: Yes
ID_OBJTYPE - Object Type (Only Required in Create Mode)
Data type: RECAC_OBJECT_TYPE_ALLOWED-OBJTYPEOptional: Yes
Call by Reference: Yes
ID_INTRENO -
Data type: RECAINTRENOOptional: Yes
Call by Reference: Yes
ID_OBJNR - CO Object Number
Data type: RECAOBJNROptional: Yes
Call by Reference: Yes
IF_LEAVE_CURRENT - 'X' = LEAVE TRANSACTION
Data type: ABAP_BOOLDefault: ABAP_FALSE
Optional: Yes
Call by Reference: Yes
IF_NEW_EXTERNAL_MODE - Open New Window?
Data type: ABAP_BOOLDefault: ABAP_FALSE
Optional: Yes
Call by Reference: Yes
IF_NEW_INTERNAL_MODE - New Internal Mode (CALL TRANSACTION)?
Data type: ABAP_BOOLDefault: ABAP_FALSE
Optional: Yes
Call by Reference: Yes
IS_NAVIGATION_DATA - Possible Navigation Information
Data type: RECA_WB_NAVIGATIONOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
ERROR - Errors
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RECA_GUI_BUSOBJ_APPL 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_error | TYPE STRING, " | |||
| lv_id_activity | TYPE RECA1_ACTIVITY, " '03' | |||
| lv_id_objtype | TYPE RECAC_OBJECT_TYPE_ALLOWED-OBJTYPE, " | |||
| lv_id_intreno | TYPE RECAINTRENO, " | |||
| lv_id_objnr | TYPE RECAOBJNR, " | |||
| lv_if_leave_current | TYPE ABAP_BOOL, " ABAP_FALSE | |||
| lv_if_new_external_mode | TYPE ABAP_BOOL, " ABAP_FALSE | |||
| lv_if_new_internal_mode | TYPE ABAP_BOOL, " ABAP_FALSE | |||
| lv_is_navigation_data | TYPE RECA_WB_NAVIGATION. " |
|   CALL FUNCTION 'RECA_GUI_BUSOBJ_APPL' "Start Application |
| EXPORTING | ||
| ID_ACTIVITY | = lv_id_activity | |
| ID_OBJTYPE | = lv_id_objtype | |
| ID_INTRENO | = lv_id_intreno | |
| ID_OBJNR | = lv_id_objnr | |
| IF_LEAVE_CURRENT | = lv_if_leave_current | |
| IF_NEW_EXTERNAL_MODE | = lv_if_new_external_mode | |
| IF_NEW_INTERNAL_MODE | = lv_if_new_internal_mode | |
| IS_NAVIGATION_DATA | = lv_is_navigation_data | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| . " RECA_GUI_BUSOBJ_APPL | ||
ABAP code using 7.40 inline data declarations to call FM RECA_GUI_BUSOBJ_APPL
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_id_activity) | = '03'. | |||
| "SELECT single OBJTYPE FROM RECAC_OBJECT_TYPE_ALLOWED INTO @DATA(ld_id_objtype). | ||||
| DATA(ld_if_leave_current) | = ABAP_FALSE. | |||
| DATA(ld_if_new_external_mode) | = ABAP_FALSE. | |||
| DATA(ld_if_new_internal_mode) | = ABAP_FALSE. | |||
Search for further information about these or an SAP related objects