SAP B1 Interview Preparation Guide

Manual says we can do format using HTML and Java Script [not css].

In all of the database systems there is maximum number of
fields allowed to create a primary key (composite key) is 16.
An in the case of cube, to fetch a single record a
combination of all dimension is used, so this is the reason
behind having maximum no. of dimension in cube is 16 only.

SAP BI InfoCube Can have maximum 16 Dimension, Why because
na Cube shape will have only 16 Dimensions and also Normal
data base table will have only 16 keyfields. When we create
InfoCube system is going to create tables like F-table and
E-table So,we should follow that database concepts Because
of that InfoCube will Have only 16 Dimensions..

1.For Requirement as per company
2.Reporting As Per Module
3.Remove Complexity From End User

Unlike the older version of BW which uses star schema, BI
7.0 uses the extended star schema. In this, master data is
stored outside the cube.
In the star schema, both master data and transaction data
resides inside the cube bringing many problems: master data
not reusable, computing of alphanumeric values and analysis
being limited.
In BI 7.0 Master data is stored outside the cube which
makes it reusable, and alphanumeric values can be computed
and many more analysis are possible.

1.NOT CORRECT USAGE.
Reason: When we change the structure of any cube which has Business Warehouse Accelerator Indexes created for it. Change in structure could mean a change as simple as adding a navigational attribute.
solution: Delete the Indexes (BWA Indexes)first then transport and then rebuild the indexes

2.Info Object not available in active version.
Reason: We get this error when we try to transport the Info Object Catalogs without transporting the info objects.
Solution: As a prerequisite first transport the info objects then transport info object catalogs.
3. Navigational attribute does not exist
Reason: If we mark an object in the cube as navigational attribute and navigational attribute does not exist as navigational in the target system.
Solution: Transport the info object with navigational attribute and then re-import this transport.

if we create aggregates on infocube then query performance
will be improved if our query accessing attributes data
frequently.The sequence when we execute the query is:
1.Query first goes into cache if it finds relevant data in
cache will fetch data otherwise
2. it goes into BI ACCELERATOR(BIA)
3. Aggregates
4. Finally it goes into IC if the data is not available in
above 3 stages.
If we maintain aggregates or BIA olap no needs to come
upto IC. So time will be reduced. Query performance will be
improved.

Yes we can.

because of for capturing deltas we need to do somthing
before load the deltas.

before going to set the delta mode. you should initialize
delta process without data transfor process. ofter
finishing the this initiazation keep the delta mode. and
exectue the infopackage.
before going to execute info package check weather data
source is reay to capture deltas or not. by using the t-
code rsa7.

every process it has own variant .selecting the variant it
will give the time period i..e immediate or time/date..

Create a job at that time when all the process chains have ended. This job will send you a email alert what process chains have errors.

normally

red - failure.
black - start the next process.