Buy

Buy

List of Posts

Get this widget
To get notifications, Please like our Facebook Page >>>>>>

Use Search box to find a topic in this Blog!!!

Showing posts with label BI Interview Questions. Show all posts
Showing posts with label BI Interview Questions. Show all posts

Interview Questions & Answers


1. What is data integrity?
Data Integrity is about eliminating duplicate entries in the database. Data integrity means no duplicate data.
2. What is the difference between SAP BW 3.0B and SAP BW 3.1C, 3.5?
The best answer here is Business Content. There is additional Business Content provided with BW 3.1C that wasn't found in BW 3.0B. SAP has a pretty decent reference library on their Web site that documents that additional objects found with 3.1C.
 3. What is the difference between SAP BW 3.5 and 7.0?
SAP BW 7.0 is called SAP BI and is one of the components of SAP NetWeaver 2004s. There are many differences between them in areas like extraction, EDW, reporting, analysis administration and so forth. For a detailed description, please refer to the documentation given on help.sap.com. 
1. No Update rules or Transfer rules (Not mandatory in data flow)
2.Instead of update rules and Transfer rules new concept introduced called transformations.
3. New ODS introduced in additional to the Standard and transactional.
4. ODS is renamed as DataStore to meet with the global data warehousing standards.
And lot more changes in the functionalities of BEX query designer and WAD etc.
5. In Infosets now you can include Infocubes as well.
6. The Re-Modeling transaction helps you adding new key figures and characteristics and handles historical data as well without much hassle. This facility is available only for info cube.
7. The BI accelerator (for now only for infocubes) helps in reducing query run time by almost a factor of 10 - 100. This BI accl is a separate box and would cost more. Vendors for these would be HP or IBM.
8. The monitoring has been improved with a new portal based cockpit. Which means you would need to have an EP guy in your project for implementing the portal ! :)
9. Search functionality has improved!! You can search any object. Not like 3.5
10. Transformations are in and routines are passe! Yes, you can always revert to the old transactions too.
4. What is index?
Indices/Indexes are used to locate needed records in a database table quickly. BW uses two types of indices, B-tree indices for regular database tables and bitmap indices for fact tables and aggregate tables.
5. What is KPIs (Key Performance Indicators)?
(1) Predefined calculations that render summarized and/or aggregated information, which is useful in making strategic decisions.
(2) Also known as Performance Measure, Performance Metric measures. KPIs are put in place and visible to an organization to indicate the level of progress and status of change efforts in an organization.
KPIs are industry-recognized measurements on which to base critical business decisions.
In SAP BW, Business Content KPIs have been developed based upon input from customers, partners, and industry experts to ensure that they reflect best practices.

6. What is the use of process chain?
The use of Process Chain is to automate the data load process.
Used to automate all the processes including Data load and all Administrative Tasks like indices creation deletion, Cube compression etc.
Highly controlled data loading.
7. Difference between Display Attribute and Navigational Attribute?
The basic difference between the two is that navigational attributes can be used to drilldown in a Bex report whereas display attributes cannot be used so. A navigational attribute would function more or less like a characteristic within a cube.

To enable these features of a navigational attribute, the attribute needs to be made navigational in the cube apart from the master data info-object.
The only difference is that navigation attributes can be used for navigation in queries, like filtering, drill-down etc.
You can also use hierarchies on navigational attributes, as it is possible for characteristics.
But an extra feature is that there is a possibility to change your history. (Please look at the relevant time scenarios). If navigation attributes changes for a characteristic, it is changed for all records in the past.
Disadvantage is also a slow down in performance.
8. If there are duplicate data in Cubes, how would you fix it?
Delete the request ID, Fix data in PSA or ODS and re-load again from PSA / ODS.

9. What are the differences between ODS and Info Cube?
ODS holds transactional level data. It’s just as a flat table. It’s not based on multidimensional model. ODS have three tables
1. Active Data table (A table containing the active data)
2. Change log Table (Contains the change history for delta updating from the ODS Object into other data targets, such as ODS Objects or InfoCubes for example.)
3. Activation Queue table (For saving ODS data records that are to be updated but that have not yet been activated. The data is deleted after the records have been activated)

Whereas Cube holds aggregated data which is not as detailed as ODS. Cube is based on multidimensional model.
An ODS is a flat structure. It is just one table that contains all data.
Most of the time you use an ODS for line item data. Then you aggregate this data to an info cube
One major difference is the manner of data storage. In ODS, data is stored in flat tables. By flat I mean to say ordinary transparent table whereas in a CUBE, it composed of multiple tables arranged in a STAR SCHEMA joined by SIDs. The purpose is to do MULTI-DIMENSIONAL Reporting

In ODS; we can delete / overwrite the data load but in cube – only add is possible, no overwrite.
10. What is the use of change log table?
Change log is used for delta updates to the target; it stores all changes per request and updates the target.
11. Difference between InfoSet and Multiprovider
a) The operation in Multiprovider is "Union" where as in Infoset it is either "inner join" or "Outer join".

b) You can add Info-cube, ODS, Info-object in Multiprovider whereas in an Infoset you can only have ODS and Info-object.
c) An Infoset is an Info-provider that joins data from ODS and Info-objects( with master data). The join may be a outer join or a inner join. Whereas a Multiprovider is created on all types of Infoproviders - Cubes, ODS, Info-object. These InfoProviders are connected to one another by a union operation.
d) A union operation is used to combine the data from these objects into a MultiProvider. Here, the system constructs the union set of the data sets involved. In other words, all values of these data sets are combined. As a comparison: InfoSets are created using joins. These joins only combine values that appear in both tables. In contrast to a union, joins form the intersection of the tables.
12. What is the T.Code for Data Archival and what is it's advantage?
SARA.
Advantage: To minimize space, Query performance and Load performance
13. What are the Data Loading Tuning from R/3 to BW, FF to BW?
a) If you have enhanced an extractor, check your code in user exit RSAP0001 for expensive SQL statements, nested selects and rectify them.
b) Watch out the ABAP code in Transfer and Update Rules, this might slow down performance
c) If you have several extraction jobs running concurrently, there probably are not enough system resources to dedicate to any single extraction job. Make sure schedule this job judiciously.
d) If you have multiple application servers, try to do load balancing by distributing the load among different servers.
e) Build secondary indexes on the under lying tables of a DataSource to correspond to the fields in the selection criteria of the datasource. ( Indexes on Source tables)
f) Try to increase the number of parallel processes so that packages are extracted parallelly instead of sequentially. (Use PSA and Data Target in parallel option in the info package.)
g) Buffer the SID number ranges if you load lot of data at once.
h) Load master data before loading transaction data.
i) Use SAP Delivered extractors as much as possible.
j) If your source is not an SAP system but a flat file, make sure that this file is housed on the application server and not on the client machine. Files stored in an ASCII format are faster to load than those stored in a CSV format.

14. Performance monitoring and analysis tools in BW
a) System Trace: Transaction ST01 lets you do various levels of system trace such as authorization checks, SQL traces, table/buffer trace etc. It is a general Basis tool but can be leveraged for BW.
b) Workload Analysis: You use transaction code ST03
c) Database Performance Analysis: Transaction ST04 gives you all that you need to know about what’s happening at the database level.
d) Performance Analysis: Transaction ST05 enables you to do performance traces in different are as namely SQL trace, Enqueue trace, RFC trace and buffer trace.

e) BW Technical Content Analysis: SAP Standard Business Content 0BWTCT that needs to be activated. It contains several InfoCubes, ODS Objects and MultiProviders and contains a variety of performance related information.
f) BW Monitor: You can get to it independently of an InfoPackage by running transaction RSMO or via an InfoPackage. An important feature of this tool is the ability to retrieve important IDoc information.
g) ABAP Runtime Analysis Tool: Use transaction SE30 to do a runtime analysis of a transaction, program or function module. It is a very helpful tool if you know the program or routine that you suspect is causing a performance bottleneck.
15. Difference between Transfer Rules and Update Rules
a) Transfer Rules:
When we maintains the transfer structure and the communication structure, we use the transfer rules to determine how we want the transfer structure fields to be assigned to the communication structure InfoObjects. We can arrange for a 1:1 assignment. We can also fill InfoObjects using routines, formulas, or constants.
Update rules:
Update rules specify how the data (key figures, time characteristics, characteristics) is updated to data targets from the communication structure of an InfoSource. You are therefore connecting an InfoSource with a data target.
b) Transfer rules are linked to InfoSource, update rules are linked to InfoProvider (InfoCube, ODS).
i. Transfer rules are source system dependant whereas update rules are Data target dependant.
ii.The no. of transfer rules would be equal to the no. of source system for a data target.

