SAP NAST_OFFICE_CALL_CHANGE Function Module for NOTRANSL: NAST: Mail über MESSAGE-Objekt - Absprung in Ändern Office









NAST_OFFICE_CALL_CHANGE is a standard nast office call change 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: NAST: Mail über MESSAGE-Objekt - Absprung in Ändern Office 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 office call change FM, simply by entering the name NAST_OFFICE_CALL_CHANGE 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_OFFICE_CALL_CHANGE 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_OFFICE_CALL_CHANGE'"NOTRANSL: NAST: Mail über MESSAGE-Objekt - Absprung in Ändern Office
EXPORTING
OBJKEY = "DE-EN-LANG-SWITCH-NO-TRANSLATION
OBJ_HANDLE = "
* DUMMY_RECEIVER = ' ' "DE-EN-LANG-SWITCH-NO-TRANSLATION

IMPORTING
PE_PARVW = "
PE_CHANGED = "DE-EN-LANG-SWITCH-NO-TRANSLATION

EXCEPTIONS
OBJECT_NOT_EXIST = 1 ERROR_IN_CHANGING = 2
.



IMPORTING Parameters details for NAST_OFFICE_CALL_CHANGE

OBJKEY - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

OBJ_HANDLE -

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

DUMMY_RECEIVER - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type: CHAR1
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for NAST_OFFICE_CALL_CHANGE

PE_PARVW -

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

PE_CHANGED - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

EXCEPTIONS details

OBJECT_NOT_EXIST - Object Does Not Exist

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

ERROR_IN_CHANGING - 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_OFFICE_CALL_CHANGE 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_pe_parvw  TYPE NAST-PARVW, "   
lv_object_not_exist  TYPE NAST, "   
lv_obj_handle  TYPE OBJ_RECORD, "   
lv_pe_changed  TYPE C, "   
lv_error_in_changing  TYPE C, "   
lv_dummy_receiver  TYPE CHAR1. "   ' '

  CALL FUNCTION 'NAST_OFFICE_CALL_CHANGE'  "NOTRANSL: NAST: Mail über MESSAGE-Objekt - Absprung in Ändern Office
    EXPORTING
         OBJKEY = lv_objkey
         OBJ_HANDLE = lv_obj_handle
         DUMMY_RECEIVER = lv_dummy_receiver
    IMPORTING
         PE_PARVW = lv_pe_parvw
         PE_CHANGED = lv_pe_changed
    EXCEPTIONS
        OBJECT_NOT_EXIST = 1
        ERROR_IN_CHANGING = 2
. " NAST_OFFICE_CALL_CHANGE




ABAP code using 7.40 inline data declarations to call FM NAST_OFFICE_CALL_CHANGE

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).
 
"SELECT single PARVW FROM NAST INTO @DATA(ld_pe_parvw).
 
 
 
 
 
DATA(ld_dummy_receiver) = ' '.
 


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!