SAP RH_MESSAGE_OUTPUT Function Module for









RH_MESSAGE_OUTPUT is a standard rh message output 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 rh message output FM, simply by entering the name RH_MESSAGE_OUTPUT into the relevant SAP transaction such as SE37 or SE38.

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



Function RH_MESSAGE_OUTPUT 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 'RH_MESSAGE_OUTPUT'"
  EXPORTING
   PLVAR =  "Plan version
*  VOBEG = '19000101' "
*  VOEND = '99991231' "
*  VOLNG = ' ' "
*  VA_REL =  "Relationship record: Business event <-> Attendee
*  DEVICE = 'PRINTER' "Output device
*  MODUS_FLAG = ' ' "Flag: Processing mode (dialog, background, batch input)
*  LFCOD =  "
*  KMIT =  "Notification Abbreviation
*  VST1 =  "Business event / Alternative
*  VST2 =  "Booked/cancelled business event
   VTYP =  "Business event type
*  TLNTYP =  "Attendee type
*  TLNID =  "Participant ID
*  TLNANZ =  "Number of attendees

 IMPORTING
   OUT_ERR =  "Error in text variable data
   ERRPROT =  "Error log

EXCEPTIONS
   NO_AUTHORITY = 1    NO_DEVICE_ADDRESS = 10    NO_PLVAR = 2    NO_LFCOD = 3    NO_ABBRIV = 4    FORM_NOT_MAINTAINED = 5    ABBRIV_USER_AUTHORITY = 6    NO_STAND_ENTRY_FOR_ABBRIV = 7    NO_EVENT_ID = 8    ADDRESSEE_ERROR = 9
.



IMPORTING Parameters details for RH_MESSAGE_OUTPUT

PLVAR - Plan version

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

VOBEG -

Data type: PKMIT-VOBEG
Default: '19000101'
Optional: Yes
Call by Reference: No ( called with pass by value option)

VOEND -

Data type: PKMIT-VOEND
Default: '99991231'
Optional: Yes
Call by Reference: No ( called with pass by value option)

VOLNG -

Data type: PKMIT-VOLNG
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

VA_REL - Relationship record: Business event <-> Attendee

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

DEVICE - Output device

Data type: PKMIT-DEVICE
Default: 'PRINTER'
Optional: Yes
Call by Reference: No ( called with pass by value option)

MODUS_FLAG - Flag: Processing mode (dialog, background, batch input)

Data type: PP0V-DIALOG
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

LFCOD -

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

KMIT - Notification Abbreviation

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

VST1 - Business event / Alternative

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

VST2 - Booked/cancelled business event

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

VTYP - Business event type

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

TLNTYP - Attendee type

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

TLNID - Participant ID

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

TLNANZ - Number of attendees

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

EXPORTING Parameters details for RH_MESSAGE_OUTPUT

OUT_ERR - Error in text variable data

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

ERRPROT - Error log

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

EXCEPTIONS details

NO_AUTHORITY - No authorization

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

NO_DEVICE_ADDRESS -

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

NO_PLVAR - Invalid plan version

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

NO_LFCOD -

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

NO_ABBRIV - Invalid notification abbreviation

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

FORM_NOT_MAINTAINED - No form found for notification abbreviation

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

ABBRIV_USER_AUTHORITY - No authorization for notification abbreviation

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

NO_STAND_ENTRY_FOR_ABBRIV - Entry for abbreviation notification not found

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

NO_EVENT_ID - Invalid business event / business event type

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

ADDRESSEE_ERROR -

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