iii.Transfer rules is mainly for data cleansing and data formatting whereas in the update rules you would write the business rules for your data target.
iv. Currency translations are possible in update rules.
c) Using transfer rules you can assign DataSource fields to corresponding InfoObjects of the InfoSource. Transfer rules give you possibility to cleanse data before it is loaded into BW.
Update rules describe how the data is updated into the InfoProvider from the communication structure of an InfoSource.
If you have several InfoCubes or ODS objects connected to one InfoSource you can for example adjust data according to them using update rules.

Only in Update Rules: a. You can use return tables in update rules which would split the incoming data package record into multiple ones. This is not possible in transfer rules.
b. Currency conversion is not possible in transfer rules.
c. If you have a key figure that is a calculated one using the base key figures you would do the calculation only in the update rules.
16. What is OSS?
OSS is Online support system runs by SAP to support the customers.
You can access this by entering OSS1 transaction or visit Service.SAP.Com and access it by providing the user name and password.
17. How to transport BW object?
Follow the steps.

i. RSA1 > Transport connection
ii. In the right window there is a category "all object according to type"
iii. Select required object you want to transport.
iv. Expand that object, there is select object, double click on this you will get the number of objects, select yours one.
v. Continue.
vi. Go with the selection, select all your required objects you want to transport.
vii. There is icon Transport Object (Truck Symbol).
viii. Click that, it will create one request, note it down this request.
ix. Go to Transport Organizer (T.code SE01).
x. In the display tab, enter the Request, and then go with display.
xi. Check your transport request whether contains the required objects or not, if not go with edit, if yes "Release" that request.

That’s it; your coordinator/Basis person will move this request to Quality or Production.
18. How to unlock objects in Transport Organizer?
To unlock a transport use Go to SE03 --> Request Task --> Unlock Objects
Enter your request and select unlock and execute. This will unlock the request.
19. What is InfoPackage Group?
An InfoPackage group is a collection of InfoPackages.

20. Differences Between Infopackage Groups and Process chains
i.Info Package Groups are used to group only Infopackages
where as Process chains are used to automate all the processes.
ii Infopackage goups:
Use to group all relevent infopackages in a group, (Automation of a group of infopackages only for dataload). Possible to Sequence the load in order.
Process Chains:
Used to automate all the processes including Dataload
and all Administrative Tasks like indices creation deletion, Cube compression etc
Highly controlled dataloading.
iii. InfoPackage Groups/Event Chains are older methods of scheduling/automation. Process Chains are newer and provide more capabilities. We can use ABAP programs and lot of additional features like ODS activation and sending emails to users based on success or failure of data loads.

21. What are the critical issues you faced and how did you solve it?
Find your own answer based on your experience.. 
22. What is Conversion Routine?
a) Conversion Routines are used to convert data types from internal format to external/display format or vice versa.
b) These are function modules.
c) There are many function modules, they will be of type
CONVERSION_EXIT_XXXX_INPUT, CONVERSION_EXIT_XXXX_OUTPUT.

example:

CONVERSION_EXIT_ALPHA_INPUT
CONVERSION_EXIT_ALPHA_OUTPUT

23. Difference between Start Routine and Conversion Routine
In the start routine you can modify data packages when data loading. Conversion routine usually refers to routines bound to InfoObjects (or data elements) for conversion of internal and display format.
24. What is the use of setup tables in LO extraction?
The use of setup table is to store your historical data in them before updating to the target system. Once you fill up the setup tables with the data, you need not to go to the application tables again and again which in turn will increase your system performance.

25. R/3 to ODS delta update is good but ODS to Cube delta is broken. How to fix it?
i. Check the Monitor (RSMO) what’s the error explanation. Based on explanation, we can check the reason

ii. Check the timings of delta load from R3 – ODS – CUBE if conflicting after ODS load

iii. Check the mapping of Transfer/Update Rules

iv. Fails in RFC connection
v. BW is not set as source system

vi. Dump (for a lot of reasons, full table space, time out, sql errors...)
Do not receive an IDOC correctly.

vii. There is a error load before the last one and so on...
26. What is short dump and how to rectify?
Short dump specifies that an ABAP runtime error has occurred and the error messages are written to the R/3 database tables. You can view the short dump through transaction ST22.
You get short dumps b'coz of runtime errors. The short dump u got is due to the termination of background job. This could be of many reasons.

You can check short dumps in T-code ST22. U can give the job tech name and your userid. It will show the status of jobs in the system. Here you can even analyze short dump. U can use ST22 in both R/3 and BW.

OR To call an analysis method,
choose Tools --> ABAP Workbench --> Test --> Dump-Analysis from the SAP Easy Access menu.
In the initial screen, you must specify whether you want to view today’s dump or the dump from yesterday. If these selection criteria are too imprecise, you can enter more specific criteria. To do this, choose Goto --> Select Short Dump
You can display a list of all ABAP dumps by choosing Edit --> Display List. You can then display and analyze a selected dump. To do this, choose Short Dump --> Dump Analysis.

Interview Questions

Q) I want to delete a BEx query that is in Production system through request. Is anyone aware about it?
A) Have you tried the RSZDELETE transaction?

Q) What are the five ASAP Methodologies?
A: Project plan, Business Blue print, Realization, Final preparation & Go-Live - support.
1. Project Preparation: In this phase, decision makers define clear project objectives and an efficient decision making process (i.e. Discussions with the client, like what are his needs and requirements etc.). Project managers will be involved in this phase (I guess). A Project Charter is issued and an implementation strategy is outlined in this phase.
2. Business Blueprint: It is a detailed documentation of your company's requirements. (i.e. what are the objects we need to develop are modified depending on the client's requirements).
3. Realization: In this only, the implementation of the project takes place (development of objects etc) and we are involved in the project from here only.
4. Final Preparation: Final preparation before going live i.e. testing, conducting pre-go-live, end user training etc. End user training is given that is in the client site you train them how to work with the new environment, as they are new to the technology.
5. Go-Live & support: The project has gone live and it is into production. The Project team will be supporting the end users.


Q) What is landscape of R/3 & what is landscape of BW. Landscape of R/3
A) Landscape of b/w: u have the development system, testing system, production system Development system: All the implementation part is done in this sys. (I.e., Analysis of objects developing, modification etc) and from here the objects are transported to the testing system, but before transporting an initial test known as Unit testing (testing of objects) is done in the development sys. Testing/Quality system: quality check is done in this system and integration testing is done.
Production system: All the extraction part takes place in this sys.

Q). Difference between infocube and ODS?
A: Infocube is structured as star schema (extended) where a fact table is surrounded by different dim table that are linked with DIM'ids. And the data wise, you will have aggregated data in the cubes. No overwrite functionality. ODS is a flat structure (flat table) with no star schema concept and which will have granular data (detailed level). Overwrite functionality.
Also check the following link:

Q) What is ODS?

Q) What is InfoSet?
A) An InfoSet is a special view of a dataset, such as logical database, table join, table, and sequential file, and is used by SAP Query as a source data. InfoSets determine the tables or fields in these tables that can be referenced by a report. In most cases, InfoSets are based on logical databases. SAP Query includes a component for maintaining InfoSets. When you create an InfoSet, a DataSource in an application system is selected. Navigating in a BW to an InfoSet Query, using one or more ODS objects or InfoObjects. You can also drill-through to BEx queries and InfoSet Queries from a second BW system that is connected as a data mart. _The InfoSet Query functions allow you to report using flat data tables (master data reporting). Choose InfoObjects or ODS objects as data sources. These can be connected using joins. You define the data sources in an InfoSet. An InfoSet can contain data from one or more tables that are connected to one another by key fields. The data sources specified in the InfoSet form the basis of the InfoSet Query.


