SAP GRM_SEND_DATA Function Module for









GRM_SEND_DATA is a standard grm send data 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 grm send data FM, simply by entering the name GRM_SEND_DATA into the relevant SAP transaction such as SE37 or SE38.

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



Function GRM_SEND_DATA 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 'GRM_SEND_DATA'"
  EXPORTING
   OBJECTS_FROM_LOGSYS =  "Logical System
*  FUNCTIONMODULE =  "Function Module Name
*  NODETEXT =  "
   FUNCKEY =  "Generic Role Manager: Function Key
   BEGIN_DATE =  "Start Date
   END_DATE =  "End Date
*  EVPATH =  "Evaluation Path
*  VALID_OTYPES =  "
*  TRANSACTIONCODE =  "Transaction Code
*  PROGRAMNAME =  "ABAP Program Name
*  PROGRAMVARIANT =  "Variant Name

TABLES
   OBJECTS =  "Extended Object

EXCEPTIONS
   WEBSERVER_NOT_FOUND = 1    NO_APPLICATION = 2    ITS_NOT_AVAILABLE = 3
.



IMPORTING Parameters details for GRM_SEND_DATA

OBJECTS_FROM_LOGSYS - Logical System

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

FUNCTIONMODULE - Function Module Name

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

NODETEXT -

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

FUNCKEY - Generic Role Manager: Function Key

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

BEGIN_DATE - Start Date

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

END_DATE - End Date

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

EVPATH - Evaluation Path

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

VALID_OTYPES -

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

TRANSACTIONCODE - Transaction Code

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

PROGRAMNAME - ABAP Program Name

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

PROGRAMVARIANT - Variant Name

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

TABLES Parameters details for GRM_SEND_DATA

OBJECTS - Extended Object

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

EXCEPTIONS details

WEBSERVER_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

NO_APPLICATION -

Data type:
Optional: No
Call by Reference: Yes

ITS_NOT_AVAILABLE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for GRM_SEND_DATA 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_objects  TYPE STANDARD TABLE OF HRSOBID, "   
lv_objects_from_logsys  TYPE LOGSYS, "   
lv_webserver_not_found  TYPE LOGSYS, "   
lv_functionmodule  TYPE RS38L_FNAM, "   
lv_nodetext  TYPE SEU_TEXT, "   
lv_funckey  TYPE GMFUNCKEY, "   
lv_no_application  TYPE GMFUNCKEY, "   
lv_begin_date  TYPE BEGDATUM, "   
lv_its_not_available  TYPE BEGDATUM, "   
lv_end_date  TYPE ENDDATUM, "   
lv_evpath  TYPE WEGID, "   
lv_valid_otypes  TYPE OTYPE_T, "   
lv_transactioncode  TYPE TCODE, "   
lv_programname  TYPE PROGRAMM, "   
lv_programvariant  TYPE RALDB_VARI. "   

  CALL FUNCTION 'GRM_SEND_DATA'  "
    EXPORTING
         OBJECTS_FROM_LOGSYS = lv_objects_from_logsys
         FUNCTIONMODULE = lv_functionmodule
         NODETEXT = lv_nodetext
         FUNCKEY = lv_funckey
         BEGIN_DATE = lv_begin_date
         END_DATE = lv_end_date
         EVPATH = lv_evpath
         VALID_OTYPES = lv_valid_otypes
         TRANSACTIONCODE = lv_transactioncode
         PROGRAMNAME = lv_programname
         PROGRAMVARIANT = lv_programvariant
    TABLES
         OBJECTS = lt_objects
    EXCEPTIONS
        WEBSERVER_NOT_FOUND = 1
        NO_APPLICATION = 2
        ITS_NOT_AVAILABLE = 3
. " GRM_SEND_DATA




ABAP code using 7.40 inline data declarations to call FM GRM_SEND_DATA

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.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!