SAP CLMM_EXCHANGE_CHARACT Function Module for









CLMM_EXCHANGE_CHARACT is a standard clmm exchange charact 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 clmm exchange charact FM, simply by entering the name CLMM_EXCHANGE_CHARACT into the relevant SAP transaction such as SE37 or SE38.

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



Function CLMM_EXCHANGE_CHARACT 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 'CLMM_EXCHANGE_CHARACT'"
EXPORTING
CLASS_NAME = "Class Number
CLASS_TYPE = "Class Type
CHARACT_OLD = "Internal Characteristic
CHARACT_NEW = "Internal Characteristic
* KEY_DATE = "Valid-From Date
* CHANGE_NUMBER = "Change Number
* NEW_LOG = 'X' "Log Control - See Documentation

EXCEPTIONS
CLASS_HAS_SUBCLASSES = 1 CLASS_HAS_NO_OBJECTS = 2 NEW_CHARACT_NOT_INSERTED = 3 OLD_CHARACT_NOT_DELETED = 4 CHANGES_NOT_SAVED = 5 INVALID_FORMAT_CHANGE = 6
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLCLMMD_001 Selection of Objects for Mass Processing

IMPORTING Parameters details for CLMM_EXCHANGE_CHARACT

CLASS_NAME - Class Number

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

CLASS_TYPE - Class Type

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

CHARACT_OLD - Internal Characteristic

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

CHARACT_NEW - Internal Characteristic

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

KEY_DATE - Valid-From Date

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

CHANGE_NUMBER - Change Number

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

NEW_LOG - Log Control - See Documentation

Data type: FLAG
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

CLASS_HAS_SUBCLASSES -

Data type:
Optional: No
Call by Reference: Yes

CLASS_HAS_NO_OBJECTS -

Data type:
Optional: No
Call by Reference: Yes

NEW_CHARACT_NOT_INSERTED -

Data type:
Optional: No
Call by Reference: Yes

OLD_CHARACT_NOT_DELETED -

Data type:
Optional: No
Call by Reference: Yes

CHANGES_NOT_SAVED -

Data type:
Optional: No
Call by Reference: Yes

INVALID_FORMAT_CHANGE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CLMM_EXCHANGE_CHARACT 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_class_name  TYPE KLASSE_D, "   
lv_class_has_subclasses  TYPE KLASSE_D, "   
lv_class_type  TYPE KLASSENART, "   
lv_class_has_no_objects  TYPE KLASSENART, "   
lv_charact_old  TYPE ATINN, "   
lv_new_charact_not_inserted  TYPE ATINN, "   
lv_charact_new  TYPE ATINN, "   
lv_old_charact_not_deleted  TYPE ATINN, "   
lv_key_date  TYPE DATUV, "   
lv_changes_not_saved  TYPE DATUV, "   
lv_change_number  TYPE AENNR, "   
lv_invalid_format_change  TYPE AENNR, "   
lv_new_log  TYPE FLAG. "   'X'

  CALL FUNCTION 'CLMM_EXCHANGE_CHARACT'  "
    EXPORTING
         CLASS_NAME = lv_class_name
         CLASS_TYPE = lv_class_type
         CHARACT_OLD = lv_charact_old
         CHARACT_NEW = lv_charact_new
         KEY_DATE = lv_key_date
         CHANGE_NUMBER = lv_change_number
         NEW_LOG = lv_new_log
    EXCEPTIONS
        CLASS_HAS_SUBCLASSES = 1
        CLASS_HAS_NO_OBJECTS = 2
        NEW_CHARACT_NOT_INSERTED = 3
        OLD_CHARACT_NOT_DELETED = 4
        CHANGES_NOT_SAVED = 5
        INVALID_FORMAT_CHANGE = 6
. " CLMM_EXCHANGE_CHARACT




ABAP code using 7.40 inline data declarations to call FM CLMM_EXCHANGE_CHARACT

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.

 
 
 
 
 
 
 
 
 
 
 
 
DATA(ld_new_log) = 'X'.
 


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!