SAP TMW_COPY_COMM Function Module for









TMW_COPY_COMM is a standard tmw copy comm SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 tmw copy comm FM, simply by entering the name TMW_COPY_COMM into the relevant SAP transaction such as SE37 or SE38.

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



Function TMW_COPY_COMM 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 'TMW_COPY_COMM'"
EXPORTING
* IV_DIALOG = 'X' "
IV_TRKORR_TO = "

TABLES
IT_OBJECT_LIST = "
IT_OBJECT_LIST_KEY = "

EXCEPTIONS
DB_ACCESS_ERROR = 1 OBJECT_NOT_PATCHABLE = 10 WRONG_CLIENT = 11 GENERAL_FAILURE = 12 TRKORR_FROM_NOT_EXIST = 2 NO_AUTHORIZATION = 3 TRKORR_TO_LOCKED = 4 TRKORR_TO_IS_REPAIR = 5 TRKORR_TO_NOT_EXIST = 6 TRKORR_TO_RELEASED = 7 USER_NOT_OWNER = 8 WRONG_CATEGORY = 9
.



IMPORTING Parameters details for TMW_COPY_COMM

IV_DIALOG -

Data type: TRPARI-W_DIALOG
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_TRKORR_TO -

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

TABLES Parameters details for TMW_COPY_COMM

IT_OBJECT_LIST -

Data type: E071
Optional: No
Call by Reference: Yes

IT_OBJECT_LIST_KEY -

Data type: E071K
Optional: No
Call by Reference: Yes

EXCEPTIONS details

DB_ACCESS_ERROR -

Data type:
Optional: No
Call by Reference: Yes

OBJECT_NOT_PATCHABLE -

Data type:
Optional: No
Call by Reference: Yes

WRONG_CLIENT -

Data type:
Optional: No
Call by Reference: Yes

GENERAL_FAILURE -

Data type:
Optional: No
Call by Reference: Yes

TRKORR_FROM_NOT_EXIST -

Data type:
Optional: No
Call by Reference: Yes

NO_AUTHORIZATION -

Data type:
Optional: No
Call by Reference: Yes

TRKORR_TO_LOCKED -

Data type:
Optional: No
Call by Reference: Yes

TRKORR_TO_IS_REPAIR -

Data type:
Optional: No
Call by Reference: Yes

TRKORR_TO_NOT_EXIST -

Data type:
Optional: No
Call by Reference: Yes

TRKORR_TO_RELEASED -

Data type:
Optional: No
Call by Reference: Yes

USER_NOT_OWNER -

Data type:
Optional: No
Call by Reference: Yes

WRONG_CATEGORY -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TMW_COPY_COMM 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_iv_dialog  TYPE TRPARI-W_DIALOG, "   'X'
lt_it_object_list  TYPE STANDARD TABLE OF E071, "   
lv_db_access_error  TYPE E071, "   
lv_object_not_patchable  TYPE E071, "   
lv_wrong_client  TYPE E071, "   
lv_general_failure  TYPE E071, "   
lv_iv_trkorr_to  TYPE E070-TRKORR, "   
lt_it_object_list_key  TYPE STANDARD TABLE OF E071K, "   
lv_trkorr_from_not_exist  TYPE E071K, "   
lv_no_authorization  TYPE E071K, "   
lv_trkorr_to_locked  TYPE E071K, "   
lv_trkorr_to_is_repair  TYPE E071K, "   
lv_trkorr_to_not_exist  TYPE E071K, "   
lv_trkorr_to_released  TYPE E071K, "   
lv_user_not_owner  TYPE E071K, "   
lv_wrong_category  TYPE E071K. "   

  CALL FUNCTION 'TMW_COPY_COMM'  "
    EXPORTING
         IV_DIALOG = lv_iv_dialog
         IV_TRKORR_TO = lv_iv_trkorr_to
    TABLES
         IT_OBJECT_LIST = lt_it_object_list
         IT_OBJECT_LIST_KEY = lt_it_object_list_key
    EXCEPTIONS
        DB_ACCESS_ERROR = 1
        OBJECT_NOT_PATCHABLE = 10
        WRONG_CLIENT = 11
        GENERAL_FAILURE = 12
        TRKORR_FROM_NOT_EXIST = 2
        NO_AUTHORIZATION = 3
        TRKORR_TO_LOCKED = 4
        TRKORR_TO_IS_REPAIR = 5
        TRKORR_TO_NOT_EXIST = 6
        TRKORR_TO_RELEASED = 7
        USER_NOT_OWNER = 8
        WRONG_CATEGORY = 9
. " TMW_COPY_COMM




ABAP code using 7.40 inline data declarations to call FM TMW_COPY_COMM

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 W_DIALOG FROM TRPARI INTO @DATA(ld_iv_dialog).
DATA(ld_iv_dialog) = 'X'.
 
 
 
 
 
 
"SELECT single TRKORR FROM E070 INTO @DATA(ld_iv_trkorr_to).
 
 
 
 
 
 
 
 
 
 


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!