SAP CNV_MBT_SUBPARAMS_SET Function Module for MBT PCL : set subactivity parameters

Search SAP Function Modules

CNV_MBT_SUBPARAMS_SET is a standard cnv mbt subparams set SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for MBT PCL : set subactivity parameters 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 cnv mbt subparams set FM, simply by entering the name CNV_MBT_SUBPARAMS_SET into the relevant SAP transaction such as SE37 or SE38.

Function Group: CNV_MBT_SUBACT
Program Name: SAPLCNV_MBT_SUBACT
Main Program: SAPLCNV_MBT_SUBACT
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function CNV_MBT_SUBPARAMS_SET 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 'CNV_MBT_SUBPARAMS_SET'"MBT PCL : set subactivity parameters
  EXPORTING
*  PACKID =  "
*  ACTIVITY_ID =  "
*  SUBACTIVITY_ID =  "
*  TASK_ID =  "
*  VARIANT =  "
*  GEN_FLAG =  "
*  ACTIVE = 'X' "

TABLES
*  T_IM_SUBACT_PARAMS =  "
*  T_IM_SUBACT_RSPARAMS =  "

EXCEPTIONS
   MODIFY_SUBPARAMS_ERROR = 1    CALLING_OF_FUNCTION_ERROR = 2    DELETE_SUBPARAMS_ERROR = 3 

.

IMPORTING Parameters details for CNV_MBT_SUBPARAMS_SET

PACKID -

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

ACTIVITY_ID -

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

SUBACTIVITY_ID -

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

TASK_ID -

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

VARIANT -

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

GEN_FLAG -

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

ACTIVE -

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

TABLES Parameters details for CNV_MBT_SUBPARAMS_SET

T_IM_SUBACT_PARAMS -

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

T_IM_SUBACT_RSPARAMS -

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

EXCEPTIONS details

MODIFY_SUBPARAMS_ERROR -

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

CALLING_OF_FUNCTION_ERROR -

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

DELETE_SUBPARAMS_ERROR -

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

Copy and paste ABAP code example for CNV_MBT_SUBPARAMS_SET 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.

ABAP code using 7.40 inline data declarations to call FM CNV_MBT_SUBPARAMS_SET

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