Q) What does InfoCube contains?
A) Each InfoCube has one FactTable & a maximum of 16 (13+3 system defined, time, unit & data packet) dimensions.

Q). Differences between STAR Schema & Extended Schema?
A) In STAR SCHEMA, A FACT Table in center, surrounded by dimensional tables and the dimension tables contains of master data. In Extended Schema the dimension tables does not contain master data, instead they are stored in Masterdata tables divided into attributes, text & hierarchy. These Masterdata & dimensional tables are linked with each other with SID keys. Masterdata tables are independent of Infocube & reusability in other InfoCubes.

Q) What does FACT Table contain?
A FactTable consists of KeyFigures. Each Fact Table can contain a maximum of 233 key figures. Dimension can contain up to 248 freely available characteristics.

Q) How many dimensions are in a CUBE?
A) 16 dimensions. (13 user defined & 3 system pre-defined [time, unit & data packet])

Q) What does SID Table contain?
SID keys linked with dimension table & master data tables (attributes, texts, hierarchies)

Q) What does ATTRIBUTE Table contain?
Master attribute data
Q) What does TEXT Table contain?
Master text data, short text, long text, medium text & language key if it is language dependent

Q) What does Hierarchy table contain?
Master hierarchy data

Q) How would we delete the data in ODS?
A) By request IDs, Selective deletion & change log entry deletion.

Q) How would we delete the data in change log table of ODS?
A) Context menu of ODS → Manage → Environment → change log entries.

Q) Difference between display attributes and navigational attributes?
A: Display attribute is one, which is used only for display purpose in the report. Where as navigational attribute is used for drilling down in the report. We don't need to maintain Navigational attribute in the cube as a characteristic (that is the advantage) to drill down.

Q) What are the extra fields does PSA contain?
A) (4) Record id, Data packet …

Q) Partitioning possible for ODS?
A) No, It's possible only for Cube.

Q) Why partitioning?
A) For performance tuning.

Q) Different types of Attributes?
A) Navigational attribute, Display attributes, Time dependent attributes, Compounding attributes, Transitive attributes, Currency attributes.



Q. CAN U ADD A NEW FIELD AT THE ODS LEVEL?
Sure you can. ODS is nothing but a table.

Q) Why we delete the setup tables (LBWG) & fill them (OLI*BW)?
A) Initially we don't delete the setup tables but when we do change in extract structure we go for it. We r changing the extract structure right, that means there are some newly added fields in that which r not before. So to get the required data (i.e.; the data which is required is taken and to avoid redundancy) we delete n then fill the setup tables. To refresh the statistical data. The extraction set up reads the dataset that you want to process such as, customers orders with the tables like VBAK, VBAP) & fills the relevant communication structure with the data. The data is stored in cluster tables from where it is read when the initialization is run. It is important that during initialization phase, no one generates or modifies application data, at least until the tables can be set up.

Q) Different types of INFOCUBES.

Q) WHAT ARE THE DIFFERENT VARIABLES USED IN BEX?
A ) Different Variable's are Texts, Formulas, Hierarchies, Hierarchy nodes & Characteristic values. Variable Types are Manual entry /default value Replacement path SAP exit Customer exit Authorization

Q) WHAT ARE INDEXES?
Indexes are data base indexes, which help in retrieving data fastly.

Q) CAN CHARECTERSTIC INFOOBJECT CAN BE INFOPROVIDER.
Of course

Q) What types of partitioning are there for BW?
There are two Partitioning Performance aspects for BW (Cube & PSA) Query Data Retrieval Performance Improvement: Partitioning by (say) Date Range improves data retrieval by making best use of database [data range] execution plans and indexes (of say Oracle database engine). B) Transactional Load Partitioning Improvement: Partitioning based on expected load volumes and data element sizes. Improves data loading into PSA and Cubes by infopackages (Eg. without timeouts).

Q) What are Process Chains?
A) TCode is RSPC, is a sequence of processes scheduled in the background & waiting to be triggered by a specific event. Process chains nothing but grouping processes. Process variant (start variant) is the place the process chain knows where to start. There should be min and max one start variant in each process chain, here we specify when should the process chain start by giving date and time or if you want to start immediately Some of theses processes trigger an event of their own that in-turn triggers other processes. Ex: - Start chain → Delete BCube indexes → Load data from the source system to PSA → Load data from PSA to DataTarget ODS → Load data from ODS to BCube → Create Indexes for BCube after loading data → Create database statistics → Roll-Up data into the aggregate → Restart chain from beginning.

Q) What are Process Types & Process variant?
A) Process types are General services, Load Process & subsequent processing, Data Target Administration, Reporting agent & Other BW services. Process variant (start variant) is the place the process type knows when & where to start.

Q) Types of Updates?
A) Full Update, Init Delta Update & Delta Update.

Q) For what we use HIDE fields, SELECT fields & CANCELLATION fields?
A) Selection fields-- The only purpose is when we check this column, the field will appear in InfoPackage Data selection tab. Hide fields -- These fields are not transferred to BW transfer structure. Cancellation - It will reverse the posted documents of keyfigures of customer defined by multiplying it with -1...and nullifying the value. I think this is reverse posting

Q) How can I compare data in R/3 with data in a BW Cube after the daily delta loads?
Are there any standard procedures for checking them or matching the number of records?
A) You can go to R/3 TCode RSA3 and run the extractor. It will give you the number of records extracted. Then go to BW Monitor to check the number of records in the PSA and check to see if it is the same & also in the monitor header tab. A) RSA3 is a simple extractor checker program that allows you to rule out extracts problems in R/3. It is simple to use, but only really tells you if the extractor works. Since records that get updated into Cubes/ODS structures are controlled by Update Rules, you will not be able to determine what is in the Cube compared to what is in the R/3 environment. You will need to compare records on a 1:1 basis against records in R/3 transactions for the functional area in question. I would recommend enlisting the help of the end user community to assist since they presumably know the data. To use RSA3, go to it and enter the extractor ex: 2LIS_02_HDR. Click execute and you will see the record count, you can also go to display that data. You are not modifying anything so what you do in RSA3 has no effect on data quality afterwards. However, it will not tell you how many records should be expected in BW for a given load. You have that information in the monitor RSMO during and after data loads. From RSMO for a given load you can determine how many records were passed through the transfer rules from R/3, how many targets were updated, and how many records passed through the Update Rules. It also gives you error messages from the PSA.

Q) X & Y Tables? X-table = A table to link material SIDs with SIDs for time-independent navigation attributes. Y-table = A table to link material SIDs with SIDS for time-dependent navigation attributes. There are four types of sid tables X time independent navigational attributes sid tables Y time dependent navigational attributes sid tables H hierarchy sid tables I hierarchy structure sid tables

Q) How to know in which table (SAP BW) contains Technical Name / Description and creation data of a particular Reports. Reports that are created using BEx Analyzer.
A) There is no such table in BW if you want to know such details while you are opening a particular query press properties button you will come to know all the details that you wanted. You will find your information about technical names and description about queries in the following tables. Directory of all reports (Table RSRREPDIR) and Directory of the reporting component elements (Table RSZELTDIR) for workbooks and the connections to queries check Where- used list for reports in workbooks (Table RSRWORKBOOK) Titles of Excel Workbooks in InfoCatalog (Table RSRWBINDEXT)

Q) What is a LUW in the delta queue?
A) A LUW from the point of view of the delta queue can be an individual document, a group of documents from a collective run or a whole data packet of an application extractor.

Q) Why does the number in the 'Total' column in the overview screen of Transaction RSA7 differ from the number of data records that is displayed when you call the detail view?
A) The number on the overview screen corresponds to the total of LUWs (see also first question) that were written to the qRFC queue and that have not yet been confirmed. The detail screen displays the records contained in the LUWs. Both, the records belonging to the previous delta request and the records that do not meet the selection conditions of the preceding delta init requests are filtered out. Thus, only the records that are ready for the next delta request are displayed on the detail screen. In the detail screen of Transaction RSA7, a possibly existing customer exit is not taken into account.

Q) Why does Transaction RSA7 still display LUWs on the overview screen after successful delta loading?
A) Only when a new delta has been requested does the source system learn that the previous delta was successfully loaded to the BW System. Then, the LUWs of the previous delta may be confirmed (and also deleted). In the meantime, the LUWs must be kept for a possible delta request repetition. In particular, the number on the overview screen does not change when the first delta was loaded to the BW System.

