SAP RH_EDIT_ANY_OBJECT Function Module for









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

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



Function RH_EDIT_ANY_OBJECT 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_EDIT_ANY_OBJECT'"
  EXPORTING
   PLVAR =  "Plan version
   OTYPE =  "Object type
   REALO =  "Object ID (long)
*  ISTAT = ' ' "Status
*  BEGDA = '19000101' "Period (start)
*  ENDDA = '99991231' "Period (end)
*  DISPLAY_ONLY = ' ' "X=display only
*  FORCE_DESC = ' ' "

EXCEPTIONS
   INTERNAL_ERROR = 1    NO_AUTHORITY = 2    OBJECT_NOT_FOUND = 3    UNKNOWN_OBJECT_TYPE = 4
.



IMPORTING Parameters details for RH_EDIT_ANY_OBJECT

PLVAR - Plan version

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

OTYPE - Object type

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

REALO - Object ID (long)

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

ISTAT - Status

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

BEGDA - Period (start)

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

ENDDA - Period (end)

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

DISPLAY_ONLY - X=display only

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

FORCE_DESC -

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

EXCEPTIONS details

INTERNAL_ERROR -

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

NO_AUTHORITY -

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

OBJECT_NOT_FOUND -

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

UNKNOWN_OBJECT_TYPE -

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

Copy and paste ABAP code example for RH_EDIT_ANY_OBJECT 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_internal_error  TYPE OBJEC, "   
lv_otype  TYPE OBJEC-OTYPE, "   
lv_no_authority  TYPE OBJEC, "   
lv_realo  TYPE OBJEC-REALO, "   
lv_object_not_found  TYPE OBJEC, "   
lv_istat  TYPE OBJEC-ISTAT, "   ' '
lv_unknown_object_type  TYPE OBJEC, "   
lv_begda  TYPE OBJEC-BEGDA, "   '19000101'
lv_endda  TYPE OBJEC-ENDDA, "   '99991231'
lv_display_only  TYPE C, "   ' '
lv_force_desc  TYPE C. "   ' '

  CALL FUNCTION 'RH_EDIT_ANY_OBJECT'  "
    EXPORTING
         PLVAR = lv_plvar
         OTYPE = lv_otype
         REALO = lv_realo
         ISTAT = lv_istat
         BEGDA = lv_begda
         ENDDA = lv_endda
         DISPLAY_ONLY = lv_display_only
         FORCE_DESC = lv_force_desc
    EXCEPTIONS
        INTERNAL_ERROR = 1
        NO_AUTHORITY = 2
        OBJECT_NOT_FOUND = 3
        UNKNOWN_OBJECT_TYPE = 4
. " RH_EDIT_ANY_OBJECT




ABAP code using 7.40 inline data declarations to call FM RH_EDIT_ANY_OBJECT

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 OTYPE FROM OBJEC INTO @DATA(ld_otype).
 
 
"SELECT single REALO FROM OBJEC INTO @DATA(ld_realo).
 
 
"SELECT single ISTAT FROM OBJEC INTO @DATA(ld_istat).
DATA(ld_istat) = ' '.
 
 
"SELECT single BEGDA FROM OBJEC INTO @DATA(ld_begda).
DATA(ld_begda) = '19000101'.
 
"SELECT single ENDDA FROM OBJEC INTO @DATA(ld_endda).
DATA(ld_endda) = '99991231'.
 
DATA(ld_display_only) = ' '.
 
DATA(ld_force_desc) = ' '.
 


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!