SAP G_SET_GET_INFO Function Module for Checks whether Set exists and Provides Information about Set
G_SET_GET_INFO is a standard g set get info SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Checks whether Set exists and Provides Information about 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 get info FM, simply by entering the name G_SET_GET_INFO 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_GET_INFO 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_GET_INFO'"Checks whether Set exists and Provides Information about Set.
EXPORTING
* CLASS = ' ' "Obsolete, do not use
* NO_SET_TITLE = ' ' "'X' --> Suppression of the title return
SETNAME = "Set ID
* TABLE = ' ' "Table for which set is used
* FIELDNAME = ' ' "Field for which set is used
* USE_TABLE_BUFFER = 'X' "'X' --> Buffered reading of set directory
* CLIENT = "Client of the Set
IMPORTING
INFO = "Information on the set
EXCEPTIONS
SET_NOT_FOUND = 1 ILLEGAL_FIELD_REPLACEMENT = 2
IMPORTING Parameters details for G_SET_GET_INFO
CLASS - Obsolete, do not use
Data type: RGSMH-CLASSDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
NO_SET_TITLE - 'X' --> Suppression of the title return
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 set is used
Data type: RGSMH-TABLEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
FIELDNAME - Field for which set is used
Data type: RGSMH-FIELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
USE_TABLE_BUFFER - 'X' --> Buffered reading of set directory
Data type: FLAGDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
CLIENT - Client of the Set
Data type: SY-MANDTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for G_SET_GET_INFO
INFO - Information on the set
Data type: SETINFOOptional: 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)
ILLEGAL_FIELD_REPLACEMENT - Set does not match field or table
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for G_SET_GET_INFO 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_info | TYPE SETINFO, " | |||
lv_class | TYPE RGSMH-CLASS, " SPACE | |||
lv_set_not_found | TYPE RGSMH, " | |||
lv_no_set_title | TYPE FLAG, " SPACE | |||
lv_illegal_field_replacement | TYPE FLAG, " | |||
lv_setname | TYPE C, " | |||
lv_table | TYPE RGSMH-TABLE, " SPACE | |||
lv_fieldname | TYPE RGSMH-FIELD, " SPACE | |||
lv_use_table_buffer | TYPE FLAG, " 'X' | |||
lv_client | TYPE SY-MANDT. " |
  CALL FUNCTION 'G_SET_GET_INFO' "Checks whether Set exists and Provides Information about Set |
EXPORTING | ||
CLASS | = lv_class | |
NO_SET_TITLE | = lv_no_set_title | |
SETNAME | = lv_setname | |
TABLE | = lv_table | |
FIELDNAME | = lv_fieldname | |
USE_TABLE_BUFFER | = lv_use_table_buffer | |
CLIENT | = lv_client | |
IMPORTING | ||
INFO | = lv_info | |
EXCEPTIONS | ||
SET_NOT_FOUND = 1 | ||
ILLEGAL_FIELD_REPLACEMENT = 2 | ||
. " G_SET_GET_INFO |
ABAP code using 7.40 inline data declarations to call FM G_SET_GET_INFO
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) | = ' '. | |||
DATA(ld_no_set_title) | = ' '. | |||
"SELECT single TABLE FROM RGSMH INTO @DATA(ld_table). | ||||
DATA(ld_table) | = ' '. | |||
"SELECT single FIELD FROM RGSMH INTO @DATA(ld_fieldname). | ||||
DATA(ld_fieldname) | = ' '. | |||
DATA(ld_use_table_buffer) | = 'X'. | |||
"SELECT single MANDT FROM SY INTO @DATA(ld_client). | ||||
Search for further information about these or an SAP related objects