SAP MDT_COPLAN_CALL Function Module for









MDT_COPLAN_CALL is a standard mdt coplan call 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 mdt coplan call FM, simply by entering the name MDT_COPLAN_CALL into the relevant SAP transaction such as SE37 or SE38.

Function Group: RHMWBRW
Program Name: SAPLRHMWBRW
Main Program: SAPLRHMWBRW
Appliation area: H
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function MDT_COPLAN_CALL 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 'MDT_COPLAN_CALL'"
EXPORTING
ACT_FCODE = "
ACT_KOKRS = "
* ACT_USER = SY-UNAME "

TABLES
* COSTCENTER = "
.



IMPORTING Parameters details for MDT_COPLAN_CALL

ACT_FCODE -

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

ACT_KOKRS -

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

ACT_USER -

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

TABLES Parameters details for MDT_COPLAN_CALL

COSTCENTER -

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

Copy and paste ABAP code example for MDT_COPLAN_CALL 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_act_fcode  TYPE COMDTPLAN-FCODE, "   
lt_costcenter  TYPE STANDARD TABLE OF PKEYK, "   
lv_act_kokrs  TYPE PKEYK-KOKRS, "   
lv_act_user  TYPE SY-UNAME. "   SY-UNAME

  CALL FUNCTION 'MDT_COPLAN_CALL'  "
    EXPORTING
         ACT_FCODE = lv_act_fcode
         ACT_KOKRS = lv_act_kokrs
         ACT_USER = lv_act_user
    TABLES
         COSTCENTER = lt_costcenter
. " MDT_COPLAN_CALL




ABAP code using 7.40 inline data declarations to call FM MDT_COPLAN_CALL

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 FCODE FROM COMDTPLAN INTO @DATA(ld_act_fcode).
 
 
"SELECT single KOKRS FROM PKEYK INTO @DATA(ld_act_kokrs).
 
"SELECT single UNAME FROM SY INTO @DATA(ld_act_user).
DATA(ld_act_user) = SY-UNAME.
 


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!