SAP TRCM_LOGGING_TABLE_DELETE Function Module for Delete TR-CM logging table
TRCM_LOGGING_TABLE_DELETE is a standard trcm logging table delete 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 TR-CM logging table 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 trcm logging table delete FM, simply by entering the name TRCM_LOGGING_TABLE_DELETE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FDTL
Program Name: SAPLFDTL
Main Program: SAPLFDTL
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TRCM_LOGGING_TABLE_DELETE 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 'TRCM_LOGGING_TABLE_DELETE'"Delete TR-CM logging table.
EXPORTING
PI_HERKU = "
* PI_IDENT = "
EXCEPTIONS
DELETE_FAILED = 1
IMPORTING Parameters details for TRCM_LOGGING_TABLE_DELETE
PI_HERKU -
Data type: T243LS-HERKUOptional: No
Call by Reference: No ( called with pass by value option)
PI_IDENT -
Data type: T243LS-IDENTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DELETE_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TRCM_LOGGING_TABLE_DELETE 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_pi_herku | TYPE T243LS-HERKU, " | |||
| lv_delete_failed | TYPE T243LS, " | |||
| lv_pi_ident | TYPE T243LS-IDENT. " |
|   CALL FUNCTION 'TRCM_LOGGING_TABLE_DELETE' "Delete TR-CM logging table |
| EXPORTING | ||
| PI_HERKU | = lv_pi_herku | |
| PI_IDENT | = lv_pi_ident | |
| EXCEPTIONS | ||
| DELETE_FAILED = 1 | ||
| . " TRCM_LOGGING_TABLE_DELETE | ||
ABAP code using 7.40 inline data declarations to call FM TRCM_LOGGING_TABLE_DELETE
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 HERKU FROM T243LS INTO @DATA(ld_pi_herku). | ||||
| "SELECT single IDENT FROM T243LS INTO @DATA(ld_pi_ident). | ||||
Search for further information about these or an SAP related objects