SAP TMW_ACTIVATE_BCSET Function Module for









TMW_ACTIVATE_BCSET is a standard tmw activate bcset 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 activate bcset FM, simply by entering the name TMW_ACTIVATE_BCSET 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): Remote-Enabled
Update:



Function TMW_ACTIVATE_BCSET 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_ACTIVATE_BCSET'"
EXPORTING
PROFID = "
PROFTEXT = "
IT_TRANSFER_TAB = "
* TASK_NUMBER_SYST = "
TASK_NUMBER_CUST = "
* MSG_TAB_FLG = ' ' "

TABLES
* MSG_TAB = "

EXCEPTIONS
NO_AUTHORITY = 1 NO_BCSET = 2 WRONG_PARAMETERS = 3 NO_RFC_AUTHORITY = 4 RFC_FAILURE = 5 INTERNAL_ERROR = 6 BATCHJOB_ERROR = 7 BCSET_ACTIVATION_ERROR = 8
.



IMPORTING Parameters details for TMW_ACTIVATE_BCSET

PROFID -

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

PROFTEXT -

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

IT_TRANSFER_TAB -

Data type: STRING_TABLE
Optional: No
Call by Reference: No ( called with pass by value option)

TASK_NUMBER_SYST -

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

TASK_NUMBER_CUST -

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

MSG_TAB_FLG -

Data type: FLAG
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for TMW_ACTIVATE_BCSET

MSG_TAB -

Data type: BAPIRET1
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

NO_AUTHORITY -

Data type:
Optional: No
Call by Reference: Yes

NO_BCSET -

Data type:
Optional: No
Call by Reference: Yes

WRONG_PARAMETERS -

Data type:
Optional: No
Call by Reference: Yes

NO_RFC_AUTHORITY -

Data type:
Optional: No
Call by Reference: Yes

RFC_FAILURE -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

BATCHJOB_ERROR -

Data type:
Optional: No
Call by Reference: Yes

BCSET_ACTIVATION_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TMW_ACTIVATE_BCSET 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_profid  TYPE SCPRATTR-ID, "   
lt_msg_tab  TYPE STANDARD TABLE OF BAPIRET1, "   
lv_no_authority  TYPE BAPIRET1, "   
lv_no_bcset  TYPE BAPIRET1, "   
lv_proftext  TYPE SCPRTEXT-TEXT, "   
lv_it_transfer_tab  TYPE STRING_TABLE, "   
lv_wrong_parameters  TYPE STRING_TABLE, "   
lv_no_rfc_authority  TYPE STRING_TABLE, "   
lv_task_number_syst  TYPE E070-TRKORR, "   
lv_rfc_failure  TYPE E070, "   
lv_task_number_cust  TYPE E070-TRKORR, "   
lv_msg_tab_flg  TYPE FLAG, "   ' '
lv_internal_error  TYPE FLAG, "   
lv_batchjob_error  TYPE FLAG, "   
lv_bcset_activation_error  TYPE FLAG. "   

  CALL FUNCTION 'TMW_ACTIVATE_BCSET'  "
    EXPORTING
         PROFID = lv_profid
         PROFTEXT = lv_proftext
         IT_TRANSFER_TAB = lv_it_transfer_tab
         TASK_NUMBER_SYST = lv_task_number_syst
         TASK_NUMBER_CUST = lv_task_number_cust
         MSG_TAB_FLG = lv_msg_tab_flg
    TABLES
         MSG_TAB = lt_msg_tab
    EXCEPTIONS
        NO_AUTHORITY = 1
        NO_BCSET = 2
        WRONG_PARAMETERS = 3
        NO_RFC_AUTHORITY = 4
        RFC_FAILURE = 5
        INTERNAL_ERROR = 6
        BATCHJOB_ERROR = 7
        BCSET_ACTIVATION_ERROR = 8
. " TMW_ACTIVATE_BCSET




ABAP code using 7.40 inline data declarations to call FM TMW_ACTIVATE_BCSET

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 ID FROM SCPRATTR INTO @DATA(ld_profid).
 
 
 
 
"SELECT single TEXT FROM SCPRTEXT INTO @DATA(ld_proftext).
 
 
 
 
"SELECT single TRKORR FROM E070 INTO @DATA(ld_task_number_syst).
 
 
"SELECT single TRKORR FROM E070 INTO @DATA(ld_task_number_cust).
 
DATA(ld_msg_tab_flg) = ' '.
 
 
 
 


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!