SAP RSDAW_REQUEST_SET_STATE Function Module for Invalidates a previously confirmed Request









RSDAW_REQUEST_SET_STATE is a standard rsdaw request set state SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Invalidates a previously confirmed Request 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 rsdaw request set state FM, simply by entering the name RSDAW_REQUEST_SET_STATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: RSDAW_NEARLINE_SERVER
Program Name: SAPLRSDAW_NEARLINE_SERVER
Main Program: SAPLRSDAW_NEARLINE_SERVER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function RSDAW_REQUEST_SET_STATE 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 'RSDAW_REQUEST_SET_STATE'"Invalidates a previously confirmed Request
EXPORTING
I_ARCHIVE_REQUEST_NAME = "Name of archiving request
I_ARCHIVE_REQUEST_SID = "Internal Number (SID) of Archiving Request
I_TARGET_STATE = "(Target) status of archiving request
I_RESTORE_REQUEST_NAME = "Name of reload-request (only for state '80')
I_RESTORE_REQUEST_SID = "Internal number (SID) of reload-request (only for state '80')
I_OWNER = "Owner (redundant, the request name is already unique)
I_TABLE_NAME = "Table name (redundant, the request name is already unique)

IMPORTING
E_ACTUAL_STATE = "Actual status of archiving requests
.



IMPORTING Parameters details for RSDAW_REQUEST_SET_STATE

I_ARCHIVE_REQUEST_NAME - Name of archiving request

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

I_ARCHIVE_REQUEST_SID - Internal Number (SID) of Archiving Request

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

I_TARGET_STATE - (Target) status of archiving request

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

I_RESTORE_REQUEST_NAME - Name of reload-request (only for state '80')

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

I_RESTORE_REQUEST_SID - Internal number (SID) of reload-request (only for state '80')

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

I_OWNER - Owner (redundant, the request name is already unique)

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

I_TABLE_NAME - Table name (redundant, the request name is already unique)

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

EXPORTING Parameters details for RSDAW_REQUEST_SET_STATE

E_ACTUAL_STATE - Actual status of archiving requests

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

Copy and paste ABAP code example for RSDAW_REQUEST_SET_STATE 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_e_actual_state  TYPE RSDAW_REQUEST_STATE, "   
lv_i_archive_request_name  TYPE RSDAW_REQUEST_NAME, "   
lv_i_archive_request_sid  TYPE RSDAW_REQUEST_SID, "   
lv_i_target_state  TYPE RSDAW_REQUEST_STATE, "   
lv_i_restore_request_name  TYPE RSDAW_REQUEST_NAME, "   
lv_i_restore_request_sid  TYPE RSDAW_REQUEST_SID, "   
lv_i_owner  TYPE RSDAW_OWNER, "   
lv_i_table_name  TYPE RSDAW_TABLE_NAME. "   

  CALL FUNCTION 'RSDAW_REQUEST_SET_STATE'  "Invalidates a previously confirmed Request
    EXPORTING
         I_ARCHIVE_REQUEST_NAME = lv_i_archive_request_name
         I_ARCHIVE_REQUEST_SID = lv_i_archive_request_sid
         I_TARGET_STATE = lv_i_target_state
         I_RESTORE_REQUEST_NAME = lv_i_restore_request_name
         I_RESTORE_REQUEST_SID = lv_i_restore_request_sid
         I_OWNER = lv_i_owner
         I_TABLE_NAME = lv_i_table_name
    IMPORTING
         E_ACTUAL_STATE = lv_e_actual_state
. " RSDAW_REQUEST_SET_STATE




ABAP code using 7.40 inline data declarations to call FM RSDAW_REQUEST_SET_STATE

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!