Reporting of multicube
I have a cube with 3 fields - A, B, C.
another cube with 4 fields - A, B, X, Y. A & B key and char.
Can i create a multicube and will the report show all in same line in the report or will it be as two difflines?
A, B, C, X, Y : displayed in same line?
or
A B C
A B X Y : displayed in two different lines?
Thanks.
I have a cube with 3 fields - A, B, C.
another cube with 4 fields - A, B, X, Y. A & B key and char.
You will have the report showing you values in one line if
X,Y are Key Figures - if the report has all the characteristics which are common to both cubes you will get the O/P in a single line - else you would have to work around using RKFs.
Similar Messages
-
Hi,
I am using Multicube for one of my report, which is using two infocubes. One infocube A has characteristics x,y and keyfigure x1 and other infocube B has characteristics x,y,z and keyfigure y1. I need to display the characeristics x,y,z values in the report along with the keyfigure x1. since there is no characeristic z in the infocube B the Report is showing two rows one has the z value and keyfigure x1 and other row z value as "not assigned" and keyfigure is y1. My requirement is to show the x,y,z values in the report along with the x1 keyfigure in a single row. If someone has worked on this type of scenario please suggest me on the solution.
Thanking you,
RajuHi Raj,
In your query select constant selection on Characteristic Z.
Check this weblog
/people/prakash.darji/blog/2006/09/19/the-hidden-secret-of-constant-selection
Jaya -
Absurd values in BEx Report on Multicube
Hi,
when i run my query on the multicube (containing 2 cubes C1 and C2), i get a result with 3 rows and the fourth row says # and "not assigned" in all columns except the KF column.
when i run my query only on the cube C1, then it shows me the correct result i.e. all the rows.
I suspect there is something absurd in the multicube but cannot detect the problem. Pls help!!
I am working on BW 2.0B
Thanks,
SDHi,
In a MultiProvider, every characteristic in each of the InfoProviders involved must correspond to exactly one characteristic or navigation attribute (wherever these are available). If it is not clear, at the MultiProvider definition stage, you have to specify to which InfoObject you want to assign the characteristic of the MultiProvider.
The MultiProvider contains the characteristic 0COUNTRY and an InfoProvider contains the characteristic 0COUNTRY as well as the navigation attribute 0CUSTOMER__0COUNTRY. In this case, select exactly one of these InfoObjects in the assignment table.
Select a key figure contained in a MultiProvider from at least one of the InfoProviders involved. In general, exactly one of the InfoProviders provides the key figure. However, there are cases where it is better to select from more than one InfoProvider:
If the 0SALES key figure is stored redundantly in more than one InfoProvider (meaning that it is contained completely in all value combinations of the characteristics) you must select from exactly one of the InfoProviders involved (otherwise the duplicated value is added incorrectly in the MultiProvider).
However, if 0SALES is stored as an actual value in one InfoProvider and as a planned value in another InfoProvider so that there is no overlap between the data records (in other words, sales are divided separately between several InfoProviders) then it makes sense to make a selection across several InfoProviders.
Identification defines where the object has to get the data.
When you create a query against MP ,each object gets the data from Infoproviders if check the identification only.
http://help.sap.com/saphelp_nw04/helpdata/en/52/1ddc37a3f57a07e10000009b38f889/frameset.htm
Hope this helps u..
Best Regards,
VVenkat.. -
Join issues with Multicube reports
I experts,
We have a Multicube M with a Real time cube A and Basic Cube B. Cube B was added to the Multicube recently.
Cube A contains Phasing data ( like Forecast) for Opportunities. See some eg records below.
Oppt PERIOD KF1
001 001 10
001 002 20
001 003 30
002 001 40
002 002 20
002 003 30.
Cube B containes Opportunities and Customer ( with Nav Attr). The Customer master data looks like below. Here both TYPE and GROUP are Nav attr of Customer.
Customer Type Grp
C1 T1 G1
C2 T2 G2
Cube B contains records as shown below
Oppt Customer KF2
001 C1 100
002 C2 300.
Now when we ran our Report on MultiCube, we expect to see below
Oppt Period Customer Type Grp KF1
001 001 C1 T1 G1 10
001 002 C1 T1 G1 20
001 003 C1 T1 G1 30
002 001 C2 T2 G2 40
002 002 C2 T2 G2 20
002 003 C2 T2 G2 30.
But in place Customer, Type, Grp, we get 'Not assinged" .
I have checked teh identification for all KFs and Chars, they are identified.
Can anyone help??
Thanks,
DVCan you check for the data inside the infoproviders in the cubes with the manage option. It possible when the grouping is not done properly. Check for the Master date entry of the customer. I dont think its because of the join issue..
Good Luck..
Sandhya -
Hi Friends,
I was face some Interview.
Please send answers to the questions?
How many data Fields and key fields we can create in DSO?
You can overwrite key fields or Data Fields?
Which up date we use in Delta queue extraction( v1 or v2 or v3)
Which message we get when transported request is failed?
what is the Structural difference between Infoucbe and DSO
Data Loading is taking huge time when we extract data from source system to BI system/ how to solve?(Before it took 3-4 Hours now data loading takes 4 days)What is the difference between Display Attribute and
Navigational Attribute? How to make display attribute and navigational
attribute?
How to load flat file data?
How to load Hierarchy file data?
What is HACR?
How to maintain HACR?
If any issue in HACR then how to resolve the issue?
What is Baby Cube?
Why we are creating Aggregates?
What is the use of Aggregates?
Is there
any particular field on that we can create Aggregates or we can maintain
Aggregate on any field?
What is
the different DSO available? And what is the difference between those DSO?
What is
replacement path?
What are
the extractor types?
• Application Specific
o BW Content FI, HR, CO, SAP CRM, LO Cockpit
o Customer-Generated Extractors
LIS, FI-SL, CO-PA
• Cross Application (Generic Extractors)
o DB View, InfoSet, Function Module
2. What are the steps involved in LO Extraction?
• The steps are:
o RSA5 Select the DataSources
o LBWE Maintain DataSources and Activate Extract Structures
o LBWG Delete Setup Tables
o 0LI*BW Setup tables
o RSA3 Check extraction and the data in Setup tables
o LBWQ Check the extraction queue
o LBWF Log for LO Extract Structures
o RSA7 BW Delta
Queue Monitor
3. How to create a connection with LIS InfoStructures?
• LBW0 Connecting LIS InfoStructures to BW
4. What is the difference between ODS and InfoCube and MultiProvider?
• ODS: Provides granular data, allows overwrite and data is in transparent
tables, ideal for drilldown and RRI.
• CUBE: Follows the star schema, we can only append data, ideal for primary
reporting.
• MultiProvider: Does not have physical data. It allows to access data from
different InfoProviders (Cube, ODS, InfoObject). It is also preferred for
reporting.
5. What are Start routines, Transfer routines and Update routines?
• Start Routines: The start routine is run for each DataPackage after the data
has been written to the PSA and before the transfer rules have been executed.
It allows complex computations for a key figure or a characteristic. It has no
return value. Its purpose is to execute preliminary calculations and to store
them in global DataStructures. This structure or table can be accessed in the
other routines. The entire DataPackage in the transfer structure format is used
as a parameter for the routine.
• Transfer / Update Routines: They are defined at the InfoObject level. It is
like the Start Routine. It is independent of the DataSource. We can use this to
define Global Data and Global Checks.
6. What is the difference between start routine and update routine, when, how
and why are they called?
• Start routine can be used to access InfoPackage while update routines are
used while updating the Data Targets.
7. What is the table that is used in start routines?
• Always the table structure will be the structure of an ODS or InfoCube. For
example if it is an ODS then active table structure will be the table.
8. Explain how you used Start routines in your project?
• Start routines are used for mass processing of records. In start routine all
the records of DataPackage is available for processing. So we can process all
these records together in start routine. In one of scenario, we wanted to apply
size % to the forecast data. For example if material M1 is forecasted to say
100 in May. Then after applying size %(Small 20%, Medium 40%, Large 20%, Extra
Large 20%), we wanted to have 4 records against one single record that is
coming in the info package. This is achieved in start routine.
9. What are Return Tables?
• When we want to return multiple records, instead of single value, we use the
return table in the Update Routine. Example: If we have total telephone expense
for a Cost Center, using a return table we can get
expense per employee.
10. How do start routine and return table synchronize with each other?
• Return table is used to return the Value following the execution of start
routine
11. What is the difference
between V1, V2 and V3 updates?
• V1 Update: It is a Synchronous update. Here the Statistics update is carried
out at the same time as the document update (in the application
tables).
• V2 Update: It is an Asynchronous update. Statistics update and the Document
update take place as different tasks.
o V1 & V2 don't need scheduling.
• Serialized V3 Update: The V3 collective update must be scheduled as a job
(via LBWE). Here, document data is collected in the order it was created and
transferred into the BW as a batch job. The transfer sequence may not be the
same as the order in which the data was created in all scenarios. V3 update
only processes the update data that is successfully processed with the V2
update.
12. What is compression?
• It is a process used to delete the Request IDs and this saves space.
13. What is Rollup?
• This is used to load new DataPackages (requests) into the InfoCube
aggregates. If we have not performed a rollup then the new InfoCube data will
not be available while reporting on the aggregate.
14. What is table partitioning and what are the benefits of partitioning in an
InfoCube?
• It is the method of dividing a table which would enable a quick reference.
SAP uses fact file partitioning to improve performance. We can partition only
at 0CALMONTH or 0FISCPER. Table partitioning helps to run the report faster as
data is stored in the relevant partitions. Also table maintenance becomes
easier. Oracle,
Informix, IBM DB2/390 supports table partitioning while SAP DB, Microsoft SQL
Server, IBM DB2/400 do not support table portioning.
15. How many extra partitions are created and why?
• Two partitions are created for date before the begin date and after the end
date.
16. What are the options available in transfer rule?
• InfoObject
• Constant
• Routine
• Formula
17. How would you optimize the dimensions?
• We should define as many dimensions as possible and we have to take care that
no single dimension crosses more than 20% of the fact table size.
18. What are Conversion Routines for units and currencies in the update rule?
• Using this option we can write ABAP
code for Units / Currencies conversion. If we enable this flag then unit of Key
Figure appears in the ABAP code as an additional parameter. For example, we can
convert units in Pounds to Kilos.
19. Can an InfoObject be an InfoProvider, how and why?
• Yes, when we want to report on Characteristics or Master Data. We have to
right click on the InfoArea and select "Insert characteristic as data
target". For example, we can make 0CUSTOMER as an InfoProvider and report
on it.
20. What is Open Hub Service?
• The Open Hub Service enables us to distribute data from an SAP BW system into
external Data Marts, analytical applications, and other applications. We can
ensure controlled distribution using several systems. The central object for
exporting data is the InfoSpoke. We can define the source and the target object
for the data. BW becomes a hub of an enterprise data warehouse.
The distribution of data becomes clear through central monitoring from the
distribution status in the BW system.
21. How do you transform Open
Hub Data?
• Using BADI we can transform Open Hub Data according to the destination
requirement.
22. What is ODS?
• Operational DataSource is used for detailed storage of data. We can overwrite
data in the ODS. The data is stored in transparent tables.
23. What are BW Statistics and what is its use?
• They are group of Business Content InfoCubes which are used to measure
performance for Query and Load Monitoring. It also shows the usage of
aggregates, OLAP and Warehouse management
http://www.ittestpapers.com/articles/713/3/SAP-BW-Interview-Questions---Part-A/Page3.html
Communication Structure and Transfer
rules
• Create and InfoPackage
• Load Data
25. What are the delta options available when you load from flat file?
• The 3 options for Delta Management with Flat Files:
o Full Upload
o New Status for Changed records (ODS Object only)
o Additive Delta (ODS Object & InfoCube)
Q) Under which menu path is the Test Workbench to be found, including in
earlier Releases?
The menu path is: Tools - ABAP Workbench - Test - Test Workbench.
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) Errors while monitoring process chains.
A) During data loading. Apart from them, in process chains you add so many
process types, for example after loading data into Info Cube, you rollup data
into aggregates, now this rolling up of data into aggregates is a process type
which you keep after the process type for loading data into Cube. This rolling
up into aggregates might fail.
Another one is after you load data into ODS, you activate ODS data (another
process type) this might also fail.
Q) In Monitor----- Details (Header/Status/Details) à Under Processing (data
packet): Everything OK à Context menu of Data Package 1 (1 Records): Everything
OK ---- Simulate update. (Here we can debug update rules or transfer rules.)
SM50 à Program/Mode à Program à Debugging & debug this work process.
Q) PSA Cleansing.
A) You know how to edit PSA. I don't think you can delete single records. You
have to delete entire PSA data for a request.
Q) Can we make a datasource to support delta.
A) If this is a custom (user-defined) datasource you can make the datasource
delta enabled. While creating datasource from RSO2, after entering datasource
name and pressing create, in the next screen there is one button at the top,
which says generic delta. If you want more details about this there is a
chapter in Extraction book, it's in last pages u find out.
Generic delta services: -
Supports delta extraction for generic extractors according to:
Time stamp
Calendar day
Numeric pointer, such as document number & counter
Only one of these attributes can be set as a delta attribute.
Delta extraction is supported for all generic extractors, such as tables/views,
SAP Query and function modules
The delta queue (RSA7) allows you to monitor the current status of the delta
attribute
Q) Workbooks, as a general rule, should be transported with the
role.
Here are a couple of scenarios:
1. If both the workbook and its role have been previously transported, then the
role does not need to be part of the transport.
2. If the role exists in both dev and the target system but the workbook has
never been transported, and then you have a choice of transporting the role
(recommended) or just the workbook. If only the workbook is transported, then
an additional step will have to be taken after import: Locate the WorkbookID
via Table RSRWBINDEXT (in Dev and verify the same exists in the target system)
and proceed to manually add it to the role in the target system via Transaction
Code PFCG -- ALWAYS use control c/control v copy/paste for manually adding!
3. If the role does not exist in the target system you should transport both
the role and workbook. Keep in mind that a workbook is an object unto itself
and has no dependencies on other objects. Thus, you do not receive an error
message from the transport of 'just a workbook' -- even though it may not be
visible, it will exist (verified via Table RSRWBINDEXT).
Overall, as a general rule, you should transport roles with workbooks.
Q) How much time does it take to extract 1 million (10 lackhs) of records into
an infocube?
A. This depends, if you have complex coding in update rules it will take longer
time, or else it will take less than 30 minutes.
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 not
sure.
Then 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) How do you measure the size of infocube?
A: In no of records.
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.
Flat file
datasources does not support 0recordmode in extraction.
x before, -after, n new, a add, d delete, r reverse
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. SOME DATA IS UPLOADED TWICE INTO INFOCUBE. HOW TO CORRECT IT?
A: But how is it possible? If you load it manually twice, then you can delete
it by requestID.
Q. CAN U ADD A NEW FIELD AT THE ODS LEVEL?
Sure you can. ODS is nothing but a table.
Q. CAN NUMBER OF DATASOURCES HAVE ONE INFOSOURCE?
A) Yes of course. For example, for loading text and hierarchies we use
different data sources but the same InfoSource.
Q. BRIEF THE DATAFLOW IN BW.
A) Data flows from transactional system to analytical system (BW). DataSources
on the transactional system needs to be replicated on BW side and attached to
infosource and update rules respectively.
Q. CURRENCY CONVERSIONS CAN BE WRITTEN IN UPDATE RULES. WHY NOT IN TRANSFER
RULES?
Q) WHAT IS PROCEDURE TO UPDATE DATA INTO DATA TARGETS?
FULL and DELTA.
Q) AS WE USE Sbwnn, sbiw1, sbiw2 for delta update in LIS THEN
WHAT IS THE PROCEDURE IN LO-COCKPIT?
No LIS in LO cockpit. We will have datasources and can be maintained (append
fields). Refer white paper
on LO-Cockpit extractions.
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) SIGNIFICANCE of ODS?
It holds granular data (detailed level).
Q) WHERE THE PSA DATA IS STORED?
In PSA table.
Q) WHAT IS DATA SIZE?
The volume of data one data target holds (in no. of records)
Q) Different types of INFOCUBES.
Basic, Virtual (remote, sap remote and multi)
Virtual Cube is used for example, if you consider railways reservation all the
information has to be updated online. For designing the Virtual cube you have
to write the function module that is linking to table, Virtual cube it is like
a the structure, when ever the table is updated the virtual cube will fetch the
data from table and display report Online... FYI.. you will get the information
: https://www.sdn.sap.com/sdn
/index.sdn and search for Designing Virtual Cube and you will get
a good material designing the Function Module
Q) INFOSET QUERY.
Can be made of ODS's and Characteristic InfoObjects with masterdata.
Q) IF THERE ARE 2 DATASOURCES HOW MANY TRANSFER STRUCTURES ARE THERE.
In R/3 or in BW? 2 in R/3 and 2 in BW
Q) ROUTINES?
Exist in the InfoObject, transfer routines, update routines and start routine
Q) BRIEF SOME STRUCTURES USED IN BEX.
Rows and Columns, you can create structures.
Q) WHAT ARE THE DIFFERENT VARIABLES USED IN BEX?
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) HOW MANY LEVELS YOU CAN GO IN REPORTING?
You can drill down to any level by using Navigational attributes and jump
targets.
Q) WHAT ARE INDEXES?
Indexes are data base indexes, which help in retrieving data fastly.
Q) DIFFERENCE BETWEEN 2.1 AND 3.X VERSIONS.
Help! Refer documentation
Q) IS IT NESSESARY TO INITIALIZE EACH TIME THE DELTA UPDATE IS USED?
No.
Q) WHAT IS THE SIGNIFICANCE OF KPI'S?
KPI's indicate the performance of a company. These are key figures
Q) AFTER THE DATA EXTRACTION
WHAT IS THE IMAGE POSITION.
After image (correct me if I am wrong)
Q) REPORTING AND RESTRICTIONS.
Help! Refer documentation.
Q) TOOLS USED FOR PERFORMANCE TUNING.
ST22, Number ranges, delete indexes before load. Etc
Q) PROCESS CHAINS: IF U has USED IT THEN HOW WILL U SCHEDULING DATA DAILY.
There should be some tool to run the job daily (SM37 jobs)
Q) AUTHORIZATIONS.
Profile generator
Q) WEB REPORTING.
What are you expecting??
Q) CAN CHARECTERSTIC INFOOBJECT CAN BE INFOPROVIDER.
Of course
Q) PROCEDURES OF REPORTING ON MULTICUBES
Refer help. What are you expecting? MultiCube works on Union condition
Q) EXPLAIN TRANPSORTATION OF OBJECTS?
Dev---àQ and Dev-------àP
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).
Q) How can I compare data in R/3 with data in a BW Cube after the daily delta
loads? Are there any standard procedures for checking them or matching the
number of records?
A) You can go to R/3 TCode RSA3 and run the extractor. It will give you the
number of records extracted. Then go to BW Monitor to check the number of
records in the PSA and check to see if it is the same & also in the monitor
header tab.
A) RSA3 is a simple extractor checker program that allows you to rule out
extracts problems in R/3. It is simple to use, but only really tells you if the
extractor works. Since records that get updated into Cubes/ODS structures are
controlled by Update Rules, you will not be able to determine what is in the
Cube compared to what is in the R/3 environment. You will need to compare
records on a 1:1 basis against records in R/3 transactions for the functional
area in question. I would recommend enlisting the help of the end user community
to assist since they presumably know the data.
To use RSA3, go to it and enter the extractor ex: 2LIS_02_HDR. Click execute
and you will see the record count, you can also go to display that data. You
are not modifying anything so what you do in RSA3 has no effect on data quality
afterwards. However, it will not tell you how many records should be expected
in BW for a given load. You have that information in the monitor RSMO during
and after data loads. From RSMO for a given load you can determine how many
records were passed through the transfer rules from R/3, how many targets were
updated, and how many records passed through the Update Rules. It also gives
you error messages from the PSA.
Q) Types of Transfer Rules?
A) Field to Field mapping, Constant, Variable & routine.
Q) Types of Update Rules?
A) (Check box), Return table
Q) Transfer Routine?
A) Routines, which we write in, transfer rules.
Q) Update Routine?
A) Routines, which we write in Update rules
Q) What is the difference between writing a routine in transfer rules and
writing a routine in update rules?
A) If you are using the same InfoSource to update data in more than one data
target its better u write in transfer rules because u can assign one InfoSource
to more than one data target & and what ever logic u write in update rules
it is specific to particular one data target.
Q) Routine with Return Table.
A) Update rules generally only have one return value. However, you can create a
routine in the tab strip key figure calculation, by choosing checkbox Return
table. The corresponding key figure routine then no longer has a return value,
but a return table. You can then generate as many key figure values, as you
like from one data record.
Q) Start routines?
A) Start routines u can write in both updates rules and transfer rules, suppose
you want to restrict (delete) some records based on conditions before getting
loaded into data targets, then you can specify this in update rules-start
routine.
Ex: - Delete Data_Package ani ante it will delete a record based on the
condition
Q) X & Y Tables?
X-table = A table to link material SIDs with SIDs for time-independent
navigation attributes.
Y-table = A table to link material SIDs with SIDS for time-dependent navigation
attributes.
There are four types of sid tables
X time independent navigational attributes sid tables
Y time dependent navigational attributes sid tables
H hierarchy sid tables
I hierarchy structure sid tables
Q) Filters & Restricted Key figures (real time example)
Restricted KF's u can have for an SD cube: billed quantity, billing value, no:
of billing documents as RKF's.
Q) Line-Item Dimension (give me an real time example)
Line-Item Dimension: Invoice no: or Doc no: is a real time example
Q) What does the number in the 'Total' column in Transaction RSA7 mean?
A) The 'Total' column displays the number of LUWs that were written in the
delta queue and that have not yet been confirmed. The number includes the LUWs
of the last delta request (for repetition of a delta request) and the LUWs for
the next delta request. A LUW only disappears from the RSA7 display when it has
been transferred to the BW System and a new delta request has been received
from the BW System.
Q) How to know in which table (SAP BW) contains Technical Name / Description
and creation data of a particular Reports. Reports that are created using BEx
Analyzer.
A) There is no such table in BW if you want to know such details while you are
opening a particular query press properties button you will come to know all
the details that you wanted.
You will find your information about technical names and description about
queries in the following tables. Directory of all reports (Table RSRREPDIR) and
Directory of the reporting component elements (Table RSZELTDIR) for workbooks
and the connections to queries check Where- used list for reports in workbooks
(Table RSRWORKBOOK) Titles of Excel Workbooks in InfoCatalog (Table
RSRWBINDEXT)
Q) What is a LUW in the delta queue?
A) A LUW from the point of view of the delta queue can be an individual
document, a group of documents from a collective run or a whole data packet of
an application
extractor.
Q) Why does the number in the 'Total' column in the overview screen of
Transaction RSA7 differ from the number of data records that is displayed when
you call the detail view?
A) The number on the overview screen corresponds to the total of LUWs (see also
first question) that were written to the qRFC queue and that have not yet been
confirmed. The detail screen displays the records contained in the LUWs. Both,
the records belonging to the previous delta request and the records that do not
meet the selection conditions of the preceding delta init requests are filtered
out. Thus, only the records that are ready for the next delta request are
displayed on the detail screen. In the detail screen of Transaction RSA7, a
possibly existing customer exit is not taken into account.
Q) Why does Transaction RSA7 still display LUWs on the overview screen after
successful delta loading?
A) Only when a new delta has been requested does the source system learn that
the previous delta was successfully loaded to the BW System. Then, the LUWs of
the previous delta may be confirmed (and also deleted). In the meantime, the
LUWs must be kept for a possible delta request repetition. In particular, the
number on the overview screen does not change when the first delta was loaded
to the BW System.
Q) Why are selections not taken into account when the delta queue is filled?
A) Filtering according to selections takes place when the system reads from the
delta queue. This is necessary for reasons of performance.
Q) Why is there a DataSource with '0' records in RSA7 if delta exists and has
also been loaded successfully?
It is most likely that this is a DataSource that does not send delta data to
the BW System via the delta queue but directly via the extractor (delta for
master data using ALE change pointers). Such a DataSource should not be
displayed in RSA7. This error is corrected with BW 2.0B Support Package 11.
Q) Do the entries in table ROIDOCPRMS have an impact on the performance of the
loading procedure from the delta queue?
A) The impact is limited. If performance problems are related to the loading
process from the delta queue, then refer to the application-specific notes (for
example in the CO-PA area, in the logistics cockpit area and so on).
Caution: As of Plug In 2000.2 patch 3 the entries in table ROIDOCPRMS are as
effective for the delta queue as for a full update. Please note, however, that
LUWs are not split during data loading for consistency reasons. This means that
when very large LUWs are written to the DeltaQueue, the actual package size may
differ considerably from the MAXSIZE and MAXLINES parameters.
Q) Why does it take so long to display the data in the delta queue (for example
approximately 2 hours)?
A) With Plug In 2001.1 the display was changed: the user has the option of
defining the amount of data to be displayed, to restrict it, to selectively
choose the number of a data record, to make a distinction between the 'actual'
delta data and the data intended for repetition and so on.
Q) What is the purpose of function 'Delete data and meta data in a queue' in
RSA7? What exactly is deleted?
A) You should act with extreme caution when you use the deletion function in
the delta queue. It is comparable to deleting an InitDelta in the BW System and
should preferably be executed there. You do not only delete all data of this
DataSource for the affected BW System, but also lose the entire information
concerning the delta initialization. Then you can only request new deltas after
another delta initialization.
When you delete the data, the LUWs kept in the qRFC queue for the corresponding
target system are confirmed. Physical deletion only takes place in the qRFC
outbound queue if there are no more references to the LUWs.
The deletion function is for example intended for a case where the BW System,
from which the delta initialization was originally executed, no longer exists
or can no longer be accessed.
Q) Why does it take so long to delete from the delta queue (for example half a
day)?
A) Import PlugIn 2000.2 patch 3. With this patch the performance during
deletion is considerably improved.
Q) Why is the delta queue not updated when you start the V3 update in the
logistics cockpit area?
A) It is most likely that a delta initialization had not yet run or that the
delta initialization was not successful. A successful delta initialization (the
corresponding request must have QM status 'green' in the BW System) is a
prerequisite for the application data being written in the delta queue.
Q) What is the relationship between RSA7 and the qRFC monitor (Transaction
SMQ1)?
A) The qRFC monitor basically displays the same data as RSA7. The internal
queue name must be used for selection on the initial screen of the qRFC
monitor. This is made up of the prefix 'BW, the client and the short name of
the DataSource. For DataSources whose name are 19 characters long or shorter,
the short name corresponds to the name of the DataSource. For DataSources whose
name is longer than 19 characters (for delta-capable DataSources only possible
as of PlugIn 2001.1) the short name is assigned in table ROOSSHORTN.
In the qRFC monitor you cannot distinguish between repeatable and new LUWs.
Moreover, the data of a LUW is displayed in an unstructured manner there.
Q) Why are the data in the delta queue although the V3 update was not started?
A) Data was posted in background. Then, the records are updated directly in the
delta queue (RSA7). This happens in particular during automatic goods receipt
posting (MRRS). There is no duplicate transfer of records to the BW system. See
Note 417189.
Q) Why does button 'Repeatable' on the RSA7 data details screen not only show
data loaded into BW during the last delta but also data that were newly added,
i.e. 'pure' delta records?
A) Was programmed in a way that the request in repeat mode fetches both
actually repeatable (old) data and new data from the source system.
Q) I loaded several delta inits with various selections. For which one is the
delta loaded?
A) For delta, all selections made via delta inits are summed up. This means, a
delta for the 'total' of all delta initializations is loaded.
Q) How many selections for delta inits are possible in the system?
A) With simple selections (intervals without complicated join conditions or
single values), you can make up to about 100 delta inits. It should not be
more.
With complicated selection conditions, it should be only up to 10-20 delta
inits.
Reason: With many selection conditions that are joined in a complicated way,
too many 'where' lines are generated in the generated ABAP
source code that may exceed the memory limit.
Q) I intend to copy the source system, i.e. make a client copy. What will
happen with may delta? Should I initialize again after that?
A) Before you copy a source client or source system, make sure that your deltas
have been fetched from the DeltaQueue into BW and that no delta is pending.
After the client copy, an inconsistency might occur between BW delta tables and
the OLTP delta tables as described in Note 405943. After the client copy, Table
ROOSPRMSC will probably be empty in the OLTP since this table is
client-independent. After the system copy, the table will contain the entries
with the old logical system name that are no longer useful for further delta
loading from the new logical system. The delta must be initialized in any case
since delta depends on both the BW system and the source system. Even if no
dump 'MESSAGE_TYPE_X' occurs in BW when editing or creating an InfoPackage, you
should expect that the delta have to be initialized after the copy.
Q) Is it allowed in Transaction SMQ1 to use the functions for manual control of
processes?
A) Use SMQ1 as an instrument for diagnosis and control only. Make changes to BW
queues only after informing the BW Support or only if this is explicitly
requested in a note for component 'BC-BW' or 'BW-WHM-SAPI'.
Q) Despite of the delta request being started after completion of the
collective run (V3 update), it does not contain all documents. Only another
delta request loads the missing documents into BW. What is the cause for this
"splitting"?
A) The collective run submits the open V2 documents for processing to the task
handler, which processes them in one or several parallel update processes in an
asynchronous way. For this reason, plan a sufficiently large "safety time
window" between the end of the collective run in the source system and the
start of the delta request in BW. An alternative solution where this problem
does not occur is described in Note 505700.
Q) Despite my deleting the delta init, LUWs are still written into the
DeltaQueue?
A) In general, delta initializations and deletions of delta inits should always
be carried out at a time when no posting takes place. Otherwise, buffer
problems may occur: If a user started the internal mode at a time when the
delta initialization was still active, he/she posts data into the queue even
though the initialization had been deleted in the meantime. This is the case in
your system.
Q) In SMQ1 (qRFC Monitor) I have status 'NOSEND'. In the table TRFCQOUT, some
entries have the status 'READY', others 'RECORDED'. ARFCSSTATE is 'READ'. What
do these statuses mean? Which values in the field 'Status' mean what and which
values are correct and which are alarming? Are the statuses BW-specific or
generally valid in qRFC?
A) Table TRFCQOUT and ARFCSSTATE: Status READ means that the record was read
once either in a delta request or in a repetition of the delta request.
However, this does not mean that the record has successfully reached the BW
yet. The status READY in the TRFCQOUT and RECORDED in the ARFCSSTATE means that
the record has been written into the DeltaQueue and will be loaded into the BW
with the next delta request or a repetition of a delta. In any case only the
statuses READ, READY and RECORDED in both tables are considered to be valid.
The status EXECUTED in TRFCQOUT can occur temporarily. It is set before
starting a DeltaExtraction for all records with status READ present at that
time. The records with status EXECUTED are usually deleted from the queue in
packages within a delta request directly after setting the status before
extracting a new delta. If you see such records, it means that either a process
which is confirming and deleting records which have been loaded into the BW is
successfully running at the moment, or, if the records remain in the table for
a longer period of time with status EXECUTED, it is likely that there are
problems with deleting the records which have already been successfully been
loaded into the BW. In this state, no more deltas are loaded into the BW. Every
other status is an indicator for an error or an inconsistency. NOSEND in SMQ1
means nothing (see note 378903).
The value 'U' in field 'NOSEND' of table TRFCQOUT is discomforting.
Q) The extract structure was changed when the DeltaQueue was empty. Afterwards
new delta records were written to the DeltaQueue. When loading the delta into
the PSA, it shows that some fields were moved. The same result occurs when the
contents of the DeltaQueue are listed via the detail display. Why are the data
displayed differently? What can be done?
Make sure that the change of the extract structure is also reflected in the
database and that all servers are synchronized. We recommend to reset the
buffers using Transaction $SYNC. If the extract structure change is not
communicated synchronously to the server where delta records are being created,
the records are written with the old structure until the new structure has been
generated. This may have disastrous consequences for the delta.
When the problem occurs, the delta needs to be re-initialized.
Q) How and where can I control whether a repeat delta is requested?
A) Via the status of the last delta in the BW Request Monitor. If the request
is RED, the next load will be of type 'Repeat'. If you need to repeat the last
load for certain reasons, set the request in the monitor to red manually. For
the contents of the repeat see Question 14. Delta requests set to red despite
of data being already updated lead to duplicate records in a subsequent repeat,
if they have not been deleted from the data targets concerned before.
Q) As of PI 2003.1, the Logistic Cockpit offers various types of update
methods. Which update method is recommended in logistics? According to which
criteria should the decision be made? How can I choose an update method in
logistics?
See the recommendation in Note 505700.
Q) Are there particular recommendations regarding the data volume the
DeltaQueue may grow to without facing the danger of a read failure due to
memory problems?
A) There is no strict limit (except for the restricted number range of the
24-digit QCOUNT counter in the LUW management table - which is of no practical
importance, however - or the restrictions regarding the volume and number of
records in a database table).
When estimating "smooth" limits, both the number of LUWs is important
and the average data volume per LUW. As a rule, we recommend to bundle data
(usually documents) already when writing to the DeltaQueue to keep number of
LUWs small (partly this can be set in the applications, e.g. in the Logistics
Cockpit). The data volume of a single LUW should not be considerably larger
than 10% of the memory available to the work process for data extraction
(in a 32-bit architecture with a memory volume of about 1GByte per work
process, 100 Mbytes per LUW should not be exceeded). That limit is of rather
small practical importance as well since a comparable limit already applies
when writing to the DeltaQueue. If the limit is observed, correct reading is
guaranteed in most cases.
If the number of LUWs cannot be reduced by bundling application transactions,
you should at least make sure that the data are fetched from all connected BWs
as quickly as possible. But for other, BW-specific, reasons, the frequency
should not be higher than one DeltaRequest per hour.
To avoid memory problems, a program-internal limit ensures that never more than
1 million LUWs are read and fetched from the database per DeltaRequest. If this
limit is reached within a request, the DeltaQueue must be emptied by several
successive DeltaRequests. We recommend, however, to try not to reach that limit
but trigger the fetching of data from the connected BWs already when the number
of LUWs reaches a 5-digit value.
Q) I would like to display the date the data was uploaded on the
report. Usually, we load the transactional data nightly. Is there any easy way
to include this information on the report for users? So that they know the
validity of the report.
A) If I understand your requirement correctly, you want to display the date on
which data was loaded into the data target from which the report is being
executed. If it is so, configure your workbook to display the text elements in
the report. This displays the relevance of data field, which is the date on which
the data load has taken place.
Q) Can we filter the fields at Transfer Structure?
Q) Can we load data directly into infoobject with out extraction is it
possible.
Yes. We can copy from other infoobject if it is same. We load data from PSA if
it is already in PSA.
Q) HOW MANY DAYS CAN WE KEEP THE DATA IN PSA, IF WE R SHEDULED DAILY, WEEKLY
AND MONTHLY.
a) We can set the time.
Q) HOW CAN U GET THE DATA FROM CLIENT IF U R WORKING ON OFFSHORE PROJECTS.
THROUGH WHICH NETWORK.
a) VPN…………….Virtual
Private Network, VPN is nothing but one sort of network
where we can connect to the client systems sitting in offshore through RAS
(Remote access server).
Q) HOW CAN U ANALIZE THE PROJECT AT FIRST?
Prepare Project Plan and Environment
Define Project Management
Standards and
Procedures
Define Implementation Standards and Procedures
Testing & Go-live + supporting.
Q) THERE is one ODS AND 4 INFOCUBES. WE SEND DATA AT TIME TO ALL CUBES IF ONE
CUBE GOT LOCK ERROR. HOW CAN U RECTIFY THE ERROR?
Go to TCode sm66 then see which one is locked select that pid from there and
goto sm12
TCode then unlock it this is happened when lock errors are occurred when u
scheduled.
Q) Can anybody tell me how to add a navigational attribute in the BEx report in
the rows?
A) Expand dimension under left side panel (that is infocube panel) select than
navigational attributes drag and drop under rows panel.
Q) IF ANY TRASACTION CODE LIKE SMPT OR STMT.
In current systems (BW 3.0B and R/3 4.6B) these Tcodes don't exist!
Q) WHAT IS TRANSACTIONAL CUBE?
A) Transactional InfoCubes differ from standard InfoCubes in that the former
have an improved write access performance level. Standard InfoCubes are
technically optimized for read-only access and for a comparatively small number
of simultaneous accesses. Instead, the transactional InfoCube was developed to
meet the demands of SAP Strategic Enterprise Management (SEM), meaning that,
data is written to the InfoCube (possibly by several users at the same time)
and re-read as soon as possible. Standard Basic cubes are not suitable for
this.
Q) Is there any way to delete cube contents within update rules from an ODS
data source? The reason for this would be to delete (or zero out) a cube record
in an "Open Order" cube if the open order quantity was 0.
I've tried using the 0recordmode but that doesn't work. Also, would it
be easier to write a program that would be run after the load and delete
the records with a zero open qty?
A) START routine for update rules u can write ABAP code.
A) Yap, you can do it. Create a start routine in Update rule.
It is not "Deleting cube contents with update rules" It is only
possible to avoid that some content is updated into the InfoCube using the
start routine. Loop at all the records and delete the record that has the
condition. "If the open order quantity was 0" You have to think also
in before and after images in case of a delta upload. In that case you may
delete the change record and keep the old and after the change the wrong
information.
Q) I am not able to access a node in hierarchy directly using variables for
reports. When I am using Tcode RSZV it is giving a message that it doesn't
exist in BW 3.0 and it is embedded in BEx. Can any one tell me the other
options to get the same functionality in BEx?
A) Tcode RSZV is used in the earlier version of 3.0B only. From 3.0B onwards,
it's possible in the Query Designer (BEx) itself. Just right click on the
InfoObject for which you want to use as variables and precede further selecting
variable type and proce -
Useful Interview Questions and Answere
Hi All
Some of the Real time question.
Q) Under which menu path is the Test Workbench to be found, including in earlier Releases?
The menu path is: Tools - ABAP Workbench - Test - Test Workbench.
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) Errors while monitoring process chains.
A) During data loading. Apart from them, in process chains you add so many process types, for example after loading data into Info Cube, you rollup data into aggregates, now this rolling up of data into aggregates is a process type which you keep after the process type for loading data into Cube. This rolling up into aggregates might fail.
Another one is after you load data into ODS, you activate ODS data (another process type) this might also fail.
Q) In Monitor----- Details (Header/Status/Details) à Under Processing (data packet): Everything OK à Context menu of Data Package 1 (1 Records): Everything OK -
Simulate update. (Here we can debug update rules or transfer rules.)
SM50 à Program/Mode à Program à Debugging & debug this work process.
Q) PSA Cleansing.
A) You know how to edit PSA. I don't think you can delete single records. You have to delete entire PSA data for a request.
Q) Can we make a datasource to support delta.
A) If this is a custom (user-defined) datasource you can make the datasource delta enabled. While creating datasource from RSO2, after entering datasource name and pressing create, in the next screen there is one button at the top, which says generic delta. If you want more details about this there is a chapter in Extraction book, it's in last pages u find out.
Generic delta services: -
Supports delta extraction for generic extractors according to:
Time stamp
Calendar day
Numeric pointer, such as document number & counter
Only one of these attributes can be set as a delta attribute.
Delta extraction is supported for all generic extractors, such as tables/views, SAP Query and function modules
The delta queue (RSA7) allows you to monitor the current status of the delta attribute
Q) Workbooks, as a general rule, should be transported with the role.
Here are a couple of scenarios:
1. If both the workbook and its role have been previously transported, then the role does not need to be part of the transport.
2. If the role exists in both dev and the target system but the workbook has never been transported, and then you have a choice of transporting the role (recommended) or just the workbook. If only the workbook is transported, then an additional step will have to be taken after import: Locate the WorkbookID via Table RSRWBINDEXT (in Dev and verify the same exists in the target system) and proceed to manually add it to the role in the target system via Transaction Code PFCG -- ALWAYS use control c/control v copy/paste for manually adding!
3. If the role does not exist in the target system you should transport both the role and workbook. Keep in mind that a workbook is an object unto itself and has no dependencies on other objects. Thus, you do not receive an error message from the transport of 'just a workbook' -- even though it may not be visible, it will exist (verified via Table RSRWBINDEXT).
Overall, as a general rule, you should transport roles with workbooks.
Q) How much time does it take to extract 1 million (10 lackhs) of records into an infocube?
A. This depends, if you have complex coding in update rules it will take longer time, or else it will take less than 30 minutes.
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 not sure.
Then 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) How do you measure the size of infocube?
A: In no of records.
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.
Flat file datasources does not support 0recordmode in extraction.
x before, -after, n new, a add, d delete, r reverse
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. SOME DATA IS UPLOADED TWICE INTO INFOCUBE. HOW TO CORRECT IT?
A: But how is it possible? If you load it manually twice, then you can delete it by requestID.
Q. CAN U ADD A NEW FIELD AT THE ODS LEVEL?
Sure you can. ODS is nothing but a table.
Q. CAN NUMBER OF DATASOURCES HAVE ONE INFOSOURCE?
A) Yes of course. For example, for loading text and hierarchies we use different data sources but the same InfoSource.
Q. BRIEF THE DATAFLOW IN BW.
A) Data flows from transactional system to analytical system (BW). DataSources on the transactional system needs to be replicated on BW side and attached to infosource and update rules respectively.
Q. CURRENCY CONVERSIONS CAN BE WRITTEN IN UPDATE RULES. WHY NOT IN TRANSFER RULES?
Q) WHAT IS PROCEDURE TO UPDATE DATA INTO DATA TARGETS?
FULL and DELTA.
Q) AS WE USE Sbwnn, sbiw1, sbiw2 for delta update in LIS THEN WHAT IS THE PROCEDURE IN LO-COCKPIT?
No LIS in LO cockpit. We will have datasources and can be maintained (append fields). Refer white paper on LO-Cockpit extractions.
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) SIGNIFICANCE of ODS?
It holds granular data (detailed level).
Q) WHERE THE PSA DATA IS STORED?
In PSA table.
Q) WHAT IS DATA SIZE?
The volume of data one data target holds (in no. of records)
Q) Different types of INFOCUBES.
Basic, Virtual (remote, sap remote and multi)
Virtual Cube is used for example, if you consider railways reservation all the information has to be updated online. For designing the Virtual cube you have to write the function module that is linking to table, Virtual cube it is like a the structure, when ever the table is updated the virtual cube will fetch the data from table and display report Online... FYI.. you will get the information : https://www.sdn.sap.com/sdn/index.sdn and search for Designing Virtual Cube and you will get a good material designing the Function Module
Q) INFOSET QUERY.
Can be made of ODS's and Characteristic InfoObjects with masterdata.
Q) IF THERE ARE 2 DATASOURCES HOW MANY TRANSFER STRUCTURES ARE THERE.
In R/3 or in BW? 2 in R/3 and 2 in BW
Q) ROUTINES?
Exist in the InfoObject, transfer routines, update routines and start routine
Q) BRIEF SOME STRUCTURES USED IN BEX.
Rows and Columns, you can create structures.
Q) WHAT ARE THE DIFFERENT VARIABLES USED IN BEX?
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) HOW MANY LEVELS YOU CAN GO IN REPORTING?
You can drill down to any level by using Navigational attributes and jump targets.
Q) WHAT ARE INDEXES?
Indexes are data base indexes, which help in retrieving data fastly.
Q) DIFFERENCE BETWEEN 2.1 AND 3.X VERSIONS.
Help! Refer documentation
Q) IS IT NESSESARY TO INITIALIZE EACH TIME THE DELTA UPDATE IS USED?
No.
Q) WHAT IS THE SIGNIFICANCE OF KPI'S?
KPI's indicate the performance of a company. These are key figures
Q) AFTER THE DATA EXTRACTION WHAT IS THE IMAGE POSITION.
After image (correct me if I am wrong)
Q) REPORTING AND RESTRICTIONS.
Help! Refer documentation.
Q) TOOLS USED FOR PERFORMANCE TUNING.
ST22, Number ranges, delete indexes before load. Etc
Q) PROCESS CHAINS: IF U has USED IT THEN HOW WILL U SCHEDULING DATA DAILY.
There should be some tool to run the job daily (SM37 jobs)
Q) AUTHORIZATIONS.
Profile generator
Q) WEB REPORTING.
What are you expecting??
Q) CAN CHARECTERSTIC INFOOBJECT CAN BE INFOPROVIDER.
Of course
Q) PROCEDURES OF REPORTING ON MULTICUBES
Refer help. What are you expecting? MultiCube works on Union condition
Q) EXPLAIN TRANPSORTATION OF OBJECTS?
Dev-àQ and Dev-----àP
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 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).
Q) How can I compare data in R/3 with data in a BW Cube after the daily delta loads? Are there any standard procedures for checking them or matching the number of records?
A) You can go to R/3 TCode RSA3 and run the extractor. It will give you the number of records extracted. Then go to BW Monitor to check the number of records in the PSA and check to see if it is the same & also in the monitor header tab.
A) RSA3 is a simple extractor checker program that allows you to rule out extracts problems in R/3. It is simple to use, but only really tells you if the extractor works. Since records that get updated into Cubes/ODS structures are controlled by Update Rules, you will not be able to determine what is in the Cube compared to what is in the R/3 environment. You will need to compare records on a 1:1 basis against records in R/3 transactions for the functional area in question. I would recommend enlisting the help of the end user community to assist since they presumably know the data.
To use RSA3, go to it and enter the extractor ex: 2LIS_02_HDR. Click execute and you will see the record count, you can also go to display that data. You are not modifying anything so what you do in RSA3 has no effect on data quality afterwards. However, it will not tell you how many records should be expected in BW for a given load. You have that information in the monitor RSMO during and after data loads. From RSMO for a given load you can determine how many records were passed through the transfer rules from R/3, how many targets were updated, and how many records passed through the Update Rules. It also gives you error messages from the PSA.
Q) Types of Transfer Rules?
A) Field to Field mapping, Constant, Variable & routine.
Q) Types of Update Rules?
A) (Check box), Return table
Q) Transfer Routine?
A) Routines, which we write in, transfer rules.
Q) Update Routine?
A) Routines, which we write in Update rules
Q) What is the difference between writing a routine in transfer rules and writing a routine in update rules?
A) If you are using the same InfoSource to update data in more than one data target its better u write in transfer rules because u can assign one InfoSource to more than one data target & and what ever logic u write in update rules it is specific to particular one data target.
Q) Routine with Return Table.
A) Update rules generally only have one return value. However, you can create a routine in the tab strip key figure calculation, by choosing checkbox Return table. The corresponding key figure routine then no longer has a return value, but a return table. You can then generate as many key figure values, as you like from one data record.
Q) Start routines?
A) Start routines u can write in both updates rules and transfer rules, suppose you want to restrict (delete) some records based on conditions before getting loaded into data targets, then you can specify this in update rules-start routine.
Ex: - Delete Data_Package ani ante it will delete a record based on the condition
Q) X & Y Tables?
X-table = A table to link material SIDs with SIDs for time-independent navigation attributes.
Y-table = A table to link material SIDs with SIDS for time-dependent navigation attributes.
There are four types of sid tables
X time independent navigational attributes sid tables
Y time dependent navigational attributes sid tables
H hierarchy sid tables
I hierarchy structure sid tables
Q) Filters & Restricted Key figures (real time example)
Restricted KF's u can have for an SD cube: billed quantity, billing value, no: of billing documents as RKF's.
Q) Line-Item Dimension (give me an real time example)
Line-Item Dimension: Invoice no: or Doc no: is a real time example
Q) What does the number in the 'Total' column in Transaction RSA7 mean?
A) The 'Total' column displays the number of LUWs that were written in the delta queue and that have not yet been confirmed. The number includes the LUWs of the last delta request (for repetition of a delta request) and the LUWs for the next delta request. A LUW only disappears from the RSA7 display when it has been transferred to the BW System and a new delta request has been received from the BW System.
Q) How to know in which table (SAP BW) contains Technical Name / Description and creation data of a particular Reports. Reports that are created using BEx Analyzer.
A) There is no such table in BW if you want to know such details while you are opening a particular query press properties button you will come to know all the details that you wanted.
You will find your information about technical names and description about queries in the following tables. Directory of all reports (Table RSRREPDIR) and Directory of the reporting component elements (Table RSZELTDIR) for workbooks and the connections to queries check Where- used list for reports in workbooks (Table RSRWORKBOOK) Titles of Excel Workbooks in InfoCatalog (Table RSRWBINDEXT)
Q) What is a LUW in the delta queue?
A) A LUW from the point of view of the delta queue can be an individual document, a group of documents from a collective run or a whole data packet of an application extractor.
Q) Why does the number in the 'Total' column in the overview screen of Transaction RSA7 differ from the number of data records that is displayed when you call the detail view?
A) The number on the overview screen corresponds to the total of LUWs (see also first question) that were written to the qRFC queue and that have not yet been confirmed. The detail screen displays the records contained in the LUWs. Both, the records belonging to the previous delta request and the records that do not meet the selection conditions of the preceding delta init requests are filtered out. Thus, only the records that are ready for the next delta request are displayed on the detail screen. In the detail screen of Transaction RSA7, a possibly existing customer exit is not taken into account.
Q) Why does Transaction RSA7 still display LUWs on the overview screen after successful delta loading?
A) Only when a new delta has been requested does the source system learn that the previous delta was successfully loaded to the BW System. Then, the LUWs of the previous delta may be confirmed (and also deleted). In the meantime, the LUWs must be kept for a possible delta request repetition. In particular, the number on the overview screen does not change when the first delta was loaded to the BW System.
Q) Why are selections not taken into account when the delta queue is filled?
A) Filtering according to selections takes place when the system reads from the delta queue. This is necessary for reasons of performance.
Q) Why is there a DataSource with '0' records in RSA7 if delta exists and has also been loaded successfully?
It is most likely that this is a DataSource that does not send delta data to the BW System via the delta queue but directly via the extractor (delta for master data using ALE change pointers). Such a DataSource should not be displayed in RSA7. This error is corrected with BW 2.0B Support Package 11.
Q) Do the entries in table ROIDOCPRMS have an impact on the performance of the loading procedure from the delta queue?
A) The impact is limited. If performance problems are related to the loading process from the delta queue, then refer to the application-specific notes (for example in the CO-PA area, in the logistics cockpit area and so on).
Caution: As of Plug In 2000.2 patch 3 the entries in table ROIDOCPRMS are as effective for the delta queue as for a full update. Please note, however, that LUWs are not split during data loading for consistency reasons. This means that when very large LUWs are written to the DeltaQueue, the actual package size may differ considerably from the MAXSIZE and MAXLINES parameters.
Q) Why does it take so long to display the data in the delta queue (for example approximately 2 hours)?
A) With Plug In 2001.1 the display was changed: the user has the option of defining the amount of data to be displayed, to restrict it, to selectively choose the number of a data record, to make a distinction between the 'actual' delta data and the data intended for repetition and so on.
Q) What is the purpose of function 'Delete data and meta data in a queue' in RSA7? What exactly is deleted?
A) You should act with extreme caution when you use the deletion function in the delta queue. It is comparable to deleting an InitDelta in the BW System and should preferably be executed there. You do not only delete all data of this DataSource for the affected BW System, but also lose the entire information concerning the delta initialization. Then you can only request new deltas after another delta initialization.
When you delete the data, the LUWs kept in the qRFC queue for the corresponding target system are confirmed. Physical deletion only takes place in the qRFC outbound queue if there are no more references to the LUWs.
The deletion function is for example intended for a case where the BW System, from which the delta initialization was originally executed, no longer exists or can no longer be accessed.
Q) Why does it take so long to delete from the delta queue (for example half a day)?
A) Import PlugIn 2000.2 patch 3. With this patch the performance during deletion is considerably improved.
Q) Why is the delta queue not updated when you start the V3 update in the logistics cockpit area?
A) It is most likely that a delta initialization had not yet run or that the delta initialization was not successful. A successful delta initialization (the corresponding request must have QM status 'green' in the BW System) is a prerequisite for the application data being written in the delta queue.
Q) What is the relationship between RSA7 and the qRFC monitor (Transaction SMQ1)?
A) The qRFC monitor basically displays the same data as RSA7. The internal queue name must be used for selection on the initial screen of the qRFC monitor. This is made up of the prefix 'BW, the client and the short name of the DataSource. For DataSources whose name are 19 characters long or shorter, the short name corresponds to the name of the DataSource. For DataSources whose name is longer than 19 characters (for delta-capable DataSources only possible as of PlugIn 2001.1) the short name is assigned in table ROOSSHORTN.
In the qRFC monitor you cannot distinguish between repeatable and new LUWs. Moreover, the data of a LUW is displayed in an unstructured manner there.
Q) Why are the data in the delta queue although the V3 update was not started?
A) Data was posted in background. Then, the records are updated directly in the delta queue (RSA7). This happens in particular during automatic goods receipt posting (MRRS). There is no duplicate transfer of records to the BW system. See Note 417189.
Q) Why does button 'Repeatable' on the RSA7 data details screen not only show data loaded into BW during the last delta but also data that were newly added, i.e. 'pure' delta records?
A) Was programmed in a way that the request in repeat mode fetches both actually repeatable (old) data and new data from the source system.
Q) I loaded several delta inits with various selections. For which one is the delta loaded?
A) For delta, all selections made via delta inits are summed up. This means, a delta for the 'total' of all delta initializations is loaded.
Q) How many selections for delta inits are possible in the system?
A) With simple selections (intervals without complicated join conditions or single values), you can make up to about 100 delta inits. It should not be more.
With complicated selection conditions, it should be only up to 10-20 delta inits.
Reason: With many selection conditions that are joined in a complicated way, too many 'where' lines are generated in the generated ABAP source code that may exceed the memory limit.
Q) I intend to copy the source system, i.e. make a client copy. What will happen with may delta? Should I initialize again after that?
A) Before you copy a source client or source system, make sure that your deltas have been fetched from the DeltaQueue into BW and that no delta is pending. After the client copy, an inconsistency might occur between BW delta tables and the OLTP delta tables as described in Note 405943. After the client copy, Table ROOSPRMSC will probably be empty in the OLTP since this table is client-independent. After the system copy, the table will contain the entries with the old logical system name that are no longer useful for further delta loading from the new logical system. The delta must be initialized in any case since delta depends on both the BW system and the source system. Even if no dump 'MESSAGE_TYPE_X' occurs in BW when editing or creating an InfoPackage, you should expect that the delta have to be initialized after the copy.
Q) Is it allowed in Transaction SMQ1 to use the functions for manual control of processes?
A) Use SMQ1 as an instrument for diagnosis and control only. Make changes to BW queues only after informing the BW Support or only if this is explicitly requested in a note for component 'BC-BW' or 'BW-WHM-SAPI'.
Q) Despite of the delta request being started after completion of the collective run (V3 update), it does not contain all documents. Only another delta request loads the missing documents into BW. What is the cause for this "splitting"?
A) The collective run submits the open V2 documents for processing to the task handler, which processes them in one or several parallel update processes in an asynchronous way. For this reason, plan a sufficiently large "safety time window" between the end of the collective run in the source system and the start of the delta request in BW. An alternative solution where this problem does not occur is described in Note 505700.
Q) Despite my deleting the delta init, LUWs are still written into the DeltaQueue?
A) In general, delta initializations and deletions of delta inits should always be carried out at a time when no posting takes place. Otherwise, buffer problems may occur: If a user started the internal mode at a time when the delta initialization was still active, he/she posts data into the queue even though the initialization had been deleted in the meantime. This is the case in your system.
Q) In SMQ1 (qRFC Monitor) I have status 'NOSEND'. In the table TRFCQOUT, some entries have the status 'READY', others 'RECORDED'. ARFCSSTATE is 'READ'. What do these statuses mean? Which values in the field 'Status' mean what and which values are correct and which are alarming? Are the statuses BW-specific or generally valid in qRFC?
A) Table TRFCQOUT and ARFCSSTATE: Status READ means that the record was read once either in a delta request or in a repetition of the delta request. However, this does not mean that the record has successfully reached the BW yet. The status READY in the TRFCQOUT and RECORDED in the ARFCSSTATE means that the record has been written into the DeltaQueue and will be loaded into the BW with the next delta request or a repetition of a delta. In any case only the statuses READ, READY and RECORDED in both tables are considered to be valid. The status EXECUTED in TRFCQOUT can occur temporarily. It is set before starting a DeltaExtraction for all records with status READ present at that time. The records with status EXECUTED are usually deleted from the queue in packages within a delta request directly after setting the status before extracting a new delta. If you see such records, it means that either a process which is confirming and deleting records which have been loaded into the BW is successfully running at the moment, or, if the records remain in the table for a longer period of time with status EXECUTED, it is likely that there are problems with deleting the records which have already been successfully been loaded into the BW. In this state, no more deltas are loaded into the BW. Every other status is an indicator for an error or an inconsistency. NOSEND in SMQ1 means nothing (see note 378903).
The value 'U' in field 'NOSEND' of table TRFCQOUT is discomforting.
Q) The extract structure was changed when the DeltaQueue was empty. Afterwards new delta records were written to the DeltaQueue. When loading the delta into the PSA, it shows that some fields were moved. The same result occurs when the contents of the DeltaQueue are listed via the detail display. Why are the data displayed differently? What can be done?
Make sure that the change of the extract structure is also reflected in the database and that all servers are synchronized. We recommend to reset the buffers using Transaction $SYNC. If the extract structure change is not communicated synchronously to the server where delta records are being created, the records are written with the old structure until the new structure has been generated. This may have disastrous consequences for the delta.
When the problem occurs, the delta needs to be re-initialized.
Q) How and where can I control whether a repeat delta is requested?
A) Via the status of the last delta in the BW Request Monitor. If the request is RED, the next load will be of type 'Repeat'. If you need to repeat the last load for certain reasons, set the request in the monitor to red manually. For the contents of the repeat see Question 14. Delta requests set to red despite of data being already updated lead to duplicate records in a subsequent repeat, if they have not been deleted from the data targets concerned before.
Q) As of PI 2003.1, the Logistic Cockpit offers various types of update methods. Which update method is recommended in logistics? According to which criteria should the decision be made? How can I choose an update method in logistics?
See the recommendation in Note 505700.
Q) Are there particular recommendations regarding the data volume the DeltaQueue may grow to without facing the danger of a read failure due to memory problems?
A) There is no strict limit (except for the restricted number range of the 24-digit QCOUNT counter in the LUW management table - which is of no practical importance, however - or the restrictions regarding the volume and number of records in a database table).
When estimating "smooth" limits, both the number of LUWs is important and the average data volume per LUW. As a rule, we recommend to bundle data (usually documents) already when writing to the DeltaQueue to keep number of LUWs small (partly this can be set in the applications, e.g. in the Logistics Cockpit). The data volume of a single LUW should not be considerably larger than 10% of the memory available to the work process for data extraction (in a 32-bit architecture with a memory volume of about 1GByte per work process, 100 Mbytes per LUW should not be exceeded). That limit is of rather small practical importance as well since a comparable limit already applies when writing to the DeltaQueue. If the limit is observed, correct reading is guaranteed in most cases.
If the number of LUWs cannot be reduced by bundling application transactions, you should at least make sure that the data are fetched from all connected BWs as quickly as possible. But for other, BW-specific, reasons, the frequency should not be higher than one DeltaRequest per hour.
To avoid memory problems, a program-internal limit ensures that never more than 1 million LUWs are read and fetched from the database per DeltaRequest. If this limit is reached within a request, the DeltaQueue must be emptied by several successive DeltaRequests. We recommend, however, to try not to reach that limit but trigger the fetching of data from the connected BWs already when the number of LUWs reaches a 5-digit value.
Q) I would like to display the date the data was uploaded on the report. Usually, we load the transactional data nightly. Is there any easy way to include this information on the report for users? So that they know the validity of the report.
A) If I understand your requirement correctly, you want to display the date on which data was loaded into the data target from which the report is being executed. If it is so, configure your workbook to display the text elements in the report. This displays the relevance of data field, which is the date on which the data load has taken place.
Q) Can we filter the fields at Transfer Structure?
Q) Can we load data directly into infoobject with out extraction is it possible.
Yes. We can copy from other infoobject if it is same. We load data from PSA if it is already in PSA.
Q) HOW MANY DAYS CAN WE KEEP THE DATA IN PSA, IF WE R SHEDULED DAILY, WEEKLY AND MONTHLY.
a) We can set the time.
Q) HOW CAN U GET THE DATA FROM CLIENT IF U R WORKING ON OFFSHORE PROJECTS. THROUGH WHICH NETWORK.
a) VPN .Virtual Private Network, VPN is nothing but one sort of network where we can connect to the client systems sitting in offshore through RAS (Remote access server).
Q) HOW CAN U ANALIZE THE PROJECT AT FIRST?
Prepare Project Plan and Environment
Define Project Management Standards and
Procedures
Define Implementation Standards and Procedures
Testing & Go-live + supporting.
Q) THERE is one ODS AND 4 INFOCUBES. WE SEND DATA AT TIME TO ALL CUBES IF ONE CUBE GOT LOCK ERROR. HOW CAN U RECTIFY THE ERROR?
Go to TCode sm66 then see which one is locked select that pid from there and goto sm12
TCode then unlock it this is happened when lock errors are occurred when u scheduled.
Q) Can anybody tell me how to add a navigational attribute in the BEx report in the rows?
A) Expand dimension under left side panel (that is infocube panel) select than navigational attributes drag and drop under rows panel.
Q) IF ANY TRASACTION CODE LIKE SMPT OR STMT.
In current systems (BW 3.0B and R/3 4.6B) these Tcodes don't exist!
Q) WHAT IS TRANSACTIONAL CUBE?
A) Transactional InfoCubes differ from standard InfoCubes in that the former have an improved write access performance level. Standard InfoCubes are technically optimized for read-only access and for a comparatively small number of simultaneous accesses. Instead, the transactional InfoCube was developed to meet the demands of SAP Strategic Enterprise Management (SEM), meaning that, data is written to the InfoCube (possibly by several users at the same time) and re-read as soon as possible. Standard Basic cubes are not suitable for this.
Q) Is there any way to delete cube contents within update rules from an ODS data source? The reason for this would be to delete (or zero out) a cube record in an "Open Order" cube if the open order quantity was 0.
I've tried using the 0recordmode but that doesn't work. Also, would it
be easier to write a program that would be run after the load and delete
the records with a zero open qty?
A) START routine for update rules u can write ABAP code.
A) Yap, you can do it. Create a start routine in Update rule.
It is not "Deleting cube contents with update rules" It is only possible to avoid that some content is updated into the InfoCube using the start routine. Loop at all the records and delete the record that has the condition. "If the open order quantity was 0" You have to think also in before and after images in case of a delta upload. In that case you may delete the change record and keep the old and after the change the wrong information.
Q) I am not able to access a node in hierarchy directly using variables for reports. When I am using Tcode RSZV it is giving a message that it doesn't exist in BW 3.0 and it is embedded in BEx. Can any one tell me the other options to get the same functionality in BEx?
A) Tcode RSZV is used in the earlier version of 3.0B only. From 3.0B onwards, it's possible in the Query Designer (BEx) itself. Just right click on the InfoObject for which you want to use as variables and precede further selecting variable type and processing types.
Q) Wondering how can I get the values, for an example, if I run a report for month range 01/2004 - 10/2004 then monthly value is actually divide by the number of months that I selected. Which variable should I use?
Q) Why is it every time I switch from Info Provider to InfoObject or from one item to another while in modeling I always get this message " Reading Data " or "constructing workbench" in it runs for minutes.... anyway to stop this?
Q) Can any one give me info on how the BW delta works also would like to know about 'before image and after image' am currently in a BW project and have to write start routines for delta load.
Q) I am very new to BW. I would like to clarify a doubt regarding Delta extractor. If I am correct, by using delta extractors the data that has already been scheduled will not be uploaded again. Say for a specific scenario, Sales. Now I have uploaded all the sales order created till yesterday into the cube. Now say I make changes to any of the open record, which was already uploaded. Now what happens when I schedule it again? Will the same record be uploaded again with the changes or will the changes get affected to the previous record.
A)
Q) In BW we need to write abap routines. I wish to know when and what type of abap routines we got to write. Also, are these routines written in update rules? I will be glad, if this is clarified with real-time scenarios and few examples?
A) Over here we write our routines in the start routines in the update rules or in the transfer structure (you can choose between writing them in the start routines or directly behind the different characteristics. In the transfer structure you just click on the yellow triangle behind a characteristic and choose "routine". In the update rules you can choose "start routine" or click on the triangle with the green square behind an individual characteristic. Usually we only use start routine when it does not concern one single characteristic (for example when you have to read the same table for 4 characteristics). I hope this helps.
We used ABAP Routines for example:
To convert to Uppercase (transfer structure)
To convert Values out of a third party tool with different keys into the same keys as our SAP System uses (transfer structure)
To select only a part of the data for from an infosource updating the InfoCube (Start Routine) etc.
Q) What is ODS?
A) An ODS object acts as a storage location for consolidated and cleaned-up transaction data (transaction data or master data, for example) on the document (atomic) level.
This data can be evaluated using a BEx query.
Standard ODS Object
Transactional ODS object:
The data is immediately available here for reporting. For implementation, compare with the Transactional ODS Object.
A transactional ODS object differs from a standard ODS object in the way it prepares data. In a standard ODS object, data is stored in different versions ((new) delta, active, (change log) modified), where as a transactional ODS object contains the data in a single version. Therefore, data is stored in precisely the same form in which it was written to the transactional ODS object by the application. In BW, you can use a transaction ODS object as a data target for an analysis process.
The transactional ODS object is also required by diverse applications, such as SAP Strategic Enterprise Management (SEM) for example, as well as other external applications.
Transactional ODS objects allow data to be available quickly. The data from this kind of ODS object is accessed transactionally, that is, data is written to the ODS object (possibly by several users at the same time) and reread as soon as possible.
It offers no replacement for the standard ODS object. Instead, an additional function displays those that can be used for special applications.
The transactional ODS object simply consists of a table for active data. It retrieves its data from external systems via fill- or delete- APIs. The loading process is not supported by the BW system. The advantage to the way it is structured is that data is easy to access. They are made available for reporting immediately after being loaded.
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) 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 )
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?Hi DST
This is a great effort and gesture. thank you on behalf of all the newbies.
PJ -
HI,
friends i need some FAQS for the interviews .
thanks and regards
shafeeq ahmedHi Shafeed,
Here are some questions and answers.
1)name the two table that providedetail information about data source
2)how and when can you control whether repeat delta is requested?
3)how can you improve the performance of aquery
4)how to prevent duplicate record in at the data target level
5)what is virtual cube?its significance
6)diff methods of generic datasource
7)how to connect anew data target to an existing data flow
8)what is partition
9) SAP batch process
10)how do you improve the info cube design preformance
12)is there any diff between repair run/repaire request.if yes then please tell me in detail
13)difference between process chain and infopackage group
diff between partition/aggregate
ANS--
1) Hi Santosh
Please find some of the answers here...
For Q 3) Query Performance can be improved by making the Aggregates having all the Chars & KF used in Query.
Q 5) Virtual Cube : InfoProvider with transaction data that is not stored in the object itself, but which is read directly for analysis and reporting purposes. The relevant data can be from the BI system or from other SAP or non-SAP systems.
VirtualProviders only allow read access to data.
Q 6) Diff Methods of Generic datasource using Transaction RSO2 :
a) Extraction from DB Table or View
b) Extraction from SAP Query
c) Extraction by Function Module
2) Important BW datasource relevant tables
ROOSOURCE: Table Header for SAP BW OLTP Sources
RODELTAM: BW Delta Process
ROOSFIELD: DataSource Fields
ROOSGEN: Generated Objects for OLTP Source, Last changed date and who etc.
3) For Q 8) i think you mean table partition
You use partition to improve performance. You can only partiton on 0CALMONTH or 0FISCPER
4) 1. ROOSOURCE
6. Generic Extarction using 1.Views 2. Infoset Queries , 3. Function modules
5) Hi Santosh
Pls note down the Q& ANS
Some of the Real time question.
Q) Under which menu path is the Test Workbench to be found, including in earlier Releases?
The menu path is: Tools - ABAP Workbench - Test - Test Workbench.
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) Errors while monitoring process chains.
A) During data loading. Apart from them, in process chains you add so many process types, for example after loading data into Info Cube, you rollup data into aggregates, now this rolling up of data into aggregates is a process type which you keep after the process type for loading data into Cube. This rolling up into aggregates might fail.
Another one is after you load data into ODS, you activate ODS data (another process type) this might also fail.
Q) In Monitor----- Details (Header/Status/Details) à Under Processing (data packet): Everything OK à Context menu of Data Package 1 (1 Records): Everything OK -
Simulate update. (Here we can debug update rules or transfer rules.)
SM50 à Program/Mode à Program à Debugging & debug this work process.
Q) PSA Cleansing.
A) You know how to edit PSA. I don't think you can delete single records. You have to delete entire PSA data for a request.
Q) Can we make a datasource to support delta.
A) If this is a custom (user-defined) datasource you can make the datasource delta enabled. While creating datasource from RSO2, after entering datasource name and pressing create, in the next screen there is one button at the top, which says generic delta. If you want more details about this there is a chapter in Extraction book, it's in last pages u find out.
Generic delta services: -
Supports delta extraction for generic extractors according to:
Time stamp
Calendar day
Numeric pointer, such as document number & counter
Only one of these attributes can be set as a delta attribute.
Delta extraction is supported for all generic extractors, such as tables/views, SAP Query and function modules
The delta queue (RSA7) allows you to monitor the current status of the delta attribute
Q) Workbooks, as a general rule, should be transported with the role.
Here are a couple of scenarios:
1. If both the workbook and its role have been previously transported, then the role does not need to be part of the transport.
2. If the role exists in both dev and the target system but the workbook has never been transported, and then you have a choice of transporting the role (recommended) or just the workbook. If only the workbook is transported, then an additional step will have to be taken after import: Locate the WorkbookID via Table RSRWBINDEXT (in Dev and verify the same exists in the target system) and proceed to manually add it to the role in the target system via Transaction Code PFCG -- ALWAYS use control c/control v copy/paste for manually adding!
3. If the role does not exist in the target system you should transport both the role and workbook. Keep in mind that a workbook is an object unto itself and has no dependencies on other objects. Thus, you do not receive an error message from the transport of 'just a workbook' -- even though it may not be visible, it will exist (verified via Table RSRWBINDEXT).
Overall, as a general rule, you should transport roles with workbooks.
Q) How much time does it take to extract 1 million (10 lackhs) of records into an infocube?
A. This depends, if you have complex coding in update rules it will take longer time, or else it will take less than 30 minutes.
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 not sure.
Then 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) How do you measure the size of infocube?
A: In no of records.
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.
Flat file datasources does not support 0recordmode in extraction.
x before, -after, n new, a add, d delete, r reverse
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. SOME DATA IS UPLOADED TWICE INTO INFOCUBE. HOW TO CORRECT IT?
A: But how is it possible? If you load it manually twice, then you can delete it by requestID.
Q. CAN U ADD A NEW FIELD AT THE ODS LEVEL?
Sure you can. ODS is nothing but a table.
Q. CAN NUMBER OF DATASOURCES HAVE ONE INFOSOURCE?
A) Yes of course. For example, for loading text and hierarchies we use different data sources but the same InfoSource.
Q. BRIEF THE DATAFLOW IN BW.
A) Data flows from transactional system to analytical system (BW). DataSources on the transactional system needs to be replicated on BW side and attached to infosource and update rules respectively.
Q. CURRENCY CONVERSIONS CAN BE WRITTEN IN UPDATE RULES. WHY NOT IN TRANSFER RULES?
Q) WHAT IS PROCEDURE TO UPDATE DATA INTO DATA TARGETS?
FULL and DELTA.
Q) AS WE USE Sbwnn, sbiw1, sbiw2 for delta update in LIS THEN WHAT IS THE PROCEDURE IN LO-COCKPIT?
No LIS in LO cockpit. We will have datasources and can be maintained (append fields). Refer white paper on LO-Cockpit extractions.
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) SIGNIFICANCE of ODS?
It holds granular data (detailed level).
Q) WHERE THE PSA DATA IS STORED?
In PSA table.
Q) WHAT IS DATA SIZE?
The volume of data one data target holds (in no. of records)
Q) Different types of INFOCUBES.
Basic, Virtual (remote, sap remote and multi)
Virtual Cube is used for example, if you consider railways reservation all the information has to be updated online. For designing the Virtual cube you have to write the function module that is linking to table, Virtual cube it is like a the structure, when ever the table is updated the virtual cube will fetch the data from table and display report Online... FYI.. you will get the information : https://www.sdn.sap.com/sdn/index.sdn and search for Designing Virtual Cube and you will get a good material designing the Function Module
Q) INFOSET QUERY.
Can be made of ODS's and Characteristic InfoObjects with masterdata.
Q) IF THERE ARE 2 DATASOURCES HOW MANY TRANSFER STRUCTURES ARE THERE.
In R/3 or in BW? 2 in R/3 and 2 in BW
Q) ROUTINES?
Exist in the InfoObject, transfer routines, update routines and start routine
Q) BRIEF SOME STRUCTURES USED IN BEX.
Rows and Columns, you can create structures.
Q) WHAT ARE THE DIFFERENT VARIABLES USED IN BEX?
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) HOW MANY LEVELS YOU CAN GO IN REPORTING?
You can drill down to any level by using Navigational attributes and jump targets.
Q) WHAT ARE INDEXES?
Indexes are data base indexes, which help in retrieving data fastly.
Q) DIFFERENCE BETWEEN 2.1 AND 3.X VERSIONS.
Help! Refer documentation
Q) IS IT NESSESARY TO INITIALIZE EACH TIME THE DELTA UPDATE IS USED?
No.
Q) WHAT IS THE SIGNIFICANCE OF KPI'S?
KPI's indicate the performance of a company. These are key figures
Q) AFTER THE DATA EXTRACTION WHAT IS THE IMAGE POSITION.
After image (correct me if I am wrong)
Q) REPORTING AND RESTRICTIONS.
Help! Refer documentation.
Q) TOOLS USED FOR PERFORMANCE TUNING.
ST22, Number ranges, delete indexes before load. Etc
Q) PROCESS CHAINS: IF U has USED IT THEN HOW WILL U SCHEDULING DATA DAILY.
There should be some tool to run the job daily (SM37 jobs)
Q) AUTHORIZATIONS.
Profile generator
Q) WEB REPORTING.
What are you expecting??
Q) CAN CHARECTERSTIC INFOOBJECT CAN BE INFOPROVIDER.
Of course
Q) PROCEDURES OF REPORTING ON MULTICUBES
Refer help. What are you expecting? MultiCube works on Union condition
Q) EXPLAIN TRANPSORTATION OF OBJECTS?
Dev-àQ and Dev-----àP
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 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).
Q) How can I compare data in R/3 with data in a BW Cube after the daily delta loads? Are there any standard procedures for checking them or matching the number of records?
A) You can go to R/3 TCode RSA3 and run the extractor. It will give you the number of records extracted. Then go to BW Monitor to check the number of records in the PSA and check to see if it is the same & also in the monitor header tab.
A) RSA3 is a simple extractor checker program that allows you to rule out extracts problems in R/3. It is simple to use, but only really tells you if the extractor works. Since records that get updated into Cubes/ODS structures are controlled by Update Rules, you will not be able to determine what is in the Cube compared to what is in the R/3 environment. You will need to compare records on a 1:1 basis against records in R/3 transactions for the functional area in question. I would recommend enlisting the help of the end user community to assist since they presumably know the data.
To use RSA3, go to it and enter the extractor ex: 2LIS_02_HDR. Click execute and you will see the record count, you can also go to display that data. You are not modifying anything so what you do in RSA3 has no effect on data quality afterwards. However, it will not tell you how many records should be expected in BW for a given load. You have that information in the monitor RSMO during and after data loads. From RSMO for a given load you can determine how many records were passed through the transfer rules from R/3, how many targets were updated, and how many records passed through the Update Rules. It also gives you error messages from the PSA.
Q) Types of Transfer Rules?
A) Field to Field mapping, Constant, Variable & routine.
Q) Types of Update Rules?
A) (Check box), Return table
Q) Transfer Routine?
A) Routines, which we write in, transfer rules.
Q) Update Routine?
A) Routines, which we write in Update rules
Q) What is the difference between writing a routine in transfer rules and writing a routine in update rules?
A) If you are using the same InfoSource to update data in more than one data target its better u write in transfer rules because u can assign one InfoSource to more than one data target & and what ever logic u write in update rules it is specific to particular one data target.
Q) Routine with Return Table.
A) Update rules generally only have one return value. However, you can create a routine in the tab strip key figure calculation, by choosing checkbox Return table. The corresponding key figure routine then no longer has a return value, but a return table. You can then generate as many key figure values, as you like from one data record.
Q) Start routines?
A) Start routines u can write in both updates rules and transfer rules, suppose you want to restrict (delete) some records based on conditions before getting loaded into data targets, then you can specify this in update rules-start routine.
Ex: - Delete Data_Package ani ante it will delete a record based on the condition
Q) X & Y Tables?
X-table = A table to link material SIDs with SIDs for time-independent navigation attributes.
Y-table = A table to link material SIDs with SIDS for time-dependent navigation attributes.
There are four types of sid tables
X time independent navigational attributes sid tables
Y time dependent navigational attributes sid tables
H hierarchy sid tables
I hierarchy structure sid tables
Q) Filters & Restricted Key figures (real time example)
Restricted KF's u can have for an SD cube: billed quantity, billing value, no: of billing documents as RKF's.
Q) Line-Item Dimension (give me an real time example)
Line-Item Dimension: Invoice no: or Doc no: is a real time example
Q) What does the number in the 'Total' column in Transaction RSA7 mean?
A) The 'Total' column displays the number of LUWs that were written in the delta queue and that have not yet been confirmed. The number includes the LUWs of the last delta request (for repetition of a delta request) and the LUWs for the next delta request. A LUW only disappears from the RSA7 display when it has been transferred to the BW System and a new delta request has been received from the BW System.
Q) How to know in which table (SAP BW) contains Technical Name / Description and creation data of a particular Reports. Reports that are created using BEx Analyzer.
A) There is no such table in BW if you want to know such details while you are opening a particular query press properties button you will come to know all the details that you wanted.
You will find your information about technical names and description about queries in the following tables. Directory of all reports (Table RSRREPDIR) and Directory of the reporting component elements (Table RSZELTDIR) for workbooks and the connections to queries check Where- used list for reports in workbooks (Table RSRWORKBOOK) Titles of Excel Workbooks in InfoCatalog (Table RSRWBINDEXT)
Q) What is a LUW in the delta queue?
A) A LUW from the point of view of the delta queue can be an individual document, a group of documents from a collective run or a whole data packet of an application extractor.
Q) Why does the number in the 'Total' column in the overview screen of Transaction RSA7 differ from the number of data records that is displayed when you call the detail view?
A) The number on the overview screen corresponds to the total of LUWs (see also first question) that were written to the qRFC queue and that have not yet been confirmed. The detail screen displays the records contained in the LUWs. Both, the records belonging to the previous delta request and the records that do not meet the selection conditions of the preceding delta init requests are filtered out. Thus, only the records that are ready for the next delta request are displayed on the detail screen. In the detail screen of Transaction RSA7, a possibly existing customer exit is not taken into account.
Q) Why does Transaction RSA7 still display LUWs on the overview screen after successful delta loading?
A) Only when a new delta has been requested does the source system learn that the previous delta was successfully loaded to the BW System. Then, the LUWs of the previous delta may be confirmed (and also deleted). In the meantime, the LUWs must be kept for a possible delta request repetition. In particular, the number on the overview screen does not change when the first delta was loaded to the BW System.
Q) Why are selections not taken into account when the delta queue is filled?
A) Filtering according to selections takes place when the system reads from the delta queue. This is necessary for reasons of performance.
Q) Why is there a DataSource with '0' records in RSA7 if delta exists and has also been loaded successfully?
It is most likely that this is a DataSource that does not send delta data to the BW System via the delta queue but directly via the extractor (delta for master data using ALE change pointers). Such a DataSource should not be displayed in RSA7. This error is corrected with BW 2.0B Support Package 11.
Q) Do the entries in table ROIDOCPRMS have an impact on the performance of the loading procedure from the delta queue?
A) The impact is limited. If performance problems are related to the loading process from the delta queue, then refer to the application-specific notes (for example in the CO-PA area, in the logistics cockpit area and so on).
Caution: As of Plug In 2000.2 patch 3 the entries in table ROIDOCPRMS are as effective for the delta queue as for a full update. Please note, however, that LUWs are not split during data loading for consistency reasons. This means that when very large LUWs are written to the DeltaQueue, the actual package size may differ considerably from the MAXSIZE and MAXLINES parameters.
Q) Why does it take so long to display the data in the delta queue (for example approximately 2 hours)?
A) With Plug In 2001.1 the display was changed: the user has the option of defining the amount of data to be displayed, to restrict it, to selectively choose the number of a data record, to make a distinction between the 'actual' delta data and the data intended for repetition and so on.
Q) What is the purpose of function 'Delete data and meta data in a queue' in RSA7? What exactly is deleted?
A) You should act with extreme caution when you use the deletion function in the delta queue. It is comparable to deleting an InitDelta in the BW System and should preferably be executed there. You do not only delete all data of this DataSource for the affected BW System, but also lose the entire information concerning the delta initialization. Then you can only request new deltas after another delta initialization.
When you delete the data, the LUWs kept in the qRFC queue for the corresponding target system are confirmed. Physical deletion only takes place in the qRFC outbound queue if there are no more references to the LUWs.
The deletion function is for example intended for a case where the BW System, from which the delta initialization was originally executed, no longer exists or can no longer be accessed.
Q) Why does it take so long to delete from the delta queue (for example half a day)?
A) Import PlugIn 2000.2 patch 3. With this patch the performance during deletion is considerably improved.
Q) Why is the delta queue not updated when you start the V3 update in the logistics cockpit area?
A) It is most likely that a delta initialization had not yet run or that the delta initialization was not successful. A successful delta initialization (the corresponding request must have QM status 'green' in the BW System) is a prerequisite for the application data being written in the delta queue.
Q) What is the relationship between RSA7 and the qRFC monitor (Transaction SMQ1)?
A) The qRFC monitor basically displays the same data as RSA7. The internal queue name must be used for selection on the initial screen of the qRFC monitor. This is made up of the prefix 'BW, the client and the short name of the DataSource. For DataSources whose name are 19 characters long or shorter, the short name corresponds to the name of the DataSource. For DataSources whose name is longer than 19 characters (for delta-capable DataSources only possible as of PlugIn 2001.1) the short name is assigned in table ROOSSHORTN.
In the qRFC monitor you cannot distinguish between repeatable and new LUWs. Moreover, the data of a LUW is displayed in an unstructured manner there.
Q) Why are the data in the delta queue although the V3 update was not started?
A) Data was posted in background. Then, the records are updated directly in the delta queue (RSA7). This happens in particular during automatic goods receipt posting (MRRS). There is no duplicate transfer of records to the BW system. See Note 417189.
Q) Why does button 'Repeatable' on the RSA7 data details screen not only show data loaded into BW during the last delta but also data that were newly added, i.e. 'pure' delta records?
A) Was programmed in a way that the request in repeat mode fetches both actually repeatable (old) data and new data from the source system.
Q) I loaded several delta inits with various selections. For which one is the delta loaded?
A) For delta, all selections made via delta inits are summed up. This means, a delta for the 'total' of all delta initializations is loaded.
Q) How many selections for delta inits are possible in the system?
A) With simple selections (intervals without complicated join conditions or single values), you can make up to about 100 delta inits. It should not be more.
With complicated selection conditions, it should be only up to 10-20 delta inits.
Reason: With many selection conditions that are joined in a complicated way, too many 'where' lines are generated in the generated ABAP source code that may exceed the memory limit.
Q) I intend to copy the source system, i.e. make a client copy. What will happen with may delta? Should I initialize again after that?
A) Before you copy a source client or source system, make sure that your deltas have been fetched from the DeltaQueue into BW and that no delta is pending. After the client copy, an inconsistency might occur between BW delta tables and the OLTP delta tables as described in Note 405943. After the client copy, Table ROOSPRMSC will probably be empty in the OLTP since this table is client-independent. After the system copy, the table will contain the entries with the old logical system name that are no longer useful for further delta loading from the new logical system. The delta must be initialized in any case since delta depends on both the BW system and the source system. Even if no dump 'MESSAGE_TYPE_X' occurs in BW when editing or creating an InfoPackage, you should expect that the delta have to be initialized after the copy.
Q) Is it allowed in Transaction SMQ1 to use the functions for manual control of processes?
A) Use SMQ1 as an instrument for diagnosis and control only. Make changes to BW queues only after informing the BW Support or only if this is explicitly requested in a note for component 'BC-BW' or 'BW-WHM-SAPI'.
Q) Despite of the delta request being started after completion of the collective run (V3 update), it does not contain all documents. Only another delta request loads the missing documents into BW. What is the cause for this "splitting"?
A) The collective run submits the open V2 documents for processing to the task handler, which processes them in one or several parallel update processes in an asynchronous way. For this reason, plan a sufficiently large "safety time window" between the end of the collective run in the source system and the start of the delta request in BW. An alternative solution where this problem does not occur is described in Note 505700.
Q) Despite my deleting the delta init, LUWs are still written into the DeltaQueue?
A) In general, delta initializations and deletions of delta inits should always be carried out at a time when no posting takes place. Otherwise, buffer problems may occur: If a user started the internal mode at a time when the delta initialization was still active, he/she posts data into the queue even though the initialization had been deleted in the meantime. This is the case in your system.
Q) In SMQ1 (qRFC Monitor) I have status 'NOSEND'. In the table TRFCQOUT, some entries have the status 'READY', others 'RECORDED'. ARFCSSTATE is 'READ'. What do these statuses mean? Which values in the field 'Status' mean what and which values are correct and which are alarming? Are the statuses BW-specific or generally valid in qRFC?
A) Table TRFCQOUT and ARFCSSTATE: Status READ means that the record was read once either in a delta request or in a repetition of the delta request. However, this does not mean that the record has successfully reached the BW yet. The status READY in the TRFCQOUT and RECORDED in the ARFCSSTATE means that the record has been written into the DeltaQueue and will be loaded into the BW with the next delta request or a repetition of a delta. In any case only the statuses READ, READY and RECORDED in both tables are considered to be valid. The status EXECUTED in TRFCQOUT can occur temporarily. It is set before starting a DeltaExtraction for all records with status READ present at that time. The records with status EXECUTED are usually deleted from the queue in packages within a delta request directly after setting the status before extracting a new delta. If you see such records, it means that either a process which is confirming and deleting records which have been loaded into the BW is successfully running at the moment, or, if the records remain in the table for a longer period of time with status EXECUTED, it is likely that there are problems with deleting the records which have already been successfully been loaded into the BW. In this state, no more deltas are loaded into the BW. Every other status is an indicator for an error or an inconsistency. NOSEND in SMQ1 means nothing (see note 378903).
The value 'U' in field 'NOSEND' of table TRFCQOUT is discomforting.
Q) The extract structure was changed when the DeltaQueue was empty. Afterwards new delta records were written to the DeltaQueue. When loading the delta into the PSA, it shows that some fields were moved. The same result occurs when the contents of the DeltaQueue are listed via the detail display. Why are the data displayed differently? What can be done?
Make sure that the change of the extract structure is also reflected in the database and that all servers are synchronized. We recommend to reset the buffers using Transaction $SYNC. If the extract structure change is not communicated synchronously to the server where delta records are being created, the records are written with the old structure until the new structure has been generated. This may have disastrous consequences for the delta.
When the problem occurs, the delta needs to be re-initialized.
Q) How and where can I control whether a repeat delta is requested?
A) Via the status of the last delta in the BW Request Monitor. If the request is RED, the next load will be of type 'Repeat'. If you need to repeat the last load for certain reasons, set the request in the monitor to red manually. For the contents of the repeat see Question 14. Delta requests set to red despite of data being already updated lead to duplicate records in a subsequent repeat, if they have not been deleted from the data targets concerned before.
Q) As of PI 2003.1, the Logistic Cockpit offers various types of update methods. Which update method is recommended in logistics? According to which criteria should the decision be made? How can I choose an update method in logistics?
See the recommendation in Note 505700.
Q) Are there particular recommendations regarding the data volume the DeltaQueue may grow to without facing the danger of a read failure due to memory problems?
A) There is no strict limit (except for the restricted number range of the 24-digit QCOUNT counter in the LUW management table - which is of no practical importance, however - or the restrictions regarding the volume and number of records in a database table).
When estimating "smooth" limits, both the number of LUWs is important and the average data volume per LUW. As a rule, we recommend to bundle data (usually documents) already when writing to the DeltaQueue to keep number of LUWs small (partly this can be set in the applications, e.g. in the Logistics Cockpit). The data volume of a single LUW should not be considerably larger than 10% of the memory available to the work process for data extraction (in a 32-bit architecture with a memory volume of about 1GByte per work process, 100 Mbytes per LUW should not be exceeded). That limit is of rather small practical importance as well since a comparable limit already applies when writing to the DeltaQueue. If the limit is observed, correct reading is guaranteed in most cases.
If the number of LUWs cannot be reduced by bundling application transactions, you should at least make sure that the data are fetched from all connected BWs as quickly as possible. But for other, BW-specific, reasons, the frequency should not be higher than one DeltaRequest per hour.
To avoid memory problems, a program-internal limit ensures that never more than 1 million LUWs are read and fetched from the database per DeltaRequest. If this limit is reached within a request, the DeltaQueue must be emptied by several successive DeltaRequests. We recommend, however, to try not to reach that limit but trigger the fetching of data from the connected BWs already when the number of LUWs reaches a 5-digit value.
Q) I would like to display the date the data was uploaded on the report. Usually, we load the transactional data nightly. Is there any easy way to include this information on the report for users? So that they know the validity of the report.
A) If I understand your requirement correctly, you want to display the date on which data was loaded into the data target from which the report is being executed. If it is so, configure your workbook to display the text elements in the report. This displays the relevance of data field, which is the date on which the data load has taken place.
Q) Can we filter the fields at Transfer Structure?
Q) Can we load data directly into infoobject with out extraction is it possible.
Yes. We can copy from other infoobject if it is same. We load data from PSA if it is already in PSA.
Q) HOW MANY DAYS CAN WE KEEP THE DATA IN PSA, IF WE R SHEDULED DAILY, WEEKLY AND MONTHLY.
a) We can set the time.
Q) HOW CAN U GET THE DATA FROM CLIENT IF U R WORKING ON OFFSHORE PROJECTS. THROUGH WHICH NETWORK.
a) VPN .Virtual Private Network, VPN is nothing but one sort of network where we can connect to the client systems sitting in offshore through RAS (Remote access server).
Q) HOW CAN U ANALIZE THE PROJECT AT FIRST?
Prepare Project Plan and Environment
Define Project Management Standards and
Procedures
Define Implementation Standards and Procedures
Testing & Go-live + supporting.
Q) THERE is one ODS AND 4 INFOCUBES. WE SEND DATA AT TIME TO ALL CUBES IF ONE CUBE GOT LOCK ERROR. HOW CAN U RECTIFY THE ERROR?
Go to TCode sm66 then see which one is locked select that pid from there and goto sm12
TCode then unlock it this is happened when lock errors are occurred when u scheduled.
Q) Can anybody tell me how to add a navigational attribute in the BEx report in the rows?
A) Expand dimension under left side panel (that is infocube panel) select than navigational attributes drag and drop under rows panel.
Q) IF ANY TRASACTION CODE LIKE SMPT OR STMT.
In current systems (BW 3.0B and R/3 4.6B) these Tcodes don't exist!
Q) WHAT IS TRANSACTIONAL CUBE?
A) Transactional InfoCubes differ from standard InfoCubes in that the former have an improved write access performance level. Standard InfoCubes are technically optimized for read-only access and for a comparatively small number of simultaneous accesses. Instead, the transactional InfoCube was developed to meet the demands of SAP Strategic Enterprise Management (SEM), meaning that, data is written to the InfoCube (possibly by several users at the same time) and re-read as soon as possible. Standard Basic cubes are not suitable for this.
Q) Is there any way to delete cube contents within update rules from an ODS data source? The reason for this would be to delete (or zero out) a cube record in an "Open Order" cube if the open order quantity was 0.
I've tried using the 0recordmode but that doesn't work. Also, would it
be easier to write a program that would be run after the load and delete
the records with a zero open qty?
A) START routine for update rules u can write ABAP code.
A) Yap, you can do it. Create a start routine in Update rule.
It is not "Deleting cube contents with update rules" It is only possible to avoid that some content is updated into the InfoCube using the start routine. Loop at all the records and delete the record that has the condition. "If the open order quantity was 0" You have to think also in before and after images in case of a delta upload. In that case you may delete the change record and keep the old and after the change the wrong information.
Q) I am not able to access a node in hierarchy directly using variables for reports. When I am using Tcode RSZV it is giving a message that it doesn't exist in BW 3.0 and it is embedded in BEx. Can any one tell me the other options to get the same functionality in BEx?
A) Tcode RSZV is used in the earlier version of 3.0B only. From 3.0B onwards, it's possible in the Query Designer (BEx) itself. Just right click on the InfoObject for which you want to use as variables and precede further selecting variable type and processing types.
Q) Wondering how can I get the values, for an example, if I run a report for month range 01/2004 - 10/2004 then monthly value is actually divide by the number of months that I selected. Which variable should I use?
Q) Why is it every time I switch from Info Provider to InfoObject or from one item to another while in modeling I always get this message " Reading Data " or "constructing workbench" in it runs for minutes.... anyway to stop this?
Q) Can any one give me info on how the BW delta works also would like to know about 'before image and after image' am currently in a BW project and have to write start routines for delta load.
Q) I am very new to BW. I would like to clarify a doubt regarding Delta extractor. If I am correct, by using delta extractors the data that has already been scheduled will not be uploaded again. Say for a specific scenario, Sales. Now I have uploaded all the sales order created till yesterday into the cube. Now say I make changes to any of the open record, which was already uploaded. Now what happens when I schedule it again? Will the same record be uploaded again with the changes or will the changes get affected to the previous record.
A)
Q) In BW we need to write abap routines. I wish to know when and what type of abap routines we got to write. Also, are these routines written in update rules? I will be glad, if this is clarified with real-time scenarios and few examples?
A) Over here we write our routines in the start routines in the update rules or in the transfer structure (you can choose between writing them in the start routines or directly behind the different characteristics. In the transfer structure you just click on the yellow triangle behind a characteristic and choose "routine". In the update rules you can choose "start routine" or click on the triangle with the green square behind an individual characteristic. Usually we only use start routine when it does not concern one single characteristic (for example when you have to read the same table for 4 characteristics). I hope this helps.
We used ABAP Routines for example:
To convert to Uppercase (transfer structure)
To convert Values out of a third party tool with different keys into the same keys as our SAP System uses (transfer structure)
To select only a part of the data for from an infosource updating the InfoCube (Start Routine) etc.
Q) What is ODS?
A) An ODS object acts as a storage location for consolidated and cleaned-up transaction data (transaction data or master data, for example) on the document (atomic) level.
This data can be evaluated using a BEx query.
Standard ODS Object
Transactional ODS object:
The data is immediately available here for reporting. For implementation, compare with the Transactional ODS Object.
A transactional ODS object differs from a standard ODS object in the way it prepares data. In a standard ODS object, data is stored in different versions ((new) delta, active, (change log) modified), where as a transactional ODS object contains the data in a single version. Therefore, data is stored in precisely the same form in which it was written to the transactional ODS object by the application. In BW, you can use a transaction ODS object as a data target for an analysis process.
The transactional ODS object is also required by diverse applications, such as SAP Strategic Enterprise Management (SEM) for example, as well as other external applications.
Transactional ODS objects allow data to be available quickly. The data from this kind of ODS object is accessed transactionally, that is, data is written to the ODS object (possibly by several users at the same time) and reread as soon as possible.
It offers no replacement for the standard ODS object. Instead, an additio -
Material moved to plant date data
How can I get the date data on which the material moved to plant i.e on which particular datae the material has come to plant for caluclating the non moving items
Should calculate materials which are not moving from 1 year from plants & I should show the value of that
Report format should be like this
Jan 07 Feb07
Non Moving items 50 10.92
I am using the cube 0ic_c03 for this
I should not shoe the nonmoving items material wise but shouls show it for all the material & it sum
In the above example from 1year up to the month of Jan the total no of materials that are not moving are 5 & each of the value is Rs 10 then it shouls show me 10* 5 = 50 its value is 15.90(Sum of all materials)
If the issued qty is 0 for particular material from 1 year then we say it as nonmoving
Kindly suggest me how to work on thisHello Priya,
You have to create a report on multicube based on 0material and 0ic_c03 .
There is a SAP document available for non moving items .
http://help.sap.com/saphelp_bw33/helpdata/en/3a/d1603d13b5c72ee10000000a114084/content.htm
Jaya
Jaya Mogali -
Performance of a report over a multicube?
Hi,
I have a report built on a multiprovider which sits over 3 ODS.This query takes a long time to run.
To improve the performance...i was thinking of changing the indexes for ODS..
And i cannot think of changing the query design..cuz i dont have an idea of query requirement..
I am only here for Tuning..
So r there anyother ways of improving the performance..
Thanks,
Sai.Hi.
Creating index enhances the performance. Also since it is ODs, check in settings whether Bex reporting is ticked.. If not selected.. and you are running reports.. it creats SIDs at the time of reporting and the performance gets affected.
Also go thru this How to build an efficient queries on multiprovider.this is a general document for the queries either Infocube/ODS built on multiprovider.
https://websmp202.sap-ag.de/~sapdownload/011000358700009385892004E/HowToMultiProvider.pdf
Hope it helps. Plz assign points if it is helpful for u.
Thanks & Regarda,
Pradeep.E -
Data Error in the Query/Report after selective data deletion for infocube
Hi Experts,
Please advise what i was missing and what went wrong...
I got a Query (Forecast) on a Multicube...which is based on 2 Infocubes with Aggregates...
As i identified some data discrepency..yesteraday i performed selective data deleation on one of the Infocube
and executed report yesteraday and the results in the query are correct...
When today i executed the same report i am getting different results..
When i compared the results of the report with that of data in cube they are not matching
The report is not displaying the data in cube..for some rows it is displaying the data in the cube but for some rows it is just displaying same as the above row
there is no data loaded into info cube after selective deleation
Do i need to perform request compression and fill the aggregated after selective deleation
Please advise what went wrongHi Venkat,
No i haven't done anything on aggregates before or after selective delete
As there is not data load after the selective delete according to SAP Manual we don't need to perform any thing on aggregates...as selective data deletion on cube will delete data from aggregates as well
Please update how to identify error -
The issue I have has been addressed in oss note(541559) but I am unable to get the solution outlined to work.
The situation is I would like to show all characteristic values for 0material__PNL that we have a history of transactional data, even if there is not transactional data during the current period or for the current customer the report is filtered for, displaying a blank or a zero when there is no data. I just want the list of PNLs to be consistent over different runnings of the report regardless of whether or not there is a transaction.Hi JSG,
well, if I understand your requirement correctly you want to show lines in a query that do not exist in the cube. Normally this can be done by creating a multicube on the cube and the infoobject (ofcourse the infoobject has to be activated as infoprovider too) and running a query against this multiprovider.
Hope this helps
regards
Siggi -
People, I activated the BI Statistics in SAP/BW.
The Multicube 0BWTC_C10 is active.
Will I can generate a report related to load data (time of loading, the load status, etc), using this multicube (0BWTC_C10)?Hi Akash,
The below standard queries will provide you the required details,
Info
Provider
Bex Query
Technical Name
Bex Query
description
0TCT_MC11
0TCT_MC11_Q0140
InfoCube Status
0TCT_MC11
0TCT_MC11_Q0141
InfoCube
Correctness
0TCT_MC11
0TCT_MC11_Q0240
InfoCube Status: Analysis
0TCT_MC22
ZCS_CUBE_DATADETAIL_STAT
ZCS_CUBE_DATADETAIL_STAT
0TCT_MC21
ZTCT_MC21_Q_FB_01
Dashboard - process
chain historical loading time
0TCT_MC22
ZCS_STAT_SPEND_LOADS
Statistics Spend
Overview Loads
0TCT_MC22
ZCS_STAT_SPEND_LOADS_PERF
Statistics Spend
Overview Loads Performance
0TCT_MC22
ZTCT_MC22_Q_FB_02
Dashboard - DSO
loading time top 10
0TCT_MC22
ZTCT_MC22_Q_FB_04
Dashboard - IC
loading time top 10
0TCT_MC22
ZTCT_MC22_Q_FB_06
Dashboard - IO
loading time top 10
-Arun.M.D -
Reporting Question - Detail and Summary info in the same report
Hello All,
I have a situation where I have to report the detail and summary information from one cube (or multiple cubes) in a single report. Following is the example cube with smaple data and the required report
Cube - Char - 0CUSTOMER
0MATERIAL
0MATL_GRP
0CURRENCY
Key Fig - 0AMOUNT
Data
0CUSTOMER 0MATERIAL 0MATL_GRP 0AMOUNT 0CURRENCY
CUS1 MAT1 GRP1 1000 USD
CUS1 MAT2 GRP1 2000 USD
CUS1 MAT3 GRP2 3000 USD
CUS1 MAT4 GRP2 4000 USD
CUS2 MAT2 GRP1 2222 USD
If I run a report to See Which Customers have bought Material MAT1, I want to produce a report like
Material Cust Matl_Gr Amt(Matl) Amt(Cust/Mtgr) Amt(Cust)
MAT1 CUS1 GRP1 1000 USD 3000 USD 10000 USD
MAT1 CUS2 GRP1 2222 USD 2222 USD 2222 USD
Any Ideas to create such a report is welcome. I am open to use multiple cubes, Multicubes, summarized data joins etc.
Thanks in advance for the help.
Amit GuptaAmit,
You can acheive this using single cube.
All you need to do is to define 2 restricted keyfigures the following way.
1. Amount (Cust/Material Group)
In the Restricted KF (either global or local), pull in the Material to the right side, right click on it and select "Constant Selection". Save it.
2. Amount (Customer)
Pull in both Material and Material Group and do the same step as above for both. Save it.
Now run the query and tests it. Let us know if i worked.
Gova -
Setting IT performance report in Solman
Hi,
We are trying to set up IT performance reporting in Solution Manager. BI client is same as production client. The Info objects are not getting activated. The job fails with the message to use a different BI client.
SOLMAN SM37 Job log:
Message text
Message class
Message no.
Message type
Job started
00
516
S
Step 001 started (program CCMSBI_SETUP_BATCH, variant , user ID KZHX33)
00
550
S
Incorrect client 025
00
001
S
use BI client 001.
00
001
S
Prerequisites check failed
00
001
A
Job cancelled
00
518
A
If any one faced this issue and resolved, kindly throw some light on it.
Thank you.
Regards,
ManjuHi Manju,
The issue is due to inactive object in the infocube .
Please check the note: 1110013 - ST: Manual activation of BI Content for E2E Diagnostics SP13 attachment . it will help to activate the inactive object.
or
Go to basis configuration -> step 5. configure automatically ->re-excute the Activate BW Source System. so it will reactive the infocube.
Also check the below discussion,
CCMS_BI_SETUP IT Performance Reporting Activation
Error :
20140620 050208[ERROR ]: Activation of InfoCube 0CCMDAY1 failed
20140620 050208[HELP ]: Attempt to activate object CUBE:0CCMDAY1 manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoCube 0CCMDAY2 failed
20140620 050208[HELP ]: Attempt to activate object CUBE:0CCMDAY2 manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoCube 0CCMMIN1 failed
20140620 050208[HELP ]: Attempt to activate object CUBE:0CCMMIN1 manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoCube 0CCMMIN2 failed
20140620 050208[HELP ]: Attempt to activate object CUBE:0CCMMIN2 manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoCube 0CCMMNTH1 failed
20140620 050208[HELP ]: Attempt to activate object CUBE:0CCMMNTH1 manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoCube 0CCMMNTH2 failed
20140620 050208[HELP ]: Attempt to activate object CUBE:0CCMMNTH2 manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoCube 0CCMQTR1 failed
20140620 050208[HELP ]: Attempt to activate object CUBE:0CCMQTR1 manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoCube 0CCMQTR2 failed
20140620 050208[HELP ]: Attempt to activate object CUBE:0CCMQTR2 manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoCube 0CCMVRKF failed
20140620 050208[HELP ]: Attempt to activate object CUBE:0CCMVRKF manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoCube 0CCMWEEK1 failed
20140620 050208[HELP ]: Attempt to activate object CUBE:0CCMWEEK1 manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoCube 0CCMWEEK2 failed
20140620 050208[HELP ]: Attempt to activate object CUBE:0CCMWEEK2 manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoCube 0SMD_PE2H failed
20140620 050208[HELP ]: Attempt to activate object CUBE:0SMD_PE2H manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoSet 0CCMIAGGR failed
20140620 050208[HELP ]: Attempt to activate object ISET:0CCMIAGGR manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoSet 0CCMIAVDT failed
20140620 050208[HELP ]: Attempt to activate object ISET:0CCMIAVDT manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoSet 0CCMICURR failed
20140620 050208[HELP ]: Attempt to activate object ISET:0CCMICURR manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of MultiCube 0CCMPDATA failed
20140620 050208[HELP ]: Attempt to activate object MPRO:0CCMPDATA manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of MultiCube 0CCMSDSR failed
20140620 050208[HELP ]: Attempt to activate object MPRO:0CCMSDSR manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of MultiCube 0CCMSMTPH failed
20140620 050208[HELP ]: Attempt to activate object MPRO:0CCMSMTPH manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of MultiCube 0SMD_MPEH failed
20140620 050208[HELP ]: Attempt to activate object MPRO:0SMD_MPEH manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of DSO 0CCMAGGR failed
20140620 050208[HELP ]: Attempt to activate object ODSO:0CCMAGGR manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of DSO 0CCMAVDT failed
20140620 050208[HELP ]: Attempt to activate object ODSO:0CCMAVDT manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of DSO 0CCMBUFF failed
20140620 050208[HELP ]: Attempt to activate object ODSO:0CCMBUFF manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of DSO 0CCMCURR failed
20140620 050208[HELP ]: Attempt to activate object ODSO:0CCMCURR manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of DSO 0CCMSDCFG failed
20140620 050208[HELP ]: Attempt to activate object ODSO:0CCMSDCFG manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of DSO 0CCMSYINF failed
20140620 050208[HELP ]: Attempt to activate object ODSO:0CCMSYINF manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of DSO 0CCMTHRS failed
20140620 050208[HELP ]: Attempt to activate object ODSO:0CCMTHRS manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of DSO 0CCM_SCFG failed
20140620 050208[HELP ]: Attempt to activate object ODSO:0CCM_SCFG manually in transaction RSOR. If this is successful, execute setup again."
Rg,
Karthik -
I need to develop a report which displays the following output for each Site / Customer selection:
- Item Code
- Item Description
- Last 7 days orders
- Stock at 05.30 (of current date)
- Orders for next day
- Resulting Stock (Stock 05.30 u2013 Orders stock next day Delivery)
- 6 additional columns u2013 orders for the next 6 days
We have a delivery performance cube which holds orders / delivery / billing data and a stock cube. I am planning to combine these two in a Multicube however I am not sure which source Tables / Fields correspond to the above output and how to go about designing this report.
One more thing, my client wants to be able to view this data realtime.
Could you pls point me in the right direction.
Thanks,
MilindHi Milind,
Can you send me details of how you were able to resolve this issue??
Thanks in advance,
Sridhar
Maybe you are looking for
-
Move Time Capsule and Laptop to New Network
I have been searching the forums it haven't found a clear answer to this question. I have been backing up my laptop using Time Machine and Time Capsule on one wireless network (TC has joined the wireless network, it does not serve as the router for
-
User cannot retrieve data in app on local PC
A certain user cannot retrieve data in one application whilst being able to send data in that application. She can access the 'Finance' application, send data in that application and retrieve data but in another application, 'ICM', she cannot retriev
-
JButton in inner class cuasing Null Pointer Excp
Ok so i have this class called "square" and in it there is a JButton. There is a method called createButton() and getButton(). In create button it takes the classes JButton called button and instantiates: public void createButton() { button = new JBu
-
I have downloaded most of the addons/extensions that say they will download flash. I have double checked my adobe flash plugin, downloaded any video converter, and real time player and I still can not download a flash movie from the web. It is NOT on
-
Installation of SAP products on older 32-bit serves
Hi, I have a special testing project. We want to install multiple SAP products on older 32-bit servers. These will be used in a proof-of-concept testing. we will install these products on Windows 2003 32-bit with 4GB of RAM Products to be installed: