SAP GET_DUNNING_CUSTOMIZING Function Module for
GET_DUNNING_CUSTOMIZING is a standard get dunning customizing 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 customizing FM, simply by entering the name GET_DUNNING_CUSTOMIZING 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_CUSTOMIZING 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_CUSTOMIZING'".
EXPORTING
I_MHNK = "Dunning Notice Header
IMPORTING
E_T001 = "Company Codes
E_T021M = "
E_T047 = "
E_T047A = "Dunning Procedure
E_T047B = "Dunning levels
E_T047C = "Dunning Charges
E_T047D = "
E_T047E = "
E_T047I = "Standard texts for dunning notices
E_T056Z = "Interest Calculation
CHANGING
C_F150D = "
EXCEPTIONS
PARAM_ERROR_T001 = 1 PARAM_ERROR_T047 = 2 PARAM_ERROR_T047A = 3 PARAM_ERROR_T047B = 4 PARAM_ERROR_T047D = 5 PARAM_ERROR_T047E = 6
IMPORTING Parameters details for GET_DUNNING_CUSTOMIZING
I_MHNK - Dunning Notice Header
Data type: MHNKOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for GET_DUNNING_CUSTOMIZING
E_T001 - Company Codes
Data type: T001Optional: No
Call by Reference: No ( called with pass by value option)
E_T021M -
Data type: T021MOptional: No
Call by Reference: No ( called with pass by value option)
E_T047 -
Data type: T047Optional: No
Call by Reference: No ( called with pass by value option)
E_T047A - Dunning Procedure
Data type: T047AOptional: No
Call by Reference: No ( called with pass by value option)
E_T047B - Dunning levels
Data type: T047BOptional: No
Call by Reference: No ( called with pass by value option)
E_T047C - Dunning Charges
Data type: T047COptional: No
Call by Reference: No ( called with pass by value option)
E_T047D -
Data type: T047DOptional: No
Call by Reference: No ( called with pass by value option)
E_T047E -
Data type: T047EOptional: No
Call by Reference: No ( called with pass by value option)
E_T047I - Standard texts for dunning notices
Data type: T047IOptional: No
Call by Reference: No ( called with pass by value option)
E_T056Z - Interest Calculation
Data type: T056ZOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for GET_DUNNING_CUSTOMIZING
C_F150D -
Data type: F150DOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
PARAM_ERROR_T001 - No Suitable Entry Found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARAM_ERROR_T047 - No Suitable Entry Found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARAM_ERROR_T047A - No Suitable Entry Found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARAM_ERROR_T047B - No Suitable Entry Found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARAM_ERROR_T047D - No Suitable Entry Found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARAM_ERROR_T047E - No Suitable Entry Found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GET_DUNNING_CUSTOMIZING 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_t001 | TYPE T001, " | |||
| lv_i_mhnk | TYPE MHNK, " | |||
| lv_c_f150d | TYPE F150D, " | |||
| lv_param_error_t001 | TYPE F150D, " | |||
| lv_e_t021m | TYPE T021M, " | |||
| lv_e_t047 | TYPE T047, " | |||
| lv_param_error_t047 | TYPE T047, " | |||
| lv_e_t047a | TYPE T047A, " | |||
| lv_param_error_t047a | TYPE T047A, " | |||
| lv_e_t047b | TYPE T047B, " | |||
| lv_param_error_t047b | TYPE T047B, " | |||
| lv_e_t047c | TYPE T047C, " | |||
| lv_param_error_t047d | TYPE T047C, " | |||
| lv_e_t047d | TYPE T047D, " | |||
| lv_param_error_t047e | TYPE T047D, " | |||
| lv_e_t047e | TYPE T047E, " | |||
| lv_e_t047i | TYPE T047I, " | |||
| lv_e_t056z | TYPE T056Z. " |
|   CALL FUNCTION 'GET_DUNNING_CUSTOMIZING' " |
| EXPORTING | ||
| I_MHNK | = lv_i_mhnk | |
| IMPORTING | ||
| E_T001 | = lv_e_t001 | |
| E_T021M | = lv_e_t021m | |
| E_T047 | = lv_e_t047 | |
| E_T047A | = lv_e_t047a | |
| E_T047B | = lv_e_t047b | |
| E_T047C | = lv_e_t047c | |
| E_T047D | = lv_e_t047d | |
| E_T047E | = lv_e_t047e | |
| E_T047I | = lv_e_t047i | |
| E_T056Z | = lv_e_t056z | |
| CHANGING | ||
| C_F150D | = lv_c_f150d | |
| EXCEPTIONS | ||
| PARAM_ERROR_T001 = 1 | ||
| PARAM_ERROR_T047 = 2 | ||
| PARAM_ERROR_T047A = 3 | ||
| PARAM_ERROR_T047B = 4 | ||
| PARAM_ERROR_T047D = 5 | ||
| PARAM_ERROR_T047E = 6 | ||
| . " GET_DUNNING_CUSTOMIZING | ||
ABAP code using 7.40 inline data declarations to call FM GET_DUNNING_CUSTOMIZING
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