SAP RH_GET_MOVEPART Function Module for Data selection of attendees still to be rebooked

Search SAP Function Modules

RH_GET_MOVEPART is a standard rh get movepart SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Data selection of attendees still to be rebooked processing and below is the pattern details for this FM, 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 get movepart FM, simply by entering the name RH_GET_MOVEPART into the relevant SAP transaction such as SE37 or SE38.

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

Function RH_GET_MOVEPART 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_GET_MOVEPART'"Data selection of attendees still to be rebooked
  EXPORTING
*  BEGDA = '19000101' "Start date of selection period
*  ENDDA = '99991231' "End date of selection period
*  ISTAT = ' ' "Object status
*  EXTEND = 'X' "Take account of BEGDA, ENDDA, ISTAT ('X')
*  SORT = 'X' "Output sorted (SORT = 'X')
*  LANGU = SY-LANGU "Business event language

TABLES
   EVENTTYP_TAB =  "Table of business event types
   PARTIC =  "Table of attendees to be rebooked
   EVENTS_EXT =  "Table of business event type with attendees to be rebooked

EXCEPTIONS
   NO_MOVEPART = 1 

.

IMPORTING Parameters details for RH_GET_MOVEPART

BEGDA - Start date of selection period

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

ENDDA - End date of selection period

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

ISTAT - Object status

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

EXTEND - Take account of BEGDA, ENDDA, ISTAT ('X')

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

SORT - Output sorted (SORT = 'X')

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

LANGU - Business event language

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

TABLES Parameters details for RH_GET_MOVEPART

EVENTTYP_TAB - Table of business event types

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

PARTIC - Table of attendees to be rebooked

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

EVENTS_EXT - Table of business event type with attendees to be rebooked

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

EXCEPTIONS details

NO_MOVEPART - No attendees to be rebooked exist

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

Copy and paste ABAP code example for RH_GET_MOVEPART 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_GET_MOVEPART

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