SAP CN_BT_MLST_COPY Function Module for NOTRANSL: Kopieren der Meilensteinzuordnungen eines Vorganges

Search SAP Function Modules

CN_BT_MLST_COPY is a standard cn bt mlst copy 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: Kopieren der Meilensteinzuordnungen eines Vorganges 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 cn bt mlst copy FM, simply by entering the name CN_BT_MLST_COPY into the relevant SAP transaction such as SE37 or SE38.

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

Function CN_BT_MLST_COPY 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 'CN_BT_MLST_COPY'"NOTRANSL: Kopieren der Meilensteinzuordnungen eines Vorganges
  EXPORTING
*  AENNR = ' ' "Change Number
   PLNAL_OLD =  "Alternative to a standard network
   PLNKN_OLD =  "Number of the task list node
   DATUV =  "Valid-From Date
*  VORNR = ' ' "Activity number in network and standard network
   PLNTY_NEW =  "Standard network type
   PLNNR_NEW =  "Standard network number
   PLNAL_NEW =  "Alternative to a standard network
   PLNKN_NEW =  "Number of the task list node
   PLNTY_OLD =  "Standard network type
   PLNNR_OLD =  "Standard network number

TABLES
   MLSTD_EXP =  "Milestone I/O Table

.

IMPORTING Parameters details for CN_BT_MLST_COPY

AENNR - Change Number

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

PLNAL_OLD - Alternative to a standard network

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

PLNKN_OLD - Number of the task list node

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

DATUV - Valid-From Date

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

VORNR - Activity number in network and standard network

Data type: MLSTD-SN_VORNR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

PLNTY_NEW - Standard network type

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

PLNNR_NEW - Standard network number

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

PLNAL_NEW - Alternative to a standard network

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

PLNKN_NEW - Number of the task list node

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

PLNTY_OLD - Standard network type

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

PLNNR_OLD - Standard network number

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

TABLES Parameters details for CN_BT_MLST_COPY

MLSTD_EXP - Milestone I/O Table

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

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

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