SAP EHHSS_EXT_RAS_REQ_MSG_COLLECT Function Module for Collect Messages for BAPI-return for RAS Request









EHHSS_EXT_RAS_REQ_MSG_COLLECT is a standard ehhss ext ras req msg collect SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Collect Messages for BAPI-return for RAS Request 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 ehhss ext ras req msg collect FM, simply by entering the name EHHSS_EXT_RAS_REQ_MSG_COLLECT into the relevant SAP transaction such as SE37 or SE38.

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



Function EHHSS_EXT_RAS_REQ_MSG_COLLECT 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 'EHHSS_EXT_RAS_REQ_MSG_COLLECT'"Collect Messages for BAPI-return for RAS Request
  EXPORTING
   IV_MSG_TYPE =  "Message type: S Success, E Error, W Warning, I Info, A Abort
*  IV_MSG_ID = 'CM_EHHSS_EXT_RAS_IF' "Message Class
   IV_MSG_NUMBER =  "Message Number
*  IV_MSG_V1 = ' ' "Message Variable 1
*  IV_MSG_V2 = ' ' "Message Variable 2
*  IV_MSG_V3 = ' ' "Message Variable 3
*  IV_MSG_V4 = ' ' "Message Variable 4
*  IV_PARAMETER = GC_PARAM_RAS_REQ_MSG "Parameter Name
*  IV_ROW = 1 "Lines in parameter

CHANGING
   CT_BAPI_RETURN =  "Table with BAPI Return Information
.



IMPORTING Parameters details for EHHSS_EXT_RAS_REQ_MSG_COLLECT

IV_MSG_TYPE - Message type: S Success, E Error, W Warning, I Info, A Abort

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

IV_MSG_ID - Message Class

Data type: SYMSGID
Default: 'CM_EHHSS_EXT_RAS_IF'
Optional: No
Call by Reference: Yes

IV_MSG_NUMBER - Message Number

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

IV_MSG_V1 - Message Variable 1

Data type: ANY
Default: SPACE
Optional: Yes
Call by Reference: Yes

IV_MSG_V2 - Message Variable 2

Data type: ANY
Default: SPACE
Optional: Yes
Call by Reference: Yes

IV_MSG_V3 - Message Variable 3

Data type: ANY
Default: SPACE
Optional: Yes
Call by Reference: Yes

IV_MSG_V4 - Message Variable 4

Data type: ANY
Default: SPACE
Optional: Yes
Call by Reference: Yes

IV_PARAMETER - Parameter Name

Data type: BAPI_PARAM
Default: GC_PARAM_RAS_REQ_MSG
Optional: Yes
Call by Reference: Yes

IV_ROW - Lines in parameter

Data type: BAPI_LINE
Default: 1
Optional: Yes
Call by Reference: Yes

CHANGING Parameters details for EHHSS_EXT_RAS_REQ_MSG_COLLECT

CT_BAPI_RETURN - Table with BAPI Return Information

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

Copy and paste ABAP code example for EHHSS_EXT_RAS_REQ_MSG_COLLECT 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_iv_msg_type  TYPE BAPI_MTYPE, "   
lv_ct_bapi_return  TYPE BAPIRETTAB, "   
lv_iv_msg_id  TYPE SYMSGID, "   'CM_EHHSS_EXT_RAS_IF'
lv_iv_msg_number  TYPE SYMSGNO, "   
lv_iv_msg_v1  TYPE ANY, "   SPACE
lv_iv_msg_v2  TYPE ANY, "   SPACE
lv_iv_msg_v3  TYPE ANY, "   SPACE
lv_iv_msg_v4  TYPE ANY, "   SPACE
lv_iv_parameter  TYPE BAPI_PARAM, "   GC_PARAM_RAS_REQ_MSG
lv_iv_row  TYPE BAPI_LINE. "   1

  CALL FUNCTION 'EHHSS_EXT_RAS_REQ_MSG_COLLECT'  "Collect Messages for BAPI-return for RAS Request
    EXPORTING
         IV_MSG_TYPE = lv_iv_msg_type
         IV_MSG_ID = lv_iv_msg_id
         IV_MSG_NUMBER = lv_iv_msg_number
         IV_MSG_V1 = lv_iv_msg_v1
         IV_MSG_V2 = lv_iv_msg_v2
         IV_MSG_V3 = lv_iv_msg_v3
         IV_MSG_V4 = lv_iv_msg_v4
         IV_PARAMETER = lv_iv_parameter
         IV_ROW = lv_iv_row
    CHANGING
         CT_BAPI_RETURN = lv_ct_bapi_return
. " EHHSS_EXT_RAS_REQ_MSG_COLLECT




ABAP code using 7.40 inline data declarations to call FM EHHSS_EXT_RAS_REQ_MSG_COLLECT

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_iv_msg_id) = 'CM_EHHSS_EXT_RAS_IF'.
 
 
DATA(ld_iv_msg_v1) = ' '.
 
DATA(ld_iv_msg_v2) = ' '.
 
DATA(ld_iv_msg_v3) = ' '.
 
DATA(ld_iv_msg_v4) = ' '.
 
DATA(ld_iv_parameter) = GC_PARAM_RAS_REQ_MSG.
 
DATA(ld_iv_row) = 1.
 


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!