SAP TPMO_UNDO_VERSION Function Module for Cumulate translation performance data
TPMO_UNDO_VERSION is a standard tpmo undo version SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Cumulate translation performance data 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 tpmo undo version FM, simply by entering the name TPMO_UNDO_VERSION into the relevant SAP transaction such as SE37 or SE38.
Function Group: LXE_TPMO
Program Name: SAPLLXE_TPMO
Main Program: SAPLLXE_TPMO
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TPMO_UNDO_VERSION 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 'TPMO_UNDO_VERSION'"Cumulate translation performance data.
EXPORTING
VERSION = "Translation performance monitor version
TARGETLANG = "ISO Language ID
EXCEPTIONS
ENQUEUE_ERROR = 1 INVALID_VERSION = 2 UPDATE_ERROR = 3
IMPORTING Parameters details for TPMO_UNDO_VERSION
VERSION - Translation performance monitor version
Data type: TPMVERSIONOptional: No
Call by Reference: Yes
TARGETLANG - ISO Language ID
Data type: LXEISOLANGOptional: No
Call by Reference: Yes
EXCEPTIONS details
ENQUEUE_ERROR - Unable to enqueue version table
Data type:Optional: No
Call by Reference: Yes
INVALID_VERSION - Input parameter version does not exist
Data type:Optional: No
Call by Reference: Yes
UPDATE_ERROR - Unable to update versioning table
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for TPMO_UNDO_VERSION 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_version | TYPE TPMVERSION, " | |||
| lv_enqueue_error | TYPE TPMVERSION, " | |||
| lv_targetlang | TYPE LXEISOLANG, " | |||
| lv_invalid_version | TYPE LXEISOLANG, " | |||
| lv_update_error | TYPE LXEISOLANG. " |
|   CALL FUNCTION 'TPMO_UNDO_VERSION' "Cumulate translation performance data |
| EXPORTING | ||
| VERSION | = lv_version | |
| TARGETLANG | = lv_targetlang | |
| EXCEPTIONS | ||
| ENQUEUE_ERROR = 1 | ||
| INVALID_VERSION = 2 | ||
| UPDATE_ERROR = 3 | ||
| . " TPMO_UNDO_VERSION | ||
ABAP code using 7.40 inline data declarations to call FM TPMO_UNDO_VERSION
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