BO Access for New User

BO Access for New User:

Step 1:


Login CMC.

Step 2:

Go to ==> Users and Groups

==> Find the User ID

==> If not available User in Users List, Create new User

==> Enter Account details ID or Name (Ex: Name: Cindy Pulido (ID - 17326), Then Create and Close.

After added new user follow the below steps


Step 3: Again Search and R-Click for properties.

Step 4:


Give Full Name and Enable check box for Import Full name, Email Address and other attributes.

Now we have provided new user access.

After provided access to the new user please verify the setting.

Change request status (Red or Green) RSBM_GUI_CHANGE_USTATE

How to change request status (Red or Green) by using functional module:


Please follow below steps:


Use T-Code SE37 – Function Builder.

FM: RSBM_GUI_CHANGE_USTATE

When You Execute this functional Module it will ask you request number.

 



Then Click on Execute, we will get one pop up window to select RED or GREEN.

 















Then Click on OK.

Example: When you are using open hubs sometimes happen all data packages ran successfully but the DTP Over all load status not turn into green. The request appears still in YELLOW status. in this scenario by using this FM will do particular request Red or Green forcefully.

Replacement Path Variables

How to use Replacement Path Variables to perform Date Calculations:-

Please follow below steps

Have you ever wanted to perform calculations using dates defined as characteristics but have never worked out how it can be done? Replacement Path Variables are the key.

Using Replacement Path in your Text and Formula variables, replace values held in a characteristic. The Characteristic value variables are replaced by the results of a query at run-time.

The steps detailed below show a technique to enable a BEx query user to determine the number of days between two dates.

Scenario:
The group HR administrator wants a detailed line item report that lists all employee absences in a given period. The report is to show the employee number, the absence start date, together with the end date of the absence and show the number of calendar days the employee was absent.

The good thing about using this technique is that no redesign work is needed from your technical BW team, no ABAP is involved and best of all, it quick and easy.

Solution:
For this example I created an ODS object called Absence that holds basic employee information along with individual absence record data.

Follow the steps below:
1. Open the BEx Query Designer and create a new report on your chosen InfoProvider.

2. Drag the Employee, Valid from and Valid to characteristics into the Rows section of the screen. If needed, apply data selection restrictions to the characteristics as shown in Figure 1.

3. Right click on the Key Figures structure and select New Formula (Figure 1).

Figure 1

4. In the new formula window right click on Formula Variable and choose New Variable ( Figure 2 ).

Figure 2

5. The Variables Wizard will launch and will require you to specify the variable details.

( Click the NEXT button if the Introduction screen appears )

6. Enter the variable details on the General Information as shown in Figure 3 .

Enter the Variable Name , Description and select Replacement Path in the Processing by field.

Click the Next Button.

Figure 3

7. In the Characteristic screen (Figure 4) select the date characteristic that represents the first date to use in the calculation (From Date).

Click the Next Button.

Figure 4

8. In the Replacement Path screen (Figure 5) select Key in the Replace Variable with field. Leave all the other options as they are (The offset values will be set automatically).

Click the Next Button.

Figure 5

9. In the Currencies and Units screen (Figure 6) select Date as the Dimension ID.

Click the Next button.

Figure 6

10. The Save Variable screen (Figure 7) displays a summary of the new variable.

Click on the Finish button to save the variable.

Figure 7

11. Repeat steps 4 to 11 to create a second variable for the second date to be used in the calculation. In the example shown, the characteristic 0DATETO is used to create the variable ABSEND (Absence End Date).

Define the Calculation

We can now use our two new replacement variables to define our new calculated key figure that generates the number of absence days for each record.

1. You will now be back at the New Formula screen (Figure 8). Drag and drop the two new variables into the formula section of the screen and insert the subtract sign (“-“) between the two.

2. Give the new formula a description and click the formula syntax check button to ensure the formula is valid.

Figure 8

3. The new calculated key figure will now show in the columns section of the BEx query designer (Figure 9).

Figure 9

4. Save the query and execute it.

In the example shown the Number of Calendar Days Absent is calculated correctly. See the table of results below.

Employee Valid From Valid To Number of Calendar

Days Absent

50000001 17/04/2004 21/04/2004 4

50000002 16/07/2004 29/09/2004 13

50000003 07/01/2004 09/02/2004 33

50000004 04/08/2004 05/08/2004 1





Source: SD Solutions

SAP BI Interview questions and Answers Part 3:

SAP BI Interview questions and Answers Part 3:


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:
http://sapbibobj.blogspot.com/2010/09/differeces-between-dso-and-infocube.html

Q) What is ODS?
http://sapbibobj.blogspot.com/2010/10/data-store-objects.html

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?
A) SID keys linked with dimension table & master data tables (attributes, texts, hierarchies)

