SAP F4UT_GET_ENVIRONMENT Function Module for Request Program Environment for F4 Field
F4UT_GET_ENVIRONMENT is a standard f4ut get environment SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Request Program Environment for F4 Field 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 f4ut get environment FM, simply by entering the name F4UT_GET_ENVIRONMENT into the relevant SAP transaction such as SE37 or SE38.
Function Group: SF4U
Program Name: SAPLSF4U
Main Program: SAPLSF4U
Appliation area: S
Release date: 30-Apr-1999
Mode(Normal, Remote etc): Normal Function Module
Update:

Function F4UT_GET_ENVIRONMENT 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 'F4UT_GET_ENVIRONMENT'"Request Program Environment for F4 Field.
IMPORTING
ENV_INFO = "Information about Program Environment with F4
EXCEPTIONS
F4_NOT_ACTIVE = 1
EXPORTING Parameters details for F4UT_GET_ENVIRONMENT
ENV_INFO - Information about Program Environment with F4
Data type: DDSHF4ENVOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
F4_NOT_ACTIVE - F4 Help is not Active
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for F4UT_GET_ENVIRONMENT 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_env_info | TYPE DDSHF4ENV, " | |||
| lv_f4_not_active | TYPE DDSHF4ENV. " |
|   CALL FUNCTION 'F4UT_GET_ENVIRONMENT' "Request Program Environment for F4 Field |
| IMPORTING | ||
| ENV_INFO | = lv_env_info | |
| EXCEPTIONS | ||
| F4_NOT_ACTIVE = 1 | ||
| . " F4UT_GET_ENVIRONMENT | ||
ABAP code using 7.40 inline data declarations to call FM F4UT_GET_ENVIRONMENT
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