SAP TRINT_DELETE_COMM_KEYS Function Module for Internal: Delete Request/Task Object Keys for Object









TRINT_DELETE_COMM_KEYS is a standard trint delete comm keys SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Internal: Delete Request/Task Object Keys for Object 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 delete comm keys FM, simply by entering the name TRINT_DELETE_COMM_KEYS into the relevant SAP transaction such as SE37 or SE38.

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



Function TRINT_DELETE_COMM_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 'TRINT_DELETE_COMM_KEYS'"Internal: Delete Request/Task Object Keys for Object
EXPORTING
WI_E071 = "E071 Input (Master for WT_E071K Entries)
WI_TRKORR = "Number of Request/Task

TABLES
WT_E071K = "E071K entries to be deleted

EXCEPTIONS
E070_UPDATE_ERROR = 1 KEYS_PROTECTED = 2 ORDER_ALREADY_RELEASED = 3 UNALLOWED_ORDERTYP = 4 USER_NOT_OWNER = 5 WRONG_CLIENT = 6
.



IMPORTING Parameters details for TRINT_DELETE_COMM_KEYS

WI_E071 - E071 Input (Master for WT_E071K Entries)

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

WI_TRKORR - Number of Request/Task

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

TABLES Parameters details for TRINT_DELETE_COMM_KEYS

WT_E071K - E071K entries to be deleted

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

EXCEPTIONS details

E070_UPDATE_ERROR - Error when saving request/task header

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

KEYS_PROTECTED - Key deletion rejected; E071 master protected

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

ORDER_ALREADY_RELEASED - Request/task already released

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

UNALLOWED_ORDERTYP - Invalid request/task type

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

USER_NOT_OWNER - Request/task only modifiable by owner

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

WRONG_CLIENT - Editing in invalid client

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

Copy and paste ABAP code example for TRINT_DELETE_COMM_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_wi_e071  TYPE E071, "   
lt_wt_e071k  TYPE STANDARD TABLE OF E071K, "   
lv_e070_update_error  TYPE E071K, "   
lv_wi_trkorr  TYPE E070-TRKORR, "   
lv_keys_protected  TYPE E070, "   
lv_order_already_released  TYPE E070, "   
lv_unallowed_ordertyp  TYPE E070, "   
lv_user_not_owner  TYPE E070, "   
lv_wrong_client  TYPE E070. "   

  CALL FUNCTION 'TRINT_DELETE_COMM_KEYS'  "Internal: Delete Request/Task Object Keys for Object
    EXPORTING
         WI_E071 = lv_wi_e071
         WI_TRKORR = lv_wi_trkorr
    TABLES
         WT_E071K = lt_wt_e071k
    EXCEPTIONS
        E070_UPDATE_ERROR = 1
        KEYS_PROTECTED = 2
        ORDER_ALREADY_RELEASED = 3
        UNALLOWED_ORDERTYP = 4
        USER_NOT_OWNER = 5
        WRONG_CLIENT = 6
. " TRINT_DELETE_COMM_KEYS




ABAP code using 7.40 inline data declarations to call FM TRINT_DELETE_COMM_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.

 
 
 
"SELECT single TRKORR FROM E070 INTO @DATA(ld_wi_trkorr).
 
 
 
 
 
 


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!