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

Function G_SET_INSERT 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_INSERT'"Import a set into the work area of the set manager.
EXPORTING
* CLASS = ' ' "Obsolete, use ID in parameter SETNAME!
* DATE_TO = "
* MAINTENANCE = ' ' "'X' for reading, for maintenance transaction
* NO_TITLES = ' ' "'X' for suppressing the short descriptions
SETNAME = "Set ID
* TABLE = ' ' "Table for which the set is to be used
* FIELDNAME = ' ' "Field for which the set is to be used
* CLIENT = SY-MANDT "Client of the set
* FORCE_INSERT = ' ' "'X' to reread a set already read
* DATE_FROM = "
IMPORTING
HEADER = "Header information of the set
INDEX = "Index of the set in buffer table (TMSB)
EXCEPTIONS
SET_NOT_FOUND = 1
IMPORTING Parameters details for G_SET_INSERT
CLASS - Obsolete, use ID in parameter SETNAME!
Data type: RGSMH-CLASSDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
DATE_TO -
Data type: DATBIOptional: Yes
Call by Reference: Yes
MAINTENANCE - 'X' for reading, for maintenance transaction
Data type: FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
NO_TITLES - 'X' for suppressing the short descriptions
Data type: FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
SETNAME - Set ID
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
TABLE - Table for which the set is to be used
Data type: RGSMH-TABLEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
FIELDNAME - Field for which the set is to be used
Data type: RGSMH-FIELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
CLIENT - Client of the set
Data type: SY-MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
FORCE_INSERT - 'X' to reread a set already read
Data type: FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
DATE_FROM -
Data type: DATABOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for G_SET_INSERT
HEADER - Header information of the set
Data type: RGSMHOptional: 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)
EXCEPTIONS details
SET_NOT_FOUND - Set does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for G_SET_INSERT 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_class | TYPE RGSMH-CLASS, " SPACE | |||
| lv_header | TYPE RGSMH, " | |||
| lv_set_not_found | TYPE RGSMH, " | |||
| lv_date_to | TYPE DATBI, " | |||
| lv_index | TYPE SY-TABIX, " | |||
| lv_maintenance | TYPE FLAG, " SPACE | |||
| lv_no_titles | TYPE FLAG, " SPACE | |||
| lv_setname | TYPE C, " | |||
| lv_table | TYPE RGSMH-TABLE, " SPACE | |||
| lv_fieldname | TYPE RGSMH-FIELD, " SPACE | |||
| lv_client | TYPE SY-MANDT, " SY-MANDT | |||
| lv_force_insert | TYPE FLAG, " SPACE | |||
| lv_date_from | TYPE DATAB. " |
|   CALL FUNCTION 'G_SET_INSERT' "Import a set into the work area of the set manager |
| EXPORTING | ||
| CLASS | = lv_class | |
| DATE_TO | = lv_date_to | |
| MAINTENANCE | = lv_maintenance | |
| NO_TITLES | = lv_no_titles | |
| SETNAME | = lv_setname | |
| TABLE | = lv_table | |
| FIELDNAME | = lv_fieldname | |
| CLIENT | = lv_client | |
| FORCE_INSERT | = lv_force_insert | |
| DATE_FROM | = lv_date_from | |
| IMPORTING | ||
| HEADER | = lv_header | |
| INDEX | = lv_index | |
| EXCEPTIONS | ||
| SET_NOT_FOUND = 1 | ||
| . " G_SET_INSERT | ||
ABAP code using 7.40 inline data declarations to call FM G_SET_INSERT
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 CLASS FROM RGSMH INTO @DATA(ld_class). | ||||
| DATA(ld_class) | = ' '. | |||
| "SELECT single TABIX FROM SY INTO @DATA(ld_index). | ||||
| DATA(ld_maintenance) | = ' '. | |||
| DATA(ld_no_titles) | = ' '. | |||
| "SELECT single TABLE FROM RGSMH INTO @DATA(ld_table). | ||||
| DATA(ld_table) | = ' '. | |||
| "SELECT single FIELD FROM RGSMH INTO @DATA(ld_fieldname). | ||||
| DATA(ld_fieldname) | = ' '. | |||
| "SELECT single MANDT FROM SY INTO @DATA(ld_client). | ||||
| DATA(ld_client) | = SY-MANDT. | |||
| DATA(ld_force_insert) | = ' '. | |||
Search for further information about these or an SAP related objects