SAP SAMPLE_PROCESS_00106131 Function Module for









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

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



Function SAMPLE_PROCESS_00106131 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 'SAMPLE_PROCESS_00106131'"
  EXPORTING
*  U_SCREEN_NAME =  "Field name
*  U_SCREEN_GROUP1 =  "Evaluation of Modif-group 1
*  U_SCREEN_GROUP2 =  "Evaluation of Modif-Group 2
*  U_SCREEN_GROUP3 =  "Evaluation of Modif-Group 3
*  U_SCREEN_GROUP4 =  "Evaluation of Modif-Group 4
*  U_OTHERS_SEL_CRIT =  "

CHANGING
*  C_SCREEN_REQUIRED =  "Req. field
   C_FLG_MODIFY =  "Modify Screen
*  C_SCREEN_INPUT =  "Field Ready for Input
*  C_SCREEN_OUTPUT =  "Field only used for display
*  C_SCREEN_INTENSIFIED =  "Field is highlighted
*  C_SCREEN_INVISIBLE =  "Field Is Hidden
*  C_SCREEN_ACTIVE =  "Field is Active
*  C_SCREEN_DISPLAY_3D =  "Three Dimensional Frame
*  C_SCREEN_VALUE_HELP =  "Display of Entry Help Key
*  C_SCREEN_REQUEST =  "Entry Exists
.



IMPORTING Parameters details for SAMPLE_PROCESS_00106131

U_SCREEN_NAME - Field name

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

U_SCREEN_GROUP1 - Evaluation of Modif-group 1

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

U_SCREEN_GROUP2 - Evaluation of Modif-Group 2

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

U_SCREEN_GROUP3 - Evaluation of Modif-Group 3

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

U_SCREEN_GROUP4 - Evaluation of Modif-Group 4

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

U_OTHERS_SEL_CRIT -

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

CHANGING Parameters details for SAMPLE_PROCESS_00106131

C_SCREEN_REQUIRED - Req. field

Data type: CHAR1
Optional: Yes
Call by Reference: Yes

C_FLG_MODIFY - Modify Screen

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

C_SCREEN_INPUT - Field Ready for Input

Data type: CHAR1
Optional: Yes
Call by Reference: Yes

C_SCREEN_OUTPUT - Field only used for display

Data type: CHAR1
Optional: Yes
Call by Reference: Yes

C_SCREEN_INTENSIFIED - Field is highlighted

Data type: CHAR1
Optional: Yes
Call by Reference: Yes

C_SCREEN_INVISIBLE - Field Is Hidden

Data type: CHAR1
Optional: Yes
Call by Reference: Yes

C_SCREEN_ACTIVE - Field is Active

Data type: CHAR1
Optional: Yes
Call by Reference: Yes

C_SCREEN_DISPLAY_3D - Three Dimensional Frame

Data type: CHAR1
Optional: Yes
Call by Reference: Yes

C_SCREEN_VALUE_HELP - Display of Entry Help Key

Data type: CHAR1
Optional: Yes
Call by Reference: Yes

C_SCREEN_REQUEST - Entry Exists

Data type: CHAR1
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for SAMPLE_PROCESS_00106131 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_u_screen_name  TYPE DDSHDYNFLD, "   
lv_c_screen_required  TYPE CHAR1, "   
lv_c_flg_modify  TYPE XFELD, "   
lv_c_screen_input  TYPE CHAR1, "   
lv_u_screen_group1  TYPE CHAR3, "   
lv_c_screen_output  TYPE CHAR1, "   
lv_u_screen_group2  TYPE CHAR3, "   
lv_u_screen_group3  TYPE CHAR3, "   
lv_c_screen_intensified  TYPE CHAR1, "   
lv_u_screen_group4  TYPE CHAR3, "   
lv_c_screen_invisible  TYPE CHAR1, "   
lv_c_screen_active  TYPE CHAR1, "   
lv_u_others_sel_crit  TYPE XFELD, "   
lv_c_screen_display_3d  TYPE CHAR1, "   
lv_c_screen_value_help  TYPE CHAR1, "   
lv_c_screen_request  TYPE CHAR1. "   

  CALL FUNCTION 'SAMPLE_PROCESS_00106131'  "
    EXPORTING
         U_SCREEN_NAME = lv_u_screen_name
         U_SCREEN_GROUP1 = lv_u_screen_group1
         U_SCREEN_GROUP2 = lv_u_screen_group2
         U_SCREEN_GROUP3 = lv_u_screen_group3
         U_SCREEN_GROUP4 = lv_u_screen_group4
         U_OTHERS_SEL_CRIT = lv_u_others_sel_crit
    CHANGING
         C_SCREEN_REQUIRED = lv_c_screen_required
         C_FLG_MODIFY = lv_c_flg_modify
         C_SCREEN_INPUT = lv_c_screen_input
         C_SCREEN_OUTPUT = lv_c_screen_output
         C_SCREEN_INTENSIFIED = lv_c_screen_intensified
         C_SCREEN_INVISIBLE = lv_c_screen_invisible
         C_SCREEN_ACTIVE = lv_c_screen_active
         C_SCREEN_DISPLAY_3D = lv_c_screen_display_3d
         C_SCREEN_VALUE_HELP = lv_c_screen_value_help
         C_SCREEN_REQUEST = lv_c_screen_request
. " SAMPLE_PROCESS_00106131




ABAP code using 7.40 inline data declarations to call FM SAMPLE_PROCESS_00106131

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!