SAP CLFM_GET_CLASS_FOR_CUOBJ Function Module for









CLFM_GET_CLASS_FOR_CUOBJ is a standard clfm get class for cuobj 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 clfm get class for cuobj FM, simply by entering the name CLFM_GET_CLASS_FOR_CUOBJ into the relevant SAP transaction such as SE37 or SE38.

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



Function CLFM_GET_CLASS_FOR_CUOBJ 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 'CLFM_GET_CLASS_FOR_CUOBJ'"
EXPORTING
INTERNAL_OBJ_NUMBER = "Internal object number from INOB
* DATE_OF_CHANGE = "Change date
* I_AENNR = ' ' "

IMPORTING
CLASS = "Class
CLASSTYPE = "Class type
FROM_BUFFER = "Indicator: data from buffer
FROM_DATABASE = "Indicator: data from database

EXCEPTIONS
NO_CLASS_FOUND = 1
.




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_SAPLCLFM_001 Influences Class and Value Assignment
EXIT_SAPLCLFM_002 Customer Exit for Changing Classification Data Before Saving
EXIT_SAPLCLFM_003 Customer Exit After Check on Assigned Characteristic Values

IMPORTING Parameters details for CLFM_GET_CLASS_FOR_CUOBJ

INTERNAL_OBJ_NUMBER - Internal object number from INOB

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

DATE_OF_CHANGE - Change date

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

I_AENNR -

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

EXPORTING Parameters details for CLFM_GET_CLASS_FOR_CUOBJ

CLASS - Class

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

CLASSTYPE - Class type

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

FROM_BUFFER - Indicator: data from buffer

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

FROM_DATABASE - Indicator: data from database

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

EXCEPTIONS details

NO_CLASS_FOUND - No class for INOB number

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

Copy and paste ABAP code example for CLFM_GET_CLASS_FOR_CUOBJ 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  TYPE KLAH-CLASS, "   
lv_no_class_found  TYPE KLAH, "   
lv_internal_obj_number  TYPE INOB-CUOBJ, "   
lv_classtype  TYPE KLAH-KLART, "   
lv_date_of_change  TYPE RMCLF-DATUV1, "   
lv_i_aennr  TYPE AENR-AENNR, "   SPACE
lv_from_buffer  TYPE AENR, "   
lv_from_database  TYPE RMCLKSSK-DATABASE. "   

  CALL FUNCTION 'CLFM_GET_CLASS_FOR_CUOBJ'  "
    EXPORTING
         INTERNAL_OBJ_NUMBER = lv_internal_obj_number
         DATE_OF_CHANGE = lv_date_of_change
         I_AENNR = lv_i_aennr
    IMPORTING
         CLASS = lv_class
         CLASSTYPE = lv_classtype
         FROM_BUFFER = lv_from_buffer
         FROM_DATABASE = lv_from_database
    EXCEPTIONS
        NO_CLASS_FOUND = 1
. " CLFM_GET_CLASS_FOR_CUOBJ




ABAP code using 7.40 inline data declarations to call FM CLFM_GET_CLASS_FOR_CUOBJ

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 CLASS FROM KLAH INTO @DATA(ld_class).
 
 
"SELECT single CUOBJ FROM INOB INTO @DATA(ld_internal_obj_number).
 
"SELECT single KLART FROM KLAH INTO @DATA(ld_classtype).
 
"SELECT single DATUV1 FROM RMCLF INTO @DATA(ld_date_of_change).
 
"SELECT single AENNR FROM AENR INTO @DATA(ld_i_aennr).
DATA(ld_i_aennr) = ' '.
 
 
"SELECT single DATABASE FROM RMCLKSSK INTO @DATA(ld_from_database).
 


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!