SAP RSDB2A_TABSTAT_NEW_VERSION Function Module for creates a new version in table RSDB2A_TABSTAT
RSDB2A_TABSTAT_NEW_VERSION is a standard rsdb2a tabstat new version SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for creates a new version in table RSDB2A_TABSTAT 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 rsdb2a tabstat new version FM, simply by entering the name RSDB2A_TABSTAT_NEW_VERSION into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSDB2A
Program Name: SAPLRSDB2A
Main Program: SAPLRSDB2A
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSDB2A_TABSTAT_NEW_VERSION 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 'RSDB2A_TABSTAT_NEW_VERSION'"creates a new version in table RSDB2A_TABSTAT.
IMPORTING
E_VERSION_NEW = "
E_VERSION_CARD = "
EXCEPTIONS
VERSION_NOT_CREATED = 1
EXPORTING Parameters details for RSDB2A_TABSTAT_NEW_VERSION
E_VERSION_NEW -
Data type: IOptional: No
Call by Reference: Yes
E_VERSION_CARD -
Data type: IOptional: No
Call by Reference: Yes
EXCEPTIONS details
VERSION_NOT_CREATED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RSDB2A_TABSTAT_NEW_VERSION 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_e_version_new | TYPE I, " | |||
| lv_version_not_created | TYPE I, " | |||
| lv_e_version_card | TYPE I. " |
|   CALL FUNCTION 'RSDB2A_TABSTAT_NEW_VERSION' "creates a new version in table RSDB2A_TABSTAT |
| IMPORTING | ||
| E_VERSION_NEW | = lv_e_version_new | |
| E_VERSION_CARD | = lv_e_version_card | |
| EXCEPTIONS | ||
| VERSION_NOT_CREATED = 1 | ||
| . " RSDB2A_TABSTAT_NEW_VERSION | ||
ABAP code using 7.40 inline data declarations to call FM RSDB2A_TABSTAT_NEW_VERSION
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