SAP CP_MC_MTK_SET Function Module for NOTRANSL: Setzen des Plans als Objekt für folgende Nachrichten

Search SAP Function Modules

CP_MC_MTK_SET is a standard cp mc mtk 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 NOTRANSL: Setzen des Plans als Objekt für folgende Nachrichten 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 cp mc mtk set FM, simply by entering the name CP_MC_MTK_SET into the relevant SAP transaction such as SE37 or SE38.

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

Function CP_MC_MTK_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 'CP_MC_MTK_SET'"NOTRANSL: Setzen des Plans als Objekt für folgende Nachrichten
  EXPORTING
   I_MANDT =  "Client
   I_PLNTY =  "
   I_PLNNR =  "Task List Number
   I_PLNAL =  "Alternative task list
   I_MATNR =  "Material Number
   I_WERKS =  "Plant
*  I_ZKRIZ =  "Counter for additional criteria
*  I_VBELN =  "Sales Document
*  I_POSNR =  "Sales document item

 IMPORTING
   E_LOGNUMBER =  "
   E_HANDLE =  "Application Log: Log Handle

EXCEPTIONS
   MESSAGE_OBJECT_NOT_SET = 1    OBJECT_NOT_SUPP_BY_HANDLER = 2    LOSS_OF_COLLECTED_MESSAGES = 3 

.

IMPORTING Parameters details for CP_MC_MTK_SET

I_MANDT - Client

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

I_PLNTY -

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

I_PLNNR - Task List Number

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

I_PLNAL - Alternative task list

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

I_MATNR - Material Number

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

I_WERKS - Plant

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

I_ZKRIZ - Counter for additional criteria

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

I_VBELN - Sales Document

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

I_POSNR - Sales document item

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

EXPORTING Parameters details for CP_MC_MTK_SET

E_LOGNUMBER -

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

E_HANDLE - Application Log: Log Handle

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

EXCEPTIONS details

MESSAGE_OBJECT_NOT_SET -

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

OBJECT_NOT_SUPP_BY_HANDLER -

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

LOSS_OF_COLLECTED_MESSAGES -

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

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