SAP RH_OBJECT_IN_MOVE_REGISTER Function Module for

Search SAP Function Modules

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

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

Function RH_OBJECT_IN_MOVE_REGISTER 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_OBJECT_IN_MOVE_REGISTER'"
  EXPORTING
   PLVAR =  "Plan Version
   OTYPE =  "Object Type
   OBJID =  "Object ID
*  CHNG_DATE = SY-DATUM "Date of Change
*  CHNG_TIME = SY-UZEIT "Last change at
*  CHNG_USER = SY-UNAME "
*  ORIGSYSTEM =  "

EXCEPTIONS
   OWN_LOGICAL_SYSTEM_NOT_DEFINED = 1    DUPLICATE_KEY = 2    THIS_SYSTEM_ALREADY_ORIGINAL = 3    DATUM_TIME_TOO_EARLY = 4 

.

IMPORTING Parameters details for RH_OBJECT_IN_MOVE_REGISTER

PLVAR - Plan Version

Data type: HROBJECT-PLVAR
Optional: No
Call by Reference: Yes

OTYPE - Object Type

Data type: HROBJECT-OTYPE
Optional: No
Call by Reference: Yes

OBJID - Object ID

Data type: HROBJECT-OBJID
Optional: No
Call by Reference: Yes

CHNG_DATE - Date of Change

Data type: HRMDORIGIN-END_DATE
Default: SY-DATUM
Optional: Yes
Call by Reference: Yes

CHNG_TIME - Last change at

Data type: HRMDORIGIN-END_TIME
Default: SY-UZEIT
Optional: Yes
Call by Reference: Yes

CHNG_USER -

Data type: HRMDORIGIN-CHNG_USER
Default: SY-UNAME
Optional: Yes
Call by Reference: Yes

ORIGSYSTEM -

Data type: HRMDORIGIN-ORIGSYSTEM
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

OWN_LOGICAL_SYSTEM_NOT_DEFINED -

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

DUPLICATE_KEY -

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

THIS_SYSTEM_ALREADY_ORIGINAL -

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

DATUM_TIME_TOO_EARLY -

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

Copy and paste ABAP code example for RH_OBJECT_IN_MOVE_REGISTER 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.

ABAP code using 7.40 inline data declarations to call FM RH_OBJECT_IN_MOVE_REGISTER

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.

Search for further information about these or an SAP related objects