SAP TRINT_GTABKEY_DEL_DLVUNIT Function Module for Delete GRTABKEY Component (Including Registrations)

Search SAP Function Modules

TRINT_GTABKEY_DEL_DLVUNIT is a standard trint gtabkey del dlvunit SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Delete GRTABKEY Component (Including Registrations) 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 trint gtabkey del dlvunit FM, simply by entering the name TRINT_GTABKEY_DEL_DLVUNIT into the relevant SAP transaction such as SE37 or SE38.

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

Function TRINT_GTABKEY_DEL_DLVUNIT 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 'TRINT_GTABKEY_DEL_DLVUNIT'"Delete GRTABKEY Component (Including Registrations)
  EXPORTING
   IV_CDLVUNIT =  "Software component
   IV_CRELEASE =  "R/3 Release
   IV_USERNAME =  "Last changed by
   WITH_REGISTRATIONS =  "Single-character indicator
*  IV_ARCHIVE = 'X' "Single-character indicator

EXCEPTIONS
   WRONG_CALL = 1    DLVUNIT_NOT_FOUND = 2    REGISTRATIONS_FOUND = 3    PERMISSION_DENIED = 4    ENQUEUE_FAILED = 5    GROUP_NOT_FOUND = 6 

.

IMPORTING Parameters details for TRINT_GTABKEY_DEL_DLVUNIT

IV_CDLVUNIT - Software component

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

IV_CRELEASE - R/3 Release

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

IV_USERNAME - Last changed by

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

WITH_REGISTRATIONS - Single-character indicator

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

IV_ARCHIVE - Single-character indicator

Data type: CHAR1
Default: 'X'
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

WRONG_CALL -

Data type:
Optional: No
Call by Reference: Yes

DLVUNIT_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

REGISTRATIONS_FOUND -

Data type:
Optional: No
Call by Reference: Yes

PERMISSION_DENIED -

Data type:
Optional: No
Call by Reference: Yes

ENQUEUE_FAILED -

Data type:
Optional: No
Call by Reference: Yes

GROUP_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TRINT_GTABKEY_DEL_DLVUNIT 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.

ABAP code using 7.40 inline data declarations to call FM TRINT_GTABKEY_DEL_DLVUNIT

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