Answers to SAP BI Questions

Advertisement

answers to sap bi questionsHere are the answers to sample SAP BI questions for certification.

1. c

Advertisement

Transposing a wide data record into several smaller records is called Pivoting. Pivoting can be easily implemented using the expert routine.

2. a, c

You use InfoSources if you want to run two (or more) sequential transformations in the data flow, without storing the data again. Since InfoSources are not persistent data stores, they cannot be used as targets of the data transfer process. In contrast to 3.x InfoSources, as of Release SAP NetWeaver BI 7.0, an InfoSource behaves like an InfoSource with flexible update.

3. b, d

Texts are active immediately after they have been loaded. Time-independent attributes are stored in the P table. Time-dependent attributes are stored in the Q table.

Advertisement

4. c

DataStore object uses ORECORDMODE InfoObject for delta load. ORECORDMODE has values as ‘X’, ‘D’, ‘R’. In delta data load, ‘X’ means rows to be skipped, values ‘D’ and ‘R’ are for deleting and removing the rows.

5. c

The ALPHA conversion is used in the BI system for each presetting for character characteristics. The ALPHA conversion routine is registered automatically when a characteristic is created. If you do not want to use this routine, you have to remove it manually.

6. c

Advertisement

A new DataStore type in BI 7.0 is write-optimized DataStore object. It has no change log and no activation queue. Delta would be captured on request level for a write-optimized DataStore object. Similarly, DataStore Objects for Direct Update consist of a table for active data only, and therefore, no change log and no activation queue are generated.

7. a, c, d

Virtual Providers only allow read access to data. They do not allow write access to data.

8. a

Reduced read-only performance is accepted as a drawback of real-time InfoCubes, in favor of the option of parallel (transactional) writing and improved write performance.

Advertisement

9. b, d

The system does not generate SIDs for write-optimized DataStore objects and you do not need to activate them. This means that you can save and further process data quickly. The loaded data is not aggregated; the history of the data is retained.

10. c

Direct Update DataStore object cannot be used for transformation upload scenarios – there is no loading into the DataStore object for direct update within BI. It is not possible to include Direct Update DataStore object into a MultiProvider. Direct Update DataStore object can be used for analysis processes, for example, with the Analysis Process Designer (APD). Direct Update DataStore object is perfect for using it for external data.

11. b, c

An InfoCube cannot be a right operand of a left outer join due to performance issues. Only 2 InfoCubes are allowed within 1 InfoSet.

12. e

The quality of an InfoCube is generally measured with respect to query efficiency, load efficiency and manageability.

13. a, b, d

Do not use more than one non-cumulative InfoCube because this could lead to incorrect query results. Do not use calculations before aggregation on MultiProvider because this may lead to wrong query results. Do not combine basic InfoProviders having inhomogeneous data models in a MultiProvider. Avoid using only parts of compound characteristics in the constituent basic InfoProvider of a MultiProvider.

14. c

InfoSets are exceptions to this rule, as the most recent reporting function can be switched on in the InfoSet Builder. In such an InfoSet, the most recent records are displayed in reporting, even if they are not yet active.

15. a, b

In the BEx Analyzer, it is not possible to display an exception in a cell other than the cell than contains the threshold values. In the BEx Analyzer, it is not possible to apply the selected condition on the last characteristic of a specific axis only.

16. c, d

Display attributes cannot be shown in a report in the drilldown. Navigation attributes result in slight loss in performance in comparison with using characteristics.

17. a, b, c

We can recalculate the key figures of an InfoProvider for re-use in the Query Designer using formulas. Calculated key figures consist of formula definitions containing basic key figures, restricted key figures or pre-calculated key figures.

18. a, d, e

Structures and filters can be defined for reuse. But, variables, restricted key figures and calculated key figures are always re-usable.

19. a, b, c, d

Queries, transactions, reports, and web addresses can be jump targets.

20. c

Characteristic in the filter, in the rows, columns or the free characteristics can derive properties from characteristic in InfoProvider, characteristic in re-usable filter.

