Example Of User Exit

This example code is based on enhancement SUSR0001.This enhancement uses function exit EXIT_SAPLSUSF_001 .

Enhancement : SUSR0001 User Exit after logon to SAP system.
When the User logs in the system ,this exit is called each and every time for every user after logon to the R/3 system.


Function Exit : EXIT_SAPLSUSF_001 .
Every dialog user passes thrugh this function module after logon,It can be used to execute individual customer checks and send mesages to the user.TABLE USR02 CONTAINS LOGON DATA and can be used in this exit to get the user logon data and take necessary actions as required by the customer requirement and even LOG_OFF (not recommended by SAP).

STEPS REQUIRED FOR IMPLEMETING THE EXIT

1) Open CMOD(Project maintenance) Transaction.Enter a project name starting with Z.Press enter.

2) Goto Enhancement window by clicking the enhancement button in the application tool bar.

3) Write SUSR0001 in the enhancement column and press enter.

4) Goto Components window(It will show al the exits included in this enhancement), in our case only one Function Exit will be shown.

5) Double click on the Function exit EXIT_SAPLSUSF_001.
The following function source code will be displayed in the function editor

FUNCTION EXIT_SAPLSUSF_001.*"----------------------------------------------------------------------*"*"Lokale Schnittstelle:*"----------------------------------------------------------------------
INCLUDE ZXUSRU01.
ENDFUNCTION.

6) Double click on the include ZXUSRU01 .If it will ask to create the include say yes .
7)Write the following code in the include.
DATA W_TEXT(30) TYPE C.DATA W_DATE(10) TYPE C.WRITE sy-datum TO W_DATE DD/MM/YYYY.CONCATENATE ' Date is ' W_DATE INTO W_TEXT.
CALL FUNCTION 'POPUP_TO_INFORM' EXPORTING titel = 'Welcome to Paradise !' txt1 = 'Have A Nice Day' txt2 = W_TEXT* TXT3 = ' '* TXT4 = ' '

8)Save the include and activate it .Activate the Project also by going to the menu in CMOD transaction.Now The user exit SUSR0001 has been implemented and is ready to use.
9) Logon to the R/3 system . A dialog box will appear with the message
Welcome to Paradise ! with date .

NOTE: BAPIs like BAPI_USER_GET_DETAIL can also be used to get user info or directly read from tables USR02 etc.
PP User Exit .
This user exit is used in PP and is for u to try
MCP20020 User exit for reading info structure when transferring reqtsit contains function exitEXIT_SAPMMCP6_020
When planned independent requirements are transferred from SOP to program data, the data is read at material/plant level as standard. You can use this user exit to have a greater or smaller number of characteristics for data selection. In this case, the data is read on a different level than that in the standard system.
The interface of this user exit corresponds to that of function module 'MC_PG_TRANSFER_PBED', but the info structure and the key fields table (structure IKEYF) are also transferred. YF). The characteristic attributes of the characteristics used for data must be transferred to the user exit in field 'Value' of the key fields table.
For further information, see function module: 'MC_PG_TRANSFER_PBED'

SAP BIW / BI / BO Terminalogy

Aggregate
An aggregate is a subset of an InfoCube. The objective when using aggregates is to reduce I/O volume. The BW OLAP processor selects an appropriate aggregate during a query run or a navigation step. If no appropriate aggregate exists, the BW OLAP processor retrieves data from the original InfoCube instead.

Aggregate rollup
Aggregate rollup is a procedure to update aggregates with new data loads.

Application component
Application components are used to organize InfoSources. They are similar to the InfoAreas used with InfoCubes. The maximum number of characters allowed for the technical name is 32.

Authorization
An authorization defines what a user can do, and to which SAP objects. For example, a user with an authorization can display and execute, but not change, a query. Authorizations are defined using authorization objects.

Authorization object
An authorization object is used to define user authorizations. It has fields with values to specify authorized activities, such as display and execution, on authorized business objects, such as queries. The maximum number of characters allowed for the technical name is 10.

Authorization profile
An authorization profile is made up of multiple authorizations. The maximum number of characters allowed for the technical name is 10.

