SAP ISU_MSG2DEVICE_CRE_BY_DUNNING Function Module for Create a message to device (internally triggered by dunning act. module)
ISU_MSG2DEVICE_CRE_BY_DUNNING is a standard isu msg2device cre by dunning 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 a message to device (internally triggered by dunning act. module) 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 isu msg2device cre by dunning FM, simply by entering the name ISU_MSG2DEVICE_CRE_BY_DUNNING into the relevant SAP transaction such as SE37 or SE38.
Function Group: EE_AMI_MSG_DUNN_ACT
Program Name: SAPLEE_AMI_MSG_DUNN_ACT
Main Program: SAPLEE_AMI_MSG_DUNN_ACT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_MSG2DEVICE_CRE_BY_DUNNING 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 'ISU_MSG2DEVICE_CRE_BY_DUNNING'"Create a message to device (internally triggered by dunning act. module).
EXPORTING
X_UPDATE = "Update / Productive run ('no simulation')
X_ACKEY = "Key of Dunning Activity
X_LANGU = "Language in connection with the contract account
X_TARGET_DEVICE = "Target device for messages created by dunning
IMPORTING
Y_AMI_MSG_ID = "Message ID
TABLES
T_FIMSG = "FI Messages
EXCEPTIONS
ERROR_MESSAGE = 1
IMPORTING Parameters details for ISU_MSG2DEVICE_CRE_BY_DUNNING
X_UPDATE - Update / Productive run ('no simulation')
Data type: COptional: No
Call by Reference: Yes
X_ACKEY - Key of Dunning Activity
Data type: ACKEY_KKOptional: No
Call by Reference: Yes
X_LANGU - Language in connection with the contract account
Data type: LANGU_ACCOptional: No
Call by Reference: Yes
X_TARGET_DEVICE - Target device for messages created by dunning
Data type: EAMI_DUNN_MSG_DEVOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ISU_MSG2DEVICE_CRE_BY_DUNNING
Y_AMI_MSG_ID - Message ID
Data type: E_AMI_MSG_IDOptional: No
Call by Reference: Yes
TABLES Parameters details for ISU_MSG2DEVICE_CRE_BY_DUNNING
T_FIMSG - FI Messages
Data type: FIMSGOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_MESSAGE - Error message occurred
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_MSG2DEVICE_CRE_BY_DUNNING 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: | ||||
| lt_t_fimsg | TYPE STANDARD TABLE OF FIMSG, " | |||
| lv_x_update | TYPE C, " | |||
| lv_y_ami_msg_id | TYPE E_AMI_MSG_ID, " | |||
| lv_error_message | TYPE E_AMI_MSG_ID, " | |||
| lv_x_ackey | TYPE ACKEY_KK, " | |||
| lv_x_langu | TYPE LANGU_ACC, " | |||
| lv_x_target_device | TYPE EAMI_DUNN_MSG_DEV. " |
|   CALL FUNCTION 'ISU_MSG2DEVICE_CRE_BY_DUNNING' "Create a message to device (internally triggered by dunning act. module) |
| EXPORTING | ||
| X_UPDATE | = lv_x_update | |
| X_ACKEY | = lv_x_ackey | |
| X_LANGU | = lv_x_langu | |
| X_TARGET_DEVICE | = lv_x_target_device | |
| IMPORTING | ||
| Y_AMI_MSG_ID | = lv_y_ami_msg_id | |
| TABLES | ||
| T_FIMSG | = lt_t_fimsg | |
| EXCEPTIONS | ||
| ERROR_MESSAGE = 1 | ||
| . " ISU_MSG2DEVICE_CRE_BY_DUNNING | ||
ABAP code using 7.40 inline data declarations to call FM ISU_MSG2DEVICE_CRE_BY_DUNNING
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