SAP B1

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.

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

In context to BW/BI 3.x

transfer rules - mapping the fields in the datasource to the infoobjects in Infosource or target fields. it help you to distinguish which all fields in the datasource are required in the infoobjects in the Infosource.

update rules - to update something. here it revolves around a source(infosource)and a target(data target). update rules are used to update the data targets.you have to create update rules if you supply a data target from an InfoSource with flexible update.

In BI 7.0 Transforamtion - (Tranfer and update rules)

SAP Given Three different kind dimensions for InfoCube.Those

are.

1)Data Packet Dimension : Which is going to hold the

technical information like request Number etc..

2)Unit Dimension: This dimension can hold the all Unit

characteristics like Reference Currencies , UNIT'S etc..

3)Time Dimension : This particular Dimension Can hold the

all time characteristics like 0calday,zdate, start date, end

date etc..

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.

every process it has own variant .selecting the variant it

will give the time period i..e immediate or time/date..

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.

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.

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