SAP CLCM_CHECK_ADDITIONAL Function Module for Check Additional Data of Class









CLCM_CHECK_ADDITIONAL is a standard clcm check additional SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check Additional Data of Class 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 clcm check additional FM, simply by entering the name CLCM_CHECK_ADDITIONAL into the relevant SAP transaction such as SE37 or SE38.

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



Function CLCM_CHECK_ADDITIONAL 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 'CLCM_CHECK_ADDITIONAL'"Check Additional Data of Class
EXPORTING
KLADDITIONAL = "Structure of Additional Data Fields
CLASSNAME = "Class
CLASSTYPE = "Class Type
* ACTIVITY_TYPE = '0' "Activity: 0=Create 1=Change 3=Delete
MESSAGE_COLLECT = "Collect Messages in Log

IMPORTING
ERROR_MSGID = "ID of Error Message
ERROR_MSGNO = "Number of the Error Message
ERROR = "Indicator: Error Found
ERROR_MSGV1 = "Message Variable 1
ERROR_MSGV2 = "Message Variable 2
ERROR_MSGV3 = "Message Variable 3
ERROR_MSGV4 = "Message Variable 4

EXCEPTIONS
CLASS_OR_CLASSTYPE = 1
.



IMPORTING Parameters details for CLCM_CHECK_ADDITIONAL

KLADDITIONAL - Structure of Additional Data Fields

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

CLASSNAME - 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)

ACTIVITY_TYPE - Activity: 0=Create 1=Change 3=Delete

Data type: SY-BATCH
Default: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)

MESSAGE_COLLECT - Collect Messages in Log

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

EXPORTING Parameters details for CLCM_CHECK_ADDITIONAL

ERROR_MSGID - ID of Error Message

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

ERROR_MSGNO - Number of the Error Message

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

ERROR - Indicator: Error Found

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

ERROR_MSGV1 - Message Variable 1

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

ERROR_MSGV2 - Message Variable 2

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

ERROR_MSGV3 - Message Variable 3

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

ERROR_MSGV4 - Message Variable 4

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

EXCEPTIONS details

CLASS_OR_CLASSTYPE - Class or Class Type Missing

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

Copy and paste ABAP code example for CLCM_CHECK_ADDITIONAL 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_error_msgid  TYPE SY-MSGID, "   
lv_kladditional  TYPE KLZUSD, "   
lv_class_or_classtype  TYPE KLZUSD, "   
lv_classname  TYPE KLAH-CLASS, "   
lv_error_msgno  TYPE SY-MSGNO, "   
lv_error  TYPE SY-BINPT, "   
lv_classtype  TYPE KLAH-KLART, "   
lv_error_msgv1  TYPE SY-MSGV1, "   
lv_activity_type  TYPE SY-BATCH, "   '0'
lv_error_msgv2  TYPE SY-MSGV2, "   
lv_message_collect  TYPE RMCLM-BASISD, "   
lv_error_msgv3  TYPE SY-MSGV3, "   
lv_error_msgv4  TYPE SY-MSGV4. "   

  CALL FUNCTION 'CLCM_CHECK_ADDITIONAL'  "Check Additional Data of Class
    EXPORTING
         KLADDITIONAL = lv_kladditional
         CLASSNAME = lv_classname
         CLASSTYPE = lv_classtype
         ACTIVITY_TYPE = lv_activity_type
         MESSAGE_COLLECT = lv_message_collect
    IMPORTING
         ERROR_MSGID = lv_error_msgid
         ERROR_MSGNO = lv_error_msgno
         ERROR = lv_error
         ERROR_MSGV1 = lv_error_msgv1
         ERROR_MSGV2 = lv_error_msgv2
         ERROR_MSGV3 = lv_error_msgv3
         ERROR_MSGV4 = lv_error_msgv4
    EXCEPTIONS
        CLASS_OR_CLASSTYPE = 1
. " CLCM_CHECK_ADDITIONAL




ABAP code using 7.40 inline data declarations to call FM CLCM_CHECK_ADDITIONAL

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 MSGID FROM SY INTO @DATA(ld_error_msgid).
 
 
 
"SELECT single CLASS FROM KLAH INTO @DATA(ld_classname).
 
"SELECT single MSGNO FROM SY INTO @DATA(ld_error_msgno).
 
"SELECT single BINPT FROM SY INTO @DATA(ld_error).
 
"SELECT single KLART FROM KLAH INTO @DATA(ld_classtype).
 
"SELECT single MSGV1 FROM SY INTO @DATA(ld_error_msgv1).
 
"SELECT single BATCH FROM SY INTO @DATA(ld_activity_type).
DATA(ld_activity_type) = '0'.
 
"SELECT single MSGV2 FROM SY INTO @DATA(ld_error_msgv2).
 
"SELECT single BASISD FROM RMCLM INTO @DATA(ld_message_collect).
 
"SELECT single MSGV3 FROM SY INTO @DATA(ld_error_msgv3).
 
"SELECT single MSGV4 FROM SY INTO @DATA(ld_error_msgv4).
 


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!