G_DELETE_SET SAP Function module

G_DELETE_SET is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name G_DELETE_SET into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: GSGF
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM G_DELETE_SET - G DELETE SET

CALL FUNCTION 'G_DELETE_SET' "
  EXPORTING
*   client = SPACE              " sy-mandt      Client
*   class =                     " rgsbs-class   Obsolete, Use Set ID in Parameter SET
*   no_commit_work =            " c             'X' Suppresses COMMIT WORK after the Deletion
    set =                       " c             Set ID
*   tab =                       " rgsbs-table   Obsolete, Use Set ID in Parameter SET
*   force_deletion =            " sy-datar      'X': Delete although used
  EXCEPTIONS
    NO_AUTHORITY = 1            "               No Authorization for Deleting the Set
    NOT_FOUND = 2               "               The Set does not exist
    SET_IS_USED = 3             "               Set is used (cannot be deleted)
    .  "  G_DELETE_SET

ABAP code example for Function Module G_DELETE_SET

The ABAP code below is a full code listing to execute function module G_DELETE_SET including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA(ld_client) = 'Check type of data required'.


DATA(ld_class) = some text here

DATA(ld_no_commit_work) = 'Check type of data required'.

DATA(ld_set) = 'Check type of data required'.


DATA(ld_tab) = some text here

DATA(ld_force_deletion) = 'some text here'.
.

CALL FUNCTION 'G_DELETE_SET'
  EXPORTING
*   client =                     ld_client
*   class =                      ld_class
*   no_commit_work =             ld_no_commit_work
    set =                        ld_set
*   tab =                        ld_tab
*   force_deletion =             ld_force_deletion
  EXCEPTIONS
    NO_AUTHORITY =               1
    NOT_FOUND =                  2
    SET_IS_USED =                3
    .  "  G_DELETE_SET

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_client
 
 TYPE SY-MANDT ,
ld_class
 
 TYPE RGSBS-CLASS ,
ld_no_commit_work
 
 TYPE C ,
ld_set
 
 TYPE C ,
ld_tab
 
 TYPE RGSBS-TABLE ,
ld_force_deletion
 
 TYPE SY-DATAR .


ld_client = 'Check type of data required'.

ld_class = some text here
ld_no_commit_work = 'Check type of data required'.
ld_set = 'Check type of data required'.

ld_tab = some text here
ld_force_deletion = 'some text here'.

SAP Documentation for FM G_DELETE_SET