21. a, d

When Percentage Share of the Overall Result (%GT) is used, dynamic filters play a role in calculating the overall result. When Percentage Share of the Query Result (%CT) is used, dynamic filters do not play a role in calculating the query result.

22. a, c

The processing type Authorization can be used with characteristic value variables and hierarchy node variables.

23. a, c

The Cell Editor is a function of the BEx Query Designer. You can select it if the query definition contains two structures. You can define a maximum of two structures in a query definition. You can define cells that have no direct relationship to the corresponding structure parts. Cells are not displayed, and serve as containers for auxiliary selections or formulas.

24. b, c

The processing type replacement path can be used with characteristic value variables, text variables and formula variables.

25. b, c

Selecting Variable offsets is only available for Characteristic value variables of the type single value or interval.

26. b

UD Connect transfers the data as flat data. Multi-dimensional data is converted to a flat format when we use UD Connect.

27. d

The data source for a generic data source can be transparent tables, database views and InfoSet Query.

28. b, c

The DB Connect Data Sources do not support delta processes. A (Pseudo) delta update can be performed in this case using a selection. DB Connect DataSources support only the PSA transfer method.

29. d

All the 3 restrictions apply when using InfoObjects with UD Connect.

30. c

AIM (After image) delta process does not support the direct update of data in an InfoCube. A DataStore object must always be in operation when you update data in an InfoCube.

31. e

There are 3 delta management options for files: delta only with status “new”, additive delta and “Delete and add”/”Pseudo delta”.

32. c

Relational and multidimensional data stores in the data source are designated as UD Connect source object (such as tables and cubes).

33. c

In the original system, you can restore 3.x DataSources from DataSources that were migrated in the standard way (SAP source system, file, DB Connect). 3.x XML DataSources and 3.x UD Connect DataSources cannot be migrated in the standard way because the 3.x objects are created in the Myself system and in the new data flow the DataSources need to be created in separate source systems for Web Service and UD Connect.

34. a, b

The InfoProvider defines the data basis for planning. This involves real-time InfoCubes and MultiProviders. For real-time InfoCubes you can define permitted combinations of characteristic values in the form of characteristic relationships and create data slices for data that you want to protect.

35. a, c

The standard key date is a key date that is used in the entire planning model. It can be set for every real-time enabled InfoCube in the characteristic relationships. The options that are available to set a key date are: Unspecified, Fixed Date and From Variable. If the aggregation level was created directly on a real-time enabled InfoCube, the standard key date is the same key date that is set in the characteristic relationships on this InfoCube.

36. c, d

You can create multiple aggregation levels for an InfoProvider. Aggregation levels can also be created on MultiProviders. An aggregation level is set using a set of characteristics and key figures from the underlying InfoProvider. The key figures included in the aggregation level are aggregated using the characteristics that are not included in the aggregation level. Aggregation levels are used as InfoProviders for planning: with an aggregation level, you model levels whose data can be changed manually using input-ready queries or automatically using planning functions.

37. b

The InfoProvider is an aggregation level that is defined on a MultiProvider (complex aggregation level). The following prerequisites must be fulfilled. The MultiProvider includes at least one real-time InfoCube and no simple aggregation levels.

38. d

In the default settings, navigation attributes are not relevant for lock checks. This means that they are always completely locked.

39. c

The following lock modes are available. E (exclusive): Write lock that is used for all data that is edited in change mode; the data is locked and can be edited by one user only. S (shared): Read lock that means that reference data for planning functions, for example, cannot be changed at runtime.

40. a, b, d

Unlike BEx objects, however, planning objects are written to the BEx transport request or requests, even if the standard transport system is switched on. This applies to the aggregation level, characteristic relationship, data slice, planning function, planning sequence and planning function type from the planning area.

41. c

Planning sequences are used within BI Integrated Planning to group planning functions. They allow you to save groups of planning functions in a sorted sequence and execute groups of planning functions sequentially. Planning Sequences can be linked to a variant of variable values.