Q) What does ATTRIBUTE Table contain?
A) Master attribute data

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

Q) What does Hierarchy table contain?
A) 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.

http://sapbibobj.blogspot.com/2010/10/infocube_19.html

Q) WHAT ARE THE DIFFERENT VARIABLES USED IN BEX?

A) Different Variables 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 vastly.

Q) CAN CHARECTERSTIC INFOOBJECT CAN BE INFOPROVIDER.
A) Yes.
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 info source updating the InfoCube (Start Routine) etc.
Q) Difference between Calculated Keyfigure & Formula?

A) Both of the formula and CKF serves the same purpose but still there are some differences between them:

For main difference, formula is local for a query while CKF (calculated Key figure) is global formula for a infoprovider and all the queries coming under that infoprovider.

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.

LO-EXTRACTION

LO-EXTRACTION STEP BY STEP SCREENS SHOTS IN ECC.


Take a data source 2lis_02_hdr; check the DS is available in active version by RSA6 T-code

In below screen we see it ,means it is active in ecc, if not go to t-code RSA5 and activate.























Below is the RSA5 screen, select u r ds and click on activate datasource option





Once u r ds is active check records in the ds, to see go to t-code RSA3







To see the records in the same screen click on LIST tab.









Then in the next screen seleck any data package double click u will see the data in next screen.

If u want u can down load to excel.



Next we go for lo-extraction t-code LBWE, u get the below screen.







Before changing the extract structure, we need to delete the data in setup table.

To delete the data in setup table t-code is LBWG, then in screen give the application numb and click on execute.





After deletion of data in setup table ,to see if it is deleted or not go to t-code SE11, give the communication structure name of the DS followed by word SETUP. And click on display





Then click on number of entries u get the count or click on execute icon.







Then after deleting data in setup table, then go to LBWE and select u r ds and make it inactive, to make inactive just left mouse click on ACTIVE ,it will become inactive.





Then next to change the extract structure click on MAINTENANCE Then u get below screen













Blue colour fields are predefined extract structure fields, and black colour fields are communication structure fields. First check the extracture fields as per u r recq,if u don’t find some fields then check in comm stru and select the field and move it extract struc.







Then u will come back to LBWE screen, next to regenerate the DS click on the DS name







Then u get the below screen, here select the fields from which u want data by selecting SELECTION box ,and select HIDE from the fields which u don’t want data,and click on save.





Then set the update mode and v3back ground job.







When u click update method, u get below selection screen ,select the update mode and click on tick mark.



Now after all steps again activate the ds, by just clicking on INACTIVE it will become active.





Then run the statistical setup run(oli*bw)t-code to fill the setup table, in the below screen give name of the run and give the termination date and time in future, then click on execute.



Then to see the data is loaded into setup table or not ,go to SE11 and follow the same steps u did for seeing if data is deleted in setup table or not after deleting the data using LBWG t-code.

Refer above screens.



LO-EXTRACTION STEPS IN BI SIDE:

1) LOGIN TO BI SYSTEM, go to RSA1 under modeling tabselect source systemselect u r ecc system double click on itthen u get data sources screen-search your DSthen right click ds and select replicate metadata option. when u replicate just extract structure only copies from ecc ds.

















Then next right click DS and select create info package





Then give the description of the info package and click on save.



Then check all tabs and give the inputs and in schedule tab click on start, now this IP will run and load data to PSA.





Then monitor the info package, if it has loaded data till psa or not by clicking on monitor icon

Other way to see data in psa is select u r ds right click and select manage then u get below screen then select recq and click on psa icon.



Then find the standard dso/cube, if found check if active, if not activate.

if u don’t find go to business content & find and install it.

Or create your own dso or cube.

Then create transformations, select ds right click and select create transformations, then give the source and target of transformations and activate.

