SAP LSO_CP_STRING_TO_TABLE Function Module for
LSO_CP_STRING_TO_TABLE is a standard lso cp string to table 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 lso cp string to table FM, simply by entering the name LSO_CP_STRING_TO_TABLE into the relevant SAP transaction such as SE37 or SE38.
Function Group: LSO_IF_LEARNERACCOUNT_C
Program Name: SAPLLSO_IF_LEARNERACCOUNT_C
Main Program: SAPLLSO_IF_LEARNERACCOUNT_C
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LSO_CP_STRING_TO_TABLE 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 'LSO_CP_STRING_TO_TABLE'".
EXPORTING
STRING_TO_SPLIT = "
* SPLIT_LENGTH = 4096 "
TABLES
IT_SPLITS = "
IMPORTING Parameters details for LSO_CP_STRING_TO_TABLE
STRING_TO_SPLIT -
Data type: STRINGOptional: No
Call by Reference: Yes
SPLIT_LENGTH -
Data type: INT4Default: 4096
Optional: No
Call by Reference: Yes
TABLES Parameters details for LSO_CP_STRING_TO_TABLE
IT_SPLITS -
Data type: TABLEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for LSO_CP_STRING_TO_TABLE 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: | ||||
| lt_it_splits | TYPE STANDARD TABLE OF TABLE, " | |||
| lv_string_to_split | TYPE STRING, " | |||
| lv_split_length | TYPE INT4. " 4096 |
|   CALL FUNCTION 'LSO_CP_STRING_TO_TABLE' " |
| EXPORTING | ||
| STRING_TO_SPLIT | = lv_string_to_split | |
| SPLIT_LENGTH | = lv_split_length | |
| TABLES | ||
| IT_SPLITS | = lt_it_splits | |
| . " LSO_CP_STRING_TO_TABLE | ||
ABAP code using 7.40 inline data declarations to call FM LSO_CP_STRING_TO_TABLE
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.| DATA(ld_split_length) | = 4096. | |||
Search for further information about these or an SAP related objects