SAP SSFV_CREATE_KEYVERSION Function Module for
SSFV_CREATE_KEYVERSION is a standard ssfv create keyversion SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 ssfv create keyversion FM, simply by entering the name SSFV_CREATE_KEYVERSION into the relevant SAP transaction such as SE37 or SE38.
Function Group: SSFV
Program Name: SAPLSSFV
Main Program: SAPLSSFV
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SSFV_CREATE_KEYVERSION 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 'SSFV_CREATE_KEYVERSION'".
EXPORTING
IF_APPLIC = "
EXCEPTIONS
UNKNOWN_APPLICATION = 1 NO_AUTHORIZATION = 2 SSF_KRN_ERROR = 3 DATABASE_ERROR = 4
IMPORTING Parameters details for SSFV_CREATE_KEYVERSION
IF_APPLIC -
Data type: SSFAPPLOptional: No
Call by Reference: Yes
EXCEPTIONS details
UNKNOWN_APPLICATION -
Data type:Optional: No
Call by Reference: Yes
NO_AUTHORIZATION -
Data type:Optional: No
Call by Reference: Yes
SSF_KRN_ERROR -
Data type:Optional: No
Call by Reference: Yes
DATABASE_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SSFV_CREATE_KEYVERSION 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_if_applic | TYPE SSFAPPL, " | |||
| lv_unknown_application | TYPE SSFAPPL, " | |||
| lv_no_authorization | TYPE SSFAPPL, " | |||
| lv_ssf_krn_error | TYPE SSFAPPL, " | |||
| lv_database_error | TYPE SSFAPPL. " |
|   CALL FUNCTION 'SSFV_CREATE_KEYVERSION' " |
| EXPORTING | ||
| IF_APPLIC | = lv_if_applic | |
| EXCEPTIONS | ||
| UNKNOWN_APPLICATION = 1 | ||
| NO_AUTHORIZATION = 2 | ||
| SSF_KRN_ERROR = 3 | ||
| DATABASE_ERROR = 4 | ||
| . " SSFV_CREATE_KEYVERSION | ||
ABAP code using 7.40 inline data declarations to call FM SSFV_CREATE_KEYVERSION
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