SAP CTUT_FEATURE_DATA Function Module for









CTUT_FEATURE_DATA is a standard ctut feature data 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 ctut feature data FM, simply by entering the name CTUT_FEATURE_DATA into the relevant SAP transaction such as SE37 or SE38.

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



Function CTUT_FEATURE_DATA 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 'CTUT_FEATURE_DATA'"
EXPORTING
* CLASS_TYPE = ' ' "Class type
* IGNORE_BUFFER = ' ' "Discard buffered data
* CHANGE_NUMBER = ' ' "Change Number
* FEATURE_ID = 0 "Internal feature number
* FEATURE_NAME = ' ' "Feature name
* FEATURE_NEUTRAL_NAME = ' ' "Language-independent feature name
* LANGUAGE = ' ' "Language indicator
* MESSAGE_TYPE_INP = 'E' "Message type (E,I,W,...)
* KEY_DATE = SY-DATUM "Date
* IGNORE_DELETE_FLAG = ' ' "Ignore deletion indicator
* IGNORE_RENAME = ' ' "Include renamed characteristics

IMPORTING
ECABN = "
ECABNT = "

EXCEPTIONS
INVALID_CLASS_TYPE = 1 MISSING_FEATURE_INFORMATION = 2 NO_FEATURE_FOUND = 3 NO_FEATURE_VALID = 4 NO_LANGUAGE = 5
.



IMPORTING Parameters details for CTUT_FEATURE_DATA

CLASS_TYPE - Class type

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

IGNORE_BUFFER - Discard buffered data

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

CHANGE_NUMBER - Change Number

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

FEATURE_ID - Internal feature number

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

FEATURE_NAME - Feature name

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

FEATURE_NEUTRAL_NAME - Language-independent feature name

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

LANGUAGE - Language indicator

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

MESSAGE_TYPE_INP - Message type (E,I,W,...)

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

KEY_DATE - Date

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

IGNORE_DELETE_FLAG - Ignore deletion indicator

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

IGNORE_RENAME - Include renamed characteristics

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

EXPORTING Parameters details for CTUT_FEATURE_DATA

ECABN -

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

ECABNT -

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

EXCEPTIONS details

INVALID_CLASS_TYPE - Invalid class type

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

MISSING_FEATURE_INFORMATION - Specifications not sufficient for

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

NO_FEATURE_FOUND - Feature not found

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

NO_FEATURE_VALID - No feature valid for class type fo

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

NO_LANGUAGE - Language was not specified

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

Copy and paste ABAP code example for CTUT_FEATURE_DATA 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_ecabn  TYPE CABN, "   
lv_class_type  TYPE KLAH-KLART, "   SPACE
lv_invalid_class_type  TYPE KLAH, "   
lv_ignore_buffer  TYPE RCTMV-MARK, "   SPACE
lv_change_number  TYPE CABN-AENNR, "   SPACE
lv_ecabnt  TYPE CABNT, "   
lv_feature_id  TYPE CABN-ATINN, "   0
lv_missing_feature_information  TYPE CABN, "   
lv_feature_name  TYPE CABNT-ATBEZ, "   SPACE
lv_no_feature_found  TYPE CABNT, "   
lv_no_feature_valid  TYPE CABNT, "   
lv_feature_neutral_name  TYPE CABN-ATNAM, "   SPACE
lv_language  TYPE CABNT-SPRAS, "   SPACE
lv_no_language  TYPE CABNT, "   
lv_message_type_inp  TYPE SY-MSGTY, "   'E'
lv_key_date  TYPE SY-DATUM, "   SY-DATUM
lv_ignore_delete_flag  TYPE RCTMV-MARK, "   SPACE
lv_ignore_rename  TYPE RCTMV-MARK. "   SPACE

  CALL FUNCTION 'CTUT_FEATURE_DATA'  "
    EXPORTING
         CLASS_TYPE = lv_class_type
         IGNORE_BUFFER = lv_ignore_buffer
         CHANGE_NUMBER = lv_change_number
         FEATURE_ID = lv_feature_id
         FEATURE_NAME = lv_feature_name
         FEATURE_NEUTRAL_NAME = lv_feature_neutral_name
         LANGUAGE = lv_language
         MESSAGE_TYPE_INP = lv_message_type_inp
         KEY_DATE = lv_key_date
         IGNORE_DELETE_FLAG = lv_ignore_delete_flag
         IGNORE_RENAME = lv_ignore_rename
    IMPORTING
         ECABN = lv_ecabn
         ECABNT = lv_ecabnt
    EXCEPTIONS
        INVALID_CLASS_TYPE = 1
        MISSING_FEATURE_INFORMATION = 2
        NO_FEATURE_FOUND = 3
        NO_FEATURE_VALID = 4
        NO_LANGUAGE = 5
. " CTUT_FEATURE_DATA




ABAP code using 7.40 inline data declarations to call FM CTUT_FEATURE_DATA

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 KLAH INTO @DATA(ld_class_type).
DATA(ld_class_type) = ' '.
 
 
"SELECT single MARK FROM RCTMV INTO @DATA(ld_ignore_buffer).
DATA(ld_ignore_buffer) = ' '.
 
"SELECT single AENNR FROM CABN INTO @DATA(ld_change_number).
DATA(ld_change_number) = ' '.
 
 
"SELECT single ATINN FROM CABN INTO @DATA(ld_feature_id).
 
 
"SELECT single ATBEZ FROM CABNT INTO @DATA(ld_feature_name).
DATA(ld_feature_name) = ' '.
 
 
 
"SELECT single ATNAM FROM CABN INTO @DATA(ld_feature_neutral_name).
DATA(ld_feature_neutral_name) = ' '.
 
"SELECT single SPRAS FROM CABNT INTO @DATA(ld_language).
DATA(ld_language) = ' '.
 
 
"SELECT single MSGTY FROM SY INTO @DATA(ld_message_type_inp).
DATA(ld_message_type_inp) = 'E'.
 
"SELECT single DATUM FROM SY INTO @DATA(ld_key_date).
DATA(ld_key_date) = SY-DATUM.
 
"SELECT single MARK FROM RCTMV INTO @DATA(ld_ignore_delete_flag).
DATA(ld_ignore_delete_flag) = ' '.
 
"SELECT single MARK FROM RCTMV INTO @DATA(ld_ignore_rename).
DATA(ld_ignore_rename) = ' '.
 


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!