42. a, b, e

Analysis Process Designer is the application environment for the SAP data mining solution. Analysis Process Designer makes it possible to identify hidden relationships between data in a simple way. Analysis processes are integrated into the versioning concept.

43. a, c

You can transfer data from the following sources in SAP BW to SAP CRM: (1) InfoObject attributes, such as attributes for the InfoObject Business Partner (0BPARTNER); (2) Queries, in which the master data – such as the business partner – is unique.

44. c

Remodeling can be done for InfoCubes and DataStore objects. We can change InfoCubes and DataStore objects without building them from scratch – improved flexibility. To access re-modeling option select InfoCube/DataStore object -> right click Additional function -> Remodeling.

45. b

During (dictionary-based) conversion process it is not possible to get data in queries. Aggregates will be automatically deactivated and need to be rebuilt. Hence, transporting remodeling is not possible.

46. b

An upgrade of business content does not affect the objects that are in productive use. Roles do not have D-versions (delivered versions). Business content or activated objects within a BI system can be viewed online in the Metadata Repository.

47. a, b, c

Any type of BEx Web query, Report or Web application can be converted to PDF and printed.

48. c

BEx Web Analyzer allows web-based ad-hoc query and analysis on BI and 3rd-party BI data.

49. b

BEx Report Designer allows the creation of highly formatted Enterprise Reports.

50. a, b

BEx Map is a part of the BEx Analyzer and appears in a new worksheet in the workbook. The size of the BEX Map corresponds to the initial size of the workbook.

51. d

There are four options to choose from.

1. Static geo-characteristic: For this type you can use shape files (country borders, for example), to display the characteristic on a map in the Business Explorer.

2. Dynamic Geo-Characteristic: For this type geo-attributes are generated that make it possible, for example, to display customers as a point on a map.

3. Dynamic Geo-Characteristic with Attribute Values: For this type the geo-attributes of a geo-characteristic of type 2, which is an attribute, are used.

4. Static geo-characteristic with geo-attributes: Just like static geo-characteristics, with the addition of generated geo-attributes.

52. a, c

The BEX Web Analyzer is a standalone Web application that can be called through a URL by specifying the template ID 0ANALYZER. You can also call the BEx Web Analyzer as an iView in the Enterprise Portal.

53. e

Exceptions can be defined in the BEx Query Designer, Web Applications and BEx Web Analyzer.

54. e

A document class is made up of the documents for one of the following categories of BI objects: metadata, master data and InfoProvider data. Documents in a document class are characterized by particular logical document properties.

55. a

Migrated documents are not available in the BEx Analyzer. You should migrate documents only if they do not use the BEx Analyzer or do not use it in connection with documents.

56. a

The SOAP based transfer of data is only possible for flat structures. You cannot transfer hierarchy data.

57. c

The interface used depends on the platform: OLE DB for OLAP requires MS Windows, OLAP BAPI requires an SAP platform. XML for Analysis is platform independent.

58. b

As a prerequisite for using aggregates, all the data required by an InfoCube must be readable using logical access. For an InfoCube within an InfoSet with InfoCubes, it is no longer possible to read part of the data from one aggregate and part of the data from another aggregate or the InfoCube itself. The system cannot access BI accelerator indexes within an InfoSet.

59. a, c

Aggregates can be created only for InfoCubes. Aggregates can be automatically proposed by the BI system. The various options available are Proposal from Query, proposal from BI Statistics (tables), proposal from BI Statistics (InfoCubes) and proposal from previous navigation.

60. a, d

Aggregates use the same Start Schema design that cubes use. Aggregates do not contain all the data from InfoCubes, thus, they cannot replace InfoCubes. Aggregates require no special knowledge by an end-user, as they are completely transparent. The only way the end-user might recognize the existence of an aggregate is by the performance gain that is observed. Aggregates are for InfoCubes what indexes are for database tables.

61. a, b

Usage of a BI Accelerator results in performance improvements by factor 10-100 (very fast query response time), planned support of new hardware paradigms like grid/adaptive computing (high scalability), no aggregate maintenance and minimized roll-up/change run (low maintenance).

62. b, c, d

The relational aggregate/caching approach is not obsolete with the BI Accelerator, and is suitable for some scenarios such as smaller data volumes, predictable query patterns, relaxed response time constraints and reducing potential high load on the BI Accelerator through caching.

63. b

Between using a navigational attribute versus a characteristic, the first option is better for load performance whereas the second option is better for query performance.

64. b

A special type of InfoPackage is used for real-time data acquisition (SAPI and Web service) and when using Web services for standard update (with a standard data transfer process). This InfoPackage type is called InfoPackage for Real-Time Data Acquisition. Requests that are instantiated using an InfoPackage for real-time data acquisition remain open across several load processes. For real-time data acquisition (SAPI and Web service), the daemon processes the InfoPackage. In the InfoPackage for real-time data acquisition, the size and time limits for requests can be specified.

65. b

DataSources that are used for real-time data acquisition cannot be used in the delta process for standard data transfer. A data transfer with RDA and a scheduled data transfer cannot be executed simultaneously in the delta process for a DataSource because there may be only one entry in the delta queue for each DataSource and target system.

66. a, b, e

Using API and using a Meta chain the start of the process chain can be triggered. A start process can only be used in a single process chain and only one start process is allowed for each process chain.

67. c

Collector processes are used to manage multiple predecessor processes that feed into the same subsequent process. The collector processes available are AND, OR and EXOR (Exclusive ‘OR’).

68. a, b, e

Conversion types can be used for unit conversion within transformation rules, BEx Analyzer and within planning functions.

69. a, d

By default, the type of the index on the dimension and fact tables is Bitmap. For high cardinality dimensions, the system will use B-Tree index.

70. d

You can only partition a dataset using one of the two partitioning criteria ‘calendar month’ (0CALMONTH) or ‘fiscal year/period’ (0FISCPER). At least one of the two InfoObjects must be contained in the InfoProvider.

71. a, b, c, d

You cannot migrate hierarchy DataSources, DataSources that use the IDoc transfer method, DataSources from BAPI source systems, or export DataSources (namespace 8* or /*/8*) that are used by the data mart interface.

72. a, b, c, d

BI objects such as InfoCubes, DataStore objects, MultiProviders or InfoObjects (attributes or texts) can function as open hub data sources.

73. c

The maximum number of key fields that you can have in a DataStore object is 16.

74. d

The maximum number of hierarchy levels that can be created for a characteristic InfoObject is 98.

75. a, c

InfoCube is more normalized than DataStore object. Surrogate IDs (SIDs) are static.

76. b

If the InfoCube is compressed, delta cannot be determined -> Cache entry will be built up completely.

77. e

The distribution options available are ‘broadcast as e-mail’, ‘broadcast to portal’ and ‘print’. Additional options are available to system administrators and business experts.

78. a, d

Exceptions can be evaluated online when executing the query or the Web application. Exceptions can be evaluated for a large number of queries in the background with the BEx Broadcaster.

79. b, c

The Report Designer is a tool you use to format and adapt the layout of your business data as a report (static or dynamic) and according to your needs. The data binding for the report is provided by data providers (queries and query views). The Report Designer generates group levels according to the drilldown state of a query or query view. These group levels contain row patterns for the initial report view. The layout and formatting of the initial view can be adapted to suit customers’ requirements. The Report Designer is a standalone desktop application. You can open the Report Designer directly from the start menu or call it in the Web Application Designer using the context menu for the Report Web item. The Report Designer is a tool you use to format and adapt the layout of your business data as a report (static or dynamic) and according to your needs.

80. b

To create a report, a structure must be used in the columns of the query or query view on which the report is based.

Page last updated by Cleo Isco on

Leave a Reply

Do you have a question and want it to be answered ASAP? Post it on our FORUM here --> SAP FORUM!

Your email address will not be published. Required fields are marked *