SAP RH_ORG_OBJ_ADDRESS_MAINTAIN Function Module for









RH_ORG_OBJ_ADDRESS_MAINTAIN is a standard rh org obj address maintain 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 org obj address maintain FM, simply by entering the name RH_ORG_OBJ_ADDRESS_MAINTAIN into the relevant SAP transaction such as SE37 or SE38.

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



Function RH_ORG_OBJ_ADDRESS_MAINTAIN 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_ORG_OBJ_ADDRESS_MAINTAIN'"
  EXPORTING
*  PLVAR =  "Plan Version
*  ZAV_MODE =  "
   OTYPE =  "Object Type
   OBJID =  "Object ID
*  BEGDA = SY-DATUM "Start Date
*  ENDDA = '99991231' "End Date
*  SUBTY =  "Subtype
*  ISTAT = '1' "Planning Status
*  MAINT =  "Organizational Management: Current mode
*  SCREEN_TYPE = 'F' "Screen type: Full screen (F), Popup (P), Sub-screen (S)

EXCEPTIONS
   NO_ACTIVE_PLVAR = 1    ADDRESS_ERROR = 2
.



IMPORTING Parameters details for RH_ORG_OBJ_ADDRESS_MAINTAIN

PLVAR - Plan Version

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

ZAV_MODE -

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

OTYPE - Object Type

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

OBJID - Object ID

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

BEGDA - Start Date

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

ENDDA - End Date

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

SUBTY - Subtype

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

ISTAT - Planning Status

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

MAINT - Organizational Management: Current mode

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

SCREEN_TYPE - Screen type: Full screen (F), Popup (P), Sub-screen (S)

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

EXCEPTIONS details

NO_ACTIVE_PLVAR - Plan version not active

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

ADDRESS_ERROR -

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

Copy and paste ABAP code example for RH_ORG_OBJ_ADDRESS_MAINTAIN 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 PLVAR, "   
lv_no_active_plvar  TYPE PLVAR, "   
lv_zav_mode  TYPE FLAG, "   
lv_otype  TYPE OTYPE, "   
lv_address_error  TYPE OTYPE, "   
lv_objid  TYPE OTYPE, "   
lv_begda  TYPE BEGDATUM, "   SY-DATUM
lv_endda  TYPE ENDDATUM, "   '99991231'
lv_subty  TYPE SUBTYP, "   
lv_istat  TYPE ISTAT_D, "   '1'
lv_maint  TYPE FLAG, "   
lv_screen_type  TYPE AD_SCRTYPE. "   'F'

  CALL FUNCTION 'RH_ORG_OBJ_ADDRESS_MAINTAIN'  "
    EXPORTING
         PLVAR = lv_plvar
         ZAV_MODE = lv_zav_mode
         OTYPE = lv_otype
         OBJID = lv_objid
         BEGDA = lv_begda
         ENDDA = lv_endda
         SUBTY = lv_subty
         ISTAT = lv_istat
         MAINT = lv_maint
         SCREEN_TYPE = lv_screen_type
    EXCEPTIONS
        NO_ACTIVE_PLVAR = 1
        ADDRESS_ERROR = 2
. " RH_ORG_OBJ_ADDRESS_MAINTAIN




ABAP code using 7.40 inline data declarations to call FM RH_ORG_OBJ_ADDRESS_MAINTAIN

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_begda) = SY-DATUM.
 
DATA(ld_endda) = '99991231'.
 
 
DATA(ld_istat) = '1'.
 
 
DATA(ld_screen_type) = 'F'.
 


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!