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

Function G_SET_FIND_SET 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 'G_SET_FIND_SET'"Fins Set in a Set.
EXPORTING
CONTROL_BLOCK = "Number of control block (1-50)
INDEX = "Index of the set in buffer table (TMSB)
SETID = "Level of the sets (0=all)
* NO_VARIABLES_REPLACEMENT = ' ' "'X'--> variables not replaced by default sets
IMPORTING
HEADER = "Header information of the set
EXCEPTIONS
END_OF_SETS = 1 INVALID_INDEX = 2
IMPORTING Parameters details for G_SET_FIND_SET
CONTROL_BLOCK - Number of control block (1-50)
Data type: SY-TABIXOptional: No
Call by Reference: No ( called with pass by value option)
INDEX - Index of the set in buffer table (TMSB)
Data type: SY-TABIXOptional: No
Call by Reference: No ( called with pass by value option)
SETID - Level of the sets (0=all)
Data type: SETIDOptional: No
Call by Reference: No ( called with pass by value option)
NO_VARIABLES_REPLACEMENT - 'X'--> variables not replaced by default sets
Data type: FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for G_SET_FIND_SET
HEADER - Header information of the set
Data type: RGSMHOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
END_OF_SETS - No further set exists
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_INDEX - Set index is invalid
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for G_SET_FIND_SET 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_header | TYPE RGSMH, " | |||
| lv_end_of_sets | TYPE RGSMH, " | |||
| lv_control_block | TYPE SY-TABIX, " | |||
| lv_index | TYPE SY-TABIX, " | |||
| lv_invalid_index | TYPE SY, " | |||
| lv_setid | TYPE SETID, " | |||
| lv_no_variables_replacement | TYPE FLAG. " SPACE |
|   CALL FUNCTION 'G_SET_FIND_SET' "Fins Set in a Set |
| EXPORTING | ||
| CONTROL_BLOCK | = lv_control_block | |
| INDEX | = lv_index | |
| SETID | = lv_setid | |
| NO_VARIABLES_REPLACEMENT | = lv_no_variables_replacement | |
| IMPORTING | ||
| HEADER | = lv_header | |
| EXCEPTIONS | ||
| END_OF_SETS = 1 | ||
| INVALID_INDEX = 2 | ||
| . " G_SET_FIND_SET | ||
ABAP code using 7.40 inline data declarations to call FM G_SET_FIND_SET
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 TABIX FROM SY INTO @DATA(ld_control_block). | ||||
| "SELECT single TABIX FROM SY INTO @DATA(ld_index). | ||||
| DATA(ld_no_variables_replacement) | = ' '. | |||
Search for further information about these or an SAP related objects