SAP CME_API_DTYPE_MAKE_NEW_VERSION Function Module for CME Data Type - Create New Version of Data Type

Search SAP Function Modules

CME_API_DTYPE_MAKE_NEW_VERSION is a standard cme api dtype make new version SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for CME Data Type - Create New Version of Data Type 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 cme api dtype make new version FM, simply by entering the name CME_API_DTYPE_MAKE_NEW_VERSION into the relevant SAP transaction such as SE37 or SE38.

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

Function CME_API_DTYPE_MAKE_NEW_VERSION 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 'CME_API_DTYPE_MAKE_NEW_VERSION'"CME Data Type - Create New Version of Data Type
  EXPORTING
*  IS_KEY =  "CME Data Type -Key Fields in Internal/External Format-
*  IS_CHANGE_ORDER =  "Data for Change State
*  I_NEW_VERSION =  "New Version of Characteristic

 IMPORTING
   ES_KEY =  "CME Data Type -Key Fields in Internal/External Format-

TABLES
*  ET_RETURN =  "Messages

EXCEPTIONS
   EX_ERROR = 1 

.

IMPORTING Parameters details for CME_API_DTYPE_MAKE_NEW_VERSION

IS_KEY - CME Data Type -Key Fields in Internal/External Format-

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

IS_CHANGE_ORDER - Data for Change State

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

I_NEW_VERSION - New Version of Characteristic

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

EXPORTING Parameters details for CME_API_DTYPE_MAKE_NEW_VERSION

ES_KEY - CME Data Type -Key Fields in Internal/External Format-

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

TABLES Parameters details for CME_API_DTYPE_MAKE_NEW_VERSION

ET_RETURN - Messages

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

EXCEPTIONS details

EX_ERROR - An error has occurred

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

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

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