SAP RSPC_PROCESS_FINISH Function Module for Finish a Process
RSPC_PROCESS_FINISH is a standard rspc process finish SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Finish a Process 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 process finish FM, simply by entering the name RSPC_PROCESS_FINISH 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): Remote-Enabled
Update:

Function RSPC_PROCESS_FINISH 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_PROCESS_FINISH'"Finish a Process.
EXPORTING
I_LOGID = "Log ID of a Process Chain Run
* I_BATCHDATE = "Release date for background schedule
* I_BATCHTIME = "Release time of scheduled background job
* I_DUMP_AT_ERROR = "Upon Error Create Dump
* I_CHAIN = "Process Chain
I_TYPE = "Process Type
I_VARIANT = "Process Variant (Name)
I_INSTANCE = "Process Instance (Value)
* I_STATE = "Status of a Process
* I_EVENTNO = "Case; Decision; Number of Events
* I_HOLD = "Repress Sending the Follow-On Event
* I_JOB_COUNT = "Job ID
IMPORTING Parameters details for RSPC_PROCESS_FINISH
I_LOGID - Log ID of a Process Chain Run
Data type: RSPC_LOGIDOptional: No
Call by Reference: No ( called with pass by value option)
I_BATCHDATE - Release date for background schedule
Data type: BTCRELDTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_BATCHTIME - Release time of scheduled background job
Data type: BTCRELTMOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DUMP_AT_ERROR - Upon Error Create Dump
Data type: RS_BOOLOptional: Yes
Call by Reference: No ( called with pass by value option)
I_CHAIN - Process Chain
Data type: RSPC_CHAINOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TYPE - Process Type
Data type: RSPC_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
I_VARIANT - Process Variant (Name)
Data type: RSPC_VARIANTOptional: No
Call by Reference: No ( called with pass by value option)
I_INSTANCE - Process Instance (Value)
Data type: RSPC_INSTANCEOptional: No
Call by Reference: No ( called with pass by value option)
I_STATE - Status of a Process
Data type: RSPC_STATEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_EVENTNO - Case; Decision; Number of Events
Data type: RSPC_EVENTNOOptional: Yes
Call by Reference: No ( called with pass by value option)
I_HOLD - Repress Sending the Follow-On Event
Data type: RSPC_HOLDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_JOB_COUNT - Job ID
Data type: BTCJOBCNTOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RSPC_PROCESS_FINISH 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_i_logid | TYPE RSPC_LOGID, " | |||
| lv_i_batchdate | TYPE BTCRELDT, " | |||
| lv_i_batchtime | TYPE BTCRELTM, " | |||
| lv_i_dump_at_error | TYPE RS_BOOL, " | |||
| lv_i_chain | TYPE RSPC_CHAIN, " | |||
| lv_i_type | TYPE RSPC_TYPE, " | |||
| lv_i_variant | TYPE RSPC_VARIANT, " | |||
| lv_i_instance | TYPE RSPC_INSTANCE, " | |||
| lv_i_state | TYPE RSPC_STATE, " | |||
| lv_i_eventno | TYPE RSPC_EVENTNO, " | |||
| lv_i_hold | TYPE RSPC_HOLD, " | |||
| lv_i_job_count | TYPE BTCJOBCNT. " |
|   CALL FUNCTION 'RSPC_PROCESS_FINISH' "Finish a Process |
| EXPORTING | ||
| I_LOGID | = lv_i_logid | |
| I_BATCHDATE | = lv_i_batchdate | |
| I_BATCHTIME | = lv_i_batchtime | |
| I_DUMP_AT_ERROR | = lv_i_dump_at_error | |
| I_CHAIN | = lv_i_chain | |
| I_TYPE | = lv_i_type | |
| I_VARIANT | = lv_i_variant | |
| I_INSTANCE | = lv_i_instance | |
| I_STATE | = lv_i_state | |
| I_EVENTNO | = lv_i_eventno | |
| I_HOLD | = lv_i_hold | |
| I_JOB_COUNT | = lv_i_job_count | |
| . " RSPC_PROCESS_FINISH | ||
ABAP code using 7.40 inline data declarations to call FM RSPC_PROCESS_FINISH
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