SAP RSD_OBJECT_IS_GENERATED Function Module for BW Namespace: Checks Whether an Object Is Generated









RSD_OBJECT_IS_GENERATED is a standard rsd object is generated SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BW Namespace: Checks Whether an Object Is Generated 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 rsd object is generated FM, simply by entering the name RSD_OBJECT_IS_GENERATED into the relevant SAP transaction such as SE37 or SE38.

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



Function RSD_OBJECT_IS_GENERATED 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 'RSD_OBJECT_IS_GENERATED'"BW Namespace: Checks Whether an Object Is Generated
  EXPORTING
   I_OBJNM =  "Object Name
*  I_TLOGO =  "Object Type of Generated Object (TTYP, SHLP, TABL,...)

 IMPORTING
   E_OBJECT_GENERATED =  "Object Is Generated (Indicator)
   E_SYSTP =  "System Type
   E_BWAPPL =  "BW Application
   E_IDENTIFIER =  "Identifier
   E_N' 'GEN =  "Namespace (Prefix) of Generated Object
   E_NAME_W_O_PREFIX =  "Name (without prefix)
   E_IOBJNM =  "Name of InfoObject for Which I_OBJNM Was Generated
   E_INFOCUBE =  "Name of InfoCube for Which I_OBJNM Was Generated
   E_MULTIPROV =  "Name of MultiProvider...
   E_HYBRPROV =  "Name of HybridProvider
   E_ODSOBJECT =  "Name of ODS Object for Which I_OBJNM Was Generated
   E_INFOSET =  "InfoSet Name

EXCEPTIONS
   NSPACEGEN_INVALID = 1
.



IMPORTING Parameters details for RSD_OBJECT_IS_GENERATED

I_OBJNM - Object Name

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

I_TLOGO - Object Type of Generated Object (TTYP, SHLP, TABL,...)

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

EXPORTING Parameters details for RSD_OBJECT_IS_GENERATED

E_OBJECT_GENERATED - Object Is Generated (Indicator)

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

E_SYSTP - System Type

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

E_BWAPPL - BW Application

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

E_IDENTIFIER - Identifier

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

E_NSPACEGEN - Namespace (Prefix) of Generated Object

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

E_NAME_W_O_PREFIX - Name (without prefix)

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

E_IOBJNM - Name of InfoObject for Which I_OBJNM Was Generated

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

E_INFOCUBE - Name of InfoCube for Which I_OBJNM Was Generated

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

E_MULTIPROV - Name of MultiProvider...

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

E_HYBRPROV - Name of HybridProvider

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

E_ODSOBJECT - Name of ODS Object for Which I_OBJNM Was Generated

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

E_INFOSET - InfoSet Name

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

EXCEPTIONS details

NSPACEGEN_INVALID - Generated Namespace Is Invalid

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RSD_OBJECT_IS_GENERATED 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 RS_CHAR30, "   
lv_nspacegen_invalid  TYPE RS_CHAR30, "   
lv_e_object_generated  TYPE RS_BOOL, "   
lv_e_systp  TYPE RSSYSTP, "   
lv_e_bwappl  TYPE RSBWAPPL, "   
lv_e_identifier  TYPE RS_CHAR3, "   
lv_i_tlogo  TYPE RS_TLOGO, "   
lv_e_nspacegen  TYPE NAMESPACE, "   
lv_e_name_w_o_prefix  TYPE RS_CHAR30, "   
lv_e_iobjnm  TYPE RSIOBJNM, "   
lv_e_infocube  TYPE RSINFOCUBE, "   
lv_e_multiprov  TYPE RSMULTIPROV, "   
lv_e_hybrprov  TYPE RSINFOPROV, "   
lv_e_odsobject  TYPE RSDODSOBJECT, "   
lv_e_infoset  TYPE RSQINFOSET. "   

  CALL FUNCTION 'RSD_OBJECT_IS_GENERATED'  "BW Namespace: Checks Whether an Object Is Generated
    EXPORTING
         I_OBJNM = lv_i_objnm
         I_TLOGO = lv_i_tlogo
    IMPORTING
         E_OBJECT_GENERATED = lv_e_object_generated
         E_SYSTP = lv_e_systp
         E_BWAPPL = lv_e_bwappl
         E_IDENTIFIER = lv_e_identifier
         E_NSPACEGEN = lv_e_nspacegen
         E_NAME_W_O_PREFIX = lv_e_name_w_o_prefix
         E_IOBJNM = lv_e_iobjnm
         E_INFOCUBE = lv_e_infocube
         E_MULTIPROV = lv_e_multiprov
         E_HYBRPROV = lv_e_hybrprov
         E_ODSOBJECT = lv_e_odsobject
         E_INFOSET = lv_e_infoset
    EXCEPTIONS
        NSPACEGEN_INVALID = 1
. " RSD_OBJECT_IS_GENERATED




ABAP code using 7.40 inline data declarations to call FM RSD_OBJECT_IS_GENERATED

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!