Copy and paste ABAP code example for RH_MESSAGE_OUTPUT 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_plvar  TYPE PKMIT-PLVAR, "   
lv_out_err  TYPE SY-SUBRC, "   
lv_no_authority  TYPE SY, "   
lv_vobeg  TYPE PKMIT-VOBEG, "   '19000101'
lv_no_device_address  TYPE PKMIT, "   
lv_voend  TYPE PKMIT-VOEND, "   '99991231'
lv_volng  TYPE PKMIT-VOLNG, "   ' '
lv_va_rel  TYPE P1001, "   
lv_device  TYPE PKMIT-DEVICE, "   'PRINTER'
lv_modus_flag  TYPE PP0V-DIALOG, "   ' '
lv_lfcod  TYPE PKMIT-LFCOD, "   
lv_errprot  TYPE PD01_MITDAT, "   
lv_no_plvar  TYPE PD01_MITDAT, "   
lv_kmit  TYPE PKMIT-KMIT, "   
lv_no_lfcod  TYPE PKMIT, "   
lv_vst1  TYPE PKMIT-KRS1_ID, "   
lv_no_abbriv  TYPE PKMIT, "   
lv_vst2  TYPE PKMIT-KRS2_ID, "   
lv_form_not_maintained  TYPE PKMIT, "   
lv_vtyp  TYPE PKMIT-TYP_ID, "   
lv_abbriv_user_authority  TYPE PKMIT, "   
lv_tlntyp  TYPE PKMIT-TEILNTYP, "   
lv_no_stand_entry_for_abbriv  TYPE PKMIT, "   
lv_tlnid  TYPE PKMIT-TEILN_ID, "   
lv_no_event_id  TYPE PKMIT, "   
lv_tlnanz  TYPE PKMIT-MANZL, "   
lv_addressee_error  TYPE PKMIT. "   

  CALL FUNCTION 'RH_MESSAGE_OUTPUT'  "
    EXPORTING
         PLVAR = lv_plvar
         VOBEG = lv_vobeg
         VOEND = lv_voend
         VOLNG = lv_volng
         VA_REL = lv_va_rel
         DEVICE = lv_device
         MODUS_FLAG = lv_modus_flag
         LFCOD = lv_lfcod
         KMIT = lv_kmit
         VST1 = lv_vst1
         VST2 = lv_vst2
         VTYP = lv_vtyp
         TLNTYP = lv_tlntyp
         TLNID = lv_tlnid
         TLNANZ = lv_tlnanz
    IMPORTING
         OUT_ERR = lv_out_err
         ERRPROT = lv_errprot
    EXCEPTIONS
        NO_AUTHORITY = 1
        NO_DEVICE_ADDRESS = 10
        NO_PLVAR = 2
        NO_LFCOD = 3
        NO_ABBRIV = 4
        FORM_NOT_MAINTAINED = 5
        ABBRIV_USER_AUTHORITY = 6
        NO_STAND_ENTRY_FOR_ABBRIV = 7
        NO_EVENT_ID = 8
        ADDRESSEE_ERROR = 9
. " RH_MESSAGE_OUTPUT




ABAP code using 7.40 inline data declarations to call FM RH_MESSAGE_OUTPUT

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 PLVAR FROM PKMIT INTO @DATA(ld_plvar).
 
"SELECT single SUBRC FROM SY INTO @DATA(ld_out_err).
 
 
"SELECT single VOBEG FROM PKMIT INTO @DATA(ld_vobeg).
DATA(ld_vobeg) = '19000101'.
 
 
"SELECT single VOEND FROM PKMIT INTO @DATA(ld_voend).
DATA(ld_voend) = '99991231'.
 
"SELECT single VOLNG FROM PKMIT INTO @DATA(ld_volng).
DATA(ld_volng) = ' '.
 
 
"SELECT single DEVICE FROM PKMIT INTO @DATA(ld_device).
DATA(ld_device) = 'PRINTER'.
 
"SELECT single DIALOG FROM PP0V INTO @DATA(ld_modus_flag).
DATA(ld_modus_flag) = ' '.
 
"SELECT single LFCOD FROM PKMIT INTO @DATA(ld_lfcod).
 
 
 
"SELECT single KMIT FROM PKMIT INTO @DATA(ld_kmit).
 
 
"SELECT single KRS1_ID FROM PKMIT INTO @DATA(ld_vst1).
 
 
"SELECT single KRS2_ID FROM PKMIT INTO @DATA(ld_vst2).
 
 
"SELECT single TYP_ID FROM PKMIT INTO @DATA(ld_vtyp).
 
 
"SELECT single TEILNTYP FROM PKMIT INTO @DATA(ld_tlntyp).
 
 
"SELECT single TEILN_ID FROM PKMIT INTO @DATA(ld_tlnid).
 
 
"SELECT single MANZL FROM PKMIT INTO @DATA(ld_tlnanz).
 
 


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!