SAP NAST_GET_MESSAGE_OBJECT_DATA Function Module for NOTRANSL: WFMC: Mailversand über MESSAGE-Objekt - Lesen Felder aus Objekt
NAST_GET_MESSAGE_OBJECT_DATA is a standard nast get message object data 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: WFMC: Mailversand über MESSAGE-Objekt - Lesen Felder aus Objekt 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 nast get message object data FM, simply by entering the name NAST_GET_MESSAGE_OBJECT_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: WMCM
Program Name: SAPLWMCM
Main Program: SAPLWMCM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function NAST_GET_MESSAGE_OBJECT_DATA 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 'NAST_GET_MESSAGE_OBJECT_DATA'"NOTRANSL: WFMC: Mailversand über MESSAGE-Objekt - Lesen Felder aus Objekt.
EXPORTING
OBJKEY = "DE-EN-LANG-SWITCH-NO-TRANSLATION
IMPORTING
MAIL_FIELDS = "DE-EN-LANG-SWITCH-NO-TRANSLATION
EXCEPTIONS
MAILDATA_NOT_READABLE = 1
IMPORTING Parameters details for NAST_GET_MESSAGE_OBJECT_DATA
OBJKEY - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: SWOTOBJID-OBJKEYOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for NAST_GET_MESSAGE_OBJECT_DATA
MAIL_FIELDS - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: NACH_HELPOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
MAILDATA_NOT_READABLE - Object Does Not Exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for NAST_GET_MESSAGE_OBJECT_DATA 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_objkey | TYPE SWOTOBJID-OBJKEY, " | |||
| lv_mail_fields | TYPE NACH_HELP, " | |||
| lv_maildata_not_readable | TYPE NACH_HELP. " |
|   CALL FUNCTION 'NAST_GET_MESSAGE_OBJECT_DATA' "NOTRANSL: WFMC: Mailversand über MESSAGE-Objekt - Lesen Felder aus Objekt |
| EXPORTING | ||
| OBJKEY | = lv_objkey | |
| IMPORTING | ||
| MAIL_FIELDS | = lv_mail_fields | |
| EXCEPTIONS | ||
| MAILDATA_NOT_READABLE = 1 | ||
| . " NAST_GET_MESSAGE_OBJECT_DATA | ||
ABAP code using 7.40 inline data declarations to call FM NAST_GET_MESSAGE_OBJECT_DATA
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 OBJKEY FROM SWOTOBJID INTO @DATA(ld_objkey). | ||||
Search for further information about these or an SAP related objects