SAP RSPC_GET_DELAY Function Module for Calculate expected next start

Search SAP Function Modules

RSPC_GET_DELAY is a standard rspc get delay SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Calculate expected next start 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 rspc get delay FM, simply by entering the name RSPC_GET_DELAY into the relevant SAP transaction such as SE37 or SE38.

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

Function RSPC_GET_DELAY 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 'RSPC_GET_DELAY'"Calculate expected next start
  EXPORTING
   I_CHAIN =  "Process Chain
*  I_LOGID =  "Log ID of a Process Chain Run

 IMPORTING
   E_NEXT_START_DATE =  "Current Date of Application Server
   E_NEXT_START_TIME =  "Current Time of Application Server
   E_ACT_DELAY =  "Runtime: Seconds with Decimal Places
   E_AVG_DELTA =  "Runtime: Seconds with Decimal Places
   E_AVG_DELAY =  "Runtime: Seconds with Decimal Places
   E_S_JOB =  "Structure for Transferring Job Header Data (BI-API)
   E_T_STARTTIMES =  "Start Times on Time Axis
   E_PREDECESSOR_WEEKDAY =  "Day of Week

EXCEPTIONS
   FAILED = 1    UNREGULAR = 2    UNSCHEDULED = 3    SCHEDULING_ERROR = 4    UNUSED = 5 

.

IMPORTING Parameters details for RSPC_GET_DELAY

I_CHAIN - Process Chain

Data type: RSPC_CHAIN
Optional: No
Call by Reference: Yes

I_LOGID - Log ID of a Process Chain Run

Data type: RSPC_LOGID
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for RSPC_GET_DELAY

E_NEXT_START_DATE - Current Date of Application Server

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

E_NEXT_START_TIME - Current Time of Application Server

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

E_ACT_DELAY - Runtime: Seconds with Decimal Places

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

E_AVG_DELTA - Runtime: Seconds with Decimal Places

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

E_AVG_DELAY - Runtime: Seconds with Decimal Places

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

E_S_JOB - Structure for Transferring Job Header Data (BI-API)

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

E_T_STARTTIMES - Start Times on Time Axis

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

E_PREDECESSOR_WEEKDAY - Day of Week

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

EXCEPTIONS details

FAILED - General Error

Data type:
Optional: No
Call by Reference: Yes

UNREGULAR - Chain has no detectable periodicity

Data type:
Optional: No
Call by Reference: Yes

UNSCHEDULED - Chain is not currently scheduled

Data type:
Optional: No
Call by Reference: Yes

SCHEDULING_ERROR - Chain is not properly planned

Data type:
Optional: No
Call by Reference: Yes

UNUSED - Chain ihas not run for a longer time

Data type:
Optional: No
Call by Reference: Yes

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

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