Bw General

Huge Performance Problems on SAP BW 3.10. We have huge performance problems on SAP BW 3.10. (Oracle 9.2, AIX). Our users don't get the results of theirs queries, and they often have to log-off from sap when they use the bex analyzer . I have read the differents topics regarding this problem , and read the differents SAP notes. *The database statistics are refreshed every moring , after the data loads. (statistic for the fact table is always current, transaction db20) * Oracle Parameters are set according to SAP notes 632556. * Oracle indices are deleted and recreated every day * Fact table is partitioned * I have tried to change the read mode in RSRT but it didn't work I have checked the BW statistics (st03 and table RSDDSTAT). The database proportion is very high FOR ALL QUERIES (40 to 90%), and for the infocube (64%). The ratio of selected to transfered record is 397 for the infocube and for the queries : 270.000 to 30. We do not use aggregates and we do not use Cube compression. At first , I thought it was the reason of our problem but now I'm wondering If we do not have a database problem. Is there anyone who could give me some advice ? Further informations : Data Buffer Quality : 96,3 % I/O read times : Read (Avg ms) : 2 to 7 Write (Avg ms) :150 to 459 According to OSS note 443544 , IO timesbelow should be acceptable below 10 ms, but in BW only the read mode (queries performances) is important, right ? It looks like you are doing a great job tuning the database, an area I tend to neglect (as a non DBA BW consultant). However you say you are not using aggregates. I have to ask why? The fact you have a selected to transfered ration of 270,000 in some queries suggests having to read many base level records to produce a summary result. By using the BW server to summarise into aggregates at load time, generally a quiet time, you will reduce the amount of work it has to do at query time.

If you decide to use aggregates you can let BW design aggregates for you, in which case you get many aggregates based on navigations in statistics, or design a few levels yourself, which means you control the extra storage. I tend to create a summary level aggregate, and mid level aggregate and sometimes additional customer without material or material without customer aggregates. As you are using Oracle did you also know you can run an 'explain' on the SQL statement of a poorly performing query - run the query -> trans SM66 to find the Process ID (PID) of a the query -> trans ST04 -> detailed analysis -> oracle session -> select SQL text from DBA_VIEWS where PID -> use DBA tools to run an explain on the SQL statement. From this you may also find some areas for improvement. Not much to add to the above great answer: looks like you're a textbook example to use aggregates. In addition also have a look at compression: note 590370 explains the advantages you could get from it. The above note may mention this , but in order to reap the benefits of fact table partioning you need to compress your infocube. Database partioning works on the 'E' table within the infocube (not the 'F' fact table that hold the uncompressed data).

How to build an extractor? Using SAP BW 2.1C and soon 3.0A we have to extract data from R/3 FI. Standard extractor can´t be used, since data need to be enhanced and go throug various routines before data contains all information needed in BW. Delta upload mechanism is needed. Where can information on - building a new extractor (including delta mechanism) - enhancing a standard extractor be found? Technically, programming a function module data source would be a modification. There's also a way that allows you to stay close to the standard, especially if you extract data from standard tables: In OLTP: 1) Find out which change document object points to the table. 2) Use the generic extractor to build a data source for _master data_ over the table. 3) Use the "enhance extract structure" feature in the BW img to add computed fields to the data source 4) Use the user exit for extraction to program your enhancement logic and compute additional fields

5) In data source maintenance, enter the change document object to delta-enable the data source In BW: 7) Create an infoobject with attributes. (Key figures can be attributes, too.) Use concatenated keys or "Klammerung" to make the key fields identical to the key fields of your source table. 8) Create infopackages for initial load and delta load, and load data. Now you need to load the data from your infoobject into a data target for transactional data (ODS or InfoCube). In BW: 9) In infoobject maintenance, look up the view for master data for your new infoobject. 10) Use the generic extractor to create a generic datasource for transactional data out of this view. 11) Load data from this second generic extractor into your Cube/ODS. As far as I know, BW 3.0 will allow loading data straight from OLTP _master_data datasources into BW ODS/Cubes, so as soon as you've upgraded, steps 7 - 11 will be obsolete.