then select the ds and right click and select create Data transfer transfer process and give the inputs and activate and run and monitor the DTP.

SAP BI Interviews Question and Answers Part 2:

SAP BI Interviews Question and Answers Part 2:


Source: Collected from GoogleBlogs By: Sasi

1. What is the t-code to see log of transport connection?

In RSA1 -> Transport Connection you can collect the Queries and the Role and after this you can transport them (enabling the transport in SE10, import it in STMS

1. RSA1

2. Transport connection (button on the left bar menu)

3. Sap transport -> Object Types (button on the left bar menu)

4. Find Query Elements -> Query

5. Find your query

6. Group necessary object

7. Transport Object (car icon)

8. Release transport (SE10 T-code)

9. Load transport (STMS T-code)



2. Lo; mm inventory data source with marker significance?

Marker is as like check point when u upload the data from inventory data source

2lis_03_bx data source for current stock and BF for movement type

after uploading data from BX u should rlise the request in cube or i menn to say compress it then load data from another data source BF and set this updated data to no marker update so marker is use as a check point if u don’t do this u getting data mismatch at bex level bcz system get confuse.

(2LIS_03_BF Goods Movement from Inventory Management-- -----Uncheck the no marker update tab)

(2LIS_03_BX Stock Initialization for Inventory Management-- ---select the no marker update check box)

2LIS_03_UM Revaluations ----Uncheck the no marker update tab) in the infopackege of "collapse"


3. How can you navigate to see the error idocs?

If it is fine check the IDOCs in source system go to BD87->give Ur user ID and date->execute->you can find Red status Idocs select the erroneous Idoc->Rt.click and select Manual process.

You need to reprocess this IDOC which are RED. For this you can take help of Any of your Team (ALE IDOC Team or Basis Team) Or Else

you can push it manually. Just search it in bd87 screen only to reprocess.

Also, try to find why this Idocs are stuck there.

 

4) Difference between v1, v2, v3 jobs in extraction?

V1 Update: whenever we create a transaction in R/3(e.g.Sales Order) then the entries get into the R/3 Tables (VBAK, VBAP..) and this takes place in V1 Update.

V2 Update: V2 Update starts a few seconds after V1 Update and in this update the values get into Statistical Tables, from where we do the extraction into BW.

V3 Update: Its purely for BW extraction.

But in the Document below, V1, V2 and V3 are defined in a different way. Can You please explain me in detail what exactly V1, V2 and V3 updates means?



5. What are statistical update and document update?

Synchronous Updating (V1 Update)

The statistics update is made synchronously with the document update.

While updating, if problems that result in the termination of the

statistics update occur, the original documents are NOT saved. The cause

of the termination should be investigated and the problem solved.

Subsequently, the documents can be entered again.

Radio button: V2 updating



6. Do you have any idea how to improve the performance of the BW..?

Asynchronous Updating (V2 Update)

With this update type, the document update is made separately from the statistics update. A termination of the statistics update has NO influence on the document update (see V1 Update).

Radio button: Updating in U3 update program

Asynchronous Updating (V3 Update)

With this update type, updating is made separately from the document update. The difference between this update type and the V2 Update lies, however, with the time schedule. If the V3 update is active, then the update can be executed at a later time.

In contrast to V1 and V2 Updates, no single documents are updated. The V3 update is, therefore, also described as a collective update.


7) How can you decide the query performance is slow or fast?

You can check that in RSRT tcode.

execute the query in RSRT and after that follow the below steps

Go to SE16 and in the resulting screen give table name as RSDDSTAT for BW 3.x and RSDDSTAT_DM for BI 7.0 and press enter you can view all the details about the query like time taken to execute the query and the timestamps


8) What is statistical setup and what is the need and why?

Follow these steps to filling the set up table.


1. Go to transaction code RSA3 and see if any data is available related to your DataSource. If data is there in RSA3 then go to transaction code LBWG (Delete Setup data) and delete the data by entering the application name.

2. Go to transaction SBIW --> Settings for Application Specific Datasource --> Logistics --> Managing extract structures --> Initialization --> Filling the Setup table --> Application specific setup of statistical data --> perform setup (relevant application)

3. In OLI*** (for example OLI7BW for Statistical setup for old documents: Orders) give the name of the run and execute. Now all the available records from R/3 will be loaded to setup tables.

