SAP BM_OBJECT_MESSAGE_SET Function Module for









BM_OBJECT_MESSAGE_SET is a standard bm object message set SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 bm object message set FM, simply by entering the name BM_OBJECT_MESSAGE_SET into the relevant SAP transaction such as SE37 or SE38.

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



Function BM_OBJECT_MESSAGE_SET 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 'BM_OBJECT_MESSAGE_SET'"
  EXPORTING
   OBJECT_TYPE =  "Object Type
*  MSGV3 =  "Message Variable 3
*  MSGV4 =  "Message Variable 4
*  ERROR_CLASS = ' ' "Error class repository API
*  SET_OBJECTTEXT = ' ' "
   OBJECT_ID =  "
*  OBJECTTEXT = ' ' "
*  SCRTEXT = ' ' "
   MSGID =  "Message Class
   MSGTY =  "Message Type
   MSGNO =  "Message Number
*  MSGV1 =  "Message Variable 1
*  MSGV2 =  "Message Variable 2

 IMPORTING
   MESSAGE =  "Message
   ERROR =  "Error structure of repository interface
.



IMPORTING Parameters details for BM_OBJECT_MESSAGE_SET

OBJECT_TYPE - Object Type

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

MSGV3 - Message Variable 3

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

MSGV4 - Message Variable 4

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

ERROR_CLASS - Error class repository API

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

SET_OBJECTTEXT -

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

OBJECT_ID -

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

OBJECTTEXT -

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

SCRTEXT -

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

MSGID - Message Class

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

MSGTY - Message Type

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

MSGNO - Message Number

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

MSGV1 - Message Variable 1

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

MSGV2 - Message Variable 2

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

EXPORTING Parameters details for BM_OBJECT_MESSAGE_SET

MESSAGE - Message

Data type: BMMSG
Optional: No
Call by Reference: Yes

ERROR - Error structure of repository interface

Data type: RPYGSER
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BM_OBJECT_MESSAGE_SET 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_message  TYPE BMMSG, "   
lv_object_type  TYPE BMOBJECT-TYPE, "   
lv_msgv3  TYPE ANY, "   
lv_msgv4  TYPE ANY, "   
lv_error_class  TYPE RPYGSERCLS, "   SPACE
lv_set_objecttext  TYPE BMT_FLAG, "   SPACE
lv_error  TYPE RPYGSER, "   
lv_object_id  TYPE ANY, "   
lv_objecttext  TYPE C, "   SPACE
lv_scrtext  TYPE C, "   SPACE
lv_msgid  TYPE SYMSGID, "   
lv_msgty  TYPE SYMSGTY, "   
lv_msgno  TYPE SYMSGNO, "   
lv_msgv1  TYPE ANY, "   
lv_msgv2  TYPE ANY. "   

  CALL FUNCTION 'BM_OBJECT_MESSAGE_SET'  "
    EXPORTING
         OBJECT_TYPE = lv_object_type
         MSGV3 = lv_msgv3
         MSGV4 = lv_msgv4
         ERROR_CLASS = lv_error_class
         SET_OBJECTTEXT = lv_set_objecttext
         OBJECT_ID = lv_object_id
         OBJECTTEXT = lv_objecttext
         SCRTEXT = lv_scrtext
         MSGID = lv_msgid
         MSGTY = lv_msgty
         MSGNO = lv_msgno
         MSGV1 = lv_msgv1
         MSGV2 = lv_msgv2
    IMPORTING
         MESSAGE = lv_message
         ERROR = lv_error
. " BM_OBJECT_MESSAGE_SET




ABAP code using 7.40 inline data declarations to call FM BM_OBJECT_MESSAGE_SET

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 TYPE FROM BMOBJECT INTO @DATA(ld_object_type).
 
 
 
DATA(ld_error_class) = ' '.
 
DATA(ld_set_objecttext) = ' '.
 
 
 
DATA(ld_objecttext) = ' '.
 
DATA(ld_scrtext) = ' '.
 
 
 
 
 
 


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!