SAP RH_MODIFY_SCHEDULE Function Module for Copy an existing schedule to a new business event

Search SAP Function Modules

RH_MODIFY_SCHEDULE is a standard rh modify schedule SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Copy an existing schedule to a new business event 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 modify schedule FM, simply by entering the name RH_MODIFY_SCHEDULE into the relevant SAP transaction such as SE37 or SE38.

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

Function RH_MODIFY_SCHEDULE 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_MODIFY_SCHEDULE'"Copy an existing schedule to a new business event
  EXPORTING
   PLVAR =  "Plan version
   OTYPE =  "Object type of new business event
   OBJID =  "Object ID of new business event
   ISTAT =  "Planning status of new business event
*  BEGDA = ' ' "Start date of new business event
*  CALID = ' ' "Calendar ID for schedule

TABLES
   SCHEDULE_TAB =  "Input/output table for schedule

EXCEPTIONS
   CANNOT_READ_TABLE = 1    CALID_ERROR = 2 

.

IMPORTING Parameters details for RH_MODIFY_SCHEDULE

PLVAR - Plan version

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

OTYPE - Object type of new business event

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

OBJID - Object ID of new business event

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

ISTAT - Planning status of new business event

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

BEGDA - Start date of new business event

Data type: PLOG-BEGDA
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

CALID - Calendar ID for schedule

Data type: P1027-CALID
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for RH_MODIFY_SCHEDULE

SCHEDULE_TAB - Input/output table for schedule

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

EXCEPTIONS details

CANNOT_READ_TABLE - It is not possible to read SCHEDULE_TAB to Index 1

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

CALID_ERROR - Invalid factory calendar

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

Copy and paste ABAP code example for RH_MODIFY_SCHEDULE 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_MODIFY_SCHEDULE

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