SAP RSSTATMAN_GET_STATUS Function Module for get status of Apollo status management
RSSTATMAN_GET_STATUS is a standard rsstatman 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 get status of Apollo status management 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 rsstatman get status FM, simply by entering the name RSSTATMAN_GET_STATUS into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSSTATMAN
Program Name: SAPLRSSTATMAN
Main Program: SAPLRSSTATMAN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSSTATMAN_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 'RSSTATMAN_GET_STATUS'"get status of Apollo status management.
EXPORTING
* I_DTA = "InfoProvider
* I_DTA_TYPE = "Data Target Type
* I_METHOD = 'GET_STATUS' "30 Characters
* I_RNR = "Request ID (Data Package)
* I_PROCESS = "Process Type
* I_CHECK_FLAG = ' ' "Boolean
* I_WITH_COMMIT = 'X' "Boolean
IMPORTING
E_STATUS = "Request status (internal display)
TABLES
* E_T_STATUS = "
* E_T_REQMAP = "Mapping from father to son-request of state manager
EXCEPTIONS
REQUEST_NOT_EXIST = 1
IMPORTING Parameters details for RSSTATMAN_GET_STATUS
I_DTA - InfoProvider
Data type: RSSTATMANDTAOptional: Yes
Call by Reference: Yes
I_DTA_TYPE - Data Target Type
Data type: RSSTATMANDTA_TYPEOptional: Yes
Call by Reference: Yes
I_METHOD - 30 Characters
Data type: CHAR30Default: 'GET_STATUS'
Optional: Yes
Call by Reference: Yes
I_RNR - Request ID (Data Package)
Data type: RSREQUIDOptional: Yes
Call by Reference: Yes
I_PROCESS - Process Type
Data type: RSPC_TYPEOptional: Yes
Call by Reference: Yes
I_CHECK_FLAG - Boolean
Data type: RS_BOOLDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_WITH_COMMIT - Boolean
Data type: RS_BOOLDefault: 'X'
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for RSSTATMAN_GET_STATUS
E_STATUS - Request status (internal display)
Data type: RSSTATUSOptional: No
Call by Reference: Yes
TABLES Parameters details for RSSTATMAN_GET_STATUS
E_T_STATUS -
Data type: RSSTATMANSTATUSOptional: Yes
Call by Reference: Yes
E_T_REQMAP - Mapping from father to son-request of state manager
Data type: RSSTATMANREQMAPOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
REQUEST_NOT_EXIST - Request Does Not Exist
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RSSTATMAN_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_dta | TYPE RSSTATMANDTA, " | |||
| lv_e_status | TYPE RSSTATUS, " | |||
| lt_e_t_status | TYPE STANDARD TABLE OF RSSTATMANSTATUS, " | |||
| lv_request_not_exist | TYPE RSSTATMANSTATUS, " | |||
| lt_e_t_reqmap | TYPE STANDARD TABLE OF RSSTATMANREQMAP, " | |||
| lv_i_dta_type | TYPE RSSTATMANDTA_TYPE, " | |||
| lv_i_method | TYPE CHAR30, " 'GET_STATUS' | |||
| lv_i_rnr | TYPE RSREQUID, " | |||
| lv_i_process | TYPE RSPC_TYPE, " | |||
| lv_i_check_flag | TYPE RS_BOOL, " SPACE | |||
| lv_i_with_commit | TYPE RS_BOOL. " 'X' |
|   CALL FUNCTION 'RSSTATMAN_GET_STATUS' "get status of Apollo status management |
| EXPORTING | ||
| I_DTA | = lv_i_dta | |
| I_DTA_TYPE | = lv_i_dta_type | |
| I_METHOD | = lv_i_method | |
| I_RNR | = lv_i_rnr | |
| I_PROCESS | = lv_i_process | |
| I_CHECK_FLAG | = lv_i_check_flag | |
| I_WITH_COMMIT | = lv_i_with_commit | |
| IMPORTING | ||
| E_STATUS | = lv_e_status | |
| TABLES | ||
| E_T_STATUS | = lt_e_t_status | |
| E_T_REQMAP | = lt_e_t_reqmap | |
| EXCEPTIONS | ||
| REQUEST_NOT_EXIST = 1 | ||
| . " RSSTATMAN_GET_STATUS | ||
ABAP code using 7.40 inline data declarations to call FM RSSTATMAN_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.| DATA(ld_i_method) | = 'GET_STATUS'. | |||
| DATA(ld_i_check_flag) | = ' '. | |||
| DATA(ld_i_with_commit) | = 'X'. | |||
Search for further information about these or an SAP related objects