SAP MRSS_COMMUNICATION_CREATE Function Module for









MRSS_COMMUNICATION_CREATE is a standard mrss communication create 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 mrss communication create FM, simply by entering the name MRSS_COMMUNICATION_CREATE into the relevant SAP transaction such as SE37 or SE38.

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



Function MRSS_COMMUNICATION_CREATE 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 'MRSS_COMMUNICATION_CREATE'"
EXPORTING
* BOR_OBJECT = "
* COMMIT_WORK = 'X' "
* CHAIN_DOC = 'X' "
* DEF_DOC_TITLE = "

IMPORTING
MESSAGE_OBJECT = "

TABLES
COMM_TAB = "
TEXT = "

EXCEPTIONS
NO_RECEIVER = 1
.



IMPORTING Parameters details for MRSS_COMMUNICATION_CREATE

BOR_OBJECT -

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

COMMIT_WORK -

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

CHAIN_DOC -

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

DEF_DOC_TITLE -

Data type: CHAR128
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for MRSS_COMMUNICATION_CREATE

MESSAGE_OBJECT -

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

TABLES Parameters details for MRSS_COMMUNICATION_CREATE

COMM_TAB -

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

TEXT -

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

EXCEPTIONS details

NO_RECEIVER -

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

Copy and paste ABAP code example for MRSS_COMMUNICATION_CREATE 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:
lt_comm_tab  TYPE STANDARD TABLE OF MSM_COMMUNICATE, "   
lv_bor_object  TYPE BORIDENT, "   
lv_no_receiver  TYPE BORIDENT, "   
lv_message_object  TYPE SWOTOBJID, "   
lt_text  TYPE STANDARD TABLE OF SOLI, "   
lv_commit_work  TYPE CHAR1, "   'X'
lv_chain_doc  TYPE CHAR1, "   'X'
lv_def_doc_title  TYPE CHAR128. "   

  CALL FUNCTION 'MRSS_COMMUNICATION_CREATE'  "
    EXPORTING
         BOR_OBJECT = lv_bor_object
         COMMIT_WORK = lv_commit_work
         CHAIN_DOC = lv_chain_doc
         DEF_DOC_TITLE = lv_def_doc_title
    IMPORTING
         MESSAGE_OBJECT = lv_message_object
    TABLES
         COMM_TAB = lt_comm_tab
         TEXT = lt_text
    EXCEPTIONS
        NO_RECEIVER = 1
. " MRSS_COMMUNICATION_CREATE




ABAP code using 7.40 inline data declarations to call FM MRSS_COMMUNICATION_CREATE

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.

 
 
 
 
 
DATA(ld_commit_work) = 'X'.
 
DATA(ld_chain_doc) = 'X'.
 
 


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!