SAP NAST_GET_MESSAGE_OBJECT_RECV Function Module for NOTRANSL: WFMC: Mailversand über MESSAGE-Objekt - Lesen Partner aus Objekt
NAST_GET_MESSAGE_OBJECT_RECV is a standard nast get message object recv 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 Partner 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 recv FM, simply by entering the name NAST_GET_MESSAGE_OBJECT_RECV 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_RECV 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_RECV'"NOTRANSL: WFMC: Mailversand über MESSAGE-Objekt - Lesen Partner aus Objekt.
EXPORTING
PI_OBJKEY = "DE-EN-LANG-SWITCH-NO-TRANSLATION
IMPORTING
PE_ADDR = "DE-EN-LANG-SWITCH-NO-TRANSLATION
PE_RECESC = "DE-EN-LANG-SWITCH-NO-TRANSLATION
PE_PARVW = "Partner Role
PE_PARNR = "Partner
CHANGING
PC_OBJHANDLE = "
EXCEPTIONS
MAILDATA_NOT_READABLE = 1
IMPORTING Parameters details for NAST_GET_MESSAGE_OBJECT_RECV
PI_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_RECV
PE_ADDR - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: SOXNA-FULLNAMEOptional: No
Call by Reference: No ( called with pass by value option)
PE_RECESC - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: SOOS1-RECESCOptional: No
Call by Reference: No ( called with pass by value option)
PE_PARVW - Partner Role
Data type: NACH-PARVWOptional: No
Call by Reference: No ( called with pass by value option)
PE_PARNR - Partner
Data type: NACH_HELP-PARNROptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for NAST_GET_MESSAGE_OBJECT_RECV
PC_OBJHANDLE -
Data type: OBJ_RECORDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
MAILDATA_NOT_READABLE - 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 NAST_GET_MESSAGE_OBJECT_RECV 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_pe_addr | TYPE SOXNA-FULLNAME, " | |||
| lv_pi_objkey | TYPE SWOTOBJID-OBJKEY, " | |||
| lv_pc_objhandle | TYPE OBJ_RECORD, " | |||
| lv_maildata_not_readable | TYPE OBJ_RECORD, " | |||
| lv_pe_recesc | TYPE SOOS1-RECESC, " | |||
| lv_pe_parvw | TYPE NACH-PARVW, " | |||
| lv_pe_parnr | TYPE NACH_HELP-PARNR. " |
|   CALL FUNCTION 'NAST_GET_MESSAGE_OBJECT_RECV' "NOTRANSL: WFMC: Mailversand über MESSAGE-Objekt - Lesen Partner aus Objekt |
| EXPORTING | ||
| PI_OBJKEY | = lv_pi_objkey | |
| IMPORTING | ||
| PE_ADDR | = lv_pe_addr | |
| PE_RECESC | = lv_pe_recesc | |
| PE_PARVW | = lv_pe_parvw | |
| PE_PARNR | = lv_pe_parnr | |
| CHANGING | ||
| PC_OBJHANDLE | = lv_pc_objhandle | |
| EXCEPTIONS | ||
| MAILDATA_NOT_READABLE = 1 | ||
| . " NAST_GET_MESSAGE_OBJECT_RECV | ||
ABAP code using 7.40 inline data declarations to call FM NAST_GET_MESSAGE_OBJECT_RECV
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 FULLNAME FROM SOXNA INTO @DATA(ld_pe_addr). | ||||
| "SELECT single OBJKEY FROM SWOTOBJID INTO @DATA(ld_pi_objkey). | ||||
| "SELECT single RECESC FROM SOOS1 INTO @DATA(ld_pe_recesc). | ||||
| "SELECT single PARVW FROM NACH INTO @DATA(ld_pe_parvw). | ||||
| "SELECT single PARNR FROM NACH_HELP INTO @DATA(ld_pe_parnr). | ||||
Search for further information about these or an SAP related objects