SAP PREPARE_FIELD_SELECT_STRING Function Module for
PREPARE_FIELD_SELECT_STRING is a standard prepare field select string 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 prepare field select string FM, simply by entering the name PREPARE_FIELD_SELECT_STRING into the relevant SAP transaction such as SE37 or SE38.
Function Group: F006
Program Name: SAPLF006
Main Program: SAPLF006
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PREPARE_FIELD_SELECT_STRING 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 'PREPARE_FIELD_SELECT_STRING'".
EXPORTING
INCOMING_STRING = "incoming field status definition
STRING_ID = "Identifier from table TMODI
TEXT1 = "Heading line 1
TEXT2 = "Heading line 2
* TEXT3 = ' ' "Header line 3
* XCHANGE = ' ' "Change allowed? X=Yes ' '=No
* XNODISP = ' ' "Should display column be suppressed?
IMPORTING
ACTTYP = "Space=Back, S=Save E=Exit
OUTGOING_STRING = "outgoing field status definition
XCHANGE = "Change allowed? X=Yes ' '=No
IMPORTING Parameters details for PREPARE_FIELD_SELECT_STRING
INCOMING_STRING - incoming field status definition
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
STRING_ID - Identifier from table TMODI
Data type: TMODO-FAUNAOptional: No
Call by Reference: No ( called with pass by value option)
TEXT1 - Heading line 1
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TEXT2 - Heading line 2
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TEXT3 - Header line 3
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
XCHANGE - Change allowed? X=Yes SPACE=No
Data type: T020-AKTYPDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
XNODISP - Should display column be suppressed?
Data type: T020-AKTYPDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for PREPARE_FIELD_SELECT_STRING
ACTTYP - Space=Back, S=Save E=Exit
Data type: T020-AKTYPOptional: No
Call by Reference: No ( called with pass by value option)
OUTGOING_STRING - outgoing field status definition
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
XCHANGE - Change allowed? X=Yes SPACE=No
Data type: T020-AKTYPOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for PREPARE_FIELD_SELECT_STRING 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_acttyp | TYPE T020-AKTYP, " | |||
| lv_incoming_string | TYPE T020, " | |||
| lv_string_id | TYPE TMODO-FAUNA, " | |||
| lv_outgoing_string | TYPE TMODO, " | |||
| lv_text1 | TYPE TMODO, " | |||
| lv_xchange | TYPE T020-AKTYP, " | |||
| lv_text2 | TYPE T020, " | |||
| lv_text3 | TYPE T020, " SPACE | |||
| lv_xchange | TYPE T020-AKTYP, " SPACE | |||
| lv_xnodisp | TYPE T020-AKTYP. " SPACE |
|   CALL FUNCTION 'PREPARE_FIELD_SELECT_STRING' " |
| EXPORTING | ||
| INCOMING_STRING | = lv_incoming_string | |
| STRING_ID | = lv_string_id | |
| TEXT1 | = lv_text1 | |
| TEXT2 | = lv_text2 | |
| TEXT3 | = lv_text3 | |
| XCHANGE | = lv_xchange | |
| XNODISP | = lv_xnodisp | |
| IMPORTING | ||
| ACTTYP | = lv_acttyp | |
| OUTGOING_STRING | = lv_outgoing_string | |
| XCHANGE | = lv_xchange | |
| . " PREPARE_FIELD_SELECT_STRING | ||
ABAP code using 7.40 inline data declarations to call FM PREPARE_FIELD_SELECT_STRING
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 AKTYP FROM T020 INTO @DATA(ld_acttyp). | ||||
| "SELECT single FAUNA FROM TMODO INTO @DATA(ld_string_id). | ||||
| "SELECT single AKTYP FROM T020 INTO @DATA(ld_xchange). | ||||
| DATA(ld_text3) | = ' '. | |||
| "SELECT single AKTYP FROM T020 INTO @DATA(ld_xchange). | ||||
| DATA(ld_xchange) | = ' '. | |||
| "SELECT single AKTYP FROM T020 INTO @DATA(ld_xnodisp). | ||||
| DATA(ld_xnodisp) | = ' '. | |||
Search for further information about these or an SAP related objects