SAP RSQ_ODSO_GET_RELATED Function Module for determine Infoset to ODS object









RSQ_ODSO_GET_RELATED is a standard rsq odso get related SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for determine Infoset to ODS object 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 rsq odso get related FM, simply by entering the name RSQ_ODSO_GET_RELATED into the relevant SAP transaction such as SE37 or SE38.

Function Group: RSQ_REPOSITORY
Program Name: SAPLRSQ_REPOSITORY
Main Program: SAPLRSQ_REPOSITORY
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RSQ_ODSO_GET_RELATED 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 'RSQ_ODSO_GET_RELATED'"determine Infoset to ODS object
EXPORTING
I_OBJNM = "Object Name

IMPORTING
E_T_OBJ_USED = "Where-Used List

EXCEPTIONS
INVALID_ODS_OBJECT = 1
.



IMPORTING Parameters details for RSQ_ODSO_GET_RELATED

I_OBJNM - Object Name

Data type:
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for RSQ_ODSO_GET_RELATED

E_T_OBJ_USED - Where-Used List

Data type: RSO_T_TLOGO_ASC
Optional: No
Call by Reference: Yes

EXCEPTIONS details

INVALID_ODS_OBJECT - inadmissible ODS object

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RSQ_ODSO_GET_RELATED 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_objnm  TYPE STRING, "   
lv_e_t_obj_used  TYPE RSO_T_TLOGO_ASC, "   
lv_invalid_ods_object  TYPE RSO_T_TLOGO_ASC. "   

  CALL FUNCTION 'RSQ_ODSO_GET_RELATED'  "determine Infoset to ODS object
    EXPORTING
         I_OBJNM = lv_i_objnm
    IMPORTING
         E_T_OBJ_USED = lv_e_t_obj_used
    EXCEPTIONS
        INVALID_ODS_OBJECT = 1
. " RSQ_ODSO_GET_RELATED




ABAP code using 7.40 inline data declarations to call FM RSQ_ODSO_GET_RELATED

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!