SAP BCSET_ACTIVATE_TEMPLATE Function Module for









BCSET_ACTIVATE_TEMPLATE is a standard bcset activate template 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 bcset activate template FM, simply by entering the name BCSET_ACTIVATE_TEMPLATE into the relevant SAP transaction such as SE37 or SE38.

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



Function BCSET_ACTIVATE_TEMPLATE 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 'BCSET_ACTIVATE_TEMPLATE'"
EXPORTING
I_OBJECTNAME = "Object Name
I_OBJECTTYPE = "Object Type
I_ACTIVATION = "BC Set Activation
* I_COMPLETE_ONLY = ' ' "
* I_NO_CORRECTION = ' ' "
* I_NO_AUTHORITY_CHECK = ' ' "
* I_TEST_MODE = ' ' "
I_ORDER = "Request/Task

IMPORTING
E_RETURNCODE = "Return Code

EXCEPTIONS
NO_AUTHORITY = 1 FOREIGN_LOCK = 2 SHOW_ONLY = 3 INTERNAL_ERROR = 4
.



IMPORTING Parameters details for BCSET_ACTIVATE_TEMPLATE

I_OBJECTNAME - Object Name

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

I_OBJECTTYPE - Object Type

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

I_ACTIVATION - BC Set Activation

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

I_COMPLETE_ONLY -

Data type: BCSET_BOOL
Default: SPACE
Optional: No
Call by Reference: No ( called with pass by value option)

I_NO_CORRECTION -

Data type: BCSET_BOOL
Default: SPACE
Optional: No
Call by Reference: No ( called with pass by value option)

I_NO_AUTHORITY_CHECK -

Data type: BCSET_BOOL
Default: SPACE
Optional: No
Call by Reference: No ( called with pass by value option)

I_TEST_MODE -

Data type: BCSET_BOOL
Default: SPACE
Optional: No
Call by Reference: No ( called with pass by value option)

I_ORDER - Request/Task

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

EXPORTING Parameters details for BCSET_ACTIVATE_TEMPLATE

E_RETURNCODE - Return Code

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

EXCEPTIONS details

NO_AUTHORITY - No Authorization

Data type:
Optional: No
Call by Reference: Yes

FOREIGN_LOCK -

Data type:
Optional: No
Call by Reference: Yes

SHOW_ONLY - No changes allowed

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR - Internal Error

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BCSET_ACTIVATE_TEMPLATE 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_e_returncode  TYPE SY-SUBRC, "   
lv_i_objectname  TYPE OBJH-OBJECTNAME, "   
lv_no_authority  TYPE OBJH, "   
lv_foreign_lock  TYPE OBJH, "   
lv_i_objecttype  TYPE OBJH-OBJECTTYPE, "   
lv_show_only  TYPE OBJH, "   
lv_i_activation  TYPE IF_BCSET_ACTIVATION, "   
lv_internal_error  TYPE IF_BCSET_ACTIVATION, "   
lv_i_complete_only  TYPE BCSET_BOOL, "   SPACE
lv_i_no_correction  TYPE BCSET_BOOL, "   SPACE
lv_i_no_authority_check  TYPE BCSET_BOOL, "   SPACE
lv_i_test_mode  TYPE BCSET_BOOL, "   SPACE
lv_i_order  TYPE E070-TRKORR. "   

  CALL FUNCTION 'BCSET_ACTIVATE_TEMPLATE'  "
    EXPORTING
         I_OBJECTNAME = lv_i_objectname
         I_OBJECTTYPE = lv_i_objecttype
         I_ACTIVATION = lv_i_activation
         I_COMPLETE_ONLY = lv_i_complete_only
         I_NO_CORRECTION = lv_i_no_correction
         I_NO_AUTHORITY_CHECK = lv_i_no_authority_check
         I_TEST_MODE = lv_i_test_mode
         I_ORDER = lv_i_order
    IMPORTING
         E_RETURNCODE = lv_e_returncode
    EXCEPTIONS
        NO_AUTHORITY = 1
        FOREIGN_LOCK = 2
        SHOW_ONLY = 3
        INTERNAL_ERROR = 4
. " BCSET_ACTIVATE_TEMPLATE




ABAP code using 7.40 inline data declarations to call FM BCSET_ACTIVATE_TEMPLATE

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 SUBRC FROM SY INTO @DATA(ld_e_returncode).
 
"SELECT single OBJECTNAME FROM OBJH INTO @DATA(ld_i_objectname).
 
 
 
"SELECT single OBJECTTYPE FROM OBJH INTO @DATA(ld_i_objecttype).
 
 
 
 
DATA(ld_i_complete_only) = ' '.
 
DATA(ld_i_no_correction) = ' '.
 
DATA(ld_i_no_authority_check) = ' '.
 
DATA(ld_i_test_mode) = ' '.
 
"SELECT single TRKORR FROM E070 INTO @DATA(ld_i_order).
 


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!