SAP Interview Questions -13

SAP Interview Questions -13

1. 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.

2. 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.

3. What are the steps involved in LO Extraction?

The steps are:
1.RSA5 Select the DataSources
2.LBWE Maintain DataSources and Activate Extract Structures
3.LBWG Delete Setup Tables
4.0LI*BW Setup tables
5.RSA3 Check extraction and the data in Setup tables
6.LBWQ Check the extraction queue
7.LBWF Log for LO Extract Structures
8.RSA7 BW Delta Queue Monitor

4. 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.

5. 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.

6. How to create a connection with LIS InfoStructures?

LBW0 Connecting LIS InfoStructures to BW

7. 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.

8. 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.

9. 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

10. 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.
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.

11. What is compression?

It is a process used to delete the Request IDs and this saves space.

12. 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.

13. 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.

14. How many extra partitions are created and why?

Two partitions are created for date before the begin date and after the end  date.

15. What are the options available in transfer rule?


16. 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.

17. 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.

18. 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.

19. 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

20. How do you transform Open Hub Data?

Using BADI we can transform Open Hub Data according to the destination  requirement.

21. 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.

22. 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.

23. What are the steps to extract data from R/3?

i.Replicate DataSources
ii.Assign InfoSources
iii.Maintain Communication Structure and Transfer rules
iv.Create and InfoPackage
v.Load Data

24. What are the delta options available when you load from flat file?

The 3 options for Delta Management with Flat Files:
i.Full Upload
ii.New Status for Changed records (ODS Object only)
iii.Additive Delta (ODS Object & InfoCube)

25.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.

26.I want to delete a BEx query that is in Production system through request.  Is anyone aware about it?

Have you tried the RSZDELETE transaction?

27.Errors while monitoring process chains.

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.

28.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.

29.PSA Cleansing.

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.

30.How do you measure the size of infocube?

In no of records.

31.Difference between infocube and ODS?

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

32.Difference between display attributes and navigational attributes?

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.


But how is it possible? If you load it manually twice, then you can  delete it by requestID.


Sure you can. ODS is nothing but a table.


Yes of course. For example, for loading text and hierarchies we use  different data sources but the same InfoSource.


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.

37.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.

38.Why we delete the setup tables (LBWG) & fill them (OLI*BW)?

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.


It holds granular data (detailed level).


In PSA table.


The volume of data one data target holds (in no. of records)

42.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  : /index.sdn and search for Designing Virtual Cube  and you will get a good material designing the Function Module


Different Variable's are Texts, Formulas, Hierarchies, Hierarchy nodes &  Characteristic values.
Variable Types are
Manual entry /default value
Replacement path
SAP exit
Customer exit


You can drill down to any level by using Navigational attributes and jump  targets.


Indexes are data base indexes, which help in retrieving data fastly.


Help! Refer documentation




KPI's indicate the performance of a company. These are key figures

49.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).

50.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?

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.

51.Types of Update Rules?

(Check box), Return table

52.Transfer Routine?

Routines, which we write in, transfer rules.

53.Update Routine?

Routines, which we write in Update rules

54.What is the difference between writing a routine in transfer rules and  writing a routine in update rules?

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.

55.Routine with Return Table.

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.

56.Start routines?

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

57.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

58.What does the number in the 'Total' column in Transaction RSA7 mean?

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.

59.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.

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)

60.What is a LUW in the delta queue?

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.

61.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?

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.

62.Why does Transaction RSA7 still display LUWs on the overview screen after  successful delta loading?

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.

63.Why are selections not taken into account when the delta queue is filled?

Filtering according to selections takes place when the system reads from the  delta queue. This is necessary for reasons of performance.

64.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.

65.Do the entries in table ROIDOCPRMS have an impact on the performance of  the loading procedure from the delta queue?

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.

66.Why does it take so long to display the data in the delta queue (for  example approximately 2 hours)?

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.

67.What is the purpose of function 'Delete data and meta data in a queue' in  RSA7? What exactly is deleted?

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.

68.Why does it take so long to delete from the delta queue (for example half  a day)?

Import PlugIn 2000.2 patch 3. With this patch the performance during deletion  is considerably improved.

69.Why is the delta queue not updated when you start the V3 update in the  logistics cockpit area?

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.

70.What is the relationship between RSA7 and the qRFC monitor (Transaction  SMQ1)?

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.

71.Why are the data in the delta queue although the V3 update was not  started?

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.

72.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?

Was programmed in a way that the request in repeat mode fetches both  actually repeatable (old) data and new data from the source system.

73.I loaded several delta inits with various selections. For which one is the  delta loaded?

For delta, all selections made via delta inits are summed up. This means, a  delta for the 'total' of all delta initializations is loaded.

74.How many selections for delta inits are possible in the system?

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.

75.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?

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.

76.Is it allowed in Transaction SMQ1 to use the functions for manual control  of processes?

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'.

77.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"?

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.

78.Despite my deleting the delta init, LUWs are still written into the  DeltaQueue?

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.

79.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?

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.

80.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.

81.How and where can I control whether a repeat delta is requested?

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.

82.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?

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.

83.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.

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.

84.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.


We can set the time.


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).


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.

88.Can anybody tell me how to add a navigational attribute in the BEx report  in the rows?

Expand dimension under left side panel (that is infocube panel) select than  navigational attributes drag and drop under rows panel.


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.

90.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?

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.

91.What is ODS?

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.

92.What does InfoCube contains?

Each InfoCube has one FactTable & a maximum of 16 (13+3 system defined, time,  unit & data packet) dimensions.

93.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.

94.How many dimensions are in a CUBE?

16 dimensions. (13 user defined & 3 system pre-defined [time, unit & data  packet])

95.What does SID Table contain?

SID keys linked with dimension table & master data tables (attributes, texts,  hierarchies)

96.What does ATTRIBUTE Table contain?

Master attribute data

97.What does TEXT Table contain?

Master text data, short text, long text, medium text & language key if it is  language dependent

98.What does Hierarchy table contain?

Master hierarchy data

99.As to where in BW do you go to add a character like a ; # so that BW will  accept it. This is transaction data which loads fine in the PSA but not the data  target.

Check transaction SPRO ---Then click the "Goggles"-Button => BusinessInformation Warehouse => Global Settings => 2nd point in the list. I hope you can use my "Guide" (my BW is in german, so i don't know all the english  descriptions).

100.When are Dimension ID's created?

When Transaction data is loaded into InfoCube.

101.When are SID's generated?

When Master data loaded into Master Tables (Attr, Text, Hierarchies).

102.How would we delete the data in ODS?

By request IDs, Selective deletion & change log entry deletion.

103.How would we delete the data in change log table of ODS?

Context menu of ODS â ' Manage â ' Environment â ' change log entries.

104.Different types of Attributes?

Navigational attribute, Display attributes, Time dependent attributes,  Compounding attributes, Transitive attributes, Currency attributes.


Post a Comment