SAP SCAN_INPUT Function Module for

Search SAP Function Modules

SCAN_INPUT is a standard scan input 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 scan input FM, simply by entering the name SCAN_INPUT into the relevant SAP transaction such as SE37 or SE38.

Function Group: LOCAL_EDT1
Program Name: SAPLLOCAL_EDT1
Main Program: SAPLLOCAL_EDT1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SCAN_INPUT 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 'SCAN_INPUT'"
  EXPORTING
   KOMPRMODE =  "
   CASE_MODE =  "
   EDIT =  "
   CONTENT_FILL =  "
   LAST_CONTENT_DISPLAY =  "
   STATUS_FLAG =  "

CHANGING
   OVERFLOW_AREA =  "
   MSG =  "
   INCL =  "
   ROW =  "
   COL =  "
   WRD =  "
   S_MODIFIED =  "
   SCANNED =  "

TABLES
   LINEINDEX =  "
   CONTENT =  "ABAP Source Line
   TK =  "Extended String Description of Token in ABAP Source Analysis
   STM =  "

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLLOCAL_EDT1_001 User Exit for Editor (Dynamic Pattern)
EXIT_SAPLLOCAL_EDT1_002 User's Own Function Code in ABAP Editor

IMPORTING Parameters details for SCAN_INPUT

KOMPRMODE -

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

CASE_MODE -

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

EDIT -

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

CONTENT_FILL -

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

LAST_CONTENT_DISPLAY -

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

STATUS_FLAG -

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

CHANGING Parameters details for SCAN_INPUT

OVERFLOW_AREA -

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

MSG -

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

INCL -

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

ROW -

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

COL -

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

WRD -

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

S_MODIFIED -

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

SCANNED -

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

TABLES Parameters details for SCAN_INPUT

LINEINDEX -

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

CONTENT - ABAP Source Line

Data type: RSWSOURCET
Optional: No
Call by Reference: Yes

TK - Extended String Description of Token in ABAP Source Analysis

Data type: SEDI_TK
Optional: No
Call by Reference: Yes

STM -

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

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

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