SAP CNTX_SOI_SAVE_TEXT Function Module for NOTRANSL: PS-Texterstellung Text sichern
CNTX_SOI_SAVE_TEXT is a standard cntx soi save text 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: PS-Texterstellung Text sichern 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 cntx soi save text FM, simply by entering the name CNTX_SOI_SAVE_TEXT into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNTX_SOI
Program Name: SAPLCNTX_SOI
Main Program: SAPLCNTX_SOI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CNTX_SOI_SAVE_TEXT 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 'CNTX_SOI_SAVE_TEXT'"NOTRANSL: PS-Texterstellung Text sichern.
EXPORTING
* CLIENT = SY-MANDT "Client Number from Logon
HEADER = "SAPscript: Text Header
* INSERT = ' ' "
* SAVEMODE_DIRECT = ' ' "
* OWNER_SPECIFIED = ' ' "
* LOCAL_CAT = ' ' "
IMPORTING
FUNCTION = "
NEWHEADER = "SAPscript: Text Header
TABLES
LINES = "SAPscript: Text Lines
BLINES = "SAPscript: Text Lines
EXCEPTIONS
ID = 1 LANGUAGE = 2 NAME = 3 OBJECT = 4
IMPORTING Parameters details for CNTX_SOI_SAVE_TEXT
CLIENT - Client Number from Logon
Data type: SY-MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
HEADER - SAPscript: Text Header
Data type: THEADOptional: No
Call by Reference: No ( called with pass by value option)
INSERT -
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
SAVEMODE_DIRECT -
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
OWNER_SPECIFIED -
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
LOCAL_CAT -
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CNTX_SOI_SAVE_TEXT
FUNCTION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NEWHEADER - SAPscript: Text Header
Data type: THEADOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CNTX_SOI_SAVE_TEXT
LINES - SAPscript: Text Lines
Data type: TLINEOptional: No
Call by Reference: Yes
BLINES - SAPscript: Text Lines
Data type: CNSOI_BYTELINEOptional: No
Call by Reference: Yes
EXCEPTIONS details
ID - Text ID in text header invalid
Data type:Optional: No
Call by Reference: Yes
LANGUAGE - Language in text header invalid
Data type:Optional: No
Call by Reference: Yes
NAME - Text name in text header invalid
Data type:Optional: No
Call by Reference: Yes
OBJECT - Text object in text header invalid
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CNTX_SOI_SAVE_TEXT 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_id | TYPE STRING, " | |||
| lt_lines | TYPE STANDARD TABLE OF TLINE, " | |||
| lv_client | TYPE SY-MANDT, " SY-MANDT | |||
| lv_function | TYPE SY, " | |||
| lt_blines | TYPE STANDARD TABLE OF CNSOI_BYTELINE, " | |||
| lv_header | TYPE THEAD, " | |||
| lv_language | TYPE THEAD, " | |||
| lv_newheader | TYPE THEAD, " | |||
| lv_name | TYPE THEAD, " | |||
| lv_insert | TYPE THEAD, " SPACE | |||
| lv_object | TYPE THEAD, " | |||
| lv_savemode_direct | TYPE THEAD, " SPACE | |||
| lv_owner_specified | TYPE THEAD, " SPACE | |||
| lv_local_cat | TYPE THEAD. " SPACE |
|   CALL FUNCTION 'CNTX_SOI_SAVE_TEXT' "NOTRANSL: PS-Texterstellung Text sichern |
| EXPORTING | ||
| CLIENT | = lv_client | |
| HEADER | = lv_header | |
| INSERT | = lv_insert | |
| SAVEMODE_DIRECT | = lv_savemode_direct | |
| OWNER_SPECIFIED | = lv_owner_specified | |
| LOCAL_CAT | = lv_local_cat | |
| IMPORTING | ||
| FUNCTION | = lv_function | |
| NEWHEADER | = lv_newheader | |
| TABLES | ||
| LINES | = lt_lines | |
| BLINES | = lt_blines | |
| EXCEPTIONS | ||
| ID = 1 | ||
| LANGUAGE = 2 | ||
| NAME = 3 | ||
| OBJECT = 4 | ||
| . " CNTX_SOI_SAVE_TEXT | ||
ABAP code using 7.40 inline data declarations to call FM CNTX_SOI_SAVE_TEXT
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 MANDT FROM SY INTO @DATA(ld_client). | ||||
| DATA(ld_client) | = SY-MANDT. | |||
| DATA(ld_insert) | = ' '. | |||
| DATA(ld_savemode_direct) | = ' '. | |||
| DATA(ld_owner_specified) | = ' '. | |||
| DATA(ld_local_cat) | = ' '. | |||
Search for further information about these or an SAP related objects