SAP CME_API_CHAR_CHANGE Function Module for CME Characteristic - Change
CME_API_CHAR_CHANGE is a standard cme api char change 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 Characteristic - Change 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 char change FM, simply by entering the name CME_API_CHAR_CHANGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CME_API_CHAR
Program Name: SAPLCME_API_CHAR
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function CME_API_CHAR_CHANGE 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_CHAR_CHANGE'"CME Characteristic - Change.
EXPORTING
* IS_KEY = "CME Characteristic -Key Fields-
* IT_DOCUMENTS = "CME Characteristic -Documents for Characteristic-
* IT_VALUES = "CME Characteristic -Values-
* IT_VALUE_TEXT = "CME Data Type -Texts for Values-
* IT_VALUE_DOCUMENTS = "CME Characteristic - Documents for Characteristic Value
* IT_REFERENCE = "CME Characteristic -Data Reference-
* IT_TEXT = "CME Characteristic -Short Texts-
* IT_EXTENSIONS = "CME Characteristic -Extensions-
* IT_EXTENSIONS_TEXTS = "CME Characteristic -Texts for Extensions-
* IS_DTYPE_KEY = "CME Data Type -Key Fields in Internal/External Format-
* I_GROUP = "CME Characteristic -Group-
* IT_STATUS = "CME Characteristic -Status of Characteristic-
* IS_CHANGE_ORDER = "CME Characteristic -Data Change Status-
* IS_ATTRIBUTES = "CME Characteristic -Global Attributes-
* IS_DTYPE_FORMAT = "CME Data Type: Format Fields
* IS_ADMIN_DATA = "CME Characteristic -Administrative Data-
* IS_PROCESS = "CME Char. - Bit String for Controlling Changes to Chars
IMPORTING
ES_KEY = "CME Characteristic -Key Fields-
TABLES
* ET_RETURN = "Messages
EXCEPTIONS
EX_ERROR = 1
IMPORTING Parameters details for CME_API_CHAR_CHANGE
IS_KEY - CME Characteristic -Key Fields-
Data type: CME_S_CHAR_KEY_INT_EXTOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_DOCUMENTS - CME Characteristic -Documents for Characteristic-
Data type: CME_T_OBJECT_DOCUMENTSOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_VALUES - CME Characteristic -Values-
Data type: CME_T_VALOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_VALUE_TEXT - CME Data Type -Texts for Values-
Data type: CME_T_VALUE_TEXTOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_VALUE_DOCUMENTS - CME Characteristic - Documents for Characteristic Value
Data type: CME_T_VALUE_DOCUMENTSOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_REFERENCE - CME Characteristic -Data Reference-
Data type: CME_T_CHAR_REFOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_TEXT - CME Characteristic -Short Texts-
Data type: CME_T_TEXTOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_EXTENSIONS - CME Characteristic -Extensions-
Data type: CME_T_EXTENSIONSOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_EXTENSIONS_TEXTS - CME Characteristic -Texts for Extensions-
Data type: CME_T_TEXT_EXTENSIONSOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_DTYPE_KEY - CME Data Type -Key Fields in Internal/External Format-
Data type: CME_S_DTYPE_KEY_INT_EXTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_GROUP - CME Characteristic -Group-
Data type: DML_GRPOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_STATUS - CME Characteristic -Status of Characteristic-
Data type: DML_T_STATUSOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_CHANGE_ORDER - CME Characteristic -Data Change Status-
Data type: DML_S_API_ECMOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_ATTRIBUTES - CME Characteristic -Global Attributes-
Data type: CME_S_CHAR_ATTROptional: Yes
Call by Reference: No ( called with pass by value option)
IS_DTYPE_FORMAT - CME Data Type: Format Fields
Data type: CME_S_DTYPE_FORMATOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_ADMIN_DATA - CME Characteristic -Administrative Data-
Data type: DML_S_ADMINOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_PROCESS - CME Char. - Bit String for Controlling Changes to Chars
Data type: CME_S_PROCESS_CHAR_CHANGEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CME_API_CHAR_CHANGE
ES_KEY - CME Characteristic -Key Fields-
Data type: CME_S_CHAR_KEY_INT_EXTOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CME_API_CHAR_CHANGE
ET_RETURN - Messages
Data type: BAPIRET2Optional: 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_CHAR_CHANGE 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_es_key | TYPE CME_S_CHAR_KEY_INT_EXT, " | |||
| lv_is_key | TYPE CME_S_CHAR_KEY_INT_EXT, " | |||
| lv_ex_error | TYPE CME_S_CHAR_KEY_INT_EXT, " | |||
| lt_et_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_it_documents | TYPE CME_T_OBJECT_DOCUMENTS, " | |||
| lv_it_values | TYPE CME_T_VAL, " | |||
| lv_it_value_text | TYPE CME_T_VALUE_TEXT, " | |||
| lv_it_value_documents | TYPE CME_T_VALUE_DOCUMENTS, " | |||
| lv_it_reference | TYPE CME_T_CHAR_REF, " | |||
| lv_it_text | TYPE CME_T_TEXT, " | |||
| lv_it_extensions | TYPE CME_T_EXTENSIONS, " | |||
| lv_it_extensions_texts | TYPE CME_T_TEXT_EXTENSIONS, " | |||
| lv_is_dtype_key | TYPE CME_S_DTYPE_KEY_INT_EXT, " | |||
| lv_i_group | TYPE DML_GRP, " | |||
| lv_it_status | TYPE DML_T_STATUS, " | |||
| lv_is_change_order | TYPE DML_S_API_ECM, " | |||
| lv_is_attributes | TYPE CME_S_CHAR_ATTR, " | |||
| lv_is_dtype_format | TYPE CME_S_DTYPE_FORMAT, " | |||
| lv_is_admin_data | TYPE DML_S_ADMIN, " | |||
| lv_is_process | TYPE CME_S_PROCESS_CHAR_CHANGE. " |
|   CALL FUNCTION 'CME_API_CHAR_CHANGE' "CME Characteristic - Change |
| EXPORTING | ||
| IS_KEY | = lv_is_key | |
| IT_DOCUMENTS | = lv_it_documents | |
| IT_VALUES | = lv_it_values | |
| IT_VALUE_TEXT | = lv_it_value_text | |
| IT_VALUE_DOCUMENTS | = lv_it_value_documents | |
| IT_REFERENCE | = lv_it_reference | |
| IT_TEXT | = lv_it_text | |
| IT_EXTENSIONS | = lv_it_extensions | |
| IT_EXTENSIONS_TEXTS | = lv_it_extensions_texts | |
| IS_DTYPE_KEY | = lv_is_dtype_key | |
| I_GROUP | = lv_i_group | |
| IT_STATUS | = lv_it_status | |
| IS_CHANGE_ORDER | = lv_is_change_order | |
| IS_ATTRIBUTES | = lv_is_attributes | |
| IS_DTYPE_FORMAT | = lv_is_dtype_format | |
| IS_ADMIN_DATA | = lv_is_admin_data | |
| IS_PROCESS | = lv_is_process | |
| IMPORTING | ||
| ES_KEY | = lv_es_key | |
| TABLES | ||
| ET_RETURN | = lt_et_return | |
| EXCEPTIONS | ||
| EX_ERROR = 1 | ||
| . " CME_API_CHAR_CHANGE | ||
ABAP code using 7.40 inline data declarations to call FM CME_API_CHAR_CHANGE
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