41)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 analyse
data only after 2006...showing sales in 2007,2008 against Materials..You have
got a keyfigure 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...
42)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 colour 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.
43)The FI Business Flow
related to BW. case studies or scenarios FI FlowBasically there are 5 major topics/areas in FI,1. GL Accounting
-related tables are SKA1, SKB1 Master dataBSIS and BSAS are the Transaction
Data2. Account Receivables- related to CustomerAll the SD related data when
transfered to FI these are created.Related Tables BSID and BSAD3. Account
Payables - related VendorAll the MM related documents data when transfered to
FI these are createdRelated Tables BSIK and BSAKAll the above six tables data
is present in BKPF and BSEG tablesYou can link these tables with the hlp of
BELNR and GJAHR and with Dates also.4. Special Purpose Ledger.. which is rarely
used.5. Asset ManagmentIn CO there are Profit center AccountingCost center
Accounting will be there.
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.
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.
Finance economy finance & insurance money derivatives wall street young money got money cash money get money
Finance economy finance & insurance money derivatives wall street young money got money cash money get money
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?
SID keys linked with dimension
table & master data tables (attributes, texts, hierarchies)
Q) What does ATTRIBUTE Table
contain?
Master attribute data
Q) What does TEXT Table
contain?
Master text data, short text,
long text, medium text & language key if it is language dependent
Q) What does Hierarchy table
contain?
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) WHAT ARE THE DIFFERENT
VARIABLES USED IN BEX?
A ) Different Variable's 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 fastly.
Q) CAN CHARECTERSTIC
INFOOBJECT CAN BE INFOPROVIDER.
Of course
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).
No comments:
Post a Comment