SAP FVD_PAY_OBJ_APP_BEPP_SUSPENSE Function Module for Create Suspense BEPPs to Suspend the Payment Segments

Search SAP Function Modules

FVD_PAY_OBJ_APP_BEPP_SUSPENSE is a standard fvd pay obj app bepp suspense SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create Suspense BEPPs to Suspend the Payment Segments 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 pay obj app bepp suspense FM, simply by entering the name FVD_PAY_OBJ_APP_BEPP_SUSPENSE into the relevant SAP transaction such as SE37 or SE38.

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

Function FVD_PAY_OBJ_APP_BEPP_SUSPENSE 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_PAY_OBJ_APP_BEPP_SUSPENSE'"Create Suspense BEPPs to Suspend the Payment Segments
  EXPORTING
   I_SUSPREASON =  " Grund für Suspense Buchung
   I_STR_VDARL =  "Loan
*  I_ORG_AMOUNT =  "Amount in Document Currency
*  I_ORG_AMOUNT_LC =  "Amount in Local Currency

CHANGING
   C_TAB_PAY_SEG =  "Table Type For Table BSSBSEG
   C_TAB_POSTVDBEPP =  "Transaction Data - Plan Item
   C_TAB_POSTADDBEPP =  "Additional Information on VDBEPP
*  C_TAB_POSTADDBEPP_ADD =  "Table Type for ADDBEPP_ADD

EXCEPTIONS
   BEPP_NOT_APPENDED = 1    INCONSISTENCY_ERROR = 2 

.

IMPORTING Parameters details for FVD_PAY_OBJ_APP_BEPP_SUSPENSE

I_SUSPREASON - Grund für Suspense Buchung

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

I_STR_VDARL - Loan

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

I_ORG_AMOUNT - Amount in Document Currency

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

I_ORG_AMOUNT_LC - Amount in Local Currency

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

CHANGING Parameters details for FVD_PAY_OBJ_APP_BEPP_SUSPENSE

C_TAB_PAY_SEG - Table Type For Table BSSBSEG

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

C_TAB_POSTVDBEPP - Transaction Data - Plan Item

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

C_TAB_POSTADDBEPP - Additional Information on VDBEPP

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

C_TAB_POSTADDBEPP_ADD - Table Type for ADDBEPP_ADD

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

EXCEPTIONS details

BEPP_NOT_APPENDED -

Data type:
Optional: No
Call by Reference: Yes

INCONSISTENCY_ERROR - Inconsistent status

Data type:
Optional: No
Call by Reference: Yes

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

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