SAP NAST_CHANGE_MESSAGE_OBJECT Function Module for NOTRANSL: Mail über MESSAGE-Objekt: Ändern Text wegen neuer Sprache
NAST_CHANGE_MESSAGE_OBJECT is a standard nast change message object 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: Mail über MESSAGE-Objekt: Ändern Text wegen neuer Sprache 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 change message object FM, simply by entering the name NAST_CHANGE_MESSAGE_OBJECT 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_CHANGE_MESSAGE_OBJECT 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_CHANGE_MESSAGE_OBJECT'"NOTRANSL: Mail über MESSAGE-Objekt: Ändern Text wegen neuer Sprache.
EXPORTING
OBJKEY = "DE-EN-LANG-SWITCH-NO-TRANSLATION
OBJ_HANDLE = "DE-EN-LANG-SWITCH-NO-TRANSLATION
KAPPL = "DE-EN-LANG-SWITCH-NO-TRANSLATION
KSCHL = "message type
SPRAS_CHG = "DE-EN-LANG-SWITCH-NO-TRANSLATION
EXCEPTIONS
OBJECT_NOT_EXIST = 1 ERROR_IN_READING_OBJECT = 2 ERROR_IN_CHANGING_OBJECT = 3 PARAMETER_ERROR = 4 NO_TEXT_AVAILABLE = 5 NO_TITLE_AVAILABLE = 6
IMPORTING Parameters details for NAST_CHANGE_MESSAGE_OBJECT
OBJKEY - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: SWOTOBJID-OBJKEYOptional: No
Call by Reference: No ( called with pass by value option)
OBJ_HANDLE - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: OBJ_RECORDOptional: No
Call by Reference: No ( called with pass by value option)
KAPPL - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: NAST-KAPPLOptional: No
Call by Reference: No ( called with pass by value option)
KSCHL - message type
Data type: NAST-KSCHLOptional: No
Call by Reference: No ( called with pass by value option)
SPRAS_CHG - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: NAST-SPRASOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
OBJECT_NOT_EXIST - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_IN_READING_OBJECT - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_IN_CHANGING_OBJECT - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARAMETER_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_TEXT_AVAILABLE - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_TITLE_AVAILABLE - 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_CHANGE_MESSAGE_OBJECT 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_object_not_exist | TYPE SWOTOBJID, " | |||
lv_obj_handle | TYPE OBJ_RECORD, " | |||
lv_error_in_reading_object | TYPE OBJ_RECORD, " | |||
lv_kappl | TYPE NAST-KAPPL, " | |||
lv_error_in_changing_object | TYPE NAST, " | |||
lv_kschl | TYPE NAST-KSCHL, " | |||
lv_parameter_error | TYPE NAST, " | |||
lv_spras_chg | TYPE NAST-SPRAS, " | |||
lv_no_text_available | TYPE NAST, " | |||
lv_no_title_available | TYPE NAST. " |
  CALL FUNCTION 'NAST_CHANGE_MESSAGE_OBJECT' "NOTRANSL: Mail über MESSAGE-Objekt: Ändern Text wegen neuer Sprache |
EXPORTING | ||
OBJKEY | = lv_objkey | |
OBJ_HANDLE | = lv_obj_handle | |
KAPPL | = lv_kappl | |
KSCHL | = lv_kschl | |
SPRAS_CHG | = lv_spras_chg | |
EXCEPTIONS | ||
OBJECT_NOT_EXIST = 1 | ||
ERROR_IN_READING_OBJECT = 2 | ||
ERROR_IN_CHANGING_OBJECT = 3 | ||
PARAMETER_ERROR = 4 | ||
NO_TEXT_AVAILABLE = 5 | ||
NO_TITLE_AVAILABLE = 6 | ||
. " NAST_CHANGE_MESSAGE_OBJECT |
ABAP code using 7.40 inline data declarations to call FM NAST_CHANGE_MESSAGE_OBJECT
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 KAPPL FROM NAST INTO @DATA(ld_kappl). | ||||
"SELECT single KSCHL FROM NAST INTO @DATA(ld_kschl). | ||||
"SELECT single SPRAS FROM NAST INTO @DATA(ld_spras_chg). | ||||
Search for further information about these or an SAP related objects