SAP STRING_INS Function Module for NOTRANSL: Einfügen von an in
STRING_INS is a standard string ins 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: Einfügen von
See here to view full function module documentation and code listing for string ins FM, simply by entering the name STRING_INS into the relevant SAP transaction such as SE37 or SE38.
Function Group: CO09
Program Name: SAPLCO09
Main Program: SAPLCO09
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 
Function STRING_INS 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 'STRING_INS'"NOTRANSL: Einfügen von.an in
EXPORTING
INSERT = "Generic Type
POSITION = "Predefined Type
CHANGING
TEXT = "Generic Type
EXCEPTIONS
INVALID_POSITION = 1 INSUFFICIENT_TEXT_LENGTH = 2
IMPORTING Parameters details for STRING_INS
INSERT - Generic Type
Data type: COptional: No
Call by Reference: Yes
POSITION - Predefined Type
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for STRING_INS
TEXT - Generic Type
Data type: COptional: No
Call by Reference: Yes
EXCEPTIONS details
INVALID_POSITION - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INSUFFICIENT_TEXT_LENGTH - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for STRING_INS 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_text | TYPE C, " | |||
| lv_insert | TYPE C, " | |||
| lv_invalid_position | TYPE C, " | |||
| lv_position | TYPE I, " | |||
| lv_insufficient_text_length | TYPE I. " |
|   CALL FUNCTION 'STRING_INS' "NOTRANSL: Einfügen von |
| EXPORTING | ||
| INSERT | = lv_insert | |
| POSITION | = lv_position | |
| CHANGING | ||
| TEXT | = lv_text | |
| EXCEPTIONS | ||
| INVALID_POSITION = 1 | ||
| INSUFFICIENT_TEXT_LENGTH = 2 | ||
| . " STRING_INS | ||
ABAP code using 7.40 inline data declarations to call FM STRING_INS
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