SAP G_DELETE_SET Function Module for









G_DELETE_SET is a standard g delete set 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 delete set FM, simply by entering the name G_DELETE_SET into the relevant SAP transaction such as SE37 or SE38.

Function Group: GSGF
Program Name: SAPLGSGF
Main Program:
Appliation area: G
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function G_DELETE_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_DELETE_SET'"
EXPORTING
* CLIENT = ' ' "Client
* CLASS = "Obsolete, Use Set ID in Parameter SET
* NO_COMMIT_WORK = "'X' Suppresses COMMIT WORK after the Deletion
SET = "Set ID
* TAB = "Obsolete, Use Set ID in Parameter SET
* FORCE_DELETION = "'X': Delete although used

EXCEPTIONS
NO_AUTHORITY = 1 NOT_FOUND = 2 SET_IS_USED = 3
.



IMPORTING Parameters details for G_DELETE_SET

CLIENT - Client

Data type: SY-MANDT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

CLASS - Obsolete, Use Set ID in Parameter SET

Data type: RGSBS-CLASS
Optional: Yes
Call by Reference: No ( called with pass by value option)

NO_COMMIT_WORK - 'X' Suppresses COMMIT WORK after the Deletion

Data type: C
Optional: Yes
Call by Reference: No ( called with pass by value option)

SET - Set ID

Data type: C
Optional: No
Call by Reference: No ( called with pass by value option)

TAB - Obsolete, Use Set ID in Parameter SET

Data type: RGSBS-TABLE
Optional: Yes
Call by Reference: No ( called with pass by value option)

FORCE_DELETION - 'X': Delete although used

Data type: SY-DATAR
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

NO_AUTHORITY - No Authorization for Deleting the Set

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NOT_FOUND - The Set does not exist

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

SET_IS_USED - Set is used (cannot be deleted)

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for G_DELETE_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_client  TYPE SY-MANDT, "   SPACE
lv_no_authority  TYPE SY, "   
lv_class  TYPE RGSBS-CLASS, "   
lv_not_found  TYPE RGSBS, "   
lv_set_is_used  TYPE RGSBS, "   
lv_no_commit_work  TYPE C, "   
lv_set  TYPE C, "   
lv_tab  TYPE RGSBS-TABLE, "   
lv_force_deletion  TYPE SY-DATAR. "   

  CALL FUNCTION 'G_DELETE_SET'  "
    EXPORTING
         CLIENT = lv_client
         CLASS = lv_class
         NO_COMMIT_WORK = lv_no_commit_work
         SET = lv_set
         TAB = lv_tab
         FORCE_DELETION = lv_force_deletion
    EXCEPTIONS
        NO_AUTHORITY = 1
        NOT_FOUND = 2
        SET_IS_USED = 3
. " G_DELETE_SET




ABAP code using 7.40 inline data declarations to call FM G_DELETE_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 MANDT FROM SY INTO @DATA(ld_client).
DATA(ld_client) = ' '.
 
 
"SELECT single CLASS FROM RGSBS INTO @DATA(ld_class).
 
 
 
 
 
"SELECT single TABLE FROM RGSBS INTO @DATA(ld_tab).
 
"SELECT single DATAR FROM SY INTO @DATA(ld_force_deletion).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!