COPA Extraction Steps The below are the command steps and explanation. COPA Extraction -steps R/3 System 1. KEB0 2. Select Datasource 1_CO_PA_CCA 3. Select Field Name for Partitioning (Eg, Ccode) 4. Initialise 5. Select characteristics & Value Fields & Key Figures 6. Select Development Class/Local Object 7. Workbench Request 8. Edit your Data Source to Select/Hide Fields 9. Extract Checker at RSA3 & Extract BW 1. Replicate Data Source 2. Assign Info Source 3. Transfer all Data Source elements to Info Source 4. Activate Info Source 5. Create Cube on Infoprovider (Copy str from Infosource) 6. Go to Dimensions and create dimensions, Define & Assign 7. Check & Activate 8. Create Update Rules

9. Insert/Modify KF and write routines (const, formula, abap) 10. Activate 11. Create InfoPackage for Initialization 12. Maintain Infopackage 13. Under Update Tab Select Initialize delta on Infopackage 14. Schedule/Monitor 15. Create Another InfoPackage for Delta 16. Check on DELTA OptionPls r 17. Ready for Delta Load LIS, CO/PA, and FI/SL are Customer Generated Generic Extractors, and LO is BW Content Extractors. LIS is a cross application component LIS of SAP R/3 , which includes, Sales Information System, Purchasing Information System, Inventory Controlling.... Similarly CO/PA and FI/SL are used for specific Application Component of SAP R/3. CO/PA collects all the OLTP data for calculating contribution margins (sales, cost of sales, overhead costs). FI/SL collects all the OLTP data for financial accounting, special ledger 1) Add the fields to the operating concern. So that the required field is visible in CE1XXXX table and other concerned tables CE2XXXX, CE3XXXX etc. 2) After you have enhanced the operating concern then you are ready to add it to the COPA data source. Since CO-PA is a regenerating application you can't add the field directly to the CO-PA data source. You need to delete the data source and then need to re-create using KEB2 transaction. 3) While re-creating the data source use the same old name so that there won't be any changes in the BW side when you need to assign the data source to info-source. Just replicate the new data source in BW side and map the new field in info-source. If you recreate using a different name then you will be needing extra build efforts to take the data into BW through IS all the way top to IC. I would personally suggest keep the same old data source name as before. If you are adding the fields from the same "Operating concern" then goto KE24 and edit the dataaource and add your fields. However if you are adding fields outside the "Operating concern" then you need to append the extract structure and populate the fields in user exit using ABAP code. Reference OSS note: 852443 1. Check RSA7 on your R3 to see if there is any delta queue for COPA. (just to see, sometimes there is nothing here for the datasource, sometimes there is) 2. On BW go to SE16 and open the table RSSDLINIT 3. Find the line(s) corresponding to the problem datasource.

4. You can check the load status in RSRQ using the RNR from the table 5. Delete the line(s) in question from RSSDLINIT table 6. Now you will be able to open the infopackage. So now you can ReInit. But before you try to ReInit .... 7. In the infopackage go to the 'Scheduler' menu > 'Initialization options for the source system' and delete the existing INIT (if one is listed)

The query could not be saved due to a problem in transport Submitted by : Anil Contact Email : [email protected] After creating a query in BEX, you try and save the query, it gives you the following popup message: "The query could not be saved due to a problem in transport". Steps to correct the problem: 1. Within Adminstrator Workbench click on the Transport Connection tab in the Navigation Window on the left hand side. 2. Select the Request BEx button on the toolbar. 3. Create a transport. 4. Try to change the query again.

ODS infosource not showing up To display export infosources under the Infosource hierarchy you need to do the following : 1. Right click the tree at the highest level (Infosources node) and then choose Insert Lost Nodes. 2. Also make sure that under Settings under the menu options you have selected the option to display generated objects for ODS . By default the setting is set to hide objects.

And finally refresh your tree. You should be able to the infosources and the infopkgs. They might show up under Unassigned Nodes if you have not transferred the BW app component hierarchy in which case they show up under DM (Data Marts ) node.

