SAP PAYMENT_SCHEDULE Function Module for Display/Print Payment Plan









PAYMENT_SCHEDULE is a standard payment schedule SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Display/Print Payment Plan 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 payment schedule FM, simply by entering the name PAYMENT_SCHEDULE into the relevant SAP transaction such as SE37 or SE38.

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



Function PAYMENT_SCHEDULE 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 'PAYMENT_SCHEDULE'"Display/Print Payment Plan
EXPORTING
* I_RANTYP = ' ' "Contract Type
I_GSART = "Product Type
* I_BEPP_SUPPLIED = ' ' "Single-Character Flag
I_TAB_BEPP = "Table Type for Structure VZZBEPP
* I_TAB_VDARL = "Table Type for Table VDARL
* I_STR_KOKO = "Table Condition Header

IMPORTING
E_PAYMENT_SCHEDULE = "Loan Payment Plan

CHANGING
* C_TAB_KOPO = "Table Type for Table VVZZKOPO

EXCEPTIONS
NOT_A_LOAN = 1 CASH_FLOW_OTHERS = 10 KOKO_OR_VDARL_MISSING = 2 NO_DISBURSEMENT_FOUND = 3 KEINE_TILGUNGSKONDITIONEN = 4 LAUFZEITENDE_FEHLT = 5 LAUFZEITENDE_NICHT_ERMITTELBAR = 6 LAUFZEIT_ODER_RATE_FEHLT = 7 NEGATIVE_TILGUNG_AUFGETRETEN = 8 BCD_FIELD_OVERFLOW = 9
.



IMPORTING Parameters details for PAYMENT_SCHEDULE

I_RANTYP - Contract Type

Data type: RLFVZZ-RANTYP
Default: SPACE
Optional: No
Call by Reference: No ( called with pass by value option)

I_GSART - Product Type

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

I_BEPP_SUPPLIED - Single-Character Flag

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

I_TAB_BEPP - Table Type for Structure VZZBEPP

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

I_TAB_VDARL - Table Type for Table VDARL

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

I_STR_KOKO - Table Condition Header

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

EXPORTING Parameters details for PAYMENT_SCHEDULE

E_PAYMENT_SCHEDULE - Loan Payment Plan

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

CHANGING Parameters details for PAYMENT_SCHEDULE

C_TAB_KOPO - Table Type for Table VVZZKOPO

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

EXCEPTIONS details

NOT_A_LOAN - Das Produkt wird nicht bearbeitet, da es sich nicht um ein Darlehen handelt.

Data type:
Optional: No
Call by Reference: Yes

CASH_FLOW_OTHERS - Bei der Cash-Flow-Berechnung trat die Meldung 'CASH_FLOW_OTHERS' auf

Data type:
Optional: No
Call by Reference: Yes

KOKO_OR_VDARL_MISSING - I_TAB_KOKO oder I_TAB_VDARL, sowie vzzbepp wurden nicht angegeben.

Data type:
Optional: No
Call by Reference: Yes

NO_DISBURSEMENT_FOUND - Keine Auszahlung vorhanden

Data type:
Optional: No
Call by Reference: Yes

KEINE_TILGUNGSKONDITIONEN - Bei der Cash-Flow-Berechnung trat die Meldung 'KEINE_TILGUNGSKONDITIONEN' auf

Data type:
Optional: No
Call by Reference: Yes

LAUFZEITENDE_FEHLT - Bei der Cash-Flow-Berechnung trat die Meldung 'LAUFZEITENDE_FEHLT' auf

Data type:
Optional: No
Call by Reference: Yes

LAUFZEITENDE_NICHT_ERMITTELBAR - Bei der Cash-Flow-Berechnung trat die Meldung 'LAUFZEITENDE_NICHT_ERMITTELBAR'

Data type:
Optional: No
Call by Reference: Yes

LAUFZEIT_ODER_RATE_FEHLT - Bei der Cash-Flow-Berechnung trat die Meldung 'LAUFZEIT_ODER_RATE_FEHLT' auf

Data type:
Optional: No
Call by Reference: Yes

NEGATIVE_TILGUNG_AUFGETRETEN - Bei der Cash-Flow-Berechnung trat die Meldung 'NEGATIVE_TILGUNG_AUFGETRETEN' au

Data type:
Optional: No
Call by Reference: Yes

BCD_FIELD_OVERFLOW - Bei der Cash-Flow-Berechnung trat die Meldung 'BCD_FIELD_OVERFLOW' auf

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PAYMENT_SCHEDULE 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_i_rantyp  TYPE RLFVZZ-RANTYP, "   SPACE
lv_c_tab_kopo  TYPE TRTY_VVZZKOPO, "   
lv_not_a_loan  TYPE TRTY_VVZZKOPO, "   
lv_e_payment_schedule  TYPE TRTY_RPAY_SCHEDULE, "   
lv_cash_flow_others  TYPE TRTY_RPAY_SCHEDULE, "   
lv_i_gsart  TYPE VVSART, "   
lv_koko_or_vdarl_missing  TYPE VVSART, "   
lv_i_bepp_supplied  TYPE CHAR1, "   SPACE
lv_no_disbursement_found  TYPE CHAR1, "   
lv_i_tab_bepp  TYPE TRTY_VZZBEPP, "   
lv_keine_tilgungskonditionen  TYPE TRTY_VZZBEPP, "   
lv_i_tab_vdarl  TYPE VDARL, "   
lv_laufzeitende_fehlt  TYPE VDARL, "   
lv_i_str_koko  TYPE VZZKOKO, "   
lv_laufzeitende_nicht_ermittelbar  TYPE VZZKOKO, "   
lv_laufzeit_oder_rate_fehlt  TYPE VZZKOKO, "   
lv_negative_tilgung_aufgetreten  TYPE VZZKOKO, "   
lv_bcd_field_overflow  TYPE VZZKOKO. "   

  CALL FUNCTION 'PAYMENT_SCHEDULE'  "Display/Print Payment Plan
    EXPORTING
         I_RANTYP = lv_i_rantyp
         I_GSART = lv_i_gsart
         I_BEPP_SUPPLIED = lv_i_bepp_supplied
         I_TAB_BEPP = lv_i_tab_bepp
         I_TAB_VDARL = lv_i_tab_vdarl
         I_STR_KOKO = lv_i_str_koko
    IMPORTING
         E_PAYMENT_SCHEDULE = lv_e_payment_schedule
    CHANGING
         C_TAB_KOPO = lv_c_tab_kopo
    EXCEPTIONS
        NOT_A_LOAN = 1
        CASH_FLOW_OTHERS = 10
        KOKO_OR_VDARL_MISSING = 2
        NO_DISBURSEMENT_FOUND = 3
        KEINE_TILGUNGSKONDITIONEN = 4
        LAUFZEITENDE_FEHLT = 5
        LAUFZEITENDE_NICHT_ERMITTELBAR = 6
        LAUFZEIT_ODER_RATE_FEHLT = 7
        NEGATIVE_TILGUNG_AUFGETRETEN = 8
        BCD_FIELD_OVERFLOW = 9
. " PAYMENT_SCHEDULE




ABAP code using 7.40 inline data declarations to call FM PAYMENT_SCHEDULE

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 RANTYP FROM RLFVZZ INTO @DATA(ld_i_rantyp).
DATA(ld_i_rantyp) = ' '.
 
 
 
 
 
 
 
DATA(ld_i_bepp_supplied) = ' '.
 
 
 
 
 
 
 
 
 
 
 


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!