SAP TB_IRATE_UPDATERULE_GET Function Module for Determine Update Frequency









TB_IRATE_UPDATERULE_GET is a standard tb irate updaterule get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine Update Frequency 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 tb irate updaterule get FM, simply by entering the name TB_IRATE_UPDATERULE_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function TB_IRATE_UPDATERULE_GET 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 'TB_IRATE_UPDATERULE_GET'"Determine Update Frequency
  EXPORTING
   PI_VALUEDATE_SHIFT =  "Number of days for shift in calculation of value date
   PI_DUEDATE_SHIFT =  "Anzahl der Tage bei rel. Ermittlung des Fälligkeitstermins
   PI_VALUEDATE_METHOD =  "Method for determining the next value date
   PI_DUEDATE_METHOD =  "Method for determining the next due date

 IMPORTING
   PE_UPDATEMETHOD =  "Update for Calculation/Due Date for Interest
   PE_DAYSHIFT =  "Verschiebung des Fälligkeitstermins gegen Zinsperiodenende

EXCEPTIONS
   GET_FAILED = 1    INVALID_PARAMETERS = 2
.



IMPORTING Parameters details for TB_IRATE_UPDATERULE_GET

PI_VALUEDATE_SHIFT - Number of days for shift in calculation of value date

Data type: TB_AVGSTAG
Optional: No
Call by Reference: Yes

PI_DUEDATE_SHIFT - Anzahl der Tage bei rel. Ermittlung des Fälligkeitstermins

Data type: TB_AFGSTAG
Optional: No
Call by Reference: Yes

PI_VALUEDATE_METHOD - Method for determining the next value date

Data type: TB_SVMETH
Optional: No
Call by Reference: Yes

PI_DUEDATE_METHOD - Method for determining the next due date

Data type: TB_SFMETH
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for TB_IRATE_UPDATERULE_GET

PE_UPDATEMETHOD - Update for Calculation/Due Date for Interest

Data type: TBFORTVERTZ
Optional: No
Call by Reference: Yes

PE_DAYSHIFT - Verschiebung des Fälligkeitstermins gegen Zinsperiodenende

Data type: TBVFAETZ
Optional: No
Call by Reference: Yes

EXCEPTIONS details

GET_FAILED - Determination Failed

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

INVALID_PARAMETERS - invalide Parameterkombination

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

Copy and paste ABAP code example for TB_IRATE_UPDATERULE_GET 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_get_failed  TYPE STRING, "   
lv_pe_updatemethod  TYPE TBFORTVERTZ, "   
lv_pi_valuedate_shift  TYPE TB_AVGSTAG, "   
lv_pe_dayshift  TYPE TBVFAETZ, "   
lv_pi_duedate_shift  TYPE TB_AFGSTAG, "   
lv_invalid_parameters  TYPE TB_AFGSTAG, "   
lv_pi_valuedate_method  TYPE TB_SVMETH, "   
lv_pi_duedate_method  TYPE TB_SFMETH. "   

  CALL FUNCTION 'TB_IRATE_UPDATERULE_GET'  "Determine Update Frequency
    EXPORTING
         PI_VALUEDATE_SHIFT = lv_pi_valuedate_shift
         PI_DUEDATE_SHIFT = lv_pi_duedate_shift
         PI_VALUEDATE_METHOD = lv_pi_valuedate_method
         PI_DUEDATE_METHOD = lv_pi_duedate_method
    IMPORTING
         PE_UPDATEMETHOD = lv_pe_updatemethod
         PE_DAYSHIFT = lv_pe_dayshift
    EXCEPTIONS
        GET_FAILED = 1
        INVALID_PARAMETERS = 2
. " TB_IRATE_UPDATERULE_GET




ABAP code using 7.40 inline data declarations to call FM TB_IRATE_UPDATERULE_GET

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



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!