Query View Workbook You formatted a query view ( By changing Fonts/column width etc ) and saved as workbook in your favorites in the Browser. When you execute the workbook thru the browser you get the format that has been saved. However, you loose the format when you click the Refresh Button. How to set permanent settings so that formatting remains same as has been designed in the workbook? You can do this :In Excel using BW, you have what I categorize as 2 different types of cells. You have "Excel" Cells and "BW" Cells. You can determine which you are in by selecting a cell and right mouse clicking. If you get the BW options (Drilldown, Swap, Insert.....) then you are in a BW Cell. If you get the standard (Cut, Copy, Paste) you are in the Excel Cells. If you are formatting an Excel Cell, Format using the option from the Excel Menu. If it is a BW Cell, Format using the option from the BW Toolbar (5th button from right). When you refresh you will retain your settings. Also, as a hint, you don't have to select all of your BW cells when formatting. Select a characteristic and format using the BW toolbar and all characteristics will format. Same goes for key figures, Free characteristics etc. BW uses the "BW Style Tool"to format. For more detail and customization follow the below steps: 1. Download OSS Note #300570. 2. On your machine Find / Execute SAPBEXS.XLA -> Click Enable Macros.

Stop a scheduled infopacket

-----Original Message----Subject: Stop a scheduled infopacket I have tried using SM50 to stop a process that has been running for quite sometime. How do I kill a scheduled infopacket. Thanks, -----Reply Message----Subject: RE: Stop a scheduled infopacket Hello select the Process and press F9. Or can kill the same from the OS level using the UNIX command kill -9 <processno>. Happy going.. -----Reply Message----Subject: RE: Stop a scheduled infopacket Kill the job on the R/3 side by using SM37 for ALEREMOTE.

BEX Query Authorizations -----Original Message----Subject: BEX Query Authorizations We are have authorization issues with Querries. We have created a generic Role that has some Standard Query's for our Company attached to this Role. We give access to this role to our user community. The problem we are having is that the users can Execute the querries and what they are suppose to do is only Save the Workbook to there favorites. We are running across a problem because some of the users are saving the workbook as existing workbook. So when they do this it wipes out the Query in that Role. How can I stop users from overlaying the MASTER Query. There has to be a way that you can protect a query so that it cannot be changed. Because we have generic querries that are being used throughout our company, I need to be able to protect the query so that it can only be saved to users Favorites. -----Reply Message----Subject: RE: BEX Query Authorizations We would appreciate anyones input that could help us with this authorization issue that we are having. Maybe if we could get input as to how other

Companies are handling there workbooks. There has to be a company that is having the same problems with Workbooks being overwritten. Any input would help -----Reply Message----Subject: RE: BEX Query Authorizations Hi, Unfortunately I haven't managed to restrict access to workbook depending on its menu location. Hey gurus, it would be great to know any more ideas... Best Regards, -----Reply Message----Subject: RE: BEX Query Authorizations Hi, We tried changing the role and are unable to overly the generic role. But we're unable to save a workbook to our favorites. Any ideas?? -----Reply Message----Subject: RE: BEX Query Authorizations Hello, Go to role maintenance (PFCG) -> Authorization -> Chanhe Authorization Data. Open Basis - General Functions -> BC-SRV-KPR-BDS and restrict the user activities set like "Display, Print, Retrieve from Archive, Determine, Assign". User with appropriate role could not be able to overwrite WORKBOOKS (!!!). As for QUERIES, address to Business Information Warehouse -> BEx - Components and restrict Activities retaled to Queries then users with appropriate role could not be able to overwrite GLOBAL DEFINITION of QUERY (!!!).

So, you can see, you need to restrict access to queries and workbooks separately.

SAP Console -----Original Message----Subject: SAPConsole Good Morning to all Can I use the standard SAPConsole for Inventory Management related transactions also. Examble: Movement 103 /105 etc. With Best Regards -----Reply Message----Subject: RE: SAPConsole Can you please explain me, What is a SAP Consule? -----Reply Message----Subject: RE: SAPConsole Dear: SapConsole is a standard SAP tool which was offered as of 46B (but is backwards compatible to earlier releases) which translates GUI screens into the Character based screens that are used with most handheld Radio Frequency devices used in Warehouses. Beginning in 46B, SAP provided standard transactions which could be used in Warehouse Management, specifically designed to be used with Radio Frequency devices. As far as I know the only one that touches IM, allows a Goods Reciept based on an Inbound Delivery number. To my knowledge, the Inbound Delivery process is not being used very widely. It is possible to design own transactions or to hire a systems integrator that has already designed them, which will allow wireless processing of IM Movements. This would be outside of the current SAP standard.

Delete unwanted Objects in QA system I have deleted unwanted Update rules and InfoSources (that have already been transported to QA system) in my DEV system. How do I get them out of my QA system? I cannot find the deletions in any transports that I have created. Although

they could be buried somewhere. Any help would be appreciated. I had the same problem with you. And I have been told there is a way to delete the unwanted objects. You may request the Basis team to open up test box temporarily to remove the obsolete Update rules and InfoSources. Remember to delete the request created in test after you have removed the Update rules and InfoSources. When I tried to delete the master data, get the following message"Lock NOT set for: Deleting master data attributes". What I need to do in order to allow me can delete the master data. Since, technically, the master data tables are not locked via SAP locks but via a BWspecific locking mechanism, it may occur in certain situations, that a lock is retained after the termination of one of the above transactions. This always happens if the monitor no longer has control, for example in the case of a short dump. If the monitor gets the control back after an update termination (regular case), it analyzes whether all update processes (data packets) for a request have been updated or whether they have terminated. If this is the case, the lock is removed. Since the master data table lock is no SAP lock, this can neither be displayed nor deleted via Transaction SM12. There is an overview transaction in the BW System, which can display and delete all currently existing master data table locks. Via the button in the monitor with the lock icon or via Transaction code RS12 you can branch to this overview. A maximum of two locks is possible for each basis characteristic: Lock of the master data attribute tables Lock of the text table Changed by, Request number, Date and Time is displayed for every lock. Furthermore, a flag in the overview shows whether locks have been created via master data maintenance or master data deletion. During a loading process the first update process starting to update data into the BW System (several processes update may update in parallel for each data request), sets the lock entry. All other processes only check whether they belong to the same data request. The last process, which has either been updated or has terminated, causes the monitor to trigger the deletion of the lock.

LO Cockpit Step By Step Here is LO Cockpit Step By Step

LO EXTRACTION - Go to Transaction LBWE (LO Customizing Cockpit) 1). Select Logistics Application SD Sales BW Extract Structures 2). Select the desired Extract Structure and deactivate it first. 3). Give the Transport Request number and continue 4). Click on `Maintenance' to maintain such Extract Structure Select the fields of your choice and continue Maintain DataSource if needed 5). Activate the extract structure 6). Give the Transport Request number and continue - Next step is to Delete the setup tables 7). Go to T-Code SBIW 8). Select Business Information Warehouse i. Setting for Application-Specific Datasources ii. Logistics iii. Managing Extract Structures iv. Initialization v. Delete the content of Setup tables (T-Code LBWG) vi. Select the application (01 – Sales & Distribution) and Execute - Now, Fill the Setup tables 9). Select Business Information Warehouse i. Setting for Application-Specific Datasources ii. Logistics iii. Managing Extract Structures iv. Initialization v. Filling the Setup tables vi. Application-Specific Setup of statistical data vii. SD Sales Orders – Perform Setup (T-Code OLI7BW) Specify a Run Name and time and Date (put future date) Execute - Check the data in Setup tables at RSA3

- Replicate the DataSource Use of setup tables: You should fill the setup table in the R/3 system and extract the data to BW - the setup tables is in SBIW - after that you can do delta extractions by initialize the extractor. Full loads are always taken from the setup tables

Differences Among Query, Workbook and View Many people are confused by the differences among: Query, Workbook, and View. Here are my thoughts on the subject: A query definition is saved on the server. Never anywhere else. Although people say a workbook contains a query (or several queries); it does not. It contains a reference to a query. The workbook can be saved on the server; or anywhere else that you might save an Excel workbook. What happens if someone changes the query definition on the server? Answer: the next time you refresh the query in the Excel workbook, the new query definition replaces the old query definition in the workbook. Maybe. It depends on what change was made. For example, if someone added a Condition to the query definition, the workbook will be virtually invisible to this. The Condition is available; but, is not implemented in the workbook. (Until the user of the workbook manually adds the view of the Condition and then activates it.) For example, if someone changed the definition of a KF in the query definition, the revised KF will show up in place of the old KF in the workbook. But ... if, for example, someone deleted the old KF and added a new KF, we get a different story. Now the old KF no longer appears (it does not exist); but, the new KF does not appear (it was not marked to be visible in the workbook). About workbooks as views ... OK, a workbook may very well have a certain "view" of the query (drilldown, filters, et cetera). And, if the workbook is saved to the server in a Role where everyone can access it, this is good. But, if the workbook is saved to one's favorites, then this "view" is only accessible to that individual. Which may be good. Or may not. A "saved view", on the other hand is stored on the server. So, it is available to all.

If you navigate in a workbook you can back up. You can back up, though, only as far as you navigated in the current session. You cannot back up to where you were in the middle of last week's session. Unless you saved that navigation state as a "saved view". Then, you can jump to that view at any time. The downside of saved views is that they are easy for anyone to set up and difficult for most to delete.

Customer Exit Variable In Bex The customer exit works at: 1. Extraction side After enhancing datasource in RSA6 we need to populate those enhanced fields in that case we have to create a project in cmod transaction and select the Enhancement assignment RSAP0001 and select the appropriate FM and need to write the select statement in the appropriate include. EXIT_SAPLRSAP_001 - Transaction data EXIT_SAPLRSAP_002 - Master data EXIT_SAPLRSAP_003 - Text EXIT_SAPLRSAP_004 - Hierarchy The above things we need to do in Source System side Ex: R/3 2. Reporting side We need to write the user-exit to populate Reporting related variables in the Enhancement assignment RSR00001 and select the FM EXIT_SAPLRRS0_001 and then in the include ZXRSRU01 we need to write the code. These are helpful especially we need to derive any varible. Along with that: BEx User Exit allows the creation and population of variables and calculations for key figures and variables on a runtime basis. R/3 User Exit is found in R/3 under CMOD and contains additional programming that is needed to fill field additions to extract structures.

What Are Routines and Transfer What are routines? are Transfer/Update rules and routines one and the same? Routines are like conditions or business rules that could be applied to filter the data while entering the BW system or could be used to apply certain conditions on the info objects itself.

There are 4 types of routines 1. Start routine- Could be used at two levels (transfer rule level and the Update rule level) This Start routine written at the transfer rule level helps filter the necessary data coming from the source system. For Example: If you decide to extract data that contain only quantity greater than 500 , then you could specify the Start rouitne to achieve this. The Start routine at the Update rule level provides similar functionality but at this point it helps direct specific data to different data targets. For Example: If there 3 data targets being fed from the Infosource, you may want to apply some condition to each data target, like send year 2000 data ti Data target1, 2001 to data target 2 and so on. This can be achieved by using Start routine at the Update rule level 2. Transfer Routine: This feature is available at the transfer rule levels While performing the transfer rules operation, there are 4 features available to the developers to create business rules on top pf the Infoobjects. 1. You could do a one to one mappping of the Infoobject 2. Provide a constant value 3. Include a formula 4. Write an ABAp routine. These 4 options refers to the transfer routine 3. Update Routine: The limitations of just having 4 options in the transfer routine is overcome at the update rule level. There are various other sophisticated features avaialable apart from the 4 options mentioned above. These business rules could be specified pertaining to each data target. 4. Conversion Routine: It provides functionality to do Currency and unit conversion.

What Is SEM and BPS What is sem & bps? Where and why we use those in relation to sap-bw? Business Planning (BW-BPS) enables you to produce planning applications. You can either develop your own planning application or use the Business Content delivered by SAP. The area of application stretches from simple data input through to complex scenarios with data extraction, automatic planning preparation, manual data input, controlling the planning process, and retracting plan data. The architecture of BW-BPS is

structured so that you are able to implement simple scenarios without great effort but are equally able to build sophisticated business-wide planning processes. Strategic Enterprise Management - Business Planning and Simulation (SEM-BPS) is SAP's new dimension product focusing on Financial Planning. It is intended to replace all financial planning functionality that exists within R/3. SEM-BPS is a BW (Business Warehouse) based application which allows for multi-dimensional planning, complex calculation programming, etc. It allows for multiple types of front-ends. Two of the biggest are the MS Excel front-end and Web enabled planning folders and layouts. SEM-BPS is a planning system, in which you can record and evaluate aggregated plan data. It is suitable for the collection and maintenance of data from the various functional plan sections in one uniform view. Business Planning (SEM-BPS) enables you to produce a group-wide strategic business plan. The business plan adds an overall plan to the detailed plans that have been put together using the transaction systems' components. The aim of strategic business planning is to produce a consistent and realistic plan from various perspectives. The plan should improve the efficiency of the enterprise and the management process. Here, the issue is – in contrast to the operational subplans – less the level of detail, but rather planning the enterprise's development over the longer term. SEM-BPS supports Web-based planning with the help of planning applications and a Status and Tracking System. With these means you can also form planning scenarios in companies with many different branches in different locations, though the technical administrative effort is limited to the availability of an internet connection. You carry out manual planning using planning layouts. You can configure these planning layouts as you wish. Here, you can use the characteristics and key figures from the data basis, and you can also define formulas for locally-calculated key figures. The planned data is saved bottom-up, which means that data from a lower level is aggregated to the next highest level. The SEM-BPS planning applications are used to solve standard tasks of business planning, for example balance sheet or profit planning, with as little configuration work possible. BW Query Performance Question: 1. What kind of tools are available to monitor the overall Query Performance? Answers: o BW Statistics o BW Workload Analysis in ST03N (Use Export Mode!) o Content of Table RSDDSTAT

Question: 2. Do I have to do something to enable such tools? Answer: o Yes, you need to turn on the BW Statistics: RSA1, choose Tools -> BW statistics for InfoCubes (Choose OLAP and WHM for your relevant Cubes) Question: 3. What kind of tools are available to analyse a specific query in detail? Answers: o Transaction RSRT o Transaction RSRTRACE Question: 4. Do I have a overall query performance problem? Answers: o Use ST03N -> BW System load values to recognize the problem. Use the number given in table 'Reporting - InfoCubes:Share of total time (s)' to check if one of the columns %OLAP, %DB, %Frontend shows a high number in all InfoCubes. o You need to run ST03N in expert mode to get these values Question: 5. What can I do if the database proportion is high for all queries? Answers: Check: o If the database statistic strategy is set up properly for your DB platform (above all for the BW specific tables) o If database parameter set up accords with SAP Notes and SAP Services (EarlyWatch) o If Buffers, I/O, CPU, memory on the database server are exhausted? o If Cube compression is used regularly o If Database partitioning is used (not available on all DB platforms) Question: 6. What can I do if the OLAP proportion is high for all queries? Answers: Check: o If the CPUs on the application server are exhausted o If the SAP R/3 memory set up is done properly (use TX ST02 to find bottlenecks)

o If the read mode of the queries is unfavourable (RSRREPDIR, RSDDSTAT, Customizing default) Question: 7. What can I do if the client proportion is high for all queries? Answer: o Check whether most of your clients are connected via a WAN Connection and the amount of data which is transferred is rather high. Question: 8. Where can I get specific runtime information for one query? Answers: o Again you can use ST03N -> BW System Load o Depending on the time frame you select, you get historical data or current data. o To get to a specific query you need to drill down using the InfoCube name o Use Aggregation Query to get more runtime information about a single query. Use tab All data to get to the details. (DB, OLAP, and Frontend time, plus Select/ Transferred records, plus number of cells and formats) Question: 9. What kind of query performance problems can I recognize using ST03N values for a specific query? Answers: (Use Details to get the runtime segments) o High Database Runtime o High OLAP Runtime o High Frontend Runtime Question: 10. What can I do if a query has a high database runtime? Answers: o Check if an aggregate is suitable (use All data to get values "selected records to transferred records", a high number here would be an indicator for query performance improvement using an aggregate) o Check if database statistics are update to data for the Cube/Aggregate, use TX RSRV output (use database check for statistics and indexes) o Check if the read mode of the query is unfavourable - Recommended (H)

Question: 11. What can I do if a query has a high OLAP runtime? Answers: o Check if a high number of Cells transferred to the OLAP (use "All data" to get value "No. of Cells") o Use RSRT technical Information to check if any extra OLAP-processing is necessary (Stock Query, Exception Aggregation, Calc. before Aggregation, Virtual Char. Key Figures, Attributes in Calculated Key Figs, Time-dependent Currency Translation) together with a high number of records transferred. o Check if a user exit Usage is involved in the OLAP runtime? o Check if large hierarchies are used and the entry hierarchy level is as deep as possible. This limits the levels of the hierarchy that must be processed. Use SE16 on the inclusion tables and use the List of Value feature on the column successor and predecessor to see which entry level of the hierarchy is used. - Check if a proper index on the inclusion table exist Question: 12. What can I do if a query has a high frontend runtime? Answers: o Check if a very high number of cells and formattings are transferred to the Frontend ( use "All data" to get value "No. of Cells") which cause high network and frontend (processing) runtime. o Check if frontend PC are within the recommendation (RAM, CPU Mhz) o Check if the bandwidth for WAN connection is sufficient