Q) Why is there a DataSource with '0' records in RSA7 if delta exists and has also been loaded successfully?
It is most likely that this is a DataSource that does not send delta data to the BW System via the delta queue but directly via the extractor (delta for master data using ALE change pointers). Such a DataSource should not be displayed in RSA7. This error is corrected with BW 2.0B Support Package 11.

Q) Do the entries in table ROIDOCPRMS have an impact on the performance of the loading procedure from the delta queue?
A) The impact is limited. If performance problems are related to the loading process from the delta queue, then refer to the application-specific notes (for example in the CO-PA area, in the logistics cockpit area and so on). Caution: As of Plug In 2000.2 patch 3 the entries in table ROIDOCPRMS are as effective for the delta queue as for a full update. Please note, however, that LUWs are not split during data loading for consistency reasons. This means that when very large LUWs are written to the DeltaQueue, the actual package size may differ considerably from the MAXSIZE and MAXLINES parameters.

Q) What is the purpose of function 'Delete data and meta data in a queue' in RSA7?
What exactly is deleted?
A) You should act with extreme caution when you use the deletion function in the delta queue. It is comparable to deleting an InitDelta in the BW System and should preferably be executed there. You do not only delete all data of this DataSource for the affected BW System, but also lose the entire information concerning the delta initialization. Then you can only request new deltas after another delta initialization. When you delete the data, the LUWs kept in the qRFC queue for the corresponding target system are confirmed. Physical deletion only takes place in the qRFC outbound queue if there are no more references to the LUWs. The deletion function is for example intended for a case where the BW System, from which the delta initialization was originally executed, no longer exists or can no longer be accessed.

Q) What is the relationship between RSA7 and the qRFC monitor (Transaction SMQ1)?
A) The qRFC monitor basically displays the same data as RSA7. The internal queue name must be used for selection on the initial screen of the qRFC monitor. This is made up of the prefix 'BW, the client and the short name of the DataSource. For DataSources whose name are 19 characters long or shorter, the short name corresponds to the name of the DataSource. For DataSources whose name is longer than 19 characters (for delta-capable DataSources only possible as of PlugIn 2001.1) the short name is assigned in table ROOSSHORTN. In the qRFC monitor you cannot distinguish between repeatable and new LUWs. Moreover, the data of a LUW is displayed in an unstructured manner there.

Q) I loaded several delta inits with various selections. For which one is the delta loaded?
A) For delta, all selections made via delta inits are summed up. This means, a delta for the 'total' of all delta initializations is loaded.

Q) How many selections for delta inits are possible in the system?
A) With simple selections (intervals without complicated join conditions or single values), you can make up to about 100 delta inits. It should not be more. With complicated selection conditions, it should be only up to 10-20 delta inits. Reason: With many selection conditions that are joined in a complicated way, too many 'where' lines are generated in the generated ABAP source code that may exceed the memory limit.

Q) I intend to copy the source system, i.e. make a client copy. What will happen with delta? Should I initialize again after that?
A) Before you copy a source client or source system, make sure that your deltas have been fetched from the DeltaQueue into BW and that no delta is pending. After the client copy, an inconsistency might occur between BW delta tables and the OLTP delta tables as described in Note 405943. After the client copy, Table ROOSPRMSC will probably be empty in the OLTP since this table is client-independent. After the system copy, the table will contain the entries with the old logical system name that are no longer useful for further delta loading from the new logical system. The delta must be initialized in any case since delta depends on both the BW system and the source system. Even if no dump 'MESSAGE_TYPE_X' occurs in BW when editing or creating an InfoPackage, you should expect that the delta have to be initialized after the copy.

Q) Despite of the delta request being started after completion of the collective run (V3 update), it does not contain all documents. Only another delta request loads the missing documents into BW. What is the cause for this "splitting"?
A) The collective run submits the open V2 documents for processing to the task handler, which processes them in one or several parallel update processes in an asynchronous way. For this reason, plan a sufficiently large "safety time window" between the end of the collective run in the source system and the start of the delta request in BW. An alternative solution where this problem does not occur is described in Note 505700.

Q) In SMQ1 (qRFC Monitor) I have status 'NOSEND'. In the table TRFCQOUT, some entries have the status 'READY', others 'RECORDED'. ARFCSSTATE is 'READ'. What do these statuses mean? Which values in the field 'Status' mean what and which values are correct and which are alarming? Are the statuses BW-specific or generally valid in qRFC?
A) Table TRFCQOUT and ARFCSSTATE: Status READ means that the record was read once either in a delta request or in a repetition of the delta request. However, this does not mean that the record has successfully reached the BW yet. The status READY in the TRFCQOUT and RECORDED in the ARFCSSTATE means that the record has been written into the DeltaQueue and will be loaded into the BW with the next delta request or a repetition of a delta. In any case only the statuses READ, READY and RECORDED in both tables are considered to be valid. The status EXECUTED in TRFCQOUT can occur temporarily. It is set before starting a DeltaExtraction for all records with status READ present at that time. The records with status EXECUTED are usually deleted from the queue in packages within a delta request directly after setting the status before extracting a new delta. If you see such records, it means that either a process which is confirming and deleting records which have been loaded into the BW is successfully running at the moment, or, if the records remain in the table for a longer period of time with status EXECUTED, it is likely that there are problems with deleting the records which have already been successfully been loaded into the BW. In this state, no more deltas are loaded into the BW. Every other status is an indicator for an error or an inconsistency. NOSEND in SMQ1 means nothing (see note 378903). The value 'U' in field 'NOSEND' of table TRFCQOUT is discomforting.

Q) How and where can I control whether a repeat delta is requested?
A) Via the status of the last delta in the BW Request Monitor. If the request is RED, the next load will be of type 'Repeat'. If you need to repeat the last load for certain reasons, set the request in the monitor to red manually. For the contents of the repeat see Question 14. Delta requests set to red despite of data being already updated lead to duplicate records in a subsequent repeat, if they have not been deleted from the data targets concerned before.

Q) THERE is one ODS AND 4 INFOCUBES. WE SEND DATA AT TIME TO ALL CUBES IF ONE CUBE GOT LOCK ERROR. HOW CAN U RECTIFY THE ERROR?
A) Go to TCode sm66 then see which one is locked select that pid from there and goto sm12 TCode then unlock it this is happened when lock errors are occurred when u scheduled.

Q) In BW we need to write abap routines. I wish to know when and what type of abap routines we got to write. Also, are these routines written in update rules? I will be glad, if this is clarified with real-time scenarios and few examples?
A) Over here we write our routines in the start routines in the update rules or in the transfer structure (you can choose between writing them in the start routines or directly behind the different characteristics. In the transfer structure you just click on the yellow triangle behind a characteristic and choose "routine". In the update rules you can choose "start routine" or click on the triangle with the green square behind an individual characteristic. Usually we only use start routine when it does not concern one single characteristic (for example when you have to read the same table for 4 characteristics). I hope this helps. We used ABAP Routines for example: To convert to Uppercase (transfer structure) To convert Values out of a third party tool with different keys into the same keys as our SAP System uses (transfer structure) To select only a part of the data for from an infosource updating the InfoCube (Start Routine) etc.

Q) Difference between Calculated KeyFigure & Formula? A)

Q) Variables in Reporting?
A) Characteristics values, Text, Hierarchies, Hierarchy nodes & Formula elements,

Q) Variable processing types in Reporting?
A) Manual, Replacement path, SAP Exit, Authorizations, Customer Exit

Q) Why we use this RSRP0001 Enhancement?
A) For enhancing the Customer Exit in reporting.

Q) We need to find the table in which query and variable assignments are stored. We must read this table in a user-exit to get which variables are used in a query.
A) Check out tables RSZELTDIR and RSZCOMPDIR for query BEx elements. I found this info on one of the previous posting, variable table, RSZGLOBV, query table - get query id from table RSRREPDIR (field RSRREPDIR-COMPUID), use this id for table start with RSZEL* When 'ZFISPER1' name of the variable when VNAM = 'ZVC_FY1' - characteristics. Step 1 - before selection Step 2 - after selection Step 3 - processed all variable at the same time

