SAP CNV_MBT_PACK_MERGE_ACT Function Module for Function Mod. for Merging Activities of selected IS









CNV_MBT_PACK_MERGE_ACT is a standard cnv mbt pack merge act SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Function Mod. for Merging Activities of selected IS 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 pack merge act FM, simply by entering the name CNV_MBT_PACK_MERGE_ACT into the relevant SAP transaction such as SE37 or SE38.

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



Function CNV_MBT_PACK_MERGE_ACT 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_PACK_MERGE_ACT'"Function Mod. for Merging Activities of selected IS
EXPORTING
IM_PACKID = "Package Number to Specify CMIS and TDMS Packages
IM_EXTPACKID = "Package Number to Specify CMIS and TDMS Packages
IM_CLIENT = "Client
IM_OBJID = "Object identification
IM_MODE = "Single-character flag

IMPORTING
EX_ALREADY_EXECUTED = "
EX_EXEC_ACTIVITY = "Unique ID for all activities to be executed

EXCEPTIONS
INVALID_CALL = 1 INVALID_VARIANT = 2 OPERATION_FAILED = 3 VARIANT_NOT_FOUND = 4
.



IMPORTING Parameters details for CNV_MBT_PACK_MERGE_ACT

IM_PACKID - Package Number to Specify CMIS and TDMS Packages

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

IM_EXTPACKID - Package Number to Specify CMIS and TDMS Packages

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

IM_CLIENT - Client

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

IM_OBJID - Object identification

Data type: CNVMBTCOPYC-COPY_VARIANT
Optional: No
Call by Reference: Yes

IM_MODE - Single-character flag

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

EXPORTING Parameters details for CNV_MBT_PACK_MERGE_ACT

EX_ALREADY_EXECUTED -

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

EX_EXEC_ACTIVITY - Unique ID for all activities to be executed

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

EXCEPTIONS details

INVALID_CALL -

Data type:
Optional: No
Call by Reference: Yes

INVALID_VARIANT -

Data type:
Optional: No
Call by Reference: Yes

OPERATION_FAILED -

Data type:
Optional: No
Call by Reference: Yes

VARIANT_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CNV_MBT_PACK_MERGE_ACT 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_im_packid  TYPE CNV_MBT_PACKID, "   
lv_invalid_call  TYPE CNV_MBT_PACKID, "   
lv_ex_already_executed  TYPE C, "   
lv_im_extpackid  TYPE CNV_MBT_EXT_PACKID, "   
lv_invalid_variant  TYPE CNV_MBT_EXT_PACKID, "   
lv_ex_exec_activity  TYPE CNV_MBT_ACTIVITY, "   
lv_im_client  TYPE MANDT, "   
lv_operation_failed  TYPE MANDT, "   
lv_im_objid  TYPE CNVMBTCOPYC-COPY_VARIANT, "   
lv_variant_not_found  TYPE CNVMBTCOPYC, "   
lv_im_mode  TYPE CNVMBTMODIF. "   

  CALL FUNCTION 'CNV_MBT_PACK_MERGE_ACT'  "Function Mod. for Merging Activities of selected IS
    EXPORTING
         IM_PACKID = lv_im_packid
         IM_EXTPACKID = lv_im_extpackid
         IM_CLIENT = lv_im_client
         IM_OBJID = lv_im_objid
         IM_MODE = lv_im_mode
    IMPORTING
         EX_ALREADY_EXECUTED = lv_ex_already_executed
         EX_EXEC_ACTIVITY = lv_ex_exec_activity
    EXCEPTIONS
        INVALID_CALL = 1
        INVALID_VARIANT = 2
        OPERATION_FAILED = 3
        VARIANT_NOT_FOUND = 4
. " CNV_MBT_PACK_MERGE_ACT




ABAP code using 7.40 inline data declarations to call FM CNV_MBT_PACK_MERGE_ACT

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 COPY_VARIANT FROM CNVMBTCOPYC INTO @DATA(ld_im_objid).
 
 
 


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!