4. Go to transaction RSA3 and check the data.

5. Go to transaction LBWE and make sure the update mode for the corresponding DataSource is serialized V3 update.

6. Go to BW system and create infopackage and under the update tab select the initialize delta process. And schedule the package. Now all the data available in the setup tables are now loaded into the data target.

7. Now for the delta records go to LBWE in R/3 and change the update mode for the corresponding DataSource to Direct/Queue delta. By doing this record will bypass SM13 and directly go to RSA7. Go to transaction code RSA7 there you can see green light # Once the new records are added immediately you can see the record in RSA7.

8. Go to BW system and create a new infopackage for delta loads. Double click on new infopackage. Under update tab you can see the delta update radio button..

9. Now you can go to your data target and see the delta record.



9. Why we have construct setup tables?

The R/3 database structure for accounting is much more easier than the Logistical structure.

Once you post in a ledger that is done. You can correct, but that give just another posting.

BI can get information direct out of this (relatively) simple database structure.

In LO, you can have an order with multiple deliveries to more than one delivery addresses. And the payer can also be different.

When 1 item (order line) changes, this can have its reflection on order, supply, delivery, invoice, etc.

Therefore a special record structure is built for Logistical reports. and this structure now is used for BI.

In order to have this special structure filled with your starting position, you must run a set-up. From that moment on R/3 will keep filling this LO-database.

If you wouldn't run the setup. BI would start with data from the moment you start the filling of LO (with the logistical cockpit)



10.How can you eliminate the duplicate records in TD, MD?

Try to check the system logs through SM21 for the same.



11. What use marker in MM?

Marker update is just like check point.

ie it will give the snapshot of the stock on a particular date ie when was the marker updated.

Because we are using Noncumulative key figure it will lot of time to calculate the current stock for example at report time. To overcome this we use marker update

Marker updates do not summarize the data.. In inventory management scenarios, we have to calculate opening stock and closing stock on a daily basis. In order to facilitate this, we set a marker which will add and subtract the values for each record.

In the absence of marker update, the data will be added up and will not provide the correct values.



12. Tell me web template?

You get information on where the web template details are stored from the following tables :

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

You can check these tables and search for your web template entry . However, If I understand your question correctly, you will have to open the template in the WAD and then make the corrections in the same to correct it.


13. What is dashboard?

A dash board can be created using the web application Designer (WAD) or the visual composer (VC). A dashboard is just a collection of reports, views and links etc in a single view. For e.g. igoogle is a dashboard.

A dashboard is a graphical reporting interface, which displays KPIs (Key Performance Indicators) as charts and graphs. A dashboard is a performance management system

when we look at the all organization measures how they are performing with helicopter view, we need a report that teaches and shows the trend in a graphical display quickly. These reports are called as Dashboard Reports, still we can report these measures individually, but by keeping all measures in a single page, we are creating single access point to the users to view all information available to them. Absolutely this will save lot of precious time, gives clarity on decision that needs to be taken, helps the users to understand the measure(s) trend with business flow creating dashboard

Dashboards : Could be built with Visual Composer & WAD

create your dashboard in BW,

(1) Create all BEx Queries with required variants, tune them perfectly.

(2) Differentiate table queries and graph queries.

(3) Choose the graph type required that meet your requirement.

(4) Draw the layout how the Dashboard page looks like.

(5) Create a web template that has navigational block / selection information.

(6) Keep navigational block fields are common across the measures.

(7) Include the relevant web items into web template.

(8) Deploy the URL/Iview to users through portal/intranet



The steps to be followed in the creation of Dashboard using WAD are summarized as below:

1) Open a New Web template in WAD.

2) Define the tabular layout as per the requirements so as to embed the necessary web items.

3) Place the appropriate web items in the appropriate tabular grids

4) Assign queries to the web items (A Query assigned to a web item is called as a data provider)

5) Care should be taken to ensure that the navigation block’s selection parameters are common across all the BEx queries of the affected data providers.

6) Properties of the individual web items are to be set as per the requirements. They can be modified in Properties window or in the HTML code.

7) The URL when this web template is executed should be used in the portal/intranet


14) About DTP ?


Data Transfer Process:
Data transfer process (DTP) loads data within BI from one object to another object with respect to

