SAP RH_ORGANIZER_REQUEST Function Module for









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

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



Function RH_ORGANIZER_REQUEST 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_ORGANIZER_REQUEST'"
  EXPORTING
   PLVAR =  "
   OTYPE =  "
   OBJID =  "
*  FIELD = 'OGSRK' "
*  TABLE = 'HRVPVA' "
*  DISPL = ' ' "
*  BEGDA = SY-DATUM "
*  ENDDA = SY-DATUM "
*  ISTAT = ' ' "

 IMPORTING
   SEL_OOTYP =  "
   SEL_OGAID =  "

EXCEPTIONS
   NO_ORGANIZER = 1
.



IMPORTING Parameters details for RH_ORGANIZER_REQUEST

PLVAR -

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

OTYPE -

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

OBJID -

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

FIELD -

Data type: HELP_INFO-FIELDNAME
Default: 'OGSRK'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLE -

Data type: HELP_INFO-TABNAME
Default: 'HRVPVA'
Optional: Yes
Call by Reference: No ( called with pass by value option)

DISPL -

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

BEGDA -

Data type: OBJEC-BEGDA
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

ENDDA -

Data type: OBJEC-ENDDA
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

ISTAT -

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

EXPORTING Parameters details for RH_ORGANIZER_REQUEST

SEL_OOTYP -

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

SEL_OGAID -

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

EXCEPTIONS details

NO_ORGANIZER -

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

Copy and paste ABAP code example for RH_ORGANIZER_REQUEST 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 OBJEC-PLVAR, "   
lv_sel_ootyp  TYPE HRVPVA-OOTYP, "   
lv_no_organizer  TYPE HRVPVA, "   
lv_otype  TYPE OBJEC-OTYPE, "   
lv_sel_ogaid  TYPE HRVPVA-OGAID, "   
lv_objid  TYPE OBJEC-OBJID, "   
lv_field  TYPE HELP_INFO-FIELDNAME, "   'OGSRK'
lv_table  TYPE HELP_INFO-TABNAME, "   'HRVPVA'
lv_displ  TYPE HELP_INFO, "   ' '
lv_begda  TYPE OBJEC-BEGDA, "   SY-DATUM
lv_endda  TYPE OBJEC-ENDDA, "   SY-DATUM
lv_istat  TYPE OBJEC-ISTAT. "   ' '

  CALL FUNCTION 'RH_ORGANIZER_REQUEST'  "
    EXPORTING
         PLVAR = lv_plvar
         OTYPE = lv_otype
         OBJID = lv_objid
         FIELD = lv_field
         TABLE = lv_table
         DISPL = lv_displ
         BEGDA = lv_begda
         ENDDA = lv_endda
         ISTAT = lv_istat
    IMPORTING
         SEL_OOTYP = lv_sel_ootyp
         SEL_OGAID = lv_sel_ogaid
    EXCEPTIONS
        NO_ORGANIZER = 1
. " RH_ORGANIZER_REQUEST




ABAP code using 7.40 inline data declarations to call FM RH_ORGANIZER_REQUEST

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 OBJEC INTO @DATA(ld_plvar).
 
"SELECT single OOTYP FROM HRVPVA INTO @DATA(ld_sel_ootyp).
 
 
"SELECT single OTYPE FROM OBJEC INTO @DATA(ld_otype).
 
"SELECT single OGAID FROM HRVPVA INTO @DATA(ld_sel_ogaid).
 
"SELECT single OBJID FROM OBJEC INTO @DATA(ld_objid).
 
"SELECT single FIELDNAME FROM HELP_INFO INTO @DATA(ld_field).
DATA(ld_field) = 'OGSRK'.
 
"SELECT single TABNAME FROM HELP_INFO INTO @DATA(ld_table).
DATA(ld_table) = 'HRVPVA'.
 
DATA(ld_displ) = ' '.
 
"SELECT single BEGDA FROM OBJEC INTO @DATA(ld_begda).
DATA(ld_begda) = SY-DATUM.
 
"SELECT single ENDDA FROM OBJEC INTO @DATA(ld_endda).
DATA(ld_endda) = SY-DATUM.
 
"SELECT single ISTAT FROM OBJEC INTO @DATA(ld_istat).
DATA(ld_istat) = ' '.
 


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!