SAP TERM_CHECK_INVALID_SPELLING Function Module for NOTRANSL: Prüft, ob Term Invalid Spelling/Synonym ist, gibt correct spelli

Search SAP Function Modules

TERM_CHECK_INVALID_SPELLING is a standard term check invalid spelling 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: Prüft, ob Term Invalid Spelling/Synonym ist, gibt correct spelli 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 term check invalid spelling FM, simply by entering the name TERM_CHECK_INVALID_SPELLING into the relevant SAP transaction such as SE37 or SE38.

Function Group: STERM_INTERFACE
Program Name: SAPLSTERM_INTERFACE
Main Program: SAPLSTERM_INTERFACE
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function TERM_CHECK_INVALID_SPELLING 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 'TERM_CHECK_INVALID_SPELLING'"NOTRANSL: Prüft, ob Term Invalid Spelling/Synonym ist, gibt correct spelli
  EXPORTING
*  LANGU = SY-LANGU "Translation Language
   TEXT =  "Term

 IMPORTING
   E_CORRECT_SPELLING =  "Term

EXCEPTIONS
   UNKNOWN_LANGU = 1    NO_ENTRY_FOUND = 2    COMMUNICATION_FAILURE = 3 

.

IMPORTING Parameters details for TERM_CHECK_INVALID_SPELLING

LANGU - Translation Language

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

TEXT - Term

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

EXPORTING Parameters details for TERM_CHECK_INVALID_SPELLING

E_CORRECT_SPELLING - Term

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

EXCEPTIONS details

UNKNOWN_LANGU -

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

NO_ENTRY_FOUND -

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

COMMUNICATION_FAILURE -

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

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

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