SAP RSPC_API_CHAIN_GET_STATUS Function Module for Status of the Process Chain
RSPC_API_CHAIN_GET_STATUS is a standard rspc api chain get status SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Status of the Process Chain 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 api chain get status FM, simply by entering the name RSPC_API_CHAIN_GET_STATUS into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSPC_API
Program Name: SAPLRSPC_API
Main Program: SAPLRSPC_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function RSPC_API_CHAIN_GET_STATUS 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_API_CHAIN_GET_STATUS'"Status of the Process Chain.
EXPORTING
I_CHAIN = "Process Chain
I_LOGID = "Log ID of a Process Chain Run
* I_DONT_UPDATE = "Don't adjust status (less impact)
* I_DONT_POLL = "Don't recalculate status (better performance)
IMPORTING
E_STATUS = "Status of a Process
E_MANUAL_ABORT = "Run Was Terminated Manually
E_MESSAGE = "Status as readable text
E_S_MESSAGE = "Message (ONLY message without anything else)
IMPORTING Parameters details for RSPC_API_CHAIN_GET_STATUS
I_CHAIN - Process Chain
Data type: RSPC_CHAINOptional: No
Call by Reference: No ( called with pass by value option)
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_DONT_UPDATE - Don't adjust status (less impact)
Data type: RS_BOOLOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DONT_POLL - Don't recalculate status (better performance)
Data type: RS_BOOLOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RSPC_API_CHAIN_GET_STATUS
E_STATUS - Status of a Process
Data type: RSPC_STATEOptional: No
Call by Reference: No ( called with pass by value option)
E_MANUAL_ABORT - Run Was Terminated Manually
Data type: RSPC_MANUAL_ABORTOptional: No
Call by Reference: No ( called with pass by value option)
E_MESSAGE - Status as readable text
Data type: SO_TEXT255Optional: No
Call by Reference: No ( called with pass by value option)
E_S_MESSAGE - Message (ONLY message without anything else)
Data type: RSPC_S_MSGOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RSPC_API_CHAIN_GET_STATUS 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_chain | TYPE RSPC_CHAIN, " | |||
| lv_e_status | TYPE RSPC_STATE, " | |||
| lv_i_logid | TYPE RSPC_LOGID, " | |||
| lv_e_manual_abort | TYPE RSPC_MANUAL_ABORT, " | |||
| lv_e_message | TYPE SO_TEXT255, " | |||
| lv_i_dont_update | TYPE RS_BOOL, " | |||
| lv_e_s_message | TYPE RSPC_S_MSG, " | |||
| lv_i_dont_poll | TYPE RS_BOOL. " |
|   CALL FUNCTION 'RSPC_API_CHAIN_GET_STATUS' "Status of the Process Chain |
| EXPORTING | ||
| I_CHAIN | = lv_i_chain | |
| I_LOGID | = lv_i_logid | |
| I_DONT_UPDATE | = lv_i_dont_update | |
| I_DONT_POLL | = lv_i_dont_poll | |
| IMPORTING | ||
| E_STATUS | = lv_e_status | |
| E_MANUAL_ABORT | = lv_e_manual_abort | |
| E_MESSAGE | = lv_e_message | |
| E_S_MESSAGE | = lv_e_s_message | |
| . " RSPC_API_CHAIN_GET_STATUS | ||
ABAP code using 7.40 inline data declarations to call FM RSPC_API_CHAIN_GET_STATUS
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