Q) What is an aggregate?
A) Aggregates are small or baby cubes. A subset of InfoCube. Flat Aggregate --when u have more than 15 characteristics for aggregate system will generate that aggregate as flat aggregate to increase performance. Roll-up--when the data is loaded for second time into cube, we have to roll-up to make that data available in aggregate.

Q) How can we stop loading data into infocube?
A) First you have to find out what is the job name from the monitor screen for this load monitor screen lo Header Tabstrip lo untadhi. SM37 (job monitoring) in r/3 select this job and from the menu u can delete the job. There are some options, just check them out in sm37 and also u have to delete the request in BW. Cancellation is not suggestible for delta load.

Interview Questions and Answers for SAP BI

1. How to use Virtual K.F/Char. ?
   Ans : This “virtual” characteristic is getting a value assigned at query runtime and must not be loaded with data in data target. Therefore, no change to existing update rules.
   The implementation can be divided into the following areas:
   1. Create of InfoObject [Key Figure / Characteristics] and attach the InfoObject to the InfoProvider.
 2. Implementation of BADI RSR_OLAP_BADI (Set filter on Infoprovider while defining BADI implementation)
   3. Adding the InfoObject into the Query.
2. Query Performance Tips :
   Ans :
   i. Don’t show too much data in initial view of report output
   ii. Limit the level of hierarchies on initial view
   iii. Always use Mandatory variables
   iv. Utilize filters based on InfoProviders 
   v. Suppress Result rows if not needed
   vi. Eliminate or Reduce Not logic in query selection
3. DataStore Objects :
Ans      : Standard DSO – Max. 16 key fields can be created.


4. Types Of DataStore Objects :
  · Standard DSO
  · Write-Optimized DSO -
  · Direct DSO - The DataStore object for direct update differs from the standard DataStore object in terms of how the data is processed. In a standard DataStore object, data is stored in different versions (active, delta, modified), whereas a DataStore object for direct update contains data in a single version. Therefore, data is stored in precisely the same form in which it was written to the DataStore object for direct update by the application. In the BI system, you can use a DataStore object for direct update as a data target for an analysis process
Type
Structure
Data Supply
SID Generation
Details
Example
Standard DataStore Object
Consists of three tables: activation queue, table of active data, change log
From data transfer process
Yes
Write-Optimized DataStore Objects
Consists of the table of active data only
From data transfer process
No
A plausible scenario for write-optimized DataStore objects is exclusive saving of new, unique data records, for example in the posting process for documents in retail. In the example below, however, write-optimized DataStore objects are used as the EDW layer for saving data.
DataStore Objects for Direct Update
Consists of the table of active data only



For APD
5. Line Item Dimension : If dimension table size (no. of rows) exceeds 20% of fact table size, then the dimension should be flagged as Line Item Dimension. This means that the system does not create a dimension table. Instead, the SID table of the characteristic takes the role of dimension table. Removing the dimension table has the following advantages:
      ○ When loading transaction data, no IDs are generated for the entries in the dimension table. This number  range operation can compromise performance precisely in the case where a degenerated dimension is involved.
     ○ A table- having a very large cardinality- is removed from the star schema. As a result, the SQL-based     queries are simpler. In many cases, the database optimizer can choose better execution plans.     Nevertheless, it also has a disadvantage: A dimension marked as a line item cannot subsequently include   additional characteristics. This is only possible with normal dimensions.
      Scenario : 0IS_DOCID(Document Identification) InfoObejct used as Line Iten Dimension.
6.  High cardinality: This means that the dimension is to have a large number of instances (that is, a high cardinality). This information is used to carry out optimizations on a physical level in depending on the database platform. Different index types are used than is normally the case. A general rule is that a dimension has a high cardinality when the number of dimension entries is at least 20% of the fact table entries. If you are unsure, do not select a dimension having high cardinality.
7.  Different Types Of InfoCubes :
  • Standard InfoCube (with physical data store)
  • VirtualProvider (without physical data store)
  • Based on a data transfer process and a DataSource with 3.x InfoSource: A VirtualProvider that allows the definition of queries with direct access to transaction data in other SAP source systems.
  • Based on a BAPI: A VirtualProvider whose data is not processed in the BI system, but externally. The data is read from an external system for reporting using a BAPI.
  • Based on a function module: A VirtualProvider without its own physical data store in the BI system. A user-defined function module is used as a data source.
8. Real Time Cube:
    Real-time-enabled InfoCubes can be distinguished from standard InfoCubes by their ability to support      parallel write accesses, whereas standard InfoCubes are technically optimized for read accesses. Real-time InfoCubes are used when creating planning data. The data is written to the InfoCube by several users at the same time. Standard InfoCubes are not suitable for this. They should be used if you only need read access (such as for reading reference data).
    Real-time-enabled InfoCubes can be filled with data using two different methods: Using the BW-BPS transaction for creating planning data and using BW Staging. You have the option to switch the real-time InfoCube between these two methods. From the context menu for your real-time InfoCube in the InfoProvider tree, choose Switch Real-Time InfoCube. If Real-Time InfoCube Can Be Planned, Data Loading not Allowed is selected by default, the Cube is filled using BW-BPS functions. If you change this setting to Real-Time InfoCube Can Be Loaded with Data; Planning Not Allowed, you can then fill the Cube using BW Staging.
      For real-time InfoCubes, a reduced read performance is compensated for by the option to read in parallel (transactionally) and an improved write performance.
9. Remodelling :
     Remodeling is a new feature available as of NW04s BI 7.0 which enables to change the structure of an InfoCube already loaded without disturbing data. This feature does not yet support remodeling of DSO and InfoObjects.
     Using remodeling a characteristic can be simply deleted or added/replaced with a constant value, value of another InfoObject (in the same dimension), with value of an attribute of another InfoObject (in the same dimension) or with a value derived using Customer Exit.
Similarly a KeyFigure can be deleted, replaced with a constant value or a new KeyFigure can be added and populated using a constant value or a Customer Exit.
This article describes how to add a new characteristic to InfoCube using the remodeling feature and populating it using a Customer Exit.
Note following before you start remodeling process:
  • Back-up of existing data
  • During remodeling process InfoCube is locked for any changes or data loads so make sure you stall all the data loads for this InfoCube till the time this process finishes.
  • If you are adding or replacing a KeyFigure compress the cube first to avoid inconsistencies unless all the records in the InfoCube are unique.

Note following after you finish remodeling process and start daily loads and querying this InfoCube:
  • All the objects dependent on InfoCube like transformations, MultiProviders will have to be re-activated.
  • If aggregates exists than they need to be reconstructed.
  • Adjust queries based on this InfoCube to accommodate the changes made.
  • If new field was added using remodeling than don’t forget to map it in the transformation rules for future data loads.

The code is written in SE24 by creating a new class. The interface for the class should be IF_RSCNV_EXIT and code is written in the Method IF_RSCNV_EXIT~EXIT.
10.Difference between With Export and Without Export Migration of 3.x datasource :
     With Export - Allows you to revert back to 3.x DataSource, Transfer Rules, etc...when you choose this option (Recommended) Without Export - Does not allow you to ever revert back to the 3.x DataSource.
11. Difference between Calculated Key Figure and Formula :
   The replacement of formula variables with the processing type Replacement Path acts differently in calculated key figures and formulas:
If you use a formula variable with “Replacement from the Value of an Attribute” in a calculated key figure, then the system automatically adds the drilldown according to the reference characteristic for the attribute. The system then evaluates the variables for each characteristic value for the reference characteristic. Afterwards, the calculated key figure is calculated and, subsequently, all of the other operations are executed, meaning all additional, calculated key figures, aggregations, and formulas. The system only calculates the operators, which are assembled in the calculated key figure itself, before the aggregation using the reference characteristic.
If you use a formula variable with Replacement from the Value of an Attribute in a formula element, then the variable is only calculated if the reference characteristic is uniquely specified in the respective row, column, or in the filter.
12. Constant Selection :
   In the Query Designer, you use selections (e.g. Characteristic restriction in Restricted Key Figure) to  determine the data you want to display at the report runtime. You can alter the selections at runtime using navigation and filters. This allows you to further restrict the selections. The Constant Selection function allows you to mark a selection in the Query Designer as constant. This means that navigation and filtering have no effect on the selection at runtime.
