SAP CUCP_CHECK_VALUE_IN_CBASE Function Module for NOTRANSL: Verwendung eines Merkmalwertes in der CBASE (IBSYMBOL)









CUCP_CHECK_VALUE_IN_CBASE is a standard cucp check value in cbase SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Verwendung eines Merkmalwertes in der CBASE (IBSYMBOL) 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 cucp check value in cbase FM, simply by entering the name CUCP_CHECK_VALUE_IN_CBASE into the relevant SAP transaction such as SE37 or SE38.

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



Function CUCP_CHECK_VALUE_IN_CBASE 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 'CUCP_CHECK_VALUE_IN_CBASE'"NOTRANSL: Verwendung eines Merkmalwertes in der CBASE (IBSYMBOL)
EXPORTING
IV_ATINN = "Characteristic
* IV_ATWRT = "Characteristic Value
* IV_CLINT = "Internal Class Number
* I_CLASS_TYPE = '300' "Class Type
* I_MAX_RECORDS = 0 "

TABLES
* ET_AUSP = "DE-EN-LANG-SWITCH-NO-TRANSLATION

EXCEPTIONS
NO_ENTRY = 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_SAPLCUCP_002 Deleted Assignment of Class to Object Despite Configured Objects
EXIT_SAPLCUCP_003 Delete assignment of characteristic to class despite configured object
EXIT_SAPLCUCP_004 Deleted Assignment of Class to Object Despite Configured Objects
EXIT_SAPLCUCP_005 Delete assignment of profile to object despite configured objects
EXIT_SAPLCUCP_006 Delete Assignment of Characteristic to Class Despite Configured Obj. CBASE
EXIT_SAPLCUCP_007 Delete ASsignment of Class to Object Despite Configured Object CBASE
EXIT_SAPLCUCP_008 Delete Assignment of Profile for Object Despite Configured Object CBASE

IMPORTING Parameters details for CUCP_CHECK_VALUE_IN_CBASE

IV_ATINN - Characteristic

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

IV_ATWRT - Characteristic Value

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

IV_CLINT - Internal Class Number

Data type: CLINT
Optional: Yes
Call by Reference: Yes

I_CLASS_TYPE - Class Type

Data type: TCLA-KLART
Default: '300'
Optional: Yes
Call by Reference: Yes

I_MAX_RECORDS -

Data type: I
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for CUCP_CHECK_VALUE_IN_CBASE

ET_AUSP - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type: AUSP
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

NO_ENTRY - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CUCP_CHECK_VALUE_IN_CBASE 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:
lt_et_ausp  TYPE STANDARD TABLE OF AUSP, "   
lv_iv_atinn  TYPE ATINN, "   
lv_no_entry  TYPE ATINN, "   
lv_iv_atwrt  TYPE ATWRT, "   
lv_iv_clint  TYPE CLINT, "   
lv_i_class_type  TYPE TCLA-KLART, "   '300'
lv_i_max_records  TYPE I. "   0

  CALL FUNCTION 'CUCP_CHECK_VALUE_IN_CBASE'  "NOTRANSL: Verwendung eines Merkmalwertes in der CBASE (IBSYMBOL)
    EXPORTING
         IV_ATINN = lv_iv_atinn
         IV_ATWRT = lv_iv_atwrt
         IV_CLINT = lv_iv_clint
         I_CLASS_TYPE = lv_i_class_type
         I_MAX_RECORDS = lv_i_max_records
    TABLES
         ET_AUSP = lt_et_ausp
    EXCEPTIONS
        NO_ENTRY = 1
. " CUCP_CHECK_VALUE_IN_CBASE




ABAP code using 7.40 inline data declarations to call FM CUCP_CHECK_VALUE_IN_CBASE

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 KLART FROM TCLA INTO @DATA(ld_i_class_type).
DATA(ld_i_class_type) = '300'.
 
 


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!