SAP GET_DUNNING_DATA_CUST_VEND Function Module for









GET_DUNNING_DATA_CUST_VEND is a standard get dunning data cust vend SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 get dunning data cust vend FM, simply by entering the name GET_DUNNING_DATA_CUST_VEND into the relevant SAP transaction such as SE37 or SE38.

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



Function GET_DUNNING_DATA_CUST_VEND 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 'GET_DUNNING_DATA_CUST_VEND'"
  EXPORTING
   I_T001 =  "Company Code
   I_MHNK =  "Dunning Notice Header

 IMPORTING
   E_ADRS =  "Address Data
   E_LFB1 =  "Vendors
   E_KNB5 =  "Customers
   E_LFB5 =  "Vendors
   E_UADRS =  "Address Data
   E_SADR =  "Address Data
   E_T001S =  "Accounting Clerks
   E_FSABE =  "Accounting clerk address data
   E_LANGU =  "Language Key
   E_KNA1 =  "Customers
   E_LFA1 =  "Vendors
   E_KNB1 =  "Customers

CHANGING
   C_F150D =  "

TABLES
*  T_MHND =  "Dunning Line Items
.



IMPORTING Parameters details for GET_DUNNING_DATA_CUST_VEND

I_T001 - Company Code

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

I_MHNK - Dunning Notice Header

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

EXPORTING Parameters details for GET_DUNNING_DATA_CUST_VEND

E_ADRS - Address Data

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

E_LFB1 - Vendors

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

E_KNB5 - Customers

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

E_LFB5 - Vendors

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

E_UADRS - Address Data

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

E_SADR - Address Data

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

E_T001S - Accounting Clerks

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

E_FSABE - Accounting clerk address data

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

E_LANGU - Language Key

Data type: SY-LANGU
Optional: No
Call by Reference: No ( called with pass by value option)

E_KNA1 - Customers

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

E_LFA1 - Vendors

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

E_KNB1 - Customers

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

CHANGING Parameters details for GET_DUNNING_DATA_CUST_VEND

C_F150D -

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

TABLES Parameters details for GET_DUNNING_DATA_CUST_VEND

T_MHND - Dunning Line Items

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

Copy and paste ABAP code example for GET_DUNNING_DATA_CUST_VEND 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_adrs  TYPE ADRS, "   
lv_i_t001  TYPE T001, "   
lt_t_mhnd  TYPE STANDARD TABLE OF MHND, "   
lv_c_f150d  TYPE F150D, "   
lv_e_lfb1  TYPE LFB1, "   
lv_e_knb5  TYPE KNB5, "   
lv_e_lfb5  TYPE LFB5, "   
lv_i_mhnk  TYPE MHNK, "   
lv_e_uadrs  TYPE ADRS, "   
lv_e_sadr  TYPE SADR, "   
lv_e_t001s  TYPE T001S, "   
lv_e_fsabe  TYPE FSABE, "   
lv_e_langu  TYPE SY-LANGU, "   
lv_e_kna1  TYPE KNA1, "   
lv_e_lfa1  TYPE LFA1, "   
lv_e_knb1  TYPE KNB1. "   

  CALL FUNCTION 'GET_DUNNING_DATA_CUST_VEND'  "
    EXPORTING
         I_T001 = lv_i_t001
         I_MHNK = lv_i_mhnk
    IMPORTING
         E_ADRS = lv_e_adrs
         E_LFB1 = lv_e_lfb1
         E_KNB5 = lv_e_knb5
         E_LFB5 = lv_e_lfb5
         E_UADRS = lv_e_uadrs
         E_SADR = lv_e_sadr
         E_T001S = lv_e_t001s
         E_FSABE = lv_e_fsabe
         E_LANGU = lv_e_langu
         E_KNA1 = lv_e_kna1
         E_LFA1 = lv_e_lfa1
         E_KNB1 = lv_e_knb1
    CHANGING
         C_F150D = lv_c_f150d
    TABLES
         T_MHND = lt_t_mhnd
. " GET_DUNNING_DATA_CUST_VEND




ABAP code using 7.40 inline data declarations to call FM GET_DUNNING_DATA_CUST_VEND

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


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!