Bitmap index
A bitmap index uses maps of bits to locate records in a table. Bitmap indices are very effective for Boolean operations of the WHERE clause of a SELECT statement. When the cardinality of a column is low, a bitmap index size will be small, thereby reducing I/O volume.

Business Content
Business Content is a complete set of BW objects developed by SAP to support the OLAP tasks. It contains roles, workbooks, queries, InfoCubes, key figures, characteristics, update rules, InfoSources, and extractors for SAP R/3, and other mySAP solutions.


BW Monitor
BW Monitor displays data loading status and provides assistance in troubleshooting if errors occur.

BW Scheduler
BW Scheduler specifies when to load data. It is based on the same techniques used for scheduling R/3 background jobs.

BW Statistics
BW Statistics is a tool for recording and reporting system activity and performance information.

Change run
Change run is a procedure used to activate characteristic data changes.

Characteristic
Characteristics are descriptions of key figures, such as Customer ID, Material Number, Sales Representative ID, Unit of Measure, and Transaction Date. The maximum number of characters allowed for the technical name is 9.

Client
A client is a subset of data in an SAP system. Data shared by all clients is called client-independent data, as compared with client-dependent data. When logging on to an SAP system, a user must specify which client to use. Once in the system, the user has access to both client-dependent data and client-independent data.

Communication structure
The communication structure is the structure underlying the InfoSource.

Compound attribute
A compound attribute differentiates a characteristic to make the characteristic uniquely identifiable. For example, if the same characteristic data from different source systems mean different things, then we can add the compound attribute 0SOURSYSTEM (source system ID) to the characteristic; 0SOURSYSTEM is provided with the Business Content.

Data packet size
For the same amount of data, the data packet size determines how work processes will be used in data loading. The smaller the data packet size, the more work processes needed.

Data Warehouse
Data Warehouse is a dedicated reporting and analysis environment based on the star schema database design technique and requiring special attention to the data ETTL process.

DataSource
A DataSource is not only a structure in which source system fields are logically grouped together, but also an object that contains ETTL-related information. Four types of DataSources exist:

DataSources for transaction data
DataSources for characteristic attributes
DataSources for characteristic texts
DataSources for characteristic hierarchies

If the source system is R/3, replicating DataSources from a source system will create identical DataSource structures in the BW system. The maximum number of characters allowed for a DataSource's technical name is 32.

Delta update
The Delta update option in the InfoPackage definition requests BW to load only the data that have been accumulated since the last update. Before a delta update occurs, the delta process must be initialized.

Development class
A development class is a group of objects that are logically related.

Display attribute
A display attribute provides supplemental information to a characteristic.

Drill-down
Drill-down is a user navigation step intended to get further detailed information.

SAP BI Accelerator

SAP BI Accelerator

Those who have worked on squeezing out as much performance as possible with aggregates can appreciate the never-ending and time-consuming nature of analyzing user behavior and creating optimal aggregates for their use (while balancing the impacts this has on data management activities such as aggregate roll-ups, attribute change runs and dreaded re-initialization scenarios.

Aggregate optimization strategies for end-user performance are a subject for the section on “Aggregates” in Chapter 12. From an administrator’s perspective, optimizing aggregates might consist of a roll-up hierarchy plan (filling aggregates from aggregates). From a modeler’s perspective, aggregate optimization may consist of aggregating data into separate data targets to avoid the performance impacts attribute change runs have on aggregates.

The BI accelerator simplifies this world by eliminating a lot of data redundancy through the use of an innovative indexing scheme leveraging SAP’s proprietary search engine technology called TREX. There is only one conceptual “aggregate” and that is the BI accelerator index. InfoCubes can have both aggregates and an BI accelerator index simultaneously, but only one or the other can be active at any given time (that is, one can toggle between the two to evaluate which option is preferred).

From a data-maintenance perspective, the BI accelerator is very similar to an aggregate roll-up. There is the build and fill of the index, as well as roll-ups. However, there are differences to be noted.

From a performance tuning perspective, the differences are a lot more apparent. While aggregates must be manually optimized based on end-user behavior, the plan is for BI Accelerator to automatically adjust it, and index accordingly (that is, zero administration from this perspective). The goal of BI Accelerator is to deliver automatic monitoring, configuration, optimization, and self-repair of the index and TREX-based BI Accelerator engine.

The build and fill of a BI Accelerator index is done manually via the data target context menu, while the roll-ups can be scheduled as process chain variants (the same exact one used for aggregates). Like aggregates, BI Accelerator indexes can be toggled active and inactive manually, and need an attribute change run scheduled after navigational attributes are changed via a master data load.

The data management impact of an attribute change run is very small in comparison to aggregates. This is because aggregates store navigational attributes inside the extended star schema (like a mini-InfoCube), while the BI Accelerator index is predicated on the InfoCube data model where navigational attributes are stored outside the extended star schema. As a result, adjusting the BI Accelerator index is like adjusting master data (no need for realignments).

From a different perspective, InfoCube compressions work differently for aggregates and the BI Accelerator index. Again, aggregates are like mini-InfoCubes and have a request dimension and use compressed (the E table) and uncompressed (the F table) fact tables just like their underlying InfoCube. This makes deletion of a specific request out of an InfoCube easy before compression is run (otherwise, aggregates must be rebuilt).

After compressing an InfoCube, it makes sense to compress the corresponding requests in the aggregates data conservation and performance reasons.

Data compression is not necessary for BI Accelerator indexes, and if compression is run frequently enough, it may prompt the need to rebuild the BI Accelerator index. This is because the index is not updated when compression is run. As a result, it is possible to have a state where there are more entries in the BI Accelerator index than in the InfoCube fact table. To keep the index optimized, at some point it makes sense to rebuild the BI Accelerator index to synchronize it with compressed data.

Identifying the Skills Opportunities Created by the SAP/BO Merger

BI/BO Skills Tips:

1. Custom Report Generation - There will be a shift in reporting emphasis from SAP's BEx tool to the Business Objects reporting environment, centered around Crystal Reports. BEx will continue to be supported in the interim period, but we will see more and more SAP customers looking into BO's reporting capabilities sooner rather than later.

Opportunities for BO Reporting Experts: There are pending opportunities for Crystal and BO reporting experts to break into SAP from the Business Objects side. The long-term SAP-BO roadmap de-emphasizes BEx in favor of BO's best-in-class reporting tools in areas such as Enterprise Reporting (Crystal Reports), Ad-hoc Query and Analysis (Webi, Voyager), and Dashboards (Xcelsius). However, it should be noted that this will more like be a gradual transition than a huge push, given that SAP has guaranteed support for BEx, as well as Web Application Designer and Report Designer, through 2016. SAP is actually combining the best aspects of BEx with BO Voyager for a product to be rolled out in the next couple years, current code named "Pioneer." We should expect the rate of reporting innovation on the BO side to be a major incentive to move SAP users off BEx, while expanding reporting across the enterprise and user base. Another nifty tool to be on the lookout for is Polestar, Business Objects' new open query tool, which Business Objects CEO John Schwarz showed off during his Sapphire '08 keynote. I have already run into some SAP customers who are interested in this tool's capabilities.

Opportunities for SAP Reporting Specialists: There will be opportunities for those SAP folks who are skilled in generating custom SAP reports via BW to bridge the gap to BO, especially if they have a mix of Java and ABAP skills and are familiar with SAP's web-based reporting options as well as customizing SAP Portals.

Opportunities for Functional SAP Specialists: In many companies, the BEx reporting options were embraced by financial users but not as much by users in other departments. Expect the usage of SAP reports to increase significantly as more SAP customers turn to BO reporting tools that are much more flexible for different functional users. This should create opportunities for SAP functional experts to help define and prioritize these expanding reporting needs, ensuring that BO is tapping into the right data sources from the right business processes.

Skills Danger Zone: This BO reporting trend is a bit of a danger zone for the ABAP-based reporting specialist and the ABAP-BW reporting person. SAP has made it clear that its long term reporting commitment will be with the Business Objects suite, meaning that this is another area of SAP where the ABAP/Java hybrid skill set will be more effective than ABAP-only. Panic is not the right response, however. This will be a gradual transition.

2. Business Objects-SAP Integration Opportunities - One of the strengths of Business Objects is that it can pull data from just about any system you can think of, legacy or otherwise. It can pull data from BW and BI as well. Therefore, companies will not be forced into integrating SAP and BO in one particular way. Going forward, however, we can count on SAP pushing the NetWeaver platform as the basis for BI/BO integration, using PI (formerly XI) as the integration hub.

Opportunities for BO Integration Specialists - In the short term, we may see some SAP customers go with a BO-specific integration strategy, especially if they don't have NetWeaver PI running yet. In other words, these projects won't worry about tying in seamlessly with SAP yet; they will just pull the data from many systems, including SAP, and handle the integration and reporting on the BO server. Therefore, there should be some opportunities for BO integration experts to get some SAP exposure here, as more data is pulled into the BO mix.

Whether it's worthwhile for SAP experts to dive into BO integration tools right away is hard to say, but what I can say is that the roadmap calls for the combined BI/BO product to utilize much of Business Object's Enterprise Information Management (EIM) toolkit. If I were an SAP person, in the short term, I'd be more inclined to chase XI/PI exposure, but if the opportunity presented itself to get skills on the BO EIM side, I wouldn't turn it down either, given that it will eventually be a part of SAP. If you want to get a head start on learning about BO's best-in-class EIM data integration toolkit, check this link out. Tools like the Business Objects Data Integrator and Business Objects Rapid Marts may be worth getting experience in.

Opportunities for XI/PI Integration Experts - As noted, we should see more Business Objects-SAP data integration through SAP's XI/PI integration hub. So, those of you who are already gaining PI experience should be in the right place at the right time, and those who are looking for another reason to get skills in PI just found one. In the short term, we may also see some work for BW-BO integration (skipping any data flow through XI/PI).

3. SAP Portals and Role-Based Reporting - It looks like SAP Portals will remain a point of emphasis in terms of delivering role-based reporting, though SAP-BO users will certainly not be tied to delivering reports through SAP's Portal. Other custom GUI options will include the BlackBerry and other handheld devices.

Opportunities for SAP Portals Experts - There will be project needs for SAP Portals experts who are well-versed in designing role-based, user-friendly SAP Portals that pull reporting data from BO or features dashboards with role-specific data and KPIs (Key Performance Indicators).

Opportunities for Visual Composer Skills - Custom GUI design will also call for folks who can work with Visual Composer. For some reason, I have not seen Web Dynpro mentioned as frequently when it comes to Business Objects displays on the SAP side, but we may well see more of that also. Visual Composer has been mentioned frequently in this context.

3. Other BO-driven Opportunities on the SAP Side - There are other BO-related needs that should create some consulting demand on the SAP side. Just how strong that demand will be remains to be seen. Here are some more areas of SAP to target, in relative order of priority:

a. SAP BI Accelerator - One reason that the BO executives were so excited about being acquired, or so they tell us, is the power of BI Accelerator to help ensure super-fast performance, in particular with some of BO's open query and ad-hoc reporting options. So, add one more reason to have BI Accelerator on your resume.

b. SAP Master Data Management (MDM) - SAP MDM figures prominently on the SAP + Business Objects combined roadmap, and we can expect tight integration between SAP MDM and BO's metadata features.

c. SAP Data Warehousing - I don't expect BO to replace the need for SAP data warehousing, which in recent years has centered around BW, and now BI. BO may even increase the need for SAP data warehouse experts who understand how to map out a business intelligence architecture that is the best fit with a particular industry. Another way of looking at it: SAP is shifting its reporting emphasis to BO, but its data warehouse and storage capabilities will remain focused on BW/BI.

d. SAP GRC - (Governance, Risk and Compliance) - the SAP-BO roadmap calls for the use of SAP's own GRC product, so folks who have (or can get) exposure to SAP GRC should be in good shape in this area.

e. SAP EPM (Enterprise Performance Management) - the EPM suite may create casualties on both sides. This is an area where the functionality from both vendors will be combined, and smaller acquisitions galore come into play, such as SAP's OutlookSoft acquisition. SEM (Strategic Enterprise Management), which now resides within BW/BI, may shift into new tools in new locations. However, the fundamentals that drive the need for these tools (better executive-level decision-making and strategic planning) will remain the same, so the tool knowledge should be transferable. For those who want the nitty gritty, here's the EPM suite breakdown:

Business Objects - History

Business Objects is a French enterprise software company, specializing in business intelligence (BI). Since 2007 is part of SAP AG. The company claims more than 42,000 customers worldwide. Their flagship product is BusinessObjects XI, with components that provide performance management, planning, reporting, query and analysis, and enterprise information management. Like many enterprise software companies, Business Objects also offers consulting and education services to help customers deploy their business intelligence projects.

Bernard Liautaud, the chairman and chief strategy officer co-founded Business Objects in 1990 together with Denis Payre and was chief executive officer until September 2005. In 1991, the first customer, France Télécom, was signed. The company went public on NASDAQ in September 1994, making it the first French software company listed in the United States.[citation needed] In 2002, the company made Time Magazine Europe's Digital Top 25 of 2002 and were BusinessWeek Europe Stars of Europe.

On 7 October 2007, SAP AG announced that it will acquire Business Objects for $6.8B. As of 22 January 2008, the corporation is fully operated by SAP; this is seen as part of a growing consolidation trend in the business software industry, with Oracle acquiring Hyperion in 2007 and IBM acquiring Cognos in 2008.

Business Objects had two headquarters in San Jose, California, and Paris, France despite the fact that the biggest office was in Vancouver, BC. The company's stock is traded on both the Nasdaq and Euronext Paris (BOB) stock exchanges.

2007, on 7 October SAP's Chief Executive Henning Kagermann announced a $6.8 billion deal to acquire Business Objects. The deal is expected to be closed in 2008.

2008, On 22 January SAP absorbed all of Business Objects offices eliminating the corporation's name. As of this point Business Objects is no more and the employees officially work for SAP.

BW Useful Function Modules

RSW_RATE_GET_BASIC -- To get exchange rate for combination of source and target currency for defined exchange rate type
WEEK_GET_FIRST_DAY -- First day of week
DATA_TO_PERIOD_CONVERT -- To derive period from Date
RSAPO_SWITCH_BATCH_TO_TRANS, RSAPO_SWITCH_TRANS_TO_BATCH -- To change Transactional cube to basic cube & basic cube to tran cube
BAPI_USER_ACTGROUPS_ASSIGN -- To assign Roles to User
BAPI_USER_GET_DETAILS - To get User Details
SUPRN_INS_OR_DEL_PROFILE -- To insert or delete a Profile
RSBCTDPE_GET_ROLE_FOR_USER -- To see Roles per User
BP_EVENT_RAISE -- To raise an EVENT
RSDTM_ICD_DATA_DOWNLOAD -- To Download data from Infocube
RSPC_API_CHAIN_START -- To Start process Chain
RSPC_PROCESS_FINISH -- To finish any process in Process Chain-- how to use : RSPC_PROCESS_FINISH (To restart PChain)
RSU5_SAPI_BADI -- To enhance Master data(Note : 709816)
RSDMD_DEL_MASTER_DATA -- To delete Master Data
RSMDM_MD_ACTIVATE -- To activate Master Data
BAPI_IOBJ_CREATE -- To Create Infoobjects
BAPI_IOBJ_REORG -- To reorganise Infoobjects
BAPI_IPAK_START -- To start Infopackage
BAPI_IPAK_CHANGE -- To Change Infopackage
BAPI_IPAK_GET_DETAIL -- To get details of Infopackage
RSSM_GET_REQUEST_STATUS -- To get request Status
BAPI_ISREQUEST_GETSTATUS -- To get request status
FILE_GET_NAME -- To get file Name.
RSW_RATE_GET_BASIC -- To Currency Translation
RSAOS_METADATA_UPLOAD -- To Replicate datasources selectively
RSDRD_DELETE_FACTS -- To delete data selectively
RSDU_CHECK_PKEY_FACTTAB_DB6 -- Checks the partitioning key for the fact table of an InfoCube.
RSDU_CHECK_PKEY_ODSTAB_DB6 -- Checks the partitioning key for an ODS table.
RSDU_CHECK_PKEY_PSATAB_DB6 -- Checks the partitioning key for a PSA table
RSDRI_INFOPROV_READ -- To read data from Infocubes

SAP BW TABLES

Transfer Structure
RSTS	Transfer Structure List
RSTSFIELD	Transfer Structure fields
RSTSRULES	Transfer Structure rules
RSAROUTT	Text name of Transfer Routine
DD03T	Text for R/3 Transfer structure Objects
Update Rules
RSUPDROUT	Update rules List
RSUPDDAT	Update rules with routines
RSUPDKEY	Update rule key fields
RSUPDINFO	InfoProvider to Infosource correlation
Embedded ABAP coding for Transfer / Update Rules
RSAABAP	ABAP source code per object routine
InfoPackage
RSLDPIO	Links datasource to infopackages
RSLDPIOT	InfoPackage Text Description
RSLDPRULE	ABAP source code for InfoPackages
RSLDPSEL	Hardcoded selections in InfoPackages
RSMONICDP	Contains the request-id number by data target
RSPAKPOS	List of InfoPackage Groups / InfoPackages

ProcessChain
RSEVENTCHAIN	Event Chain Processing Event Table
RSEVENTHEAD	Header for the event chain
RSEVENTHEADT	Header for the event chain
RSPCCHAIN	Process chain details
RSPCCHAINATTR	Attributes for a Process Chain
RSPCCHAINEVENTS	Multiple Events with Process Chains
RSPCCHAINT	Texts for Chain
RSPCCOMMANDLOG	System Command Execution Logs (Process Chains)
RSPCLOGCHAIN	Cross-Table Log ID / Chain ID
RSPCLOGS	Application Logs for the Process Chains
RSPCPROCESSLOG	Logs for the Chain Runs
RSPCRUNVARIABLES	Variables for Process Chains for Runtime
RSPC_MONITOR	Monitor individual process chains

Queries
RSZELTDIR	Directory of the reporting component elements
RSZELTTXT	Texts of reporting component elements
RSZELTXREF	Directory of query element references
RSRREPDIR	Directory of all reports (Query GENUNIID)
RSZCOMPDIR	Directory of reporting components
RSZRANGE	Selection specification for an element
RSZSELECT	Selection properties of an element
RSZELTDIR	Directory of the reporting component elements
RSZCOMPIC	Assignment reuseable component <-> InfoCube
RSZELTPRIO	Priorities with element collisions
RSZELTPROP	Element properties (settings)
RSZELTATTR	Attribute selection per dimension element
RSZCALC	Definition of a formula element
RSZCEL	Query Designer: Directory of Cells
RSZGLOBV	Global Variables in Reporting

Workbooks
RSRWBINDEX	List of binary large objects (Excel workbooks)
RSRWBINDEXT	Titles of binary objects (Excel workbooks)
RSRWBSTORE	Storage for binary large objects (Excel workbooks)
RSRWBTEMPLATE	Assignment of Excel workbooks as personal templates
RSRWORKBOOK	Where-used list for reports in workbooks

Web templates
RSZWOBJ	Storage of the Web Objects
RSZWOBJTXT	Texts for Templates/Items/Views
RSZWOBJXREF	Structure of the BW Objects in a Template
RSZWTEMPLATE	Header Table for BW HTML Templates
InfoObject
RSDIOBJ	Directory of all InfoObjects
RSDIOBJT	Texts of InfoObjects
RSDIOBJ	Directory of all InfoObjects
RSDIOBJT	Texts of InfoObjects
RSDATRNAV	Navigation Attributes
RSDATRNAVT	Navigation Attributes
RSDBCHATR	Master Data Attributes
RSDCHABAS	Basic Characteristics (for Characteristics,Time Characteristics, and Units)
RSDCHA	Characteristics Catalog
RSDDPA	Data Package Characteristic
RSDIOBJCMP	Dependencies of InfoObjects
RSKYF	Key Figures
RSDTIM	Time Characteristics
RSDUNI	Units

InfoCube
RSDCUBE	Directory of InfoCubes
RSDCUBET	Texts on InfoCubes
RSDCUBEIOBJ	Objects per InfoCube (where-used list)
RSDDIME	Directory of Dimensions
RSDDIMET	Texts on Dimensions
RSDDIMEIOBJ	InfoObjects for each Dimension (Where-Used List)
RSDCUBEMULTI	InfoCubes involved in a MultiCube
RSDICMULTIIOBJ	MultiProvider: Selection/Identification of InfoObjects
RSDICHAPRO	Characteristic Properties Specific to an InfoCube
RSDIKYFPRO	Flag Properties Specific to an InfoCube
RSDICVALIOBJ	InfoObjects of the Stock Validity Table for the InfoCube

Aggregates
RSDDAGGRDIR	Directory of Aggregates
RSDDAGGRCOMP	Description of Aggregates
RSDDAGGRT	Text on Aggregates
RSDDAGGLT	Directory of the aggregates, texts
ODS Object
RSDODSO	Directory of all ODS Objects
RSDODSOT	Texts of all ODS Objects
RSDODSOIOBJ	InfoObjects of ODS Objects
RSDODSOATRNAV	Navigation Attributes for ODS Object
RSDODSOTABL	Directory of all ODS Object Tables
PSA
RSTSODS	Directory of all PSA Tables
DataSource (= OLTP Source)
ROOSOURCE	Header Table for SAP BW DataSources (SAP Source System/BW System)
RODELTAM	BW Delta Procedure (SAP Source System)
RSOLTPSOURCE	Replication Table for DataSources in BW
InfoSource
RSIS	Directory of InfoSources with Flexible Update
RSIST	Texts on InfoSources with Flexible Update
RSISFIELD	InfoObjects of an InfoSource
Communications Structure
RSKS	Communications Structure for InfoSources with Flexible Update
RSKS	Communications Structure (View) for Attributes for an InfoSource with Direct Update
RSKSFIELD	Texts on InfoSources with Flexible Update
RSISFIELD	InfoObjects of an InfoSource with Flexible Update
Transfer Structure
RSTS	Transfer Structure in SAP BW
ROOSGEN	Generated Objects for a DataSource (Transfer Structure, for example in SAP Source System)

Mapping
RSISOSMAP	Mapping Between InfoSources and DataSources (=OLTP Sources)
RSOSFIELDMAP	Mapping Between DataSource Fields and InfoObjects
InfoSpoke
RSBSPOKESELSET	InfoSpoke Directory and Selection Options
RSBSPOKEVSELSET	InfoSpoke Directory with Selection Options and Versioning
SAP BW Statistics
RSDDSTAT	Basic Table for InfoCubes/Queries
RSDDSTATAGGR	Detail Table for Aggregate Setup
RSDDSTATAGGRDEF	Detail Table of Navigation for each InfoCube/Query
RSDDSTATCOND	InfoCube Compression
RSDDSTATDELE	InfoCube Deletions
RSDDSTATWHM	Warehouse Management
Misc
RSSELDONE	InfoPackage selection and job program
RSPSADEL	PSA Table deletion
TBTCP	Job Schedule Definition
TBTCO	Job Schedule Result
RSMONMESS	Monitor Messages
RSERRORLOG	Check loading errors in table
V_RSZGLOBV	Report Variables view table
DEVACCESS	Developer Keys table
TSTC	All Transactions in the system
RSDDAGGRDIR	Directory of the aggregates
ROIDOCPRMS	Control parameters for data transfer from the source system
SMEN_BUFFC	Objects in User's Favorites

Web Item
RSZWITEM	Header Table for BW Web Items
RSZWMDITEM	BW Web Metadata: Template Item ( Dataprovider, Item, … ).
Archiving
RSARCHIPRO	BW Archiving: General Archiving Properties
RSARCHIPROIOBJ	BW Archiving: General Archiving Properties
RSARCHIPROLOC	BW ARchiving: General Local Properties
RSARCHIPROLOCSEL	BW Archiving: Archived Data Area
RSARCHIPROPID	BW Archiving: Program References of InfoProvider
RSARCHREQ	BW Archiving: Archiving Request
RSARCHREQFILES	BW Archiving: Verfified Archive Files
RSARCHREQSEL	BW Archiving: Request-Selections