Copy Queries(RSZC) across infoproviders which are slightly differentetwork Blogs. Copying queries across infoproviders which is done using RSZC is a well discussed topic and available on help.sap.Similary, copying queries across infoproviders which are not alike is a widely discussed topic too.Some of the solutions for this are as below:
Summary of BI 7.0 performance improvements. I just want to give you an overview and not go into deep details or exact instructions.
Just wanna give you some points from where you can start your analyze and tune your system. You should try out all the tables, views and transactions by yourself. Performance issues in summaryQuery performance analyse Cache monitorST03nST13ST14StatisticsST02BW Administration CockpitOptimizing performance of InfoProvidersILM (Information Lifecycle Management)BWAQuery analyzing exampleHow Oracle 11g affects BW performanceGeneral Hints 1. The common reasons for performance issues in summary.
Why Attribute Change Run in SAP BI 7.0 i. Scenario In SAP BI 7.0, we often require a sub set of data to be accessed from Info cube.
So, in this case we need to create smaller sets of data from the larger info cube. How to create a new Factory Calendar in. This blog describes about the requirement to run the process chains on specific days of the week.
For example, if you want to run finance process chain only for 6 days of the week and would not like to run finance process chain on saturday of the week, you should be able to achieve this by following this blog. Step by Step Procedure: Step 1) Creating a new Factory Calendar to run only on Monday, Tuesday, Wednesday, Thursday, Friday and not on Saturday. Step 2) Go to SCAL transaction in R/3 system and click the Factory calendar radio button and click on change. Step 3) Click on Create Icon and then name the new Factory calendar Step 4) Go to BW system and Source system and right click on the source system and transfer global settings Step 5) Follow the next step. Why is Oracle writing out so many archivelogs in m.
Sometimes support messages have go a rather long way to finally get a solution.
The following problem came up in a support message recently and since neither the analysis steps nor the solution were obvious, I decided to make a blog out of it. Ok, so the problem statement was something like this: "Hello support,we're using SAP BI and recently re-initialized some of our datasources.From then on, our Oracle database writes out Archivelogs at a rate 4 times higher than before.What's causing this and how can we stop it? "
How to enhance CRM specific DataSource (0CRM_SALES_ORDER_I) There are a lot of topics on DataSource enhancement, all about R/3, generic DataSource, or table/view. Once I have to enhance the CRM order item DataSource, I dig a while. I can explain the theory by the following diagram. We have enhanced the table CRMD_ORDERADM_I. First, enhance the extract structure in RSA6. Then, go to BWA1, add a line in Mapping. Now we need to implement it. * Define internal table for the extract structure. * The type of the Structure is visible in transaction RSA6. * Also the enhancement of the extract structure will be done. SAP BW Indexing Scheme (ORACLE) <body>Definition: Indices are pointers which speed up the data retrieval process significantly.
In its absence the performance can take a severe beating by doing a Full table scan. The Schema<br />BW uses two fact tables per InfoCube - the "F-fact table" (request packages with ids > 0) and the "E-fact table" (consolidated request package with id=0). HowTo restrict F4 Help Values for hierarchies in Bex variable screen. I read recently some great articles about the new enhancement framework from Thomas Weiss.
You can find the series in the SDN wiki here. I got an idea, how easy it is to extend SAP classes or function modules for customers without making modifications! Network Blog: How to Debug InfoPackages in BW. Debugging DTPs is very easy.
There is an option in the Execute tab of the DTP that allows you to execute it in a Dialog Process and debug it (screen-shot). A Tour of the DBA Cockpit: Overview. Currently Being Moderated The DBA Cockpit is an SAP tool for managing the underlying databases.
Initially developed jointly by IBM and SAP for managing DB2 databases, it has been expanded to encompass all SAP-supported database platforms, and is designed to be a central point for database administration tasks and monitoring. A Treatise on Logistics Data Extraction for Business Information. BI Master Data Partitioning. Size of master data can be as large as 40 millions or even more.
One of our Utility Client has ~ 6 millions of master data records. This master data has 90 attributes making the table size really huge. We faced issue while activating the master data. The load was failing every time while activation. DataStore Objects for Direct Update. DataStore Object - DataStore Object is used to store consolidated and cleansed transaction data in transparent, flat database tables. DataStore Object Types:1) Standard DataStore Object2) Write-Optimized DataStore Object3) DataStore Object for Direct Update.