SAP TV_GET_IR_FROM_BUFFER Function Module for Zinskurvenstützstellen aus Marktdatenpuffer holen









TV_GET_IR_FROM_BUFFER is a standard tv get ir from buffer SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Zinskurvenstützstellen aus Marktdatenpuffer holen 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 tv get ir from buffer FM, simply by entering the name TV_GET_IR_FROM_BUFFER into the relevant SAP transaction such as SE37 or SE38.

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



Function TV_GET_IR_FROM_BUFFER 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 'TV_GET_IR_FROM_BUFFER'"Zinskurvenstützstellen aus Marktdatenpuffer holen
EXPORTING
KONDDATUM = "Konditionsdatum d. Zinskurve
* SZENARIO = ' ' "Szenario d. Zinskurve
SZKART = "Zinskurvenart
WAEHRUNG = "Währung der Zinskurve
* I_MSEG = "Marktdatenparameter

TABLES
E_VTVSZIWE = "Ausgabestruktur der Zinsstützstellen
* E_MESSAGE = "Application Log: Table with Messages

EXCEPTIONS
NO_DATA = 1 NOT_F_SZENARIO = 2 NO_INITIALIZATION = 3
.



IMPORTING Parameters details for TV_GET_IR_FROM_BUFFER

KONDDATUM - Konditionsdatum d. Zinskurve

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

SZENARIO - Szenario d. Zinskurve

Data type: VTVSZKO-SZENARI
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

SZKART - Zinskurvenart

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

WAEHRUNG - Währung der Zinskurve

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

I_MSEG - Marktdatenparameter

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

TABLES Parameters details for TV_GET_IR_FROM_BUFFER

E_VTVSZIWE - Ausgabestruktur der Zinsstützstellen

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

E_MESSAGE - Application Log: Table with Messages

Data type: BAL_T_MSG
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

NO_DATA - Währung nicht gefunden

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

NOT_F_SZENARIO - Szenario nicht gefunden

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

NO_INITIALIZATION - Puffer nicht initialisiert

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

Copy and paste ABAP code example for TV_GET_IR_FROM_BUFFER 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_no_data  TYPE STRING, "   
lv_konddatum  TYPE VTVSZVOLA-DKOND, "   
lt_e_vtvsziwe  TYPE STANDARD TABLE OF VTVSZIWE, "   
lv_szenario  TYPE VTVSZKO-SZENARI, "   SPACE
lt_e_message  TYPE STANDARD TABLE OF BAL_T_MSG, "   
lv_not_f_szenario  TYPE BAL_T_MSG, "   
lv_szkart  TYPE JBD11-SZKART, "   
lv_no_initialization  TYPE JBD11, "   
lv_waehrung  TYPE T001-WAERS, "   
lv_i_mseg  TYPE JBRMSEG. "   

  CALL FUNCTION 'TV_GET_IR_FROM_BUFFER'  "Zinskurvenstützstellen aus Marktdatenpuffer holen
    EXPORTING
         KONDDATUM = lv_konddatum
         SZENARIO = lv_szenario
         SZKART = lv_szkart
         WAEHRUNG = lv_waehrung
         I_MSEG = lv_i_mseg
    TABLES
         E_VTVSZIWE = lt_e_vtvsziwe
         E_MESSAGE = lt_e_message
    EXCEPTIONS
        NO_DATA = 1
        NOT_F_SZENARIO = 2
        NO_INITIALIZATION = 3
. " TV_GET_IR_FROM_BUFFER




ABAP code using 7.40 inline data declarations to call FM TV_GET_IR_FROM_BUFFER

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 DKOND FROM VTVSZVOLA INTO @DATA(ld_konddatum).
 
 
"SELECT single SZENARI FROM VTVSZKO INTO @DATA(ld_szenario).
DATA(ld_szenario) = ' '.
 
 
 
"SELECT single SZKART FROM JBD11 INTO @DATA(ld_szkart).
 
 
"SELECT single WAERS FROM T001 INTO @DATA(ld_waehrung).
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!