SAP FVD_PAYMENT_GET_SUSP_BY_REASON Function Module for Creates Overpayment with Matching Overpayment Reason









FVD_PAYMENT_GET_SUSP_BY_REASON is a standard fvd payment get susp by reason SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Creates Overpayment with Matching Overpayment Reason 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 fvd payment get susp by reason FM, simply by entering the name FVD_PAYMENT_GET_SUSP_BY_REASON into the relevant SAP transaction such as SE37 or SE38.

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



Function FVD_PAYMENT_GET_SUSP_BY_REASON 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 'FVD_PAYMENT_GET_SUSP_BY_REASON'"Creates Overpayment with Matching Overpayment Reason
  EXPORTING
   I_TAB_RANGE_BUKRS =  "Table Type for Range for Company Code
   I_TAB_RANGE_RANL =  "Table Type for Range for RANL
   I_TAB_RANGE_KUNNR =  "Table Type for Customer Range
   I_TAB_RANGE_REASONTYPE =  "Table Type for Range for REASONTYPE
*  I_LOGHANDLE =  "Application Log: Log Handle

 IMPORTING
   E_TAB_BSID =  "Table Type for Table BSID
   E_TAB_VDBEKI =  "Table Type for Table VDBEKI
   E_TAB_VDBEPI =  "Table Type for Table VDBEPI

EXCEPTIONS
   NO_SUSPENSE_POSTINGS_FOUND = 1    ERROR_READING_VDBEKI_VDBEPI = 2
.



IMPORTING Parameters details for FVD_PAYMENT_GET_SUSP_BY_REASON

I_TAB_RANGE_BUKRS - Table Type for Range for Company Code

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

I_TAB_RANGE_RANL - Table Type for Range for RANL

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

I_TAB_RANGE_KUNNR - Table Type for Customer Range

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

I_TAB_RANGE_REASONTYPE - Table Type for Range for REASONTYPE

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

I_LOGHANDLE - Application Log: Log Handle

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

EXPORTING Parameters details for FVD_PAYMENT_GET_SUSP_BY_REASON

E_TAB_BSID - Table Type for Table BSID

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

E_TAB_VDBEKI - Table Type for Table VDBEKI

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

E_TAB_VDBEPI - Table Type for Table VDBEPI

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

EXCEPTIONS details

NO_SUSPENSE_POSTINGS_FOUND -

Data type:
Optional: No
Call by Reference: Yes

ERROR_READING_VDBEKI_VDBEPI -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FVD_PAYMENT_GET_SUSP_BY_REASON 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_tab_bsid  TYPE TRTY_BSID, "   
lv_i_tab_range_bukrs  TYPE TRTY_BUKRS_RANGE, "   
lv_no_suspense_postings_found  TYPE TRTY_BUKRS_RANGE, "   
lv_e_tab_vdbeki  TYPE TRTY_VDBEKI, "   
lv_i_tab_range_ranl  TYPE TRTY_RANL_RANGE, "   
lv_error_reading_vdbeki_vdbepi  TYPE TRTY_RANL_RANGE, "   
lv_e_tab_vdbepi  TYPE TRTY_VDBEPI, "   
lv_i_tab_range_kunnr  TYPE TRTY_CUST_RANGE, "   
lv_i_tab_range_reasontype  TYPE TRTY_REASONTYPE_RANGE, "   
lv_i_loghandle  TYPE BALLOGHNDL. "   

  CALL FUNCTION 'FVD_PAYMENT_GET_SUSP_BY_REASON'  "Creates Overpayment with Matching Overpayment Reason
    EXPORTING
         I_TAB_RANGE_BUKRS = lv_i_tab_range_bukrs
         I_TAB_RANGE_RANL = lv_i_tab_range_ranl
         I_TAB_RANGE_KUNNR = lv_i_tab_range_kunnr
         I_TAB_RANGE_REASONTYPE = lv_i_tab_range_reasontype
         I_LOGHANDLE = lv_i_loghandle
    IMPORTING
         E_TAB_BSID = lv_e_tab_bsid
         E_TAB_VDBEKI = lv_e_tab_vdbeki
         E_TAB_VDBEPI = lv_e_tab_vdbepi
    EXCEPTIONS
        NO_SUSPENSE_POSTINGS_FOUND = 1
        ERROR_READING_VDBEKI_VDBEPI = 2
. " FVD_PAYMENT_GET_SUSP_BY_REASON




ABAP code using 7.40 inline data declarations to call FM FVD_PAYMENT_GET_SUSP_BY_REASON

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!