SAP L_TR_PP_CANCEL_CHECK Function Module for Check whether TR can be changed
L_TR_PP_CANCEL_CHECK is a standard l tr pp cancel check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check whether TR can be changed 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 l tr pp cancel check FM, simply by entering the name L_TR_PP_CANCEL_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: L02A
Program Name: SAPLL02A
Main Program: SAPLL02A
Appliation area: L
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function L_TR_PP_CANCEL_CHECK 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 'L_TR_PP_CANCEL_CHECK'"Check whether TR can be changed.
TABLES
T_LTBC = "Table with TR items to be changed
EXCEPTIONS
ITEM_ERROR = 1 TR_LOCKED = 2
TABLES Parameters details for L_TR_PP_CANCEL_CHECK
T_LTBC - Table with TR items to be changed
Data type: LTBCOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ITEM_ERROR - At least one item with error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TR_LOCKED - TR is locked
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for L_TR_PP_CANCEL_CHECK 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: | ||||
| lt_t_ltbc | TYPE STANDARD TABLE OF LTBC, " | |||
| lv_item_error | TYPE LTBC, " | |||
| lv_tr_locked | TYPE LTBC. " |
|   CALL FUNCTION 'L_TR_PP_CANCEL_CHECK' "Check whether TR can be changed |
| TABLES | ||
| T_LTBC | = lt_t_ltbc | |
| EXCEPTIONS | ||
| ITEM_ERROR = 1 | ||
| TR_LOCKED = 2 | ||
| . " L_TR_PP_CANCEL_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM L_TR_PP_CANCEL_CHECK
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