TPMO_STORE_STATS is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.
See here to view full function module documentation and code listing, simply by entering the name TPMO_STORE_STATS into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
LXE_TPMO
Released Date:
Not Released
Processing type: Normal fucntion module
CALL FUNCTION 'TPMO_STORE_STATS' "Store translation performance record
EXPORTING
sourcelang = " lxeisolang ISO Language ID
targetlang = " lxeisolang ISO Language ID
translator = " tpmtrans Translation Performance Monitor Translator
collname = " lxecollnam Collection Name
colltype = " lxecolltyp Collection Type
objtype = " lxeobjtype
worklist = " lxewlistid Worklist ID
domainname = " lxedomanam Domain name
domaintype = " lxedomatyp
customernr = " lxecustmnr Customer Number
line_stats = " lxesh_eval_counter_structure
word_stats = " lxesh_eval_counter_structure
EXCEPTIONS
INSERT_FAILURE = 1 " Record could not be inserted
ENQUEUE_ERROR = 2 " Unable to enqueue version table
UPDATE_FAILURE = 3 " Record could not be updated
. " TPMO_STORE_STATS
The ABAP code below is a full code listing to execute function module TPMO_STORE_STATS including all data declarations. The code uses 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 original method of declaring data variables up front. 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).
DATA(ld_sourcelang) = 'Check type of data required'.
DATA(ld_targetlang) = 'Check type of data required'.
DATA(ld_translator) = 'Check type of data required'.
DATA(ld_collname) = 'Check type of data required'.
DATA(ld_colltype) = 'Check type of data required'.
DATA(ld_objtype) = 'Check type of data required'.
DATA(ld_worklist) = 'Check type of data required'.
DATA(ld_domainname) = 'Check type of data required'.
DATA(ld_domaintype) = 'Check type of data required'.
DATA(ld_customernr) = 'Check type of data required'.
DATA(ld_line_stats) = 'Check type of data required'.
DATA(ld_word_stats) = 'Check type of data required'. . CALL FUNCTION 'TPMO_STORE_STATS' EXPORTING sourcelang = ld_sourcelang targetlang = ld_targetlang translator = ld_translator collname = ld_collname colltype = ld_colltype objtype = ld_objtype worklist = ld_worklist domainname = ld_domainname domaintype = ld_domaintype customernr = ld_customernr line_stats = ld_line_stats word_stats = ld_word_stats EXCEPTIONS INSERT_FAILURE = 1 ENQUEUE_ERROR = 2 UPDATE_FAILURE = 3 . " TPMO_STORE_STATS
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 3. "Exception "Add code for exception here ENDIF.
The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
| ld_sourcelang | TYPE LXEISOLANG , |
| ld_targetlang | TYPE LXEISOLANG , |
| ld_translator | TYPE TPMTRANS , |
| ld_collname | TYPE LXECOLLNAM , |
| ld_colltype | TYPE LXECOLLTYP , |
| ld_objtype | TYPE LXEOBJTYPE , |
| ld_worklist | TYPE LXEWLISTID , |
| ld_domainname | TYPE LXEDOMANAM , |
| ld_domaintype | TYPE LXEDOMATYP , |
| ld_customernr | TYPE LXECUSTMNR , |
| ld_line_stats | TYPE LXESH_EVAL_COUNTER_STRUCTURE , |
| ld_word_stats | TYPE LXESH_EVAL_COUNTER_STRUCTURE . |
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name TPMO_STORE_STATS or its description.