SAP INFO_OBJECT_WHERE_USED Function Module for









INFO_OBJECT_WHERE_USED is a standard info object where used SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 info object where used FM, simply by entering the name INFO_OBJECT_WHERE_USED into the relevant SAP transaction such as SE37 or SE38.

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



Function INFO_OBJECT_WHERE_USED 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 'INFO_OBJECT_WHERE_USED'"
  EXPORTING
   INFO_OBJECT =  "
*  NESTED_WHERE_USED =  "

 IMPORTING
   ERROR_MSG =  "

TABLES
*  CONTEXT =  "
*  CONVERTED_TO =  "
*  HYPERLINKS =  "
*  INCLUDES =  "
*  STRUCTURES =  "
*  STRUCT_INCLUDES =  "
*  REL_CLASSES =  "
*  PARTNER_CLASSES =  "KEN: Classes
*  RELATIONS_OUT =  "SDOK: List of relationships for information object
*  CONVERTED_FROM =  "
.



IMPORTING Parameters details for INFO_OBJECT_WHERE_USED

INFO_OBJECT -

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

NESTED_WHERE_USED -

Data type: IWPARAMS-FLAG
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for INFO_OBJECT_WHERE_USED

ERROR_MSG -

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

TABLES Parameters details for INFO_OBJECT_WHERE_USED

CONTEXT -

Data type: SDOKPROPTY
Optional: Yes
Call by Reference: Yes

CONVERTED_TO -

Data type: SDOKRELIST
Optional: Yes
Call by Reference: Yes

HYPERLINKS -

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

INCLUDES -

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

STRUCTURES -

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

STRUCT_INCLUDES -

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

REL_CLASSES -

Data type: IWCLASS
Optional: Yes
Call by Reference: Yes

PARTNER_CLASSES - KEN: Classes

Data type: IWCLASS
Optional: Yes
Call by Reference: Yes

RELATIONS_OUT - SDOK: List of relationships for information object

Data type: SDOKRELIST
Optional: Yes
Call by Reference: Yes

CONVERTED_FROM -

Data type: SDOKRELIST
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for INFO_OBJECT_WHERE_USED 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:
lt_context  TYPE STANDARD TABLE OF SDOKPROPTY, "   
lv_error_msg  TYPE IWERRORMSG, "   
lv_info_object  TYPE SDOKOBJECT, "   
lt_converted_to  TYPE STANDARD TABLE OF SDOKRELIST, "   
lt_hyperlinks  TYPE STANDARD TABLE OF SDOKOBJECT, "   
lv_nested_where_used  TYPE IWPARAMS-FLAG, "   
lt_includes  TYPE STANDARD TABLE OF SDOKOBJECT, "   
lt_structures  TYPE STANDARD TABLE OF SDOKOBJECT, "   
lt_struct_includes  TYPE STANDARD TABLE OF SDOKOBJECT, "   
lt_rel_classes  TYPE STANDARD TABLE OF IWCLASS, "   
lt_partner_classes  TYPE STANDARD TABLE OF IWCLASS, "   
lt_relations_out  TYPE STANDARD TABLE OF SDOKRELIST, "   
lt_converted_from  TYPE STANDARD TABLE OF SDOKRELIST. "   

  CALL FUNCTION 'INFO_OBJECT_WHERE_USED'  "
    EXPORTING
         INFO_OBJECT = lv_info_object
         NESTED_WHERE_USED = lv_nested_where_used
    IMPORTING
         ERROR_MSG = lv_error_msg
    TABLES
         CONTEXT = lt_context
         CONVERTED_TO = lt_converted_to
         HYPERLINKS = lt_hyperlinks
         INCLUDES = lt_includes
         STRUCTURES = lt_structures
         STRUCT_INCLUDES = lt_struct_includes
         REL_CLASSES = lt_rel_classes
         PARTNER_CLASSES = lt_partner_classes
         RELATIONS_OUT = lt_relations_out
         CONVERTED_FROM = lt_converted_from
. " INFO_OBJECT_WHERE_USED




ABAP code using 7.40 inline data declarations to call FM INFO_OBJECT_WHERE_USED

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.

 
 
 
 
 
"SELECT single FLAG FROM IWPARAMS INTO @DATA(ld_nested_where_used).
 
 
 
 
 
 
 
 


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!