SAP BSP_WD_RT_REP_GET_COMP_USAGE Function Module for OBSOLETE - Do not use Replaced by BSPWD_RT_REP_GET_COMP_USAGE









BSP_WD_RT_REP_GET_COMP_USAGE is a standard bsp wd rt rep get comp usage SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for OBSOLETE - Do not use Replaced by BSPWD_RT_REP_GET_COMP_USAGE 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 bsp wd rt rep get comp usage FM, simply by entering the name BSP_WD_RT_REP_GET_COMP_USAGE into the relevant SAP transaction such as SE37 or SE38.

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



Function BSP_WD_RT_REP_GET_COMP_USAGE 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 'BSP_WD_RT_REP_GET_COMP_USAGE'"OBSOLETE - Do not use  Replaced by BSPWD_RT_REP_GET_COMP_USAGE
  EXPORTING
*  START_ROW = 5 "
*  START_COL = 5 "
*  ADD_INTERFACE = ' ' "General Flag
*  COMPONENT_VIEWS =  "description of component usages
*  ENHANCEMENT_SET =  "Enhancement Set

 IMPORTING
   RETURNCODE =  "Character Field Length 1

CHANGING
   ID =  "
   USED_COMPONENT =  "
   INTERFACE_VIEW =  "
*  REFERENCED_USAGE =  "
.



IMPORTING Parameters details for BSP_WD_RT_REP_GET_COMP_USAGE

START_ROW -

Data type: I
Default: 5
Optional: Yes
Call by Reference: Yes

START_COL -

Data type: I
Default: 5
Optional: Yes
Call by Reference: Yes

ADD_INTERFACE - General Flag

Data type: FLAG
Default: ' '
Optional: Yes
Call by Reference: Yes

COMPONENT_VIEWS - description of component usages

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

ENHANCEMENT_SET - Enhancement Set

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

EXPORTING Parameters details for BSP_WD_RT_REP_GET_COMP_USAGE

RETURNCODE - Character Field Length 1

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

CHANGING Parameters details for BSP_WD_RT_REP_GET_COMP_USAGE

ID -

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

USED_COMPONENT -

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

INTERFACE_VIEW -

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

REFERENCED_USAGE -

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

Copy and paste ABAP code example for BSP_WD_RT_REP_GET_COMP_USAGE 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_id  TYPE STRING, "   
lv_start_row  TYPE I, "   5
lv_returncode  TYPE CHAR01, "   
lv_start_col  TYPE I, "   5
lv_used_component  TYPE STRING, "   
lv_add_interface  TYPE FLAG, "   ' '
lv_interface_view  TYPE STRING, "   
lv_component_views  TYPE BSP_WD_RT_REP_COMP_USAGE_T, "   
lv_referenced_usage  TYPE STRING, "   
lv_enhancement_set  TYPE BSP_WD_ENHANCEMENT_SET. "   

  CALL FUNCTION 'BSP_WD_RT_REP_GET_COMP_USAGE'  "OBSOLETE - Do not use Replaced by BSPWD_RT_REP_GET_COMP_USAGE
    EXPORTING
         START_ROW = lv_start_row
         START_COL = lv_start_col
         ADD_INTERFACE = lv_add_interface
         COMPONENT_VIEWS = lv_component_views
         ENHANCEMENT_SET = lv_enhancement_set
    IMPORTING
         RETURNCODE = lv_returncode
    CHANGING
         ID = lv_id
         USED_COMPONENT = lv_used_component
         INTERFACE_VIEW = lv_interface_view
         REFERENCED_USAGE = lv_referenced_usage
. " BSP_WD_RT_REP_GET_COMP_USAGE




ABAP code using 7.40 inline data declarations to call FM BSP_WD_RT_REP_GET_COMP_USAGE

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_start_row) = 5.
 
 
DATA(ld_start_col) = 5.
 
 
DATA(ld_add_interface) = ' '.
 
 
 
 
 


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!