transformations and filters. In short, DTP determines how data is transferred between two persistent objects.

It is used to load the data from PSA to data target (cube or ods or infoobject) thus, it replaced the data mart interface and the Info Package.


  15. How can you solve the data mismatch tickets between r/3 and BW?

Check the mapping at BW side for 0STREET in transfer rules. Check the data in PSA for the same field. If the PSA is also doesn't have complete data then check the field in RSA3 in source system.


16) what is difference between PSA & IDOC?


BI7 is PSA used only for Data load from Source System into BW


17) what we do in Business Blue Print Stage?

SAP has defined a business blueprint phase to help extract pertinent information about your company that is necessary for implementation. These blueprints are in the form of questionnaires that are designed to probe for information that uncovers how your company does business. As such, they also serve to document the implementation. Each business blueprint document essentially outlines your future business processes and business requirements. The kinds of questions asked are germane to the particular business function, as seen in the following sample questions:1) What information do you capture on a purchase order?2) What information is required to complete a purchase order? Accelerated SAP question and answer database: The question and answer database (QADB) is a simple although aging tool designed to facilitate the creation and maintenance of your business blueprint. This database stores the questions and the answers and serves as the heart of your blue print. Customers are provided with a customer input template for each application that collects the data. The question and answer format is standard across applications to facilitate easier use by the project team. Issues database: Another tool used in the blueprinting phase is the issues database. This database stores any open concerns and pending issues that relate to the implementation. Centrally storing this information assists in gathering and then managing issues to resolution, so that important matters do not fall through the cracks. You can then track the issues in database, assign them to team members, and update the database accordingly.



18) How do we gather the requirements for an Implementation Project?

One of the biggest and most important challenges in any implementation is gathering and understanding the end user and process team functional requirements. These functional requirements represent the scope of analysis needs and expectations (both now and in the future) of the end user. These typically involve all of the following:- Business reasons for the project and business questions answered by the implementation- Critical success factors for the implementation- Source systems that are involved and the scope of information needed from each- Intended audience and stakeholders and their analysis needs- Any major transformation that is needed in order to provide the information- Security requirements to prevent unauthorized use This process involves one seemingly simple task: Find out exactly what the end users' analysis requirements are, both now and in the future, and build the BW system to these requirements. Although simple in concept, in practice gathering and reaching a clear understanding and agreement on a complete setoff BW functional requirement is not always so simple.



19) How do we decide what cubes have to be created?

Its depends on your project requirement. Customized cubes are not mandatory for all the projects. If your business requirement is differs from given scenario (BI content cubes) then only we will opt for customized cubes. Normally your BW customization or creation of new info providers all are depending on your source system. If your source system other that R3 then you should go with customization of your all objects. If your source system is R3 and your users are using only R3 standard business scenarios like SD, MM or FI... etc., then you don’t want to create any info providers or you don’t want to enhance anything in the existing BW Business Content. But 99% this is not possible. Because surely they should have included their new business scenario or new enhancements. For example, In my first project we implemented for Solution Manager BW implementation. There we have activated all the business content in CRM. But the source systemhave new scenarios for message escalation, ageing calculation etc., according their business scenario we couldn’t use standard business content. For that we have taken only existing info objects and created new info objects which are not there in the business content. After that we have created custom data source to info providers as well as reports.


20) Who used to make the Technical and Functional Specifications?

Technical Specification: Here we will mention all the BW objects (info objects, data sources, info sources and info providers). Then we are going to say the data flow and behavior of the data load (either delta or full) also we can tell the duration of the cube activation or creation. Pure BW technical things are available in this document. This is not for End users document. Functional Specification: Here we will describe the business requirements. That means here we are going to say which are all business we are implementing like SD, MM and FI etc., then we are going to tell the KPI and deliverable reports detail to the users. This document is going to mingle with both Function Consultants and Business Users. This document is applicable for end users also.

21) Give me one example of a Functional Specification and explain what information we will get from that?

