SAP CP_MC_OPR_SET Function Module for NOTRANSL: Setzen des Vorgangs als Objekt für folgende Nachrichten









CP_MC_OPR_SET is a standard cp mc opr 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 Vorgangs 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 opr set FM, simply by entering the name CP_MC_OPR_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_OPR_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_OPR_SET'"NOTRANSL: Setzen des Vorgangs als Objekt für folgende Nachrichten
EXPORTING
I_MANDT = "Client
* I_ECN = "Change Number
* I_DATE = "Key Date
I_PLNTY = "
I_PLNNR = "Task List Number
I_PLNAL = "Alternative task list
I_PLNFL = "Sequence
* I_PLNKN = "Activity node
* I_IDENT = "
I_VORNR = "Operation Number
I_LTXA1 = "Transaction Description

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_OPR_SET

I_MANDT - Client

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

I_ECN - Change Number

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

I_DATE - Key Date

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

I_PLNTY -

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

I_PLNNR - Task List Number

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

I_PLNAL - Alternative task list

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

I_PLNFL - Sequence

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

I_PLNKN - Activity node

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

I_IDENT -

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

I_VORNR - Operation Number

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

I_LTXA1 - Transaction Description

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

EXPORTING Parameters details for CP_MC_OPR_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_OPR_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.

DATA:
lv_i_mandt  TYPE OPR_CLASS_DATA-MANDT, "   
lv_e_lognumber  TYPE BALNRI-LOGNUMBER, "   
lv_message_object_not_set  TYPE BALNRI, "   
lv_i_ecn  TYPE OPR_CLASS_DATA-AENNR, "   
lv_i_date  TYPE OPR_CLASS_DATA-DATUV, "   
lv_i_plnty  TYPE OPR_CLASS_DATA-PLNTY, "   
lv_e_handle  TYPE BALLOGHNDL, "   
lv_object_not_supp_by_handler  TYPE BALLOGHNDL, "   
lv_i_plnnr  TYPE OPR_CLASS_DATA-PLNNR, "   
lv_loss_of_collected_messages  TYPE OPR_CLASS_DATA, "   
lv_i_plnal  TYPE OPR_CLASS_DATA-PLNAL, "   
lv_i_plnfl  TYPE OPR_CLASS_DATA-PLNFL, "   
lv_i_plnkn  TYPE OPR_CLASS_DATA-PLNKN, "   
lv_i_ident  TYPE OPR_CLASS_DATA-IDENT, "   
lv_i_vornr  TYPE OPR_CLASS_DATA-VORNR, "   
lv_i_ltxa1  TYPE OPR_CLASS_DATA-LTXA1. "   

  CALL FUNCTION 'CP_MC_OPR_SET'  "NOTRANSL: Setzen des Vorgangs als Objekt für folgende Nachrichten
    EXPORTING
         I_MANDT = lv_i_mandt
         I_ECN = lv_i_ecn
         I_DATE = lv_i_date
         I_PLNTY = lv_i_plnty
         I_PLNNR = lv_i_plnnr
         I_PLNAL = lv_i_plnal
         I_PLNFL = lv_i_plnfl
         I_PLNKN = lv_i_plnkn
         I_IDENT = lv_i_ident
         I_VORNR = lv_i_vornr
         I_LTXA1 = lv_i_ltxa1
    IMPORTING
         E_LOGNUMBER = lv_e_lognumber
         E_HANDLE = lv_e_handle
    EXCEPTIONS
        MESSAGE_OBJECT_NOT_SET = 1
        OBJECT_NOT_SUPP_BY_HANDLER = 2
        LOSS_OF_COLLECTED_MESSAGES = 3
. " CP_MC_OPR_SET




ABAP code using 7.40 inline data declarations to call FM CP_MC_OPR_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.

"SELECT single MANDT FROM OPR_CLASS_DATA INTO @DATA(ld_i_mandt).
 
"SELECT single LOGNUMBER FROM BALNRI INTO @DATA(ld_e_lognumber).
 
 
"SELECT single AENNR FROM OPR_CLASS_DATA INTO @DATA(ld_i_ecn).
 
"SELECT single DATUV FROM OPR_CLASS_DATA INTO @DATA(ld_i_date).
 
"SELECT single PLNTY FROM OPR_CLASS_DATA INTO @DATA(ld_i_plnty).
 
 
 
"SELECT single PLNNR FROM OPR_CLASS_DATA INTO @DATA(ld_i_plnnr).
 
 
"SELECT single PLNAL FROM OPR_CLASS_DATA INTO @DATA(ld_i_plnal).
 
"SELECT single PLNFL FROM OPR_CLASS_DATA INTO @DATA(ld_i_plnfl).
 
"SELECT single PLNKN FROM OPR_CLASS_DATA INTO @DATA(ld_i_plnkn).
 
"SELECT single IDENT FROM OPR_CLASS_DATA INTO @DATA(ld_i_ident).
 
"SELECT single VORNR FROM OPR_CLASS_DATA INTO @DATA(ld_i_vornr).
 
"SELECT single LTXA1 FROM OPR_CLASS_DATA INTO @DATA(ld_i_ltxa1).
 


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!