SAP CLMO_CLASS_OBJECT_MAINTAIN Function Module for Maintain Classes and Similar Objects
CLMO_CLASS_OBJECT_MAINTAIN is a standard clmo class object maintain SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Maintain Classes and Similar Objects 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 clmo class object maintain FM, simply by entering the name CLMO_CLASS_OBJECT_MAINTAIN into the relevant SAP transaction such as SE37 or SE38.
Function Group: CLMO
Program Name: SAPLCLMO
Main Program: SAPLCLMO
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CLMO_CLASS_OBJECT_MAINTAIN 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 'CLMO_CLASS_OBJECT_MAINTAIN'"Maintain Classes and Similar Objects.
EXPORTING
ACTIVITY = "Activity 0,1,2,3 Create/Change/Display/Delete
* SKIP = "No Change of Specified Class is Allowed
* CLASSTYPE = "Class Type
* CLASSNAME = "Class
* OBJECTNAME = "Name of Object (Not Class)
* RETAILTYPE = "SAP for Retail Indicator (0, 1, 2, 3)
* CALL = "Internal Use: Do Not Fill
* CLASS_AREA = "Internal Use: Do Not Fill
* CHANGENUMBER = ' ' "Change Number
* KEY_DATE = SY-DATUM "Date
IMPORTING
FUNCTION_CODE = "Last Function Code
NO_CHANGES = "No Changes to be Saved
E_ACTIVITY = "New Activity
EXCEPTIONS
RETAILTYPE_MISSING = 1 NO_AUTHORITY = 2
IMPORTING Parameters details for CLMO_CLASS_OBJECT_MAINTAIN
ACTIVITY - Activity 0,1,2,3 Create/Change/Display/Delete
Data type: RMCLM-BASISDOptional: No
Call by Reference: No ( called with pass by value option)
SKIP - No Change of Specified Class is Allowed
Data type: SY-BATCHOptional: Yes
Call by Reference: No ( called with pass by value option)
CLASSTYPE - Class Type
Data type: RMCLM-KLARTOptional: Yes
Call by Reference: No ( called with pass by value option)
CLASSNAME - Class
Data type: RMCLM-CLASSOptional: Yes
Call by Reference: Yes
OBJECTNAME - Name of Object (Not Class)
Data type: RMCLM-SPATXOptional: Yes
Call by Reference: No ( called with pass by value option)
RETAILTYPE - SAP for Retail Indicator (0, 1, 2, 3)
Data type: RMCLM-WWSKZOptional: Yes
Call by Reference: No ( called with pass by value option)
CALL - Internal Use: Do Not Fill
Data type: SY-CALLDOptional: Yes
Call by Reference: No ( called with pass by value option)
CLASS_AREA - Internal Use: Do Not Fill
Data type: SY-BATCHOptional: Yes
Call by Reference: No ( called with pass by value option)
CHANGENUMBER - Change Number
Data type: RMCLM-AENNRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
KEY_DATE - Date
Data type: RMCLM-DATUVDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CLMO_CLASS_OBJECT_MAINTAIN
FUNCTION_CODE - Last Function Code
Data type: SY-PFKEYOptional: No
Call by Reference: No ( called with pass by value option)
NO_CHANGES - No Changes to be Saved
Data type: SY-BATCHOptional: No
Call by Reference: No ( called with pass by value option)
E_ACTIVITY - New Activity
Data type: RMCLM-BASISDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
RETAILTYPE_MISSING - SAP for Retail Class Type: SAP for Retail Indicator is Obligatory
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_AUTHORITY - No Authorization for the Required Activity
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CLMO_CLASS_OBJECT_MAINTAIN 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_activity | TYPE RMCLM-BASISD, " | |||
lv_function_code | TYPE SY-PFKEY, " | |||
lv_retailtype_missing | TYPE SY, " | |||
lv_skip | TYPE SY-BATCH, " | |||
lv_classtype | TYPE RMCLM-KLART, " | |||
lv_no_changes | TYPE SY-BATCH, " | |||
lv_no_authority | TYPE SY, " | |||
lv_classname | TYPE RMCLM-CLASS, " | |||
lv_e_activity | TYPE RMCLM-BASISD, " | |||
lv_objectname | TYPE RMCLM-SPATX, " | |||
lv_retailtype | TYPE RMCLM-WWSKZ, " | |||
lv_call | TYPE SY-CALLD, " | |||
lv_class_area | TYPE SY-BATCH, " | |||
lv_changenumber | TYPE RMCLM-AENNR, " SPACE | |||
lv_key_date | TYPE RMCLM-DATUV. " SY-DATUM |
  CALL FUNCTION 'CLMO_CLASS_OBJECT_MAINTAIN' "Maintain Classes and Similar Objects |
EXPORTING | ||
ACTIVITY | = lv_activity | |
SKIP | = lv_skip | |
CLASSTYPE | = lv_classtype | |
CLASSNAME | = lv_classname | |
OBJECTNAME | = lv_objectname | |
RETAILTYPE | = lv_retailtype | |
CALL | = lv_call | |
CLASS_AREA | = lv_class_area | |
CHANGENUMBER | = lv_changenumber | |
KEY_DATE | = lv_key_date | |
IMPORTING | ||
FUNCTION_CODE | = lv_function_code | |
NO_CHANGES | = lv_no_changes | |
E_ACTIVITY | = lv_e_activity | |
EXCEPTIONS | ||
RETAILTYPE_MISSING = 1 | ||
NO_AUTHORITY = 2 | ||
. " CLMO_CLASS_OBJECT_MAINTAIN |
ABAP code using 7.40 inline data declarations to call FM CLMO_CLASS_OBJECT_MAINTAIN
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 BASISD FROM RMCLM INTO @DATA(ld_activity). | ||||
"SELECT single PFKEY FROM SY INTO @DATA(ld_function_code). | ||||
"SELECT single BATCH FROM SY INTO @DATA(ld_skip). | ||||
"SELECT single KLART FROM RMCLM INTO @DATA(ld_classtype). | ||||
"SELECT single BATCH FROM SY INTO @DATA(ld_no_changes). | ||||
"SELECT single CLASS FROM RMCLM INTO @DATA(ld_classname). | ||||
"SELECT single BASISD FROM RMCLM INTO @DATA(ld_e_activity). | ||||
"SELECT single SPATX FROM RMCLM INTO @DATA(ld_objectname). | ||||
"SELECT single WWSKZ FROM RMCLM INTO @DATA(ld_retailtype). | ||||
"SELECT single CALLD FROM SY INTO @DATA(ld_call). | ||||
"SELECT single BATCH FROM SY INTO @DATA(ld_class_area). | ||||
"SELECT single AENNR FROM RMCLM INTO @DATA(ld_changenumber). | ||||
DATA(ld_changenumber) | = ' '. | |||
"SELECT single DATUV FROM RMCLM INTO @DATA(ld_key_date). | ||||
DATA(ld_key_date) | = SY-DATUM. | |||
Search for further information about these or an SAP related objects