SAP UPDATE_STATS Function Module for Refresh the optimizer statistics for a single database object
UPDATE_STATS is a standard update stats SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Refresh the optimizer statistics for a single database object 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 update stats FM, simply by entering the name UPDATE_STATS into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDBS
Program Name: SAPLSDBS
Main Program: SAPLSDBS
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UPDATE_STATS 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 'UPDATE_STATS'"Refresh the optimizer statistics for a single database object.
EXPORTING
TABLE_NAME = "
SIGNI = "
EXCEPTIONS
NOT_FOUND = 1 ERROR = 2
IMPORTING Parameters details for UPDATE_STATS
TABLE_NAME -
Data type: DD02L-TABNAMEOptional: No
Call by Reference: No ( called with pass by value option)
SIGNI -
Data type: DBSTATC-SIGNIOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for UPDATE_STATS 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_not_found | TYPE STRING, " | |||
| lv_table_name | TYPE DD02L-TABNAME, " | |||
| lv_error | TYPE DD02L, " | |||
| lv_signi | TYPE DBSTATC-SIGNI. " |
|   CALL FUNCTION 'UPDATE_STATS' "Refresh the optimizer statistics for a single database object |
| EXPORTING | ||
| TABLE_NAME | = lv_table_name | |
| SIGNI | = lv_signi | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| ERROR = 2 | ||
| . " UPDATE_STATS | ||
ABAP code using 7.40 inline data declarations to call FM UPDATE_STATS
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 TABNAME FROM DD02L INTO @DATA(ld_table_name). | ||||
| "SELECT single SIGNI FROM DBSTATC INTO @DATA(ld_signi). | ||||
Search for further information about these or an SAP related objects