SAP FIELD_SELECTION_INFLUENCE Function Module for Field selection for single field (analysis of settings)
FIELD_SELECTION_INFLUENCE is a standard field selection influence SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Field selection for single field (analysis of settings) 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 field selection influence FM, simply by entering the name FIELD_SELECTION_INFLUENCE into the relevant SAP transaction such as SE37 or SE38.
Function Group: MFAW
Program Name: SAPLMFAW
Main Program: SAPLMFAW
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FIELD_SELECTION_INFLUENCE 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 'FIELD_SELECTION_INFLUENCE'"Field selection for single field (analysis of settings).
EXPORTING
DYNPROGRUPPE = "Name of the screen group of the screen
* MODE = ' ' "Call mode: SAP mode or customer Customizing
MODULPOOL = "Name of the module pool
FIELDNAME = "Name of screen field
IMPORTING
INPUT = "Field attribute: input
OUTPUT = "Field attribute: output
ACTIVE = "Field attribute: active
REQUIRED = "Field attribute: required
INTENSIFIED = "Field attribute: highlighted
INVISIBLE = "Field attribute: invisible
EXCEPTIONS
GROUP_IS_INITIAL = 1 MODULPOOL_IS_INITIAL = 2 UNKNOWN_MODE = 3 FIELD_NOT_IN_FIELDSELECTION = 4
IMPORTING Parameters details for FIELD_SELECTION_INFLUENCE
DYNPROGRUPPE - Name of the screen group of the screen
Data type: TFAW-BLDGROptional: No
Call by Reference: No ( called with pass by value option)
MODE - Call mode: SAP mode or customer Customizing
Data type: RMFAW-CUST_MODEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
MODULPOOL - Name of the module pool
Data type: TFAW-PROGOptional: No
Call by Reference: No ( called with pass by value option)
FIELDNAME - Name of screen field
Data type: TFAWF-MFELDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FIELD_SELECTION_INFLUENCE
INPUT - Field attribute: input
Data type: TFAWF-CUST_MOptional: No
Call by Reference: No ( called with pass by value option)
OUTPUT - Field attribute: output
Data type: TFAWF-CUST_MOptional: No
Call by Reference: No ( called with pass by value option)
ACTIVE - Field attribute: active
Data type: TFAWF-CUST_MOptional: No
Call by Reference: No ( called with pass by value option)
REQUIRED - Field attribute: required
Data type: TFAWF-CUST_MOptional: No
Call by Reference: No ( called with pass by value option)
INTENSIFIED - Field attribute: highlighted
Data type: TFAWF-CUST_MOptional: No
Call by Reference: No ( called with pass by value option)
INVISIBLE - Field attribute: invisible
Data type: TFAWF-CUST_MOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
GROUP_IS_INITIAL - Screen group not yet transferred
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MODULPOOL_IS_INITIAL - Program name not yet transferred
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UNKNOWN_MODE - Unknown mode
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FIELD_NOT_IN_FIELDSELECTION - Field not maintained in feld selection
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FIELD_SELECTION_INFLUENCE 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_input | TYPE TFAWF-CUST_M, " | |||
| lv_dynprogruppe | TYPE TFAW-BLDGR, " | |||
| lv_group_is_initial | TYPE TFAW, " | |||
| lv_mode | TYPE RMFAW-CUST_MODE, " SPACE | |||
| lv_output | TYPE TFAWF-CUST_M, " | |||
| lv_modulpool_is_initial | TYPE TFAWF, " | |||
| lv_active | TYPE TFAWF-CUST_M, " | |||
| lv_modulpool | TYPE TFAW-PROG, " | |||
| lv_unknown_mode | TYPE TFAW, " | |||
| lv_required | TYPE TFAWF-CUST_M, " | |||
| lv_fieldname | TYPE TFAWF-MFELD, " | |||
| lv_field_not_in_fieldselection | TYPE TFAWF, " | |||
| lv_intensified | TYPE TFAWF-CUST_M, " | |||
| lv_invisible | TYPE TFAWF-CUST_M. " |
|   CALL FUNCTION 'FIELD_SELECTION_INFLUENCE' "Field selection for single field (analysis of settings) |
| EXPORTING | ||
| DYNPROGRUPPE | = lv_dynprogruppe | |
| MODE | = lv_mode | |
| MODULPOOL | = lv_modulpool | |
| FIELDNAME | = lv_fieldname | |
| IMPORTING | ||
| INPUT | = lv_input | |
| OUTPUT | = lv_output | |
| ACTIVE | = lv_active | |
| REQUIRED | = lv_required | |
| INTENSIFIED | = lv_intensified | |
| INVISIBLE | = lv_invisible | |
| EXCEPTIONS | ||
| GROUP_IS_INITIAL = 1 | ||
| MODULPOOL_IS_INITIAL = 2 | ||
| UNKNOWN_MODE = 3 | ||
| FIELD_NOT_IN_FIELDSELECTION = 4 | ||
| . " FIELD_SELECTION_INFLUENCE | ||
ABAP code using 7.40 inline data declarations to call FM FIELD_SELECTION_INFLUENCE
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 CUST_M FROM TFAWF INTO @DATA(ld_input). | ||||
| "SELECT single BLDGR FROM TFAW INTO @DATA(ld_dynprogruppe). | ||||
| "SELECT single CUST_MODE FROM RMFAW INTO @DATA(ld_mode). | ||||
| DATA(ld_mode) | = ' '. | |||
| "SELECT single CUST_M FROM TFAWF INTO @DATA(ld_output). | ||||
| "SELECT single CUST_M FROM TFAWF INTO @DATA(ld_active). | ||||
| "SELECT single PROG FROM TFAW INTO @DATA(ld_modulpool). | ||||
| "SELECT single CUST_M FROM TFAWF INTO @DATA(ld_required). | ||||
| "SELECT single MFELD FROM TFAWF INTO @DATA(ld_fieldname). | ||||
| "SELECT single CUST_M FROM TFAWF INTO @DATA(ld_intensified). | ||||
| "SELECT single CUST_M FROM TFAWF INTO @DATA(ld_invisible). | ||||
Search for further information about these or an SAP related objects