SAP G_SET_GET_SETID_FROM_KEYS Function Module for
G_SET_GET_SETID_FROM_KEYS is a standard g set get setid from keys 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 g set get setid from keys FM, simply by entering the name G_SET_GET_SETID_FROM_KEYS into the relevant SAP transaction such as SE37 or SE38.
Function Group: GSAC
Program Name: SAPLGSAC
Main Program: SAPLGSAC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function G_SET_GET_SETID_FROM_KEYS 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_SETID_FROM_KEYS'".
EXPORTING
IM_SETCLASS = "Set Class
* IM_SUBCLASS = "Organizational Unit as Set Subclass
IM_SETNAME = "Set Name
IMPORTING
EX_SETID = "Identification of a Set
IMPORTING Parameters details for G_SET_GET_SETID_FROM_KEYS
IM_SETCLASS - Set Class
Data type: SETCLASSOptional: No
Call by Reference: Yes
IM_SUBCLASS - Organizational Unit as Set Subclass
Data type: SETSUBCLSOptional: Yes
Call by Reference: Yes
IM_SETNAME - Set Name
Data type: SETNAMENEWOptional: No
Call by Reference: Yes
EXPORTING Parameters details for G_SET_GET_SETID_FROM_KEYS
EX_SETID - Identification of a Set
Data type: SETIDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for G_SET_GET_SETID_FROM_KEYS 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_ex_setid | TYPE SETID, " | |||
| lv_im_setclass | TYPE SETCLASS, " | |||
| lv_im_subclass | TYPE SETSUBCLS, " | |||
| lv_im_setname | TYPE SETNAMENEW. " |
|   CALL FUNCTION 'G_SET_GET_SETID_FROM_KEYS' " |
| EXPORTING | ||
| IM_SETCLASS | = lv_im_setclass | |
| IM_SUBCLASS | = lv_im_subclass | |
| IM_SETNAME | = lv_im_setname | |
| IMPORTING | ||
| EX_SETID | = lv_ex_setid | |
| . " G_SET_GET_SETID_FROM_KEYS | ||
ABAP code using 7.40 inline data declarations to call FM G_SET_GET_SETID_FROM_KEYS
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.Search for further information about these or an SAP related objects