Functional Specs are requirements of the business user.Technical Specs translate these requirements in a technical fashion.Let's say Functional Spec says,1. the user should be able to enter the Key date, Fiscal Year, Fiscal Version.2. The Company variable should be defaulted to USA but then if the user wants to change it, they can check the drop down list and choose other countries.3. The calculations or formulas for the report will be displayed in precision of one decimal point.4. The report should return values for 12 months of data depending on the fiscal year that the user enters Or it should display in quarterly values. Functional specs are also called as Software requirements.Now from this Techinal Spec follows, to resolve each of the line items listed above.1. To give the option of key date, Fiscal year and Fiscal Version – certain Info Obejcts should be availble in the system. If available, then should we create any variables for them - so that they are used as user entry variable. To create any varaibles, what is the approach, where do you do it, what is the technical of the objects you'll use, what'll be the technical name of the objects you'll Crete as a result of this report.2. Same explanation goes for the rest. How do you set up the varaible,

3. What changes in properties willu do to get the precision.4. How will you get the 12 months of data. What will be the technical and display name of the report, who'll be authorized to run this report, etc are clearly specified in the technical specs.


22) What is Customization? How do we do in LO?


How to do basic LO extraction for SAP-R3-BW1. Go to transaction code RSA3 and see if any data is available related to your DataSource. If data is there in RSA3 then go to transaction code LBWG (Delete Setup data) and delete the data by entering the application name.2. Go to transaction SBIW --> Settings for Application Specific Datasource --> Logistics --> Managing extract structures --> Initialization --> Filling the Setup table --> Application specific setup of statistical data --> perform setup (relevant application)3. In OLI*** (for example OLI7BW for Statistical setup for old documents : Orders) give the name of the run and execute. Now all the available records from R/3 will be loaded to setup tables.4. Go to transaction RSA3 and check the data.5. Go to transaction LBWE and make sure the update mode for the corresponding DataSource is serialized V3 update.6. Go to BW system and create infopackage and under the update tab select the initialize delta process. And schedule the package. Now all the data available in the setup tables are now loaded into the data target.7.Now for the delta records go to LBWE in R/3 and change the update mode for the corresponding DataSource to Direct/Queue delta. By doing this record will bypass SM13 and directly go to RSA7. Go to transaction code RSA7 there you can see green light # Once the new records are added immediately you can see the record in RSA7.


23) When we use Maintain Data Source, What we do? What we will maintain?

Go to BW system and create a new infopackage for delta loads. Double click on new infopackage. Under update tab you can see the delta update radio button.


24) Tickets and Authorization in SAP Business Warehouse What is tickets and example?

Tickets are the tracking tool by which the user will track the work which we do. It can be a change requests or data loads or whatever. They will of types critical or moderate. Critical can be (Need to solve in 1 day or half a day) depends on the client. After solving the ticket will be closed by informing the client that the issue is solved. Tickets are raised at the time of support project these may be any issues, problems.....etc. If the support person faces any issues then he will ask/request to operator to raise a ticket.

Operator will raise a ticket and assign it to the respective person. Critical means it is most complicated issues ....depends how you measure this...hope it helps. The concept of Ticket varies from contract to contract in between companies. Generally Ticket raised by the client can be considered based on the priority. Like High Priority, Low priority and so on. If a ticket is of high priority it has to be resolved ASAP. If the ticket is of low> priority it must be considered only after attending to high priority tickets. The typical tickets in a production Support work could be: 1. loading any of the missing master data attributes/texts. 2. Create ADHOC hierarchies. 3. Validating the data in Cubes/ODS. 4. If any of the loads runs into errors then resolve it. 5. Add/remove fields in any of the master data/ODS/Cube. 6. Data source Enhancement. 7. Create ADHOC reports.

1. Loading any of the missing master data attributes/texts - This would be done by scheduling the infopackage for the attributes/texts mentioned by the client. 2. Create ADHOC hierarchies. - Create hierarchies in RSA1 for the info-object. 3. Validating the data in Cubes/ODS. - By using the Validation reports or by comparing BW data with R/3. 4. If any of the loads runs into errors then resolve it. - Analyze the error and take suitable action. 5. Add/remove fields in any of the master data/ODS/Cube. - Depends upon the requirement 6. Data source Enhancement. 7. Create ADHOC reports. - Create some new reports based on the requirement of client.


25) Change attribute run.

Generally attribute change run is used when there is any change in the master data. it is used for realignment of the master data. Attribute change run is nothing but adjusting the master data after its been loaded from time to time so that it can change or generate or adjust the Sid’s so that u may not have any problem when loading the transaction data in to data targets. The detail explanation about Attribute change run. The hierarchy/attribute change run which activates hierarchy and attribute changes and adjusts the corresponding aggregates is divided, into 4 phases: 1. Finding all affected aggregates2. Set up all affected aggregates again and write the result in the new aggregate table.3. Activating attributes and hierarchies4. Rename the new aggregate table. When renaming, it is not possible to execute queries. In some databases, which cannot rename the indexes, the indexes are also created in this phase.


26) Different types of Delta updates?

Delta loads will bring any new or changed records after the last upload. This method is used for better loading in less time. Most of the std SAP data sources come as delta enabled, but some are not. In this case you can do a full load to the ODS and then do a delta from the ODS to the cube. If you create generic datasources, then you have the option of creating a delta on Cal.day, timestamp or numeric pointer fields (this can be doc number, etc.).You'll be able to see the delta changes coming in the delta queue through RSA7 on the R3 side. To do a delta, you first have to initialize the delta on the BW side and then set up the delta. The delta mechanism is the same for both Master data and Transaction data loads.============ ========= ==There are three deltas Direct Delta: With this update mode, the extraction data is transferred with each document posting directly into the BW delta queue. In doing so, each document posting with delta extraction is posted for exactly one LUW in the respective BW delta queues. Queued Delta: With this update mode, the extraction data is collected for the affected application instead of being collected in an extraction queue, and can be transferred as usual with the V3 update by means of an updating collective run into the BW delta queue. In doing so, up to 10000 delta extractions of documents for an LUW are compressed for each Data Source into the BW delta queue, depending on the application. On-serialized V3 Update: With this update mode, the extraction data for the application considered is written as before into the update tables with the help of a V3 update module. They are kept there as long as the data is selected through an updating collective run and are processed. However, in contrast to the current default settings (serialized V3 update), the data in the updating collective run are thereby read without regard to sequence from the update tables and are transferred to the BW delta queue.

27) An SAP BW functional consultant is responsible for the following: Key responsibilities include:

Maintain project plans Manage all project activities, many of which are executed by resources not directly managed by the project leader (central BW development team, source system developer, business key users) Liase with key users to agree reporting requirements, report designs Translate requirements into design specifications( report specs, data mapping / translation, functional specs) Write and execute test plans and scripts .

Coordinate and manage business / user testing Deliver training to key users Coordinate and manage product ionization and rollout activities Track CIP (continuous improvement) requests, work with users to prioritize, plan and manage CIP An SAP BW technical consultant is responsible for: SAP BW extraction using standard data extractor and available development tools for SAP and non-SAP data sources. -SAP ABAP programming with BW Data modeling, star schema, master data, ODS and cube design in BW Data loading process and procedures (performance tuning)Query and report development using Bex Analyzer and Query Designer Web report development using Web Application.

28) How to convert a BeX query Global structure to local structure (Steps involved)

BeX query Global structure to local structureSteps; ***a local structure when you want to add structure elements that are unique to the specific query. Changing the global structure changes the structure for all the queries that use the global structure. That is reason you go for a local structure.Coming to the navigation part--In the BEx Analyzer, from the SAP Business Explorer toolbar, choose the open query icon (icon tht looks like a folder) On the SAP BEx Open dialog box:Choose Queries.Select the desired InfoCubeChoose New.On the Define the query screen:In the left frame, expand the Structure node.Drag and drop the desired structure into either the Rows or Columnsframe.Select the global structure.Right-click and choose Remove reference.A local structure is created.Remember that you cannot revert back the changes made to global structure inthis regard. You will have to delete the local structure and then drag ndrop global structure into query definition.*When you try to save a global structure, a dialogue box prompts you tocomfirm changes to all queries. that is how you identify a global structure*



29) What is the use of Define cell in BeX & where it is useful?

Cell in BEX:::Use*When you define selection criteria and formulas for structural components and there are two structural components of a query, generic cell definitions are created at the intersection of the structural components that determine the values to be presented in the cell.Cell-specific definitions allow you to define explicit formulas, along with implicit cell definition, and selection conditions for cells and in this way, to override implicitly created cell values. This function allows you to design much more detailed queries.In addition, you can define cells that have no direct relationship to the structural components. These cells are not displayed and serve as containers for help selections or help formulas.you need two structures to enable cell editor in bex. In every query you have one structure for key figures, then you have to do another structure with selections or formulas inside.Then having two structures, the cross among them results in a fix reporting area of n rows * m columns. The cross of any row with any column can be defined as formula in cell editor.This is useful when you want to any cell had a diferent behaviour that the general one described in your query defininion.For example imagine you have the following where % is a formula kfB/KfA *100.kfA kfB %chA 6 4 66%chB 10 2 20%chC 8 4 50%Then you want that % for row chC was the sum of % for chA and % chB. Then in cell editor you are enable to write a formula specifically for that cell as sum of the two cell before. chC/% = chA/% + chB/% then:kfA kfB %chA 6 4 66%chB 10 2 20%chC 8 4 86%


30) What is 0Recordmode?

A. it is an info object , 0Record mode is used to identify the delta images in BW which is used in DSO .it is automatically activated when u activate DSO in BW. Like that in R/3 also have field 0cancel. It holds delta images in R/3. When ever u extracting data from R/3 using LO or Generic.. Etc. this field 0Cancel is mapping with 0Record mode in BW. Like this BW identify the Delta images.

31) What is the difference between filter & Restricted Key Figures? Examples & Steps in BI?

Filter restriction applies to entire query. RKF is restriction applied on a keyfigure. Suppose for example, you want to analyze data only after 2006...showing sales in 2007,2008 against Materials. You have got a key figure called Sales in your cube

Now you will put global restriction at query level by putting Fiscyear > 2006 in the Filter.This will make only data which have fiscyear >2006 available for query to process or show.

Now to meet your requirement. ..like belowMaterial Sales in 2007 Sales in 2008M1 200 300M2 400 700You need to create two RKF's.Sales in 2007 is one RKF which is defined on keyfigure Sales restricted by Fiscyear = 2007Similarly,Sales in 2008 is one RKF which is defined on Keyfigure Sales restricted by Fiscyear = 2008Now i think u understood the differenceFilter will make the restriction on query level..Like in above case putting filter Fiscyear>2006 willmake data from cube for yeaers 2001,2002,2003, 2004,2005 ,2006 unavailable to the query for showing up.So query is only left with data to be shown from 2007 and 2008.Within that data.....you can design your RKF to show only 2007 or something like that...

32) How to create condition and exceptions in Bi.7.0? But I know in Bw3.5 version?

From a query name or description, you would not be able to judge whether the query is having any exception. There are two ways of finding exception against a query:1. Execute queries one by one, the one which is having background color as exception reporting are with exceptions.2. Open queries in the BEX Query Designer. If you are finding exception tab at the right side of filter and rows/column tab, the query is having exception.

33) The FI Business Flow related to BW. Case studies or scenarios

FI Flow Basically there are 5 major topics/areas in FI,1. GL Accounting -related tables are SKA1, SKB1 Master Database and BSAS are the Transaction Data2. Account Receivables- related to Customer All the SD related data when transferred to FI these are created. Related Tables BSID and BSAD3. Account Payables - related Vendor All the MM related documents data when transferred to FI these are created Related Tables BSIK and BSAK All the above six tables data is present in BKPF and BSEG tables You can link these tables with the help of BELNR and GJAHR and with Dates also.4. Special Purpose Ledger. which is rarely used.5. Asset ManagmentIn CO there are Profit center Accounting Cost center Accounting will be there.

34) How we do the SD and MM configuration for BW?

You need to activate the data sources in R3 system.

You need to maintain the login information for the logical system.sm59 : Choose the RFC destination , BW system, Under logon Security, maintain the user credentials.

Maintain control parameters for data transfer.

Filling in of setup tables SBIW

I feel that these are certain prerequisites.

From an SD perspective, you as a BW consultant should first understand the basic SD process flow on the R3 side. (Search the forum for SD process flow and you'll get a wealth of information on the flow and the tables as well as transactions involved in SD).

Next you need to understand the process flow that has been implemented at the clients place. How the SD data flows and what are the integration points with other modules as well as how the integration happens.

This knowledge is essential when modeling your BW design.


From a BW perspective you need to first know all the SD extractors and what information they bring. Next look at all the cubes and ODS for SD.