SAP DG56_INTERFACE_ERR_MESSAGE Function Module for NOTRANSL: EHS: Versenden einer Fehlermeldung bei Abbruch SD_DATA
DG56_INTERFACE_ERR_MESSAGE is a standard dg56 interface err message SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: EHS: Versenden einer Fehlermeldung bei Abbruch SD_DATA 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 dg56 interface err message FM, simply by entering the name DG56_INTERFACE_ERR_MESSAGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: DG56
Program Name: SAPLDG56
Main Program: SAPLDG56
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DG56_INTERFACE_ERR_MESSAGE 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 'DG56_INTERFACE_ERR_MESSAGE'"NOTRANSL: EHS: Versenden einer Fehlermeldung bei Abbruch SD_DATA.
EXPORTING
I_ERROR_CODE = "Error code
I_REASON = "DDS: Reason/origin of delivery order
* I_INFO_FOR_ERROR_MAIL = "EHS: Data for Error Messages for SD - EHS Interface
IMPORTING
E_RECTYPE = "Recipient Type
E_RECNAME = "Recipient Name
E_DEST_SYSTEM = "Target Sys
E_DEST_CLIENT = "Target Client
TABLES
X_ERRORTEXTTAB = "DDS: Single-column text table (132 characters per line)
EXCEPTIONS
ERRORMAIL_SEND_FAILED = 1
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLDG56_001 DG: Determination of Relevant Shipping Unit
EXIT_SAPLDG56_002 DG: Filter Specifications for Tremcard Output
IMPORTING Parameters details for DG56_INTERFACE_ERR_MESSAGE
I_ERROR_CODE - Error code
Data type: CVCET-ERRCODEOptional: No
Call by Reference: No ( called with pass by value option)
I_REASON - DDS: Reason/origin of delivery order
Data type: CVDREASONOptional: No
Call by Reference: No ( called with pass by value option)
I_INFO_FOR_ERROR_MAIL - EHS: Data for Error Messages for SD - EHS Interface
Data type: RCGSDERROROptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DG56_INTERFACE_ERR_MESSAGE
E_RECTYPE - Recipient Type
Data type: CVCER-RECTYPEOptional: No
Call by Reference: No ( called with pass by value option)
E_RECNAME - Recipient Name
Data type: CVCER-RECNAMEOptional: No
Call by Reference: No ( called with pass by value option)
E_DEST_SYSTEM - Target Sys
Data type: CVCER-DSTSYSIDOptional: No
Call by Reference: No ( called with pass by value option)
E_DEST_CLIENT - Target Client
Data type: CVCER-DSTCLIENTOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for DG56_INTERFACE_ERR_MESSAGE
X_ERRORTEXTTAB - DDS: Single-column text table (132 characters per line)
Data type: CVDTLINEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERRORMAIL_SEND_FAILED - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DG56_INTERFACE_ERR_MESSAGE 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_rectype | TYPE CVCER-RECTYPE, " | |||
| lv_i_error_code | TYPE CVCET-ERRCODE, " | |||
| lt_x_errortexttab | TYPE STANDARD TABLE OF CVDTLINE, " | |||
| lv_errormail_send_failed | TYPE CVDTLINE, " | |||
| lv_i_reason | TYPE CVDREASON, " | |||
| lv_e_recname | TYPE CVCER-RECNAME, " | |||
| lv_e_dest_system | TYPE CVCER-DSTSYSID, " | |||
| lv_i_info_for_error_mail | TYPE RCGSDERROR, " | |||
| lv_e_dest_client | TYPE CVCER-DSTCLIENT. " |
|   CALL FUNCTION 'DG56_INTERFACE_ERR_MESSAGE' "NOTRANSL: EHS: Versenden einer Fehlermeldung bei Abbruch SD_DATA |
| EXPORTING | ||
| I_ERROR_CODE | = lv_i_error_code | |
| I_REASON | = lv_i_reason | |
| I_INFO_FOR_ERROR_MAIL | = lv_i_info_for_error_mail | |
| IMPORTING | ||
| E_RECTYPE | = lv_e_rectype | |
| E_RECNAME | = lv_e_recname | |
| E_DEST_SYSTEM | = lv_e_dest_system | |
| E_DEST_CLIENT | = lv_e_dest_client | |
| TABLES | ||
| X_ERRORTEXTTAB | = lt_x_errortexttab | |
| EXCEPTIONS | ||
| ERRORMAIL_SEND_FAILED = 1 | ||
| . " DG56_INTERFACE_ERR_MESSAGE | ||
ABAP code using 7.40 inline data declarations to call FM DG56_INTERFACE_ERR_MESSAGE
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 RECTYPE FROM CVCER INTO @DATA(ld_e_rectype). | ||||
| "SELECT single ERRCODE FROM CVCET INTO @DATA(ld_i_error_code). | ||||
| "SELECT single RECNAME FROM CVCER INTO @DATA(ld_e_recname). | ||||
| "SELECT single DSTSYSID FROM CVCER INTO @DATA(ld_e_dest_system). | ||||
| "SELECT single DSTCLIENT FROM CVCER INTO @DATA(ld_e_dest_client). | ||||
Search for further information about these or an SAP related objects