SAP RM_RH_GET_SHIFT_NEXT_CURSOR Function Module for Additiven Shift für eine Regel holen und statischen Cursor setzen
RM_RH_GET_SHIFT_NEXT_CURSOR is a standard rm rh get shift next cursor SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Additiven Shift für eine Regel holen und statischen Cursor setzen 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 rm rh get shift next cursor FM, simply by entering the name RM_RH_GET_SHIFT_NEXT_CURSOR into the relevant SAP transaction such as SE37 or SE38.
Function Group: RMRH
Program Name: SAPLRMRH
Main Program: SAPLRMRH
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RM_RH_GET_SHIFT_NEXT_CURSOR 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 'RM_RH_GET_SHIFT_NEXT_CURSOR'"Additiven Shift für eine Regel holen und statischen Cursor setzen.
IMPORTING
SHIFT = "
REGELID = "
EXCEPTIONS
NOT_FOUND = 1
EXPORTING Parameters details for RM_RH_GET_SHIFT_NEXT_CURSOR
SHIFT -
Data type: FOptional: No
Call by Reference: No ( called with pass by value option)
REGELID -
Data type: JBRREG-REGELIDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RM_RH_GET_SHIFT_NEXT_CURSOR 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_shift | TYPE F, " | |||
| lv_not_found | TYPE F, " | |||
| lv_regelid | TYPE JBRREG-REGELID. " |
|   CALL FUNCTION 'RM_RH_GET_SHIFT_NEXT_CURSOR' "Additiven Shift für eine Regel holen und statischen Cursor setzen |
| IMPORTING | ||
| SHIFT | = lv_shift | |
| REGELID | = lv_regelid | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " RM_RH_GET_SHIFT_NEXT_CURSOR | ||
ABAP code using 7.40 inline data declarations to call FM RM_RH_GET_SHIFT_NEXT_CURSOR
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 REGELID FROM JBRREG INTO @DATA(ld_regelid). | ||||
Search for further information about these or an SAP related objects