13. Customer Exit for Query Variables :
    The customer exit for variables is called three times maximally. These three steps are called I_STEP.      The first step (I_STEP = 1) is before the processing of the variable pop-up and gets called for every variable of the processing type “customer exit”. You can use this step to fill your variable with default values. 
     The second step (I_STEP = 2) is called after the processing of the variable pop-up. This step is called only for those variables that are not marked as “ready for input” and are set to “mandatory variable entry”.
     The third step (I_STEP = 3) is called after all variable processing and gets called only once and not per variable. Here you can validate the user entries.
    Please note that you cannot overwrite the user input values into a variable with this customer exit. You can only derive values for other variables or validate the user entries.
14. How to create Generic Datasource using Function Module :
    A structure is created first for extract structure which will contain all datasource fields. Then a Function module is created by copying the FM RSAX_BIW_GET_DATA_SIMPLE. The code needs to be modified as per requirement.
For delta functionality, if the base tables (from where data will be fetched) contain date and time field then include a dummy field (Timestamp) in the extract structure created for the FM and use this field in code. (by splitting the timestamp in date and time).
Type-Pools : SBIWA, SRSC.
15. In which scenario you have used Generic DataSource ?
We had a requirement to send Contract (Sales Order) data from BI to MERICS (external system). Selection criteria to extract data was –
o Billing Plan Date(FPLT-AFDAT) < Current month date
o Billing Status(FPLT-FKSAF) = Not yet Processed
o Contract Type(VBAK-AUART) = Fixed Price (ZSCC)
o Item Category(VBAP-PSTYV) = ZSV2
We could have used Data Source 2LIS_11_VAITM and could have enhanced that for FPLT fields. But the problem was that whenever there will be status change in a Billing Plan, that will not be captured by data source 2LIS_11_VAITM.
Thereby we have created a generic data source using Function Module.
16. Generic DS Safety Interval – Lower limit and Upper Limit ?What are the Delta Specific fields ? When to chose ‘New status for changed records’ and when ‘Additive Delta’ ?
Safety Interval Upper Limit :
The upper limit for safety interval contains the difference between the current highest value at the time of    the delta or initial delta extraction and the data that has actually been read. If this value is initial, records that are created during extraction cannot be extracted."
This would mean that if your extractor takes half an hour to run , then ideally your safety upper limit should be half hour or more , this way records created during extraction are not missed.
For example : If you start extraction at 12:00:00 with no safety interval and then your extract runs for 15 minutes , the delta pointer will read 12:15:00 and subsequent delta will read records created / changed on or after 12:15:00 - this would mean that all records created / changed during extraction are skipped.
Estimate the extraction time for your datasource and then accordingly set the safety upper limit so that no records are skipped. But then this being an additive delta - you need to be careful not to double your records . Ideally this being an additive delta - either extract records during periods of very low activity or have smaller safety limits to make sure data does not get duplicated.

Safety Interval Lower Limit : This field contains the value taken from the highest value of the previous delta extraction to determine the lowest value of the time stamp for the next delta extraction.
For example: A time stamp is used to determine a delta. The extracted data is master data: The system only transfers after-images that overwrite the status in the BW. Therefore, a record can be extracted into the BW for such data without any problems.
Taking this into account, the current time stamp can always be used as the upper limit when extracting: The lower limit of the next extraction is not seamlessly joined to the upper limit of the last extraction. Instead, its value is the same as this upper limit minus a safety margin. This safety margin needs to be big enough to contain all values in the extraction which already had a time stamp when the last extraction was carried out but which were not read. Not surprisingly, records can be transferred twice. However, for the reasons above, this is unavoidable.
1. If delta field is Date (Record Create Date or change date), then use Upper Limit of 1 day.
This will load Delta in BW as of yesterday. Leave Lower limit blank.
2. If delta field is Time Stamp, then use Upper Limit of equal to 1800 Seconds (30 minutes).
This will load Delta in BW as of 30 minutes old. Leave Lower limit blank.
3. If delta field is a Numeric Pointer i.e. generated record # like in GLPCA table, then use
Lower Limit. Use count 10-100. Leave upper limit blank. If value 10 is used then last 10
records will be loaded again. If a record is created when load was running, those records
may get lost. To prevent this situation, lower limit can be used to backup the starting
sequence number. This may result in some records being processed more than once;
therefore, be sure this DataSources is only feeding an ODS Object
Delta Specific Fields :
                                                o TimeStamp - The field is a DEC15 field which always contains the time stamp of the last change to a   record in the local time format.
                                                 o Calendar Day - The field is a DATS8 field which always contains the day of the last change.
                                                 o Numeric Pointer - The field contains another numerical pointer that  appears with each new record.
Additive Delta :
The key figures for extracted data are added up in BW. DataSources with this delta type can supply data to ODS objects and InfoCubes.
New status for changed records :
Each record to be loaded delivers the new status for the key figures and characteristics. DataSources with this delta type can write to ODS objects or master data tables.

17. How to Fill Up Set Up Table and related Transaction
18. Maximum Char. And Key Figures allowed in a Dimension of Cube ?
Max. Char. – 248
Max. Key Fig. – 233
19. Different Types of DTP :
    o Standard DTP - Standard DTP is used to update data from PSA to data targets ( Info cube, DSO  etc).
      o Direct Access DTP - DTP for Direct Access is the only available option for VirtualProviders.
     o Error DTP - Error DTP is used to update error records from Error stock to the corressponding data targets.
20. How to Create Optimized InfoCube ?
     o Define lots of small dimensions rather than a few large dimensions.
      o The size of the dimension tables should account for less than 10% of the fact table.
     o If the size of the dimension table amounts to more than 10% of the fact table, mark the dimension as a line item dimension.
21. Difference between DSO and Cube

DSO
InfoCube
Use
Consolidation of data in the data warehouse layer
Loading delta records that can subsequently be updated to InfoCubes or master data tables
Operative analysis (when being used in the operational data store)
Aggregation and performance
optimization for
multidimensional reporting
Analytical and strategic data
analysis
Type of data
Non volatile data (when being used
in the data warehouse layer)
Volatile data (when being used in the
operational data store)
Transactional data, document-type
data (line items)
Non volatile data
Aggregated data, totals
Type of data update
Overwrite (in rare cases: addition)
Addition only
Data structure
Flat and relational database tables,
semantic key fields
Enhanced star schema (fact
table and dimension tables)
Type of data analysis
Reporting at high level of granularity,
flat reporting
The number of query records should
be strictly limited by the choice of key
fields
Individual document display
Multidimensional data analysis
with low level of granularity
(OLAP analysis)
Use of InfoCube aggregates
Drill-through to document level
(stored in DataStore objects)
possible using the reportreport
interface
22. Give an example where DSO is used for Addition not overwrite.
23. Difference between 3.x and 7.0
   1. In Infosets now you can include Infocubes as well.
    2. The Remodeling transaction helps you add new key figure and characteristics and handles historical data as well without much hassle. This is only for info cube. 
    3. The BI accelerator (for now only for infocubes) helps in reducing query run time by almost a factor of 10 - 100. This BI accl is a separate box and would cost more. Vendors for these would be HP or IBM.
    4. The monitoring has been improved with a new portal based cockpit. Which means you would need to have an EP guy in ur project for implementing the portal ! :) 
     5. Search functionality hass improved!! You can search any object. Not like 3.5
     6. Transformations are in and routines are passe! Yess, you can always revert to the old transactions too.
     7. The Data Warehousing Workbench replaces the Administrator Workbench.
   8. Functional enhancements have been made for the DataStore object: New type of DataStore object Enhanced settings for performance optimization of DataStore objects. 
     9. The transformation replaces the transfer and update rules.
    10. New authorization objects have been added 
    11. Remodeling of InfoProviders supports you in Information Lifecycle Management.
    12 The Data Source:There is a new object concept for the Data Source. Options for direct access to data  have been enhanced. From BI, remote activation of Data Sources is possible in SAP source systems.
    13.There are functional changes to the Persistent Staging Area (PSA). 
    14.BI supports real-time data acquisition.
    15. SAP BW is now known formally as BI (part of NetWeaver 2004s). It implements the Enterprise Data Warehousing (EDW). The new features/ Major differences include:
     a) Renamed ODS as DataStore. 
    b) Inclusion of Write-optmized DataStore which does not have any change log and the requests do need any activation
     c) Unification of Transfer and Update rules 
     d) Introduction of "end routine" and "Expert Routine"
     e) Push of XML data into BI system (into PSA) without Service API or Delta Queue f) Intoduction of BI accelerator that significantly improves the performance.
     g) Load through PSA has become a must. I am not too sure about this. It looks like we would not have the option to bypass the PSA Yes,
    16. Load through PSA has become a mandatory. You can't skip this, and also there is no IDoc transfer method in BI 7.0. DTP (Data Transfer Process) replaced the Transfer and Update rules. Also in the Transformation now we can do "Start Routine, Expert Routine and End Routine". during data load. New features in BI 7 compared to earlier versions:
      i. New data flow capabilities such as Data Transfer Process (DTP), Real time data Acquisition (RDA). 
      ii. Enhanced and Graphical transformation capabilities such as Drag and Relate options.
    iii. One level of Transformation. This replaces the Transfer Rules and Update Rules iv. Performance optimization includes new BI Accelerator feature.
    v. User management (includes new concept for analysis authorizations) for more flexible BI end user authorizations.

24. What is Extended Start Schema ?
25. What is Compression, RollUp , Attribute Change Run?
    RollUp : You can automatically roll up and transfer into the aggregate requests in the InfoCube with “green traffic light status”, that is, with saved data quality. The process terminates if no active, initially filled aggregates exist in the system.
      Compression : After rollup, the InfoCube content is automatically compressed. The system does this by deleting the request IDs, which improves performance.
      If aggregates exist, only requests that have already been rolled up are compressed. If no aggregates exist, the system compresses all requests that have yet to be compressed.
    First we need to do aggregate roll up before compression. when we roll up data load requests, we roll them up into all the aggregates of the infocube and then carry on the compression of the cube. For performance and disk space reasons, it is recommended to roll up a request as soon as possible and then compress the infocube.
   When you Compress the cube,"COMPRESS AFTER ROLLUP" option ensures that all the data is rolledup into aggrgates before doing the compression.
     Compression - with Zero Elimination – Zero-elimination means that data rows with all keyfigs = 0 will be deleted.
26. What is Change Run ? How to resolve when a attribute change run fails because of locking problem?
27. What are the error you have faced during Transport of object ?
28. What steps need to follow when a process in Process Chain fails and we need to make it green to proceed further?
   1. Right click on the failed process and go to ‘Display Messages’. From Chain tab get VARIANT and INSTANCE value. For some cases INSTANCE is not available, that case we take Job Count Number.
   2. Go to table RSPCPROCESSLOG. Give the VARIANT and INSTANCE and get LOGID, TYPE, BATCHDATE and BATCHTIME
  3. Execute program (SE38) RSPC_PROCESS_FINISH by providing LOGID, CHAIN, TYPE, VARIANT, INSTANCE, BATCHDATE, BATCHTIME and STATE = ‘G’.
29. What is Rule Group in Transformation. Give example.
    A rule group is a group of transformation rules. It contains one transformation rule for each key field of the target. A transformation can contain multiple rule groups.
    Rule groups allow you to combine various rules. This means that for a characteristic, you can create different rules for different key figures.
      Few key points about Rule Groups:
      o A transformation can contain multiple rule groups.
     o A default rule group is created for every transformation called as Standard Group. This group contains all the default rules.
      o Standard rule group cannot be deleted. Only the additional created groups can be deleted.
      Example :
      Records in source system: Actual and Plan Amount are represented as separate fields.
      CompanyCode Account FiscalYear/Period ActualAmount Plan Amount
      1000 5010180001 01/2008 100 400
      1000 5010180001 02/2008 200 450
      1000 5010180001 03/2008 300 500
    Records in business warehouse: Single KeyFigure represents both Actual and Plan Amount. They are    differentiated using the characteristic Version (Version = 010 represents Actual Amount and Version = 020  represents Plan Amount in this example).

      CompanyCode Account FiscalYear/Period Version Amount
      1000 5010180001 01/2008 010 100
      1000 5010180001 02/2008 010 200
      1000 5010180001 03/2008 010 300
      1000 5010180001 01/2008 020 400
      1000 5010180001 02/2008 020 450
     1000 5010180001 03/2008 020 500
    To achieve this, In Standard Rule group(target), we will make the char. Version to constant value 010 and direct assignment form Actual Amount to Amount in target field.
And another rule group(New Rule group) will be created where we will make the char. Version to constant value 020 and direct assignment form Plan Amount to Amount in target field.
30. Why we cannot use DSO to load inventory data ?
     DS objects cannot admit any stock key figures (see Notes 752492 and 782314) and, among other things, they do not have a validity table, which would be necessary. Therefore, ODS objects cannot be used as non-cumulative InfoCubes, that is, they cannot calculate stocks in terms of BW technology.
31. Processing Type Replacement Path for Variable with Examples.
   You use the Replacement Path to specify the value that automatically replaces the variable when you execute the query or Web application.
      The processing type Replacement Path can be used with characteristic value variables, text variables and formula variables.
     o Text and formula variables with the processing type Replacement Path are replaced by a corresponding characteristic value.
     o Characteristic value variables with the processing type Replacement Path, are replaced by the results of a query.
      Replacement with a characteristic value :
      Replace Variable with
        · · Key The variable value is replaced with the characteristic key.
    · · External Characteristic Value Key The variable value is replaced with an external value of the  characteristic (external/internal conversion).
    · · Name (Text) The variable value is replaced with the name of the characteristic.Note that formula variables have to contain numbers in their names so that the formula variable represents a value after replacement.
     · · Attribute Value The variable value is replaced with the value of an attribute. An additional field appears for entering the attribute. When replacing the variable with an attribute value, you can create a reference to the characteristic for which the variable is defined. Choose the attribute Reference to Characteristic (Constant 1). By choosing this attribute, you can influence the aggregation behavior of calculated key figures and obtain improved performance during calculation.
     · Hierarchy Attribute The variable value is replaced with a value of a hierarchy attribute. An additional field appears for entering the hierarchy attribute. You need this setting for sign reversal with hierarchy nodes
     o Example: Replacement with Query You want to insert the result for the query Top 5 products as a variable in the query Sales – Calendar year / month.
    1. Select the characteristic Product and from the context menu, choose New Variable. The Variable Wizard appears.
      2. Enter a variable name and a description.
      3. Choose the processing type Replacement Path.
      4. Choose Next. You reach the Replacement Path dialog step.
      5. Enter the query Top 5 Products.
      6. Choose Next. You reach the Save Variable dialog step
      7. Choose Exit
     You are now able to insert the variable into the query Sales – Calendar year / month. This allows you to  determine how the sales for these five, top-selling products has developed month for month.
32. Pseudo Delta
    This is different from the normal delta in a way that, if you look at the data load it would say FULL LOAD instead of DELTA. But as a matter of fact, its only pulling the records that are changed or created after the previous load. This can be achieved multiple ways like logic in infopackage routine, selections identifying only the changed records and so on.
    In my past experience, we had a code in the infopackage that looks at when the previous request was loaded, using that date calculates the month and loads data for which CALMONTH is between the previously loaded date and today's date (since the data target is an ODS, even if there is a duplicate selection, overwriting will happen thus not affecting the data integrity).
33. Flat Aggregates
    If you have less than 16 characters in an aggregate ( including the time , data and package dimensions) then the characteristic SIDs are stored as Line items meaning the E Fact table of the aggregate ( Assuming that your aggregate is compressed ) will have 16 columns and these will have the SIDs only...
     You do not have any further tables like dimension tables etc for an aggregate in this case - hence the name FLAT - meaning that the aggregate more or less is like a standard table with the necessary SIDs and nothing else.
      Flat aggregates can be rolled up on DB Server (without loading data into Application Server)
34. Master Data Load failure recovery Steps :
     Issue :
     A delta update for a master data DataSource is aborted.The data was sent to the BW in this case but it was not posted in the PSA.In addition, there are no, as yet, executed LUWs in the TRFC outbound of the source system.Therefore, there is no way of reading the data from a buffer and transferring this to the master data tables.
      Solution :
   Import the next PI or CRM patch into your source system and execute the RSA1BDCP report. Alternatively, you can import the attached correction instructions into your system and create an executable program in the customer namespace for this using transaction SE38, into which you copy the source code of the correction instructions. Execute the report.
      The report contains 3 parameters:
1. P_OS (DataSource): Name of the DataSource
2. P_RS (BIW system): logical name of the BW system
3. P_TIME (generation time stamp):The generation date and time of the first change pointer, which are transferred into BW during the next upload, should be displayed as YYYYMMDDHHMMSS (for example, 20010131193000 for January 31, 2001, 19:30:00).(e.g. 20010131193000 for 31.01.2001, 19:30:00).For this time stamp select the time stamp of the last successful delta request of this DataSource in the corresponding BW system. After the report is executed, a dialog box appears with the number of records that should have the 'unread' status. Check the plausibility of this number of records. It should be larger than or the same as the number of records for the last, terminated request. 
After you execute the report, change the status of the last (terminated) request in BW to 'green' and request the data in 'delta' mode.

35. What is KPI ?
    (1) Predefined calculations that render summarized and/or aggregated information, which is useful in making strategic decisions.
     (2) Also known as Performance Measure, Performance Metric measures. KPIs are put in place and visible to an organization to indicate the level of progress and status of change efforts in an organization. KPIs are industry-recognized measurements on which to base critical business decisions.
     In SAP BW, Business Content KPIs have been developed based upon input from customers, partners, and industry experts to ensure that they reflect best practices.

36. Performance Monitoring and Analysis tools in BW:
   a) System Trace: Transaction ST01 lets you do various levels of system trace such as authorization checks, SQL traces, table/buffer trace etc. It is a general Basis tool but can be leveraged for BW.
     b) Workload Analysis: You use transaction code ST03
    c) Database Performance Analysis: Transaction ST04 gives you all that you need to know about what’s happening at the database level.
   d) Performance Analysis: Transaction ST05 enables you to do performance traces in different are as namely SQL trace, Enqueue trace, RFC trace and buffer trace.
   e) BW Technical Content Analysis: SAP Standard Business Content 0BWTCT that needs to be activated. It contains several InfoCubes, ODS Objects and MultiProviders and contains a variety of performance related information.
    f) BW Monitor: You can get to it independently of an InfoPackage by running transaction RSMO or via an InfoPackage. An important feature of this tool is the ability to retrieve important IDoc information.
   g) ABAP Runtime Analysis Tool: Use transaction SE30 to do a runtime analysis of a transaction, program or function module. It is a very helpful tool if you know the program or routine that you suspect is causing a performance bottleneck.
37. Runtime Error MESSAGE_TYPE_X when opening an info package in BW
    You sometimes run into error message 'Runtime error MESSAGE_TYPE_X' when you try to open an existing delta infopackage. It won't even let you create a new infopackage, it throws the same error. The error occurs in the FUNCTION-POOL FORM RSM1_CHECK_FOR_DELTAUPD.
    This error typically occurs when delta is not in sync between source system and BW system. It might happen when you copy new environments or when you refresh you QA or DEV boxes from production.
    Solution : Try to open a existing full infopackage if you have it, you will be able to open existing full infopackage because it is not going to check delta consistency. After you open the infopacke remove the delta initialization from the infopackage as shown below. Got menu scheduleer -> Initialization options for source system ->Select the entry -> click on delete button
      After that you will be able to open existing delta infopackage. You can re initialize the delta and start using the infopackage.
    Follow the steps in the note 852443 , If you do not have a existing full infopackage. There are many troubleshooting steps in this note. You can go through all of them or do what I do follow the steps below.
     1. In table RSSDLINIT check for the record with the problematic datasource. 
     2. Get the request number (RNR) from the record.
   3. Go to RSRQ transaction and enter the RNR number and say execute, It will show you the monitor screen of actual delta init request. 
    4. Now change the status of the request to red.
    That's it. Now you will be able to open your delta infopackage and run it. Of course you need to do your delta init again as we made last delta init red. These steps have always worked for me, follow the steps in the OSS note if this doesn't work for you.
38. KPIs for FI datasource :
     Accounts Payable :
      o DataSource 0FI_AP_4 (Vendors: Line Items with Delta Extrcation):
DataSource Field
BI Info Object
DMSOL
0DEBIT_LC (Debit Amount in local currency)
DMHAB
0CREDIT_LC (Credit Amount in local currency)
DMSHB
0DEB_CRE_LC (Amount in Local currency with +/- signs
WRSOL
0DEBIT_DC (Debit amount in Foreign currency)
WRHAB
0CREDIT_DC (Credit amount in Foreign currency)
WRSHB
0DEB_CRE_DC (Foreign currency amount with +/- signs
o DataSource 0FI_AP_6 (Vendor Sales Figures via Delta Extraction) :
DS Field
BI IO
UM01S
0DEBIT (Total Debit Postings)
UM01H
0CREDIT (Total credit postings)
UM01K
0BALANCE (Cumulative Balance)
UM01U
0SALES (Sales for the Period)
Accounts Receivable :
o DataSource 0FI_AR_4 (Cu
stomers: Line Items with Delta Extraction)
DS Field
BI IO
ZBD1T
0DSCT_DAYS1 (Days for Cash Discount 1)
ZBD2T
0DSCT_DAYS2 (Days for Second Cash Discount)
ZBD3T
0NETTERMS (Deadline for Net Conditions)
DMSOL
0DEBIT_LC (Debit amount in local currency)
DMHAB
0CREDIT_LC (Credit amount in local currency)
DMSHB
0DEB_CRE_LC (Amount in local currency with +/- signs
General Ledger :
o DataSource 0FI_GL_4
DS Field
BI IO
WRBTR
0AMOUNT (Amount)
DMBTR
0VALUE_LC (Amount in local currency)
DMSOL
0DEBIT_LC (Debit amount in local currency)
DMHAB
0CREDIT_LC (Credit amount in local currency)
DMSHB
0DEB_CRE_LC (Amount in local currency with +/- signs
WRSOL
0DEBIT_DC (Debit amount in Foreign currency)
WRHAB
0CREDIT_DC (Credit amount in Foreign currency)
o DataSource 3FI_GL_0L_TT (Leading
Ledger (Totals))
DataSource 3FI_GL_Y1_TT (Non-leading ledger (Statutory) (Totals) - Y1)
DS Field
BI IO
DEBIT
0DEBIT (Total Debit Postings)
CREDIT
0CREDIT (Total Credit postings)
BALANCE
0BALANCE (Cumulative Balance)
TURNOVER
0SALES (Sales for the Perod)
QUANTITY
0QUANTITY (Quantity)
o DataSource 3FI_GL_Y1_TT (Non-leading ledger (Statutory) (Totals) - Y1)
39. Example of Display Key Figure used in Master Data
    In 0MATERIAL: The display key figures are 0HEIGHT(Height), 0LENGTH(Length), 0GROSS_WT (Gross Weight), 0GROSS_CONT (Gross Content).
40. What all Custom reports you have created in your project ?
41. Infocube Optimization :
    o When designing an InfoCube, it is most important to keep the size of each dimension table as small as possible.
      o One should also try to minimise the number of dimensions.
    o Both of these objectives can usually be met by building your dimensions with characteristics that are related to each other in a 1:1 manner (for example each state is in one country) or only have a small number of entries.
    o Generally characteristics that have a large number of entries should be in a dimension by themselves, which is flagged as a "line item" dimension.
    o Characteristics that have a "many to many" relationship to each other should not be placed in the same dimension otherwise the dimension table could be huge.
     o It is generally recommended to do this if the dimension table size (number of rows) exceeds 10% of the fact table's size. You should also flag it as a "line item" dimension in an SAP InfoCube.
42. How do you handle Init without data transfer through DTP ?
      Under ‘Execute’ tab select the processing mode as s
hown in the screenshot.


Note

This blog is solely for the purpose of getting educated in SAP. This blog does not encourage distribution of SAP hold copyright and any other publication and/or materials bearing SAP mark. If you find any copyright materials, please mail me so I can remove them. This blog is not in association with SAP.

ALL Posts

Get this widget