SAP SWY_EXIST_TASK_FGROUP Function Module for
SWY_EXIST_TASK_FGROUP is a standard swy exist task fgroup 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 swy exist task fgroup FM, simply by entering the name SWY_EXIST_TASK_FGROUP into the relevant SAP transaction such as SE37 or SE38.
Function Group: SWY_API_FUNCTION_GROUP
Program Name: SAPLSWY_API_FUNCTION_GROUP
Main Program: SAPLSWY_API_FUNCTION_GROUP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SWY_EXIST_TASK_FGROUP 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 'SWY_EXIST_TASK_FGROUP'".
EXPORTING
FGROUP = "Name of function group
EXCEPTIONS
FGROUP_NOT_EXIST = 1
IMPORTING Parameters details for SWY_EXIST_TASK_FGROUP
FGROUP - Name of function group
Data type: RS38L-AREAOptional: No
Call by Reference: Yes
EXCEPTIONS details
FGROUP_NOT_EXIST - Function group does not exist
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SWY_EXIST_TASK_FGROUP 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_fgroup | TYPE RS38L-AREA, " | |||
| lv_fgroup_not_exist | TYPE RS38L. " |
|   CALL FUNCTION 'SWY_EXIST_TASK_FGROUP' " |
| EXPORTING | ||
| FGROUP | = lv_fgroup | |
| EXCEPTIONS | ||
| FGROUP_NOT_EXIST = 1 | ||
| . " SWY_EXIST_TASK_FGROUP | ||
ABAP code using 7.40 inline data declarations to call FM SWY_EXIST_TASK_FGROUP
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 AREA FROM RS38L INTO @DATA(ld_fgroup). | ||||
Search for further information about these or an SAP related objects