SAP SLIM_CHECK_TEXT_SPEC_MOD_TYPE Function Module for









SLIM_CHECK_TEXT_SPEC_MOD_TYPE is a standard slim check text spec mod type 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 slim check text spec mod type FM, simply by entering the name SLIM_CHECK_TEXT_SPEC_MOD_TYPE into the relevant SAP transaction such as SE37 or SE38.

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



Function SLIM_CHECK_TEXT_SPEC_MOD_TYPE 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 'SLIM_CHECK_TEXT_SPEC_MOD_TYPE'"
EXPORTING
USERTYPE = "
TEXT = "
ACTIVE = "

IMPORTING
CHANGE = "

EXCEPTIONS
NO_INDIVIDUAL_TEXT = 1 NO_TEXT_BUT_CLASSIFICATION = 2 OTHERS = 3
.



IMPORTING Parameters details for SLIM_CHECK_TEXT_SPEC_MOD_TYPE

USERTYPE -

Data type: TUTYP-USERTYP
Optional: No
Call by Reference: Yes

TEXT -

Data type: TUTYP-UTYPTEXT
Optional: No
Call by Reference: Yes

ACTIVE -

Data type: TUTYPA-ACTIVE
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for SLIM_CHECK_TEXT_SPEC_MOD_TYPE

CHANGE -

Data type: C
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_INDIVIDUAL_TEXT -

Data type:
Optional: No
Call by Reference: Yes

NO_TEXT_BUT_CLASSIFICATION -

Data type:
Optional: No
Call by Reference: Yes

OTHERS -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SLIM_CHECK_TEXT_SPEC_MOD_TYPE 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_change  TYPE C, "   
lv_usertype  TYPE TUTYP-USERTYP, "   
lv_no_individual_text  TYPE TUTYP, "   
lv_text  TYPE TUTYP-UTYPTEXT, "   
lv_no_text_but_classification  TYPE TUTYP, "   
lv_active  TYPE TUTYPA-ACTIVE, "   
lv_others  TYPE TUTYPA. "   

  CALL FUNCTION 'SLIM_CHECK_TEXT_SPEC_MOD_TYPE'  "
    EXPORTING
         USERTYPE = lv_usertype
         TEXT = lv_text
         ACTIVE = lv_active
    IMPORTING
         CHANGE = lv_change
    EXCEPTIONS
        NO_INDIVIDUAL_TEXT = 1
        NO_TEXT_BUT_CLASSIFICATION = 2
        OTHERS = 3
. " SLIM_CHECK_TEXT_SPEC_MOD_TYPE




ABAP code using 7.40 inline data declarations to call FM SLIM_CHECK_TEXT_SPEC_MOD_TYPE

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 USERTYP FROM TUTYP INTO @DATA(ld_usertype).
 
 
"SELECT single UTYPTEXT FROM TUTYP INTO @DATA(ld_text).
 
 
"SELECT single ACTIVE FROM TUTYPA INTO @DATA(ld_active).
 
 


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!