SAP FVD_DEFAULT_DB_READ_MHND Function Module for Default: Read Dunning Items









FVD_DEFAULT_DB_READ_MHND is a standard fvd default db read mhnd SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Default: Read Dunning Items 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 default db read mhnd FM, simply by entering the name FVD_DEFAULT_DB_READ_MHND into the relevant SAP transaction such as SE37 or SE38.

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



Function FVD_DEFAULT_DB_READ_MHND 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_DEFAULT_DB_READ_MHND'"Default: Read Dunning Items
EXPORTING
I_BUKRS = "Company Code
I_CONTRACT = "Contract Number
* I_DATE = "Current Date of Application Server
* I_OLD = "Boolean Variable (X=true, -=false, space=unknown)

IMPORTING
E_TAB_MHND = "Dunning Data

EXCEPTIONS
NO_ENTRY_FOUND = 1
.



IMPORTING Parameters details for FVD_DEFAULT_DB_READ_MHND

I_BUKRS - Company Code

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

I_CONTRACT - Contract Number

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

I_DATE - Current Date of Application Server

Data type: SY-DATUM
Optional: Yes
Call by Reference: Yes

I_OLD - Boolean Variable (X=true, -=false, space=unknown)

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

EXPORTING Parameters details for FVD_DEFAULT_DB_READ_MHND

E_TAB_MHND - Dunning Data

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

EXCEPTIONS details

NO_ENTRY_FOUND - No Entry Found

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FVD_DEFAULT_DB_READ_MHND 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_bukrs  TYPE BUKRS, "   
lv_e_tab_mhnd  TYPE TRTY_MHND, "   
lv_no_entry_found  TYPE TRTY_MHND, "   
lv_i_contract  TYPE RANL, "   
lv_i_date  TYPE SY-DATUM, "   
lv_i_old  TYPE BOOLEAN. "   

  CALL FUNCTION 'FVD_DEFAULT_DB_READ_MHND'  "Default: Read Dunning Items
    EXPORTING
         I_BUKRS = lv_i_bukrs
         I_CONTRACT = lv_i_contract
         I_DATE = lv_i_date
         I_OLD = lv_i_old
    IMPORTING
         E_TAB_MHND = lv_e_tab_mhnd
    EXCEPTIONS
        NO_ENTRY_FOUND = 1
. " FVD_DEFAULT_DB_READ_MHND




ABAP code using 7.40 inline data declarations to call FM FVD_DEFAULT_DB_READ_MHND

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 DATUM FROM SY INTO @DATA(ld_i_date).
 
 


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!