SAP DG80_MESSAGE_CREATE Function Module for NOTRANSL: Erzeugung von Nachrichtentexten









DG80_MESSAGE_CREATE is a standard dg80 message create 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: Erzeugung von Nachrichtentexten 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 dg80 message create FM, simply by entering the name DG80_MESSAGE_CREATE into the relevant SAP transaction such as SE37 or SE38.

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



Function DG80_MESSAGE_CREATE 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 'DG80_MESSAGE_CREATE'"NOTRANSL: Erzeugung von Nachrichtentexten
EXPORTING
ERROR = "Workflow Definition: Error Checking a Workflow

IMPORTING
MESSAGE = "Text, 255 Characters
ICON_ID = "
.




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_SAPLDG80_001 DG: Data Transfer from Screen 1000 to Screen Exit 8000 (Delivery)
EXIT_SAPLDG80_002 DG: Data Transfer from Screen Exit 8000 to Screen 1000
EXIT_SAPLDG80_003 DG: Handling OK Codes for Customer Screen 8000
EXIT_SAPLDG80_004 DG: Data Transfer from Dynpro 2000 to Screen Exit 8100 (Sales)
EXIT_SAPLDG80_005 DG: Data Transfer from Screen Exit 8100 to Dynpro 2000 (Sales)
EXIT_SAPLDG80_006 DG: Handling OK Codes for Customer Screen 8100

IMPORTING Parameters details for DG80_MESSAGE_CREATE

ERROR - Workflow Definition: Error Checking a Workflow

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

EXPORTING Parameters details for DG80_MESSAGE_CREATE

MESSAGE - Text, 255 Characters

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

ICON_ID -

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

Copy and paste ABAP code example for DG80_MESSAGE_CREATE 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_error  TYPE SWD_ERROR, "   
lv_message  TYPE TEXT255, "   
lv_icon_id  TYPE TEXT255. "   

  CALL FUNCTION 'DG80_MESSAGE_CREATE'  "NOTRANSL: Erzeugung von Nachrichtentexten
    EXPORTING
         ERROR = lv_error
    IMPORTING
         MESSAGE = lv_message
         ICON_ID = lv_icon_id
. " DG80_MESSAGE_CREATE




ABAP code using 7.40 inline data declarations to call FM DG80_MESSAGE_CREATE

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



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!