SAP FVD_DEFAULT_DB_READ_TDDEFPROD Function Module for Default: Read Dunning Area for Product Type
FVD_DEFAULT_DB_READ_TDDEFPROD is a standard fvd default db read tddefprod 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 Area for Product Type 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 tddefprod FM, simply by entering the name FVD_DEFAULT_DB_READ_TDDEFPROD 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_TDDEFPROD 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_TDDEFPROD'"Default: Read Dunning Area for Product Type.
EXPORTING
I_BUKRS = "Company Code
I_GSART = "Product Type
IMPORTING
E_MABER = "Dunning Area
IMPORTING Parameters details for FVD_DEFAULT_DB_READ_TDDEFPROD
I_BUKRS - Company Code
Data type: VDARL-BUKRSOptional: No
Call by Reference: Yes
I_GSART - Product Type
Data type: VDARL-GSARTOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FVD_DEFAULT_DB_READ_TDDEFPROD
E_MABER - Dunning Area
Data type: TZPAB-MABEROptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FVD_DEFAULT_DB_READ_TDDEFPROD 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_maber | TYPE TZPAB-MABER, " | |||
| lv_i_bukrs | TYPE VDARL-BUKRS, " | |||
| lv_i_gsart | TYPE VDARL-GSART. " |
|   CALL FUNCTION 'FVD_DEFAULT_DB_READ_TDDEFPROD' "Default: Read Dunning Area for Product Type |
| EXPORTING | ||
| I_BUKRS | = lv_i_bukrs | |
| I_GSART | = lv_i_gsart | |
| IMPORTING | ||
| E_MABER | = lv_e_maber | |
| . " FVD_DEFAULT_DB_READ_TDDEFPROD | ||
ABAP code using 7.40 inline data declarations to call FM FVD_DEFAULT_DB_READ_TDDEFPROD
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 MABER FROM TZPAB INTO @DATA(ld_e_maber). | ||||
| "SELECT single BUKRS FROM VDARL INTO @DATA(ld_i_bukrs). | ||||
| "SELECT single GSART FROM VDARL INTO @DATA(ld_i_gsart). | ||||
Search for further information about these or an SAP related objects