Top 31 Sap Design Studio Interview Questions You Must Prepare 03.Oct.2023

If asking about defined BW – do not have – planned for 1.3 release. if jump from one app to another, can use opendoc link today  .

There are 3 ways in which Xcelcius can access data from the universe:

Query as a Web Service: Using Query as a Web Service tool, we can create a queries from the universe along with filter condition. The QAAWS qury panel is similar to the WebIntelligence query panel. In Xcelcius dashboard, we can create a QAAWS connection that would point to a particular Query and import the data into the excel data sheet of the xlf

Business Intelligence Web Service: In this method, we can use the output of a report directly in the Xcelcius dashboard. Using Webi Rich Client, we export the report to repository, then select a block from the report, right click and select Publish as Web Service option. However BIWS does not have a connection of its own. We access this BIWS through a QAAWS connection only.

LiveOffice: LiveOffice is an additional component that needs to be installed. This creates a sort of plugin for all MS Office applications, though which they can access data from Web Intelligence reports. I MS Excel, we can launch the Live Office Insert Wizard by Insert -> Web Intelligence Content. We can use this wizard to add selective content from a webi report. In the Xcelcius dashboard, a Live Office connection is created andwe access this Live Office excel sheet though this connection.

Design Studio 1.1  can connect to BW and HANA as backend systems.  Plan to connect to other data sources such as universes in the future releases. 

Cannot generally say limit for that – not like Xcelsius limitation.  DS uses BICS interface to connect to BW / HANA (analytic/calc views).

With 1.1 do not have; with 1.2 will not have geo maps; partner using SDK could do that but beta program has just started. 

It has 2 uses:

The Scope of Analysis pane sets the limit of drill down in the report. Suppose we have a hierarchy defined in 3 levels, but if we set the scope of analysis is set to 2 levels, the report will not be able to drill down to the 3rd level. We can also remove objects showing in the scope of analysis pane and limit the drill down.

If the analysis level is set to custom, the objects from existing hierarchies can be dragged in the scope of analysis panel to set the scope for drilldown in the report. This has an advantage that we can drill down to more than 3 levels, which is not possible in the normal level setting, since it is up to 3 only.

The 2 approaches are as follows:

Aggregate tables are built in the database, which contains the dimension fields(not foreign keys) along with the aggregated measures. In the universe they are present as standalone tables, i.e they are not joined with any dimensions. Aggregate aware function is used to define both the dimensions and measures of such tables.

No aggregate tables are built in the database level. They contain the normal fact table at different granularities. In the universe, aggregate aware is used only to define the measures and aggregate incompatibility is set accordingly.

The first approach is better in terms of performance, since for the higher levels of aggregation, all the information is obtained for a single table. However, a large scale implementation of this approach in a dimensional schema is difficult. In most BI projects, the second approach is preferred.

We can use ‘Swf Loader’ as well as ‘Slideshow’ components for linking multiple dashboards. ‘Swf Loader’ can open swf files only, while ‘Slideshow’ can open both swf files and image files.

For presentation purposes, we often need text and images. Hence these are embedded in image files are added to a ‘Slideshow’ along with dashboard outputs. Moreover ‘Swf Loader’ can only open swf through ‘Push Button’ or selector components, whereas ‘Slideshow’ has a feature of automatic slide transition, which loads the image and swf files in the specified sequence. Hence, ‘Slideshow’ is the only feasible option for a complete presentation.

A Personal connection is created by one user and cannot be used by other users. The connection details are stored in PDAC.LSI file.

A shared connection can be used by other users through a shared server. The connection details are stored in SDAC.LSI file in the Business Objects installation folder. However one cannot set rights and securities on objects in a shared connection. Neither can a Universe to exported to repository using a shared connection.

A secured connection overcomes these limitations. Through it rights can be set on objects and documents. Universes can be exported to the central repository only through a secured connection. The connection parameters in this case are saved in the CMS.

If a data warehouse is based on the Kimball model, it is a dimensional schema. In a universe built on that DW, for a fan trap to occur in such a schema, we require direct join between two fact tables, which is against the principles of dimensional modeling.

On the other hand in a data warehouse based on Inmon model, it is a normalized schema. Though in such a case, universes are generally designed on Data Marts, which are dimensional schemas (where fan traps should not occur). However, if a universe is built on the DW (for the purpose of operational reporting), then a fan trap can occur in that universe.

An extended prompt syntax is available since BO 3.@It is as follows

@Prompt( ’message’, ‘type’, [lov],
mono/multi,
free/constrained/primary_key,
persistent/not_persistent,
{‘default value’:’default key’} )

If the indexes for the dimension object is defined in the universe and we define the prompt condition on the object with the clause ‘primary key’ in place of free or constrained, then the filter condition will convert the prompt values entered to their corresponding indexes and eliminate the join with the dimension table

A condition object is a filter condition created in the universe level. When this object is dragged in the Query Panel, the filter condition appears in the query SQL.

However a query filter exists in the report only. It is added during building a query. This also appears in the query SQL.

Yes Design Studio supports all OLAP features that BW provides – time dependent hierarchy, attributes, etc.

DS is HTML5 based and Dashboard has provided HTML5 version answered before, will become one tool in long-time.  DS is optimized for BW and HANA and will offer support for  universes. 

Yes this is planned for  the future as Design Studio is a successor to WAD.

We can access one derived table from another using the function @derived_table.

The syntax is:

@derived_table(Derived Table Name)

The choice of query or report filter has to take in consideration the performance of the report.

Suppose we have report where are multiple tabs having different objects requiring same or different filter conditions, it is advisable to use a Query Filter.

In case where there are multiple tabs having same objects, but with slightly differing filter conditions, it is advisable to fetch the whole data in the query and then apply report filters to the various tabs to get the desired data instead of using separate queries for each tab.

2 options – 1 for end users use the Mobile BI solution using the Bi platform, category mobile to DS application then see it on the MobI app. Developers can do it locally using QR codes.

Yes, exactly; technology is HTML5 and can deploy on mobile devices.  Deploy on iPhone, iPad, or Mobile BI solution .

After creating a link if the ‘Include’ button is clicked then the tables from core universe are permanently copied into the derived universe and the link is severed.

Only ‘List Builder’ gives the option of multiple selection in Xcelcius. We select multiple rows from the input list and add them to the output list using Add button. The output list gives the selection parameter.

A derived table is present only in the universe level, while a view is created in data base level. Generally views are preferred since, in its case the onus of calculation remains on the database and it does not load the BO server. However, in cases where developers do not have access to database, derived table is the only solution.

Input context consists of any dimension objects that need to be included directly in the calculation itself.

Output context consists of one or more dimension objects that determine the aggregation level at which the calculation is displayed.

No, as Design Studio is the premium alternative to WAD/Xcelsius and VC is different technology .

In a universe structure, we may have 3 tables joined in such a way that, the 1st table has a one to many join with the 2nd table, which in turn has a one to many join with the 3rd table(A -< B -< C). In such a scenario, if a measure is present in the 2nd table and it is dragged along with any dimension from the 3rd table, the value of the measure will be inflated. Such a condition is known as a fan trap.

A fan trap is solved by creating an alias of the 2nd table and defining contexts such that, the normal table is joined only with the first table, while the alias is joined with both the 1st and the 3rd table. We would take 2nd table’s measure only from the normal table and other dimensions of the 2nd table from the alias table.

We have to use context Operator In along with keyword report. This will give the total sum of the measure in row level(and anywhere in the report).

The expression will be like:

Sum( Measure In Report )

When Web Intelligence is in Interactive mode, one can create variables, input controls, add report filters, tables and charts in the view mode itself. This is not possible in the normal Java report panel.

The advantage of interactive mode is for power users, who want to do further manipulations on an existing report. Since, it does not allow user to modify queries or existing variables in the report, but allows doing the above mentioned activities on top of the report, it provides a very good means for analysis by the power users without changing the core report in any way.