SAP BW Important Interview Questions Paper- Part - 1 1. What are the extractor types?

Application Specific BW Content FI, HR, CO, SAP CRM, LO Cockpit Customer-Generated Extractors LIS, FI-SL, CO-PA Cross Application (Generic Extractors) 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. 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
SAP BW Important Interview Questions Paper- Part - 2 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.

I don't think you can delete single records. 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. Q) In Monitor----. it's in last pages u find out.Simulate update. in process chains you add so many process types.Test . If you want more details about this there is a chapter in Extraction book. including in earlier Releases? The menu path is: Tools .24.Details (Header/Status/Details) à Under Processing (data packet): Everything OK à Context menu of Data Package 1 (1 Records): Everything OK ---. you activate ODS data (another process type) this might also fail. you rollup data into aggregates. after entering datasource name and pressing create. Q) Can we make a datasource to support delta. A) During data loading.Test Workbench. (Here we can debug update rules or transfer rules. Apart from them. Another one is after you load data into ODS. Q) I want to delete a BEx query that is in Production system through request.) SM50 à Program/Mode à Program à Debugging & debug this work process. A) If this is a custom (user-defined) datasource you can make the datasource delta enabled. Is anyone aware about it? A) Have you tried the RSZDELETE transaction? Q) Errors while monitoring process chains. A) You know how to edit PSA. now this rolling up of data into aggregates is a process type which you keep after the process type for loading data into Cube. What are the steps to extract data from R/3? ¢ Replicate DataSources ¢ Assign InfoSources ¢ Maintain Communication Structure and Transfer rules ¢ Create and InfoPackage ¢ Load Data 25. for example after loading data into Info Cube. Generic delta services: Supports delta extraction for generic extractors according to: . While creating datasource from RSO2. Q) PSA Cleansing. in the next screen there is one button at the top. which says generic delta.ABAP Workbench . You have to delete entire PSA data for a request. This rolling up into aggregates might fail.

). then the role does not need to be part of the transport.even though it may not be visible. decision makers define clear project objectives and an efficient decision making process ( i. Project managers will be involved in this phase (I guess).ALWAYS use control c/control v copy/paste for manually adding! 3. like what are his needs and requirements etc. Project Preparation: In this phase. 1. 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 -. and then you have a choice of transporting the role (recommended) or just the workbook. you do not receive an error message from the transport of 'just a workbook' -. Thus. Discussions with the client. should be transported with the role. as a general rule. This depends. Final preparation & Go-Live . Here are a couple of scenarios: 1.Time stamp Calendar day Numeric pointer.support. If both the workbook and its role have been previously transported. 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. Keep in mind that a workbook is an object unto itself and has no dependencies on other objects. Q) How much time does it take to extract 1 million (10 lackhs) of records into an infocube? A. Business Blue print. If the role exists in both dev and the target system but the workbook has never been transported. or else it will take less than 30 minutes. If the role does not exist in the target system you should transport both the role and workbook. as a general rule. . Delta extraction is supported for all generic extractors. such as document number & counter Only one of these attributes can be set as a delta attribute. If only the workbook is transported. Q) What are the five ASAP Methodologies? A: Project plan. Realization. if you have complex coding in update rules it will take longer time. 2. it will exist (verified via Table RSRWBINDEXT). you should transport roles with workbooks. Overall.e.

A Project Charter is issued and an implementation strategy is outlined in this phase. 2..e. as they are new to the technology.e. testing system. And the data wise. No overwrite functionality ODS is a flat structure (flat table) with no star schema concept and which will have granular data (detailed level). 4. Business Blueprint: It is a detailed documentation of your company's requirements. Testing/Quality system: quality check is done in this system and integration testing is done. (i. Landscape of R/3 not sure. Q) How do you measure the size of infocube? A: In no of records. Overwrite functionality.e. Analysis of objects developing. d delete. Final Preparation: Final preparation before going live i. modification etc) and from here the objects are transported to the testing system. a add. testing. you will have aggregated data in the cubes. r reverse . end user training etc. Flat file datasources does not support 0recordmode in extraction. Production system: All the extraction part takes place in this sys. End user training is given that is in the client site you train them how to work with the new environment. -after. Q) What is landscape of R/3 & what is landscape of BW. 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. Then Landscape of b/w: u have the development system. the implementation of the project takes place (development of objects etc) and we are involved in the project from here only. 5. n new. (I. what are the objects we need to develop are modified depending on the client's requirements). 3. conducting pre-go-live. production system Development system: All the implementation part is done in this sys. Realization: In this only. but before transporting an initial test known as Unit testing (testing of objects) is done in the development sys. Q). Go-Live & support: The project has gone live and it is into production. x before. The Project team will be supporting the end users.

CAN NUMBER OF DATASOURCES HAVE ONE INFOSOURCE? A) Yes of course. For example. CURRENCY CONVERSIONS CAN BE WRITTEN IN UPDATE RULES. We r changing the extract structure right. Q. Previous Page | Next Page Page . which is used only for display purpose in the report. Q. The extraction set up reads the dataset that you want to process such as. ODS is nothing but a table. Q. Q. Refer white paper on LO-Cockpit extractions. no . So to get the required data ( i.e. sbiw1. HOW TO CORRECT IT? A: But how is it possible? If you load it manually twice.2 SAP BW Important Interview Questions Paper.. The data is stored in cluster tables from where it is read when the initialization is run. 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. then you can delete it by requestID. To refresh the statistical data. We will have datasources and can be maintained (append fields).Part . that means there are some newly added fields in that which r not before. SOME DATA IS UPLOADED TWICE INTO INFOCUBE. customers orders with the tables like VBAK. DataSources on the transactional system needs to be replicated on BW side and attached to infosource and update rules respectively. the data which is required is taken and to avoid redundancy) we delete n then fill the setup tables. BRIEF THE DATAFLOW IN BW. WHY NOT IN TRANSFER RULES? Q) WHAT IS PROCEDURE TO UPDATE DATA INTO DATA TARGETS? FULL and DELTA. sbiw2 for delta update in LIS THEN WHAT IS THE PROCEDURE IN LO-COCKPIT? No LIS in LO cockpit. Where as navigational attribute is used for drilling down in the report. Q. It is important that during initialization phase. We don't need to maintain Navigational attribute in the cube as a characteristic (that is the advantage) to drill down. A) Data flows from transactional system to analytical system (BW). CAN U ADD A NEW FIELD AT THE ODS LEVEL? Sure you can. VBAP) & fills the relevant communication structure with the data.Q) Difference between display attributes and navigational attributes? A: Display attribute is one. for loading text and hierarchies we use different data sources but the same InfoSource.3 Q) AS WE USE Sbwnn.

sdn and search for Designing Virtual Cube and you will get a good material designing the Function Module Q) INFOSET QUERY. In R/3 or in BW? 2 in R/3 and 2 in BW Q) ROUTINES? Exist in the InfoObject. Formulas. of records) Q) Different types of INFOCUBES. you will get the information : https://www. Can be made of ODS's and Characteristic InfoObjects with masterdata.one generates or modifies application data. Q) WHAT IS DATA SIZE? The volume of data one data target holds (in no.sdn.com/sdn /index. Q) WHAT ARE THE DIFFERENT VARIABLES USED IN BEX? Different Variable's are Texts.. Virtual cube it is like a the structure. sap remote and multi) Virtual Cube is used for example. at least until the tables can be set up. Hierarchies. For designing the Virtual cube you have to write the function module that is linking to table.sap. Q) IF THERE ARE 2 DATASOURCES HOW MANY TRANSFER STRUCTURES ARE THERE. Q) WHERE THE PSA DATA IS STORED? In PSA table. FYI. update routines and start routine Q) BRIEF SOME STRUCTURES USED IN BEX. you can create structures. Rows and Columns.. Q) SIGNIFICANCE of ODS? It holds granular data (detailed level). transfer routines. Virtual (remote. if you consider railways reservation all the information has to be updated online. Basic. when ever the table is updated the virtual cube will fetch the data from table and display report Online. Hierarchy nodes & Characteristic ..

1 AND 3.X VERSIONS. Q) WHAT IS THE SIGNIFICANCE OF KPI'S? KPI's indicate the performance of a company. which help in retrieving data fastly. Etc Q) PROCESS CHAINS: IF U has USED IT THEN HOW WILL U SCHEDULING .values. Help! Refer documentation. 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) DIFFERENCE BETWEEN 2. Help! Refer documentation Q) IS IT NESSESARY TO INITIALIZE EACH TIME THE DELTA UPDATE IS USED? No. delete indexes before load. Q) WHAT ARE INDEXES? Indexes are data base indexes. These are key figures Q) AFTER THE DATA EXTRACTION WHAT IS THE IMAGE POSITION. Q) TOOLS USED FOR PERFORMANCE TUNING. Number ranges. After image (correct me if I am wrong) Q) REPORTING AND RESTRICTIONS. ST22.

Improves data loading into PSA and Cubes by infopackages (Eg. but only really tells you if the extractor works. A) RSA3 is a simple extractor checker program that allows you to rule out extracts problems in R/3. Since records that get updated into Cubes/ODS structures are controlled by Update Rules.DATA DAILY. What are you expecting?? Q) CAN CHARECTERSTIC INFOOBJECT CAN BE INFOPROVIDER. I would recommend enlisting the help of . 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). Profile generator Q) WEB REPORTING. 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. without timeouts). There should be some tool to run the job daily (SM37 jobs) Q) AUTHORIZATIONS. B) Transactional Load Partitioning Improvement: Partitioning based on expected load volumes and data element sizes. You will need to compare records on a 1:1 basis against records in R/3 transactions for the functional area in question. It is simple to use. It will give you the number of records extracted. you will not be able to determine what is in the Cube compared to what is in the R/3 environment. 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. Of course Q) PROCEDURES OF REPORTING ON MULTICUBES Refer help.

From RSMO for a given load you can determine how many records were passed through the transfer rules from R/3.the end user community to assist since they presumably know the data. Constant. it will not tell you how many records should be expected in BW for a given load. Click execute and you will see the record count. which we write in. Q) Types of Transfer Rules? A) Field to Field mapping. However. and how many records passed through the Update Rules. The . you can also go to display that data. how many targets were updated. Variable & routine. Q) Routine with Return Table. go to it and enter the extractor ex: 2LIS_02_HDR. by choosing checkbox Return table. Q) Update Routine? A) Routines. To use RSA3. Return table Q) Transfer 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. It also gives you error messages from the PSA. However. transfer rules. Q) Types of Update Rules? A) (Check box). A) Update rules generally only have one return value. You are not modifying anything so what you do in RSA3 has no effect on data quality afterwards. You have that information in the monitor RSMO during and after data loads. you can create a routine in the tab strip key figure calculation.

Ex: .corresponding key figure routine then no longer has a return value. no: of billing documents as RKF's. You can then generate as many key figure values. as you like from one data record. Q) Line-Item Dimension (give me an real time example) Line-Item Dimension: Invoice no: or Doc no: is a real time example .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. but a return table. 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. Y-table = A table to link material SIDs with SIDS for time-dependent navigation attributes. suppose you want to restrict (delete) some records based on conditions before getting loaded into data targets. billing value. then you can specify this in update rules-start routine. Q) Start routines? A) Start routines u can write in both updates rules and transfer rules.

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. Thus. a group of documents from a collective run or a whole data packet of an application extractor. Q) How to know in which table (SAP BW) contains Technical Name / Description and creation data of a particular Reports. The detail screen displays the records contained in the LUWs. 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. 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.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. Both. only the records that are ready for the next delta request are displayed on the detail screen. In the detail screen of Transaction RSA7.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. a possibly existing customer exit is not taken into account. The number includes the LUWs of the last delta request (for repetition of a delta request) and the LUWs for the next delta request. Directory of all reports (Table RSRREPDIR) and Directory of the reporting component elements (Table RSZELTDIR) for workbooks and the connections to queries check Where. You will find your information about technical names and description about queries in the following tables. Reports that are created using BEx Analyzer. 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. Q) Why does Transaction RSA7 still display LUWs on the overview screen after successful delta loading? .

the LUWs of the previous delta may be confirmed (and also deleted). the actual package size may differ considerably from the MAXSIZE and MAXLINES parameters. 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 means that when very large LUWs are written to the DeltaQueue. In particular. to restrict it. Please note. 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. This is necessary for reasons of performance. This error is corrected with BW 2.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. that LUWs are not split during data loading for consistency reasons. In the meantime. then refer to the application-specific notes (for example in the COPA area. the number on the overview screen does not change when the first delta was loaded to the BW System. to make a distinction between the 'actual' delta data and the data intended for repetition and so on. to selectively choose the number of a data record. 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).0B Support Package 11. If performance problems are related to the loading process from the delta queue. 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. Such a DataSource should not be displayed in RSA7. however. Then. Caution: As of Plug In 2000. . the LUWs must be kept for a possible delta request repetition. in the logistics cockpit area and so on).2 patch 3 the entries in table ROIDOCPRMS are as effective for the delta queue as for a full update.

The internal queue name must be used for selection on the initial screen of the qRFC monitor. the data of a LUW is displayed in an unstructured manner there. You do not only delete all data of this DataSource for the affected BW System. When you delete the data. the LUWs kept in the qRFC queue for the corresponding target system are confirmed. 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. the client and the short name of the DataSource. no longer exists or can no longer be accessed. Moreover. In the qRFC monitor you cannot distinguish between repeatable and new LUWs. the short name corresponds to the name of the DataSource. Q) Why does it take so long to delete from the delta queue (for example half a day)? A) Import PlugIn 2000. Physical deletion only takes place in the qRFC outbound queue if there are no more references to the LUWs. 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. For DataSources whose name are 19 characters long or shorter. from which the delta initialization was originally executed.1) the short name is assigned in table ROOSSHORTN. With this patch the performance during deletion is considerably improved. This is made up of the prefix 'BW. but also lose the entire information concerning the delta initialization. Then you can only request new deltas after another delta initialization.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.2 patch 3. It is comparable to deleting an InitDelta in the BW System and should preferably be executed there. The deletion function is for example intended for a case where the BW System. For DataSources whose name is longer than 19 characters (for deltacapable DataSources only possible as of PlugIn 2001. Q) What is the relationship between RSA7 and the qRFC monitor (Transaction SMQ1)? A) The qRFC monitor basically displays the same data as RSA7. .

all selections made via delta inits are summed up. See Note 417189. i. This happens in particular during automatic goods receipt posting (MRRS). After the client copy. Reason: With many selection conditions that are joined in a complicated way. Table ROOSPRMSC will probably be empty in the OLTP since this table is client-independent. Even if no dump 'MESSAGE_TYPE_X' occurs in BW when editing or creating an InfoPackage. an inconsistency might occur between BW delta tables and the OLTP delta tables as described in Note 405943. 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. make a client copy. It should not be more. a delta for the 'total' of all delta initializations is loaded. . Then.e. This means. '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 intend to copy the source system. With complicated selection conditions. it should be only up to 10-20 delta inits. i. For which one is the delta loaded? A) For delta. the records are updated directly in the delta queue (RSA7).e. After the system copy. The delta must be initialized in any case since delta depends on both the BW system and the source system. 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. you can make up to about 100 delta inits. make sure that your deltas have been fetched from the DeltaQueue into BW and that no delta is pending. too many 'where' lines are generated in the generated ABAP source code that may exceed the memory limit. There is no duplicate transfer of records to the BW system. After the client copy.Q) Why are the data in the delta queue although the V3 update was not started? A) Data was posted in background. Q) How many selections for delta inits are possible in the system? A) With simple selections (intervals without complicated join conditions or single values). What will happen with may delta? Should I initialize again after that? A) Before you copy a source client or source system. Q) I loaded several delta inits with various selections.

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. others 'RECORDED'. this does not mean that the record has successfully reached the BW yet.you should expect that the delta have to be initialized after the copy. However. some entries have the status 'READY'. 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'. LUWs are still written into the DeltaQueue? A) In general. READY and RECORDED in both tables are considered to be valid. Otherwise. Q) Despite of the delta request being started after completion of the collective run (V3 update). Q) In SMQ1 (qRFC Monitor) I have status 'NOSEND'. 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. ARFCSSTATE is 'READ'. What is the cause for this "splitting"? A) The collective run submits the open V2 documents for processing to the task handler. An alternative solution where this problem does not occur is described in Note 505700. buffer problems may occur: If a user started the internal mode at a time when the delta initialization was still active. 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. Only another delta request loads the missing documents into BW. which processes them in one or several parallel update processes in an asynchronous way. In the table TRFCQOUT. The records with status EXECUTED are usually deleted . Q) Despite my deleting the delta init. For this reason. The status EXECUTED in TRFCQOUT can occur temporarily. 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. he/she posts data into the queue even though the initialization had been deleted in the meantime. This is the case in your system. delta initializations and deletions of delta inits should always be carried out at a time when no posting takes place. it does not contain all documents. It is set before starting a DeltaExtraction for all records with status READ present at that time.

the delta needs to be re-initialized. if they have not been deleted from the data targets concerned before. it shows that some fields were moved. Q) As of PI 2003. The value 'U' in field 'NOSEND' of table TRFCQOUT is discomforting. it is likely that there are problems with deleting the records which have already been successfully been loaded into the BW. 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. For the contents of the repeat see Question 14. If the request is RED. or. Delta requests set to red despite of data being already updated lead to duplicate records in a subsequent repeat. no more deltas are loaded into the BW. When the problem occurs. Every other status is an indicator for an error or an inconsistency. When loading the delta into the PSA. the records are written with the old structure until the new structure has been generated. the Logistic Cockpit offers various types of update methods.from the queue in packages within a delta request directly after setting the status before extracting a new delta.1. This may have disastrous consequences for the delta. 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. If the extract structure change is not communicated synchronously to the server where delta records are being created. If you see such records. Q) Are there particular recommendations regarding the data volume the DeltaQueue may . We recommend to reset the buffers using Transaction $SYNC. the next load will be of type 'Repeat'. NOSEND in SMQ1 means nothing (see note 378903). set the request in the monitor to red manually. 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. The same result occurs when the contents of the DeltaQueue are listed via the detail display. If you need to repeat the last load for certain reasons. In this state. Q) The extract structure was changed when the DeltaQueue was empty. if the records remain in the table for a longer period of time with status EXECUTED. 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. Afterwards new delta records were written to the DeltaQueue.

A) If I understand your requirement correctly. 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. correct reading is guaranteed in most cases. you should at least make sure that the data are fetched from all connected BWs as quickly as possible. To avoid memory problems. We recommend. the DeltaQueue must be emptied by several successive DeltaRequests.Part . the frequency should not be higher than one DeltaRequest per hour. If the limit is observed. If the number of LUWs cannot be reduced by bundling application transactions. however . SAP BW Important Interview Questions Paper. 100 Mbytes per LUW should not be exceeded). But for other. which is the date on which the data load has taken place. BW-specific. in the Logistics Cockpit).g. We load data from PSA if it is already in PSA. As a rule. however. . e. reasons.4 Q) I would like to display the date the data was uploaded on the report. a program-internal limit ensures that never more than 1 million LUWs are read and fetched from the database per DeltaRequest. If it is so. We can copy from other infoobject if it is same. If this limit is reached within a request. both the number of LUWs is important and the average data volume per LUW. you want to display the date on which data was loaded into the data target from which the report is being executed.which is of no practical importance. This displays the relevance of data field. Usually.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 . When estimating "smooth" limits. configure your workbook to display the text elements in the report.or the restrictions regarding the volume and number of records in a database table). That limit is of rather small practical importance as well since a comparable limit already applies when writing to the DeltaQueue. Is there any easy way to include this information on the report for users? So that they know the validity of the report. Q) Can we filter the fields at Transfer Structure? Q) Can we load data directly into infoobject with out extraction is it possible. 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. we load the transactional data nightly. Yes. 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.

a) VPN.Virtual Private Network. Q) IF ANY TRASACTION CODE LIKE SMPT OR STMT. 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) HOW CAN U GET THE DATA FROM CLIENT IF U R WORKING ON OFFSHORE PROJECTS.6B) these Tcodes don't exist! Q) WHAT IS TRANSACTIONAL CUBE? .0B and R/3 4. THROUGH WHICH NETWORK. In current systems (BW 3. WEEKLY AND MONTHLY.Q) HOW MANY DAYS CAN WE KEEP THE DATA IN PSA. 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. IF WE R SHEDULED DAILY. Q) THERE is one ODS AND 4 INFOCUBES. WE SEND DATA AT TIME TO ALL CUBES IF ONE CUBE GOT LOCK ERROR. a) We can set the time. 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) I am not able to access a node in hierarchy directly using variables for reports.0B onwards. "If the open order quantity was 0" You have to think also in before and after images in case of a delta upload. When I am using Tcode RSZV it is giving a message that it doesn't exist in BW 3. the transactional InfoCube was developed to meet the demands of SAP Strategic Enterprise Management (SEM). Loop at all the records and delete the record that has the condition. meaning that. data is written to the InfoCube (possibly by several users at the same time) and re-read as soon as possible. Standard InfoCubes are technically optimized for read-only access and for a comparatively small number of simultaneous accesses. I've tried using the 0recordmode but that doesn't work. Standard Basic cubes are not suitable for this. if I run a report for month range 01/2004 . A) Yap. it's possible in the Query Designer (BEx) itself. Instead.10/2004 then monthly value is actually divide by the number of months that I selected.A) Transactional InfoCubes differ from standard InfoCubes in that the former have an improved write access performance level. you can do it.0B only. 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. From 3. for an example. Also.0 and it is embedded in BEx. 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. Q) Wondering how can I get the values. 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 . Create a start routine in Update rule. Just right click on the InfoObject for which you want to use as variables and precede further selecting variable type and processing types. 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. In that case you may delete the change record and keep the old and after the change the wrong information. 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.

which was already uploaded. by using delta extractors the data that has already been scheduled will not be uploaded again. 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). If I am correct... In the transfer structure you just click on the yellow triangle behind a characteristic and choose "routine". A)? Q) In BW we need to write abap routines. Say for a specific scenario. are these routines written in update rules? I will be glad. I wish to know when and what type of abap routines we got to write..workbench" in it runs for minutes. Sales. I would like to clarify a doubt regarding Delta extractor. Q) I am very new to BW. I hope this helps. Now I have uploaded all the sales order created till yesterday into the cube. 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. Now say I make changes to any of the open record. Also. 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 . 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. 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. In the update rules you can choose "start routine" or click on the triangle with the green square behind an individual characteristic.

In BW. The transactional ODS object simply consists of a table for active data.or delete. They are made available for reporting immediately after being loaded. The transactional ODS object is also required by diverse applications. The advantage to the way it is structured is that data is easy to access. For implementation. (change log) modified). time.APIs. The loading process is not supported by the BW system. data is stored in precisely the same form in which it was written to the transactional ODS object by the application. such as SAP Strategic Enterprise Management (SEM) for example. Instead. compare with the Transactional ODS Object. active. Standard ODS Object Transactional ODS object: The data is immediately available here for reporting. It offers no replacement for the standard ODS object. unit & data packet) dimensions. It retrieves its data from external systems via fill. you can use a transaction ODS object as a data target for an analysis process. Q) What does InfoCube contains? A) Each InfoCube has one FactTable & a maximum of 16 (13+3 system defined. Q) What does FACT Table contain? A FactTable consists of KeyFigures. . In a standard ODS object. data is stored in different versions ((new) delta. This data can be evaluated using a BEx query. Therefore. as well as other external applications. A transactional ODS object differs from a standard ODS object in the way it prepares data. data is written to the ODS object (possibly by several users at the same time) and reread as soon as possible. an additional function displays those that can be used for special applications. that is. The data from this kind of ODS object is accessed transactionally. for example) on the document (atomic) level. Transactional ODS objects allow data to be available quickly.data (transaction data or master data. where as a transactional ODS object contains the data in a single version.

Dimension can contain up to 248 freely available characteristics. texts. surrounded by dimensional tables and the dimension tables contains of master data. Q) As to where in BW do you go to add a character like a .Each Fact Table can contain a maximum of 233 key figures. medium text & language key if it is language dependent Q) What does Hierarchy table contain? Master hierarchy data Q) What is the advantage of extended STAR Schema? Q). unit & data packet]) Q) What does SID Table contain? SID keys linked with dimension table & master data tables (attributes. (13 user defined & 3 system pre-defined [time. text & hierarchy. In Extended Schema the dimension tables does not contain master data. Differences between STAR Schema & Extended Schema? A) In STAR SCHEMA. long text. hierarchies) Q) What does ATTRIBUTE Table contain? Master attribute data Q) What does TEXT Table contain? Master text data. Masterdata tables are independent of Infocube & reusability in other InfoCubes. short text. . # so that BW will accept it. Q) How many dimensions are in a CUBE? A) 16 dimensions. instead they are stored in Masterdata tables divided into attributes. A FACT Table in center. These Masterdata & dimensional tables are linked with each other with SID keys.

Q) What are the extra fields does PSA contain? A) (4) Record id. Hierarchies). Q) How would we delete the data in ODS? A) By request IDs. A) Check transaction SPRO ---Then click the "Goggles"-Button => Business Information Warehouse => Global Settings => 2nd point in the list. Text. . It's possible only for Cube. Selective deletion & change log entry deletion. (when created)? Q) When are Dimension ID's created? A) When Transaction data is loaded into InfoCube. I hope you can use my "Guide" (my BW is in german. Q) Does data packets exits even if you don't enter the master data.This is transaction data which loads fine in the PSA but not the data target. Q) Why partitioning? A) For performance tuning. Q) How would we delete the data in change log table of ODS? A) Context menu of ODS â ' Manage â ' Environment â ' change log entries. Q) When are SID's generated? A) When Master data loaded into Master Tables (Attr. so i don't know all the english descriptions). Data packet Q) Partitioning possible for ODS? A) No.

Currency attributes. Time dependent attributes. Q) Transitive Attributes? A) Navigational attributes having nav attrthese nav attrs are called transitive attrs Q) Navigational attribute? A) Are used for drill down reporting (RRI). Q) Different types of Attributes? A) Navigational attribute. Q) Compounding attribute? A)? Q) Time dependent attributes? A)? Q) Currency attributes? A)? Q) Authorization relevant object.Q) Have you ever tried to load data from 2 InfoPackages into one cube? A) Yes. Why authorization needed? . Compounding attributes. Q) Display attributes? A) You can show DISPLAY attributes in a report. Transitive attributes. Q) How does u recognize an attribute whether it is a display attribute or not? A) In Edit characteristics of char. Display attributes. on general tab checked as attribute only. which are used only for displaying.

* Assign InfoSources. (R/3) * InfoPackage for Delta uploads. Q) Steps in LIS are Extraction? A) Q) Steps in LO are Extraction? A) * Maintain extract structures. (R/3) * Replicate DataSource in BW. (R/3) * InfoPackage for the Delta initialization. Q) Steps in FlatFile Extraction? . * Maintain communication structures/transfer rules. (R/3) * Maintain DataSources. (R/3) * Delete setup tables/setup extraction. * Set-up periodic V3 update. * Activate extract structures. Q) How do we load the data if a FlatFile consists of both Master and Transaction data? A) Using Flexible update method while creating InfoSource. * Maintain InfoCubes & Update rules.A)? Q) How do we convert Master data InfoObject to a Data target? A) InfoArea â ' Infoprovider (context menu) â ' Insert characteristic Data as DataTarget.

Maintain DataSources. . * Activating Updates. Queued Delta: .TCode for LIS.Delete set-up tables in LO's. Q) LBW0 --. * Maintaining DataSources. Direct Delta: .Extract checker. as in the V3 update. Unserialized V3 Update. Q) RSA6 --. Q) What does LO Cockpit contain? A) * Maintaining Extract structure. Each document posting with delta extraction becomes exactly one LUW in the corresponding Delta queue.Fill Set-up tables. * Controlling Updates.With every document posted in R/3. Q) RSA7 ---.Delta Queue (allows you to monitor the current status of the delta attribute) Q) RSA3 ---. Q) LBWG --. Serialized V3 update. Q) OLI*BW --.The extraction data from the application is collected in extraction queue instead of as update data and can be transferred to the BW delta queue by an update collection run. the extraction data is transferred directly into the BW delta queue.A) ? Q) Different types in LO's? A) Direct Delta. Queued Delta.

Selective deletion & change log entry deletion. Q) MC21 ----. Change or Delete the InfoCube.Role maintenance. Text. Q) RSDCUBEM --. SAP BW Important Interview Questions Paper.Changeability of the BW namespace.5 Q) Does data packets exits even if you don't enter the master data. Q) How would we delete the data in change log table of ODS? . assign users to these roles. Q) How would we delete the data in ODS? A) By request IDs. Hierarchies). Q) MC24 ---.TCode for Logistics extractors.Creating Updating rules for LO's.Data packet characteristics maint.For Delete. Q) RSD5 -.Creating user-defined Information Structure for LIS (It is InfoSource in SAP BW).Part .Q) LBWE ---. (when created)? Q) When are Dimension ID's created? A) When Transaction data is loaded into InfoCube. Q) SE03 -.Maintaining Generic DataSources. Q) When are SID's generated? A) When Master data loaded into Master Tables (Attr. Q) RSO2 --. Q) PFCG ---.

It's possible only for Cube. Compounding attributes. Q) Have you ever tried to load data from 2 InfoPackages into one cube? A) Yes. Display attributes. Currency attributes. Transitive attributes. Q) How does u recognize an attribute whether it is a display attribute or not? . which are used only for displaying. Q) Display attributes? A) You can show DISPLAY attributes in a report. Q) Transitive Attributes? A) Navigational attributes having nav attrthese nav attrs are called transitive attrs Q) Navigational attribute? A) Are used for drill down reporting (RRI).A) Context menu of ODS â ' Manage â ' Environment â ' change log entries. Q) What are the extra fields does PSA contain? A) (4) Record id. Q) Different types of Attributes? A) Navigational attribute. Data packet Q) Partitioning possible for ODS? A) No. Time dependent attributes. Q) Why partitioning? A) For performance tuning.

Why authorization needed? A)? Q) How do we convert Master data InfoObject to a Data target? A) InfoArea â ' Infoprovider (context menu) â ' Insert characteristic Data as DataTarget. (R/3) * Replicate DataSource in BW. Q) How do we load the data if a FlatFile consists of both Master and Transaction data? A) Using Flexible update method while creating InfoSource. Q) Steps in LIS are Extraction? A)? Q) Steps in LO are Extraction? A) * Maintain extract structures. Q) Compounding attribute? A)? Q) Time dependent attributes? A)? Q) Currency attributes? A)? Q) Authorization relevant object. (R/3) * Maintain DataSources. on general tab checked as attribute only.A) In Edit characteristics of char. .

Each document posting with delta extraction becomes exactly one LUW in the corresponding Delta queue. as in the V3 update. . * Maintaining DataSources.With every document posted in R/3. Unserialized V3 Update. (R/3) * InfoPackage for the Delta initialization. Q) What does LO Cockpit contain? A) * Maintaining Extract structure. * Controlling Updates. Queued Delta. the extraction data is transferred directly into the BW delta queue. * Maintain InfoCubes & Update rules. Serialized V3 update.* Assign InfoSources. * Activating Updates. Q) Steps in FlatFile Extraction? A)? Q) Different types in LO's? A) Direct Delta. * Maintain communication structures/transfer rules. * Activate extract structures. * Set-up periodic V3 update. (R/3) * Delete setup tables/setup extraction.The extraction data from the application is collected in extraction queue instead of as update data and can be transferred to the BW delta queue by an update collection run. (R/3) * InfoPackage for Delta uploads. Direct Delta: . Queued Delta: .

TCode for Logistics extractors.Creating user-defined Information Structure for LIS (It is InfoSource in SAP BW).Q) RSA6 --. Q) SE03 -. Q) RSDBC . Q) LBWE ---. Change or Delete the InfoCube.Data packet characteristics maint.Delete set-up tables in LO's.Delta Queue (allows you to monitor the current status of the delta attribute) Q) RSA3 ---.Changeability of the BW namespace. Q) RSDCUBEM --.Extract checker.Maintain DataSources. Q) RSD5 -. Q) RSO2 --. Q) LBWG --.TCode for LIS.Maintaining Generic DataSources. Q) MC21 ----. assign users to these roles. Q) PFCG ---.Role maintenance. Q) RSA7 ---.Creating Updating rules for LO's. Q) LBW0 --. Q) OLI*BW --.For Delete.Fill Set-up tables. Q) MC24 ---.DB Connect .

Report to Report interface (RRI). Q) RSMONMESS -. Q) RSRT -. Q) SPRO -.Finding for modes of records (i.e. Q) RSCUSTV6 -.Definition . Q) RODELTAM .Table to find out delta update methods.Character permit checker. Q) SM37 .Partitioning of PSA. Q) RSRV . Q) RSKC -. Q) RSDDV .Open Hub Service: Create InfoSpoke.Query monitor. Q) ROOSOURCE .Maintaining Aggregates.Q) RSMO --.IMG (To make configurations in BW).Scheduling Background jobs. before image & after image) Q) SMOD .Monitoring of Dataloads.BEx Analyzer Q) RSBBS ."Messages for the monitor" table.Checking ShortDump.Analysis and Repair of BW Objects Q) RRMX . Q) RSBOH1 -. Q) ST22 .

Data Target Administration. Reporting agent & Other BW services. here we specify when should the process chain start by giving date and time or if you want to start immediately Some of theses processes trigger an event of their own that in-turn triggers other processes. .ABAP Dictionary Q) SE09 . There should be min and max one start variant in each process chain. Q) What are Process Types & Process variant? A) Process types are General services.Implementation guide Q) Statistical Update? A) ? Q) What are Process Chains? A) TCode is RSPC.Start chain â ' Delete BCube indexes â ' Load data from the source system to PSA â ' Load data from PSA to DataTarget ODS â ' Load data from ODS to BCube â ' Create Indexes for BCube after loading data â ' Create database statistics â ' Roll-Up data into the aggregate â ' Restart chain from beginning. Load Process & subsequent processing. Ex: .Program Compare Q) SE11 . Process variant (start variant) is the place the process chain knows where to start.Transport Organizer (Extended View) Q) SBIW .Q) CMOD . Process chains nothing but grouping processes. is a sequence of processes scheduled in the background & waiting to be triggered by a specific event.Transport Organizer (workbench organizer) Q) SE10 .Project Management enhancing Q) SPAU .

Q) Difference between MasterData & Transaction InfoPackage? A) 5 tabs in Masterdata & 6 tabs in Transaction data. Init Delta Update & Delta Update. even if no master data exits for the data)? A) Because while loading the data it has to create SID keys for transaction data . Q) Why it takes more time while loading the transaction data even to load the transaction without master data (we check the checkbox. the extra tab in Transaction data is DATA TARGETS. Q) Types of Updates? A) Full Update. Q) For Full update possible while loading data from R/3? A) InfoPackage â ' Scheduler â ' Repair Request flag (check). This is only possible when we use MM & SD modules. Always Update data.Process variant (start variant) is the place the process type knows when & where to start.

Sign up to vote on this title
UsefulNot useful

Master Your Semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master Your Semester with a Special Offer from Scribd & The New York Times

Cancel anytime.