SAP FKK_GET_OLD_NEW_VERSION Function Module for
FKK_GET_OLD_NEW_VERSION is a standard fkk get old 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 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 fkk get old new version FM, simply by entering the name FKK_GET_OLD_NEW_VERSION into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKK_RARE_USED
Program Name: SAPLFKK_RARE_USED
Main Program: SAPLFKK_RARE_USED
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function FKK_GET_OLD_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 'FKK_GET_OLD_NEW_VERSION'".
EXPORTING
I_ADDON_ID = "
IMPORTING
E_OLD_REL = "
E_NEW_REL = "
EXCEPTIONS
ADDONID_NOT_FOUND = 1
IMPORTING Parameters details for FKK_GET_OLD_NEW_VERSION
I_ADDON_ID -
Data type: AVERS-ADDONIDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FKK_GET_OLD_NEW_VERSION
E_OLD_REL -
Data type: AVERS-ADDONRLOptional: No
Call by Reference: Yes
E_NEW_REL -
Data type: AVERS-ADDONRLOptional: No
Call by Reference: Yes
EXCEPTIONS details
ADDONID_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FKK_GET_OLD_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_old_rel | TYPE AVERS-ADDONRL, " | |||
lv_i_addon_id | TYPE AVERS-ADDONID, " | |||
lv_addonid_not_found | TYPE AVERS, " | |||
lv_e_new_rel | TYPE AVERS-ADDONRL. " |
  CALL FUNCTION 'FKK_GET_OLD_NEW_VERSION' " |
EXPORTING | ||
I_ADDON_ID | = lv_i_addon_id | |
IMPORTING | ||
E_OLD_REL | = lv_e_old_rel | |
E_NEW_REL | = lv_e_new_rel | |
EXCEPTIONS | ||
ADDONID_NOT_FOUND = 1 | ||
. " FKK_GET_OLD_NEW_VERSION |
ABAP code using 7.40 inline data declarations to call FM FKK_GET_OLD_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."SELECT single ADDONRL FROM AVERS INTO @DATA(ld_e_old_rel). | ||||
"SELECT single ADDONID FROM AVERS INTO @DATA(ld_i_addon_id). | ||||
"SELECT single ADDONRL FROM AVERS INTO @DATA(ld_e_new_rel). | ||||
Search for further information about these or an SAP related objects