SAP CTUV_TABLE_FIELD_CHECK Function Module for Check whether table field exists for characteristic

Search SAP Function Modules

CTUV_TABLE_FIELD_CHECK is a standard ctuv table field check 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 whether table field exists for characteristic 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 ctuv table field check FM, simply by entering the name CTUV_TABLE_FIELD_CHECK into the relevant SAP transaction such as SE37 or SE38.

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

Function CTUV_TABLE_FIELD_CHECK 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 'CTUV_TABLE_FIELD_CHECK'"Check whether table field exists for characteristic
  EXPORTING
   CHARACT_NEUTRAL_NAME =  "Language-independent name of characteristic
   FIELDNAME =  "Field name of table element
   TABLENAME =  "Table name
*  KEY_DATE = SY-DATUM "Date
*  STANDARD = ' ' "Standard object

 IMPORTING
   CHARACT_ID =  "
   NEW_CHARACTERISTIC =  "New characteristic created

EXCEPTIONS
   INVALID_FIELDNAME = 1    INVALID_NAME = 2 

.

IMPORTING Parameters details for CTUV_TABLE_FIELD_CHECK

CHARACT_NEUTRAL_NAME - Language-independent name of characteristic

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

FIELDNAME - Field name of table element

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

TABLENAME - Table name

Data type:
Optional: No
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)

STANDARD - Standard object

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

EXPORTING Parameters details for CTUV_TABLE_FIELD_CHECK

CHARACT_ID -

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

NEW_CHARACTERISTIC - New characteristic created

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

EXCEPTIONS details

INVALID_FIELDNAME - Field not in table

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

INVALID_NAME - Characteristic name already assigned

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

Copy and paste ABAP code example for CTUV_TABLE_FIELD_CHECK 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.

ABAP code using 7.40 inline data declarations to call FM CTUV_TABLE_FIELD_CHECK

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.

Search for further information about these or an SAP related objects