SAP RM_VAKO_SHIFT_FOR_RF Function Module for Norm Scaled Shift (Standard Variance) For Risk Factors

Search SAP Function Modules

RM_VAKO_SHIFT_FOR_RF is a standard rm vako shift for rf SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Norm Scaled Shift (Standard Variance) For Risk Factors 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 rm vako shift for rf FM, simply by entering the name RM_VAKO_SHIFT_FOR_RF into the relevant SAP transaction such as SE37 or SE38.

Function Group: RMTVVK
Program Name: SAPLRMTVVK
Main Program: SAPLRMTVVK
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RM_VAKO_SHIFT_FOR_RF 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 'RM_VAKO_SHIFT_FOR_RF'"Norm Scaled Shift (Standard Variance) For Risk Factors
  EXPORTING
   I_VDATUM =  "Date on Which Volatility Valid
   I_VOLART =  "Volatility Type
   I_RFNAME =  "
*  I_KONFIDENZ =  "Confidence Level
   I_HALTEDAUER =  "Holding Period
*  I_KALID =  "Factory Calendar

 IMPORTING
   E_SHIFT =  "Shift Calculated
   E_SAMPTYP =  "

EXCEPTIONS
   NO_VOLA_DEFINITION = 1    NO_VOLA_VALUE = 2    CANNOT_SCALE_UP = 3 

.

IMPORTING Parameters details for RM_VAKO_SHIFT_FOR_RF

I_VDATUM - Date on Which Volatility Valid

Data type: ATIVO-DATAB
Optional: No
Call by Reference: No ( called with pass by value option)

I_VOLART - Volatility Type

Data type: ATVO1-VOLART
Optional: No
Call by Reference: No ( called with pass by value option)

I_RFNAME -

Data type: ATRF-RFNAME
Optional: No
Call by Reference: No ( called with pass by value option)

I_KONFIDENZ - Confidence Level

Data type: ATVO3-KNIVEAU
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_HALTEDAUER - Holding Period

Data type: JBRIHSDEF-UNWIND
Optional: No
Call by Reference: No ( called with pass by value option)

I_KALID - Factory Calendar

Data type: JBRIHSDEF-KALENDER
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for RM_VAKO_SHIFT_FOR_RF

E_SHIFT - Shift Calculated

Data type: F
Optional: No
Call by Reference: No ( called with pass by value option)

E_SAMPTYP -

Data type: ATVO3-SAMPLETYP
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NO_VOLA_DEFINITION - No Master Data

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_VOLA_VALUE - No Movement Types

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

CANNOT_SCALE_UP -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for RM_VAKO_SHIFT_FOR_RF 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.

ABAP code using 7.40 inline data declarations to call FM RM_VAKO_SHIFT_FOR_RF

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