SAP RSOD_GET_DOC_STORAGE Function Module for Returns Document Repository (SKWF or Portal)
RSOD_GET_DOC_STORAGE is a standard rsod get doc storage SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Returns Document Repository (SKWF or Portal) 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 rsod get doc storage FM, simply by entering the name RSOD_GET_DOC_STORAGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSOD
Program Name: SAPLRSOD
Main Program: SAPLRSOD
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSOD_GET_DOC_STORAGE 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 'RSOD_GET_DOC_STORAGE'"Returns Document Repository (SKWF or Portal).
EXPORTING
I_DOC_CLASS = "BW Document Class
* I_RFCDEST = "RFC destination of portal (' ': Default Portal)
IMPORTING
E_STORED_IN_PORTAL = "='X': Repository in KM Portal; = ' ': Repository in SKWF
E_CM_RM_PREFIX = "Prefix of BI CM Repository Manager (After Migration)
E_SYSTEM_NAME = "System Name in Portal System Landscape
EXCEPTIONS
PORTAL_NOT_FOUND = 1
IMPORTING Parameters details for RSOD_GET_DOC_STORAGE
I_DOC_CLASS - BW Document Class
Data type: RSOD_DOC_CLASSOptional: No
Call by Reference: Yes
I_RFCDEST - RFC destination of portal (SPACE: Default Portal)
Data type: RFCDESTOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for RSOD_GET_DOC_STORAGE
E_STORED_IN_PORTAL - ='X': Repository in KM Portal; = SPACE: Repository in SKWF
Data type: RS_BOOLOptional: No
Call by Reference: Yes
E_CM_RM_PREFIX - Prefix of BI CM Repository Manager (After Migration)
Data type: RSPOR_KM_BI_CM_RM_PREFIXOptional: No
Call by Reference: Yes
E_SYSTEM_NAME - System Name in Portal System Landscape
Data type: RSPOR_SYSTEM_NAMEOptional: No
Call by Reference: Yes
EXCEPTIONS details
PORTAL_NOT_FOUND - Could not find portal
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RSOD_GET_DOC_STORAGE 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_doc_class | TYPE RSOD_DOC_CLASS, " | |||
| lv_portal_not_found | TYPE RSOD_DOC_CLASS, " | |||
| lv_e_stored_in_portal | TYPE RS_BOOL, " | |||
| lv_i_rfcdest | TYPE RFCDEST, " | |||
| lv_e_cm_rm_prefix | TYPE RSPOR_KM_BI_CM_RM_PREFIX, " | |||
| lv_e_system_name | TYPE RSPOR_SYSTEM_NAME. " |
|   CALL FUNCTION 'RSOD_GET_DOC_STORAGE' "Returns Document Repository (SKWF or Portal) |
| EXPORTING | ||
| I_DOC_CLASS | = lv_i_doc_class | |
| I_RFCDEST | = lv_i_rfcdest | |
| IMPORTING | ||
| E_STORED_IN_PORTAL | = lv_e_stored_in_portal | |
| E_CM_RM_PREFIX | = lv_e_cm_rm_prefix | |
| E_SYSTEM_NAME | = lv_e_system_name | |
| EXCEPTIONS | ||
| PORTAL_NOT_FOUND = 1 | ||
| . " RSOD_GET_DOC_STORAGE | ||
ABAP code using 7.40 inline data declarations to call FM RSOD_GET_DOC_STORAGE
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