SAP S_DB_INFORMIX_STUI_CONFIG Function Module for Edit persistent STUI configuration
S_DB_INFORMIX_STUI_CONFIG is a standard s db informix stui config SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Edit persistent STUI configuration 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 s db informix stui config FM, simply by entering the name S_DB_INFORMIX_STUI_CONFIG into the relevant SAP transaction such as SE37 or SE38.
Function Group: STUI
Program Name: SAPLSTUI
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function S_DB_INFORMIX_STUI_CONFIG 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 'S_DB_INFORMIX_STUI_CONFIG'"Edit persistent STUI configuration.
EXPORTING
* REFRESH = ' ' "Refresh system data
IMPORTING
INF_MONITOR_VERSION = "Field of type DATS
CHANGING
* TEMPDIR = "Pathname: $TMP or $TEMP or %TMP% or %TEMP%
* VERSION = "INFORMIX version (short one)
* DBHOST = "Hostname (short) of DB host
* DBHOST_OS = "R/3 System, operating system of application server
* SYSID = "RFC: SAP machine ID
* PAGESIZE = "Informix Page Size in Bytes
EXCEPTIONS
SYSTEM_FAILURE = 1 WRONG_DATABASE = 2 NOT_ON_DBHOST = 3
IMPORTING Parameters details for S_DB_INFORMIX_STUI_CONFIG
REFRESH - Refresh system data
Data type: SY-DAYSTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for S_DB_INFORMIX_STUI_CONFIG
INF_MONITOR_VERSION - Field of type DATS
Data type: DATSOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for S_DB_INFORMIX_STUI_CONFIG
TEMPDIR - Pathname: $TMP or $TEMP or %TMP% or %TEMP%
Data type: STUITMPDIROptional: Yes
Call by Reference: No ( called with pass by value option)
VERSION - INFORMIX version (short one)
Data type: STUI_VERSOptional: Yes
Call by Reference: No ( called with pass by value option)
DBHOST - Hostname (short) of DB host
Data type: RFCSI-RFCHOSTOptional: Yes
Call by Reference: No ( called with pass by value option)
DBHOST_OS - R/3 System, operating system of application server
Data type: RFCSI-RFCOPSYSOptional: Yes
Call by Reference: No ( called with pass by value option)
SYSID - RFC: SAP machine ID
Data type: RFCSI-RFCMACHOptional: Yes
Call by Reference: No ( called with pass by value option)
PAGESIZE - Informix Page Size in Bytes
Data type: PAGSIZEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
SYSTEM_FAILURE - something went wrong
Data type:Optional: No
Call by Reference: Yes
WRONG_DATABASE - SAP system is not running on Informix
Data type:Optional: No
Call by Reference: Yes
NOT_ON_DBHOST - RFC destination DBSERVER doesn't point to DB host
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for S_DB_INFORMIX_STUI_CONFIG 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_refresh | TYPE SY-DAYST, " SPACE | |||
| lv_tempdir | TYPE STUITMPDIR, " | |||
| lv_system_failure | TYPE STUITMPDIR, " | |||
| lv_inf_monitor_version | TYPE DATS, " | |||
| lv_version | TYPE STUI_VERS, " | |||
| lv_wrong_database | TYPE STUI_VERS, " | |||
| lv_dbhost | TYPE RFCSI-RFCHOST, " | |||
| lv_not_on_dbhost | TYPE RFCSI, " | |||
| lv_dbhost_os | TYPE RFCSI-RFCOPSYS, " | |||
| lv_sysid | TYPE RFCSI-RFCMACH, " | |||
| lv_pagesize | TYPE PAGSIZE. " |
|   CALL FUNCTION 'S_DB_INFORMIX_STUI_CONFIG' "Edit persistent STUI configuration |
| EXPORTING | ||
| REFRESH | = lv_refresh | |
| IMPORTING | ||
| INF_MONITOR_VERSION | = lv_inf_monitor_version | |
| CHANGING | ||
| TEMPDIR | = lv_tempdir | |
| VERSION | = lv_version | |
| DBHOST | = lv_dbhost | |
| DBHOST_OS | = lv_dbhost_os | |
| SYSID | = lv_sysid | |
| PAGESIZE | = lv_pagesize | |
| EXCEPTIONS | ||
| SYSTEM_FAILURE = 1 | ||
| WRONG_DATABASE = 2 | ||
| NOT_ON_DBHOST = 3 | ||
| . " S_DB_INFORMIX_STUI_CONFIG | ||
ABAP code using 7.40 inline data declarations to call FM S_DB_INFORMIX_STUI_CONFIG
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 DAYST FROM SY INTO @DATA(ld_refresh). | ||||
| DATA(ld_refresh) | = ' '. | |||
| "SELECT single RFCHOST FROM RFCSI INTO @DATA(ld_dbhost). | ||||
| "SELECT single RFCOPSYS FROM RFCSI INTO @DATA(ld_dbhost_os). | ||||
| "SELECT single RFCMACH FROM RFCSI INTO @DATA(ld_sysid). | ||||
Search for further information about these or an SAP related objects