Beruflich Dokumente
Kultur Dokumente
From a BW perspective you need to first know all the SD extractors and what
information they bring. Next look at all the cubes and ODS for SD.
You need to Reprocess this IDOC which are RED. For this you can take help of Any of
your Team (ALE IDOC Team or BAsis Team)Or Else
youcan push it manually. Just search it in bd87 screen only to Reprocess.
Also, Try to find why this IDocs are stuck there.
V1 Update: when ever we create a transaction in R/3(e.g.,Sales Order) then the entries
get into the R/3 Tables(VBAK, VBAP..) and this takes place in V1 Update.
V2 Update: V2 Update starts a few seconds after V1 Update and in this update the values
get into Statistical Tables, from where we do the extraction into BW.
V3 Update: Its purely for BW extraction.
But in the Document below, V1, V2 and V3 are defined in a different way. Can You
please explain me in detial what exactly V1, V2 and V3 updates means?
6.Do you have any idea how to improve the performance of the BW..?
Asynchronous Updating (V2 Update)
With this update type, the document update is made separately from the statistics update.
A termination of the statistics update has NO influence on the document update (see V1
Update).
Radio button: Updating in U3 update program
Asynchronous Updating (V3 Update)
With this update type, updating is made separately from the document update. The
difference between this update type and the V2 Update lies,however, with the time
schedule. If the V3 update is active, then the update can be executed at a later time.
In contrast to V1 and V2 Updates, no single documents are updated. The V3 update is,
therefore, also described as a collective update.
1. Go to transaction code RSA3 and see if any data is available related to your
DataSource. If data is there in RSA3 then go to transaction code LBWG (Delete Setup
data) and delete the data by entering the application name.
2. Go to transaction SBIW --> Settings for Application Specific Datasource --> Logistics
--> Managing extract structures --> Initialization --> Filling the Setup table -->
Application specific setup of statistical data --> perform setup (relevant application)
3. In OLI*** (for example OLI7BW for Statistical setup for old documents : Orders) give
the name of the run and execute. Now all the available records from R/3 will be loaded to
setup tables.
4. Go to transaction RSA3 and check the data.
5. Go to transaction LBWE and make sure the update mode for the corresponding
DataSource is serialized V3 update.
6. Go to BW system and create infopackage and under the update tab select the initialize
delta process. And schedule the package. Now all the data available in the setup tables
are now loaded into the data target.
7. Now for the delta records go to LBWE in R/3 and change the update mode for the
corresponding DataSource to Direct/Queue delta. By doing this record will bypass SM13
and directly go to RSA7. Go to transaction code RSA7 there you can see green light #
Once the new records are added immediately you can see the record in RSA7.
8. Go to BW system and create a new infopackage for delta loads. Double click on new
infopackage. Under update tab you can see the delta update radio button..
9. Now you can go to your data target and see the delta record.
13.What is dashboard?
A dash board can be created using the web application Designer (WAD) or the visual
composer (VC). A dashboard is just a collection of reports, views and links etc in a single
view. For e.g. igoogle is a dashboard.
When we look at the all organization measures how they are performing with helicopter
view, we need a report that teaches and shows the trend in a graphical display quickly.
These reports are called as Dashboard Reports, still we can report these measures
individually, but by keeping all measures in a single page, we are creating single access
point to the users to view all information available to them. Absolutely this will save lot
of precious time, gives clarity on decision that needs to be taken, helps the users to
understand the measure(s) trend with business flow creating dashboard
Dashboards : Could be built with Visual Composer & WAD
create your dashboard in BW,
(1) Create all BEx Queries with required variants,tune them perfectly.
(2) Differentiate table queries and graph queries.
(3) Choose the graph type required that meet your requirement.
(4) Draw the layout how the Dashboard page looks like.
(5) Create a web template that has navigational block / selection information.
(6) Keep navigational block fields are common across the measures.
(7) Include the relevant web items into web template.
(8) Deploy the URL/Iview to users through portal/intranet
The steps to be followed in the creation of Dashboard using WAD are summarized as
below:
14.How can you solve the data mismatch tickets between r/3 and bw?
Check the mapping at BW side for 0STREET in transfer rules.Check the data in PSA for
the same field.If the PSA is also doesn't have complete data then check the field in RSA3
in source system.
How to do basic LO extraction for SAP-R3-BW1. Go to transaction code RSA3 and see
if any data is available related to your DataSource. If data is there in RSA3 then go to
transaction code LBWG (Delete Setup data) and delete the data by entering the
application name.2. Go to transaction SBIW --> Settings for Application Specific
Datasource --> Logistics --> Managing extract structures --> Initialization --> Filling the
Setup table --> Application specific setup of statistical data --> perform setup (relevant
application)3. In OLI*** (for example OLI7BW for Statistical setup for old documents :
Orders) give the name of the run and execute. Now all the available records from R/3 will
be loaded to setup tables.4. Go to transaction RSA3 and check the data.5. Go to
transaction LBWE and make sure the update mode for the corresponding DataSource is
serialized V3 update.6. Go to BW system and create infopackage and under the update
tab select the initialize delta process. And schedule the package. Now all the data
available in the setup tables are now loaded into the data target.7.Now for the delta
records go to LBWE in R/3 and change the update mode for the corresponding
DataSource to Direct/Queue delta. By doing this record will bypass SM13 and directly go
to RSA7. Go to transaction code RSA7 there you can see green light # Once the new
records are added immediately you can see the record in RSA7.
24) When we use Maintain Data Source, What we do? What we will maintain?
Go to BW system and create a new infopackage for delta loads. Double click on new
infopackage. Under update tab you can see the delta update radio button.
25) Tickets and Authorization in SAP Business Warehouse What is tickets? And
example?
Tickets are the tracking tool by which the user will track the work which we do. It can be
a change requests or data loads or what ever. They will of types critical or moderate.
Critical can be (Need to solve in 1 day or half a day) depends on the client. After solving
the ticket will be closed by informing the client that the issue is solved. Tickets are raised
at the time of support project these may be any issues, problems.... .etc. If the support
person faces any issues then he will ask/request to operator to raise a ticket.
Operator will raise a ticket and assign it to the respective person. Critical means it is most
complicated issues ....depends how you measure this...hope it helps. The concept of
Ticket varies from contract to contract in between companies. Generally Ticket raised by
the client can be considered based on the priority. Like High Priority, Low priority and so
on. If a ticket is of high priority it has to be resolved ASAP. If the ticket is of low>
priority it must be considered only after attending to high priority tickets. The typical
tickets in a production Support work could be: 1. Loading any of the missing master data
attributes/texts. 2. Create ADHOC hierarchies. 3. Validating the data in Cubes/ODS. 4. If
any of the loads runs into errors then resolve it. 5. Add/remove fields in any of the master
data/ODS/Cube. 6. Data source Enhancement. 7. Create ADHOC reports.
1. Loading any of the missing master data attributes/texts - This would be done by
scheduling the infopackages for the attributes/texts mentioned by the client. 2. Create
ADHOC hierarchies. - Create hierarchies in RSA1 for the info-object. 3. Validating the
data in Cubes/ODS. - By using the Validation reports or by comparing BW data with R/3.
4. If any of the loads runs into errors then resolve it. - Analyze the error and take suitable
action. 5. Add/remove fields in any of the master data/ODS/Cube. - Depends upon the
requirement 6. Data source Enhancement. 7. Create ADHOC reports. - Create some new
reports based on the requirement of client.
30) How to convert a BeX query Global structure to local structure (Steps involved)
BeX query Global structure to local structureSteps; ***a local structure when you want
to add structure elements that are unique to the specific query. Changing the global
structure changes the structure for all the queries that use the global structure. That is
reason you go for a local structure.Coming to the navigation part--In the BEx Analyzer,
from the SAP Business Explorer toolbar, choose the open query icon (icon tht looks like
a folder) On the SAP BEx Open dialog box:Choose Queries.Select the desired
InfoCubeChoose New.On the Define the query screen:In the left frame, expand the
Structure node.Drag and drop the desired structure into either the Rows or
Columnsframe.Select the global structure.Right-click and choose Remove reference.A
local structure is created.Remember that you cannot revert back the changes made to
global structure inthis regard. You will have to delete the local structure and then drag
ndrop global structure into query definition.*When you try to save a global structure, a
dialogue box prompts you tocomfirm changes to all queries. that is how you identify a
global structure*
31) What is the use of Define cell in BeX & where it is useful?
Cell in BEX:::Use*When you define selection criteria and formulas for structural
components and there are two structural components of a query, generic cell definitions
are created at the intersection of the structural components that determine the values to be
presented in the cell.Cell-specific definitions allow you to define explicit formulas, along
with implicit cell definition, and selection conditions for cells and in this way, to override
implicitly created cell values. This function allows you to design much more detailed
queries.In addition, you can define cells that have no direct relationship to the structural
components. These cells are not displayed and serve as containers for help selections or
help formulas.you need two structures to enable cell editor in bex. In every query you
have one structure for key figures, then you have to do another structure with selections
or formulas inside.Then having two structures, the cross among them results in a fix
reporting area of n rows * m columns. The cross of any row with any column can be
defined as formula in cell editor.This is useful when you want to any cell had a diferent
behaviour that the general one described in your query defininion.For example imagine
you have the following where % is a formula kfB/KfA *100.kfA kfB %chA 6 4 66%chB
10 2 20%chC 8 4 50%Then you want that % for row chC was the sum of % for chA and
% chB. Then in cell editor you are enable to write a formula specifically for that cell as
sum of the two cell before. chC/% = chA/% + chB/% then:kfA kfB %chA 6 4 66%chB
10 2 20%chC 8 4 86%
Manager Round Review Questions.
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.