Claim Management Sap R/3 Pdf

SAP BW Powered by SAP HANAFor a tool which is known to give great insight in a business environment it is ironic that it is lacking information of one of its own key performance indicators. SAP BW has been a very successful platform for BI over the last 2. Almost from day one people have asked the question which areas use the most space on my databaseThis question has become increasingly important in recent years when customers are considering whether they are willing to pay a premium price for a HANA database. The reporting abilities on database usage were first introduced five years ago as part of the technical content reporting in BW 7. There are still some flaws with the database space usage reporting Setting up the technical content reporting is fiddly and needs looking after. It takes an expert to interpret the results and turn it into easy to understand reporting. It is incomplete, only showing the sizes of BW objects and not of any other objects of significant size which might be sitting in the same BW database Basis tables or other. The last point is the most important point. Claim Management Sap R/3 Pdf' title='Claim Management Sap R/3 Pdf' />Below is an example from a production system BWo. H which filled up much faster than was anticipated. The blue bars are part of standard business content reporting. Claim Management Sap R/3 Pdf' title='Claim Management Sap R/3 Pdf' />All SAP R3 Transaction Codes, Tables, Reports, complete ABAP dictionary list with descriptions httpvbautomation. INVENTORY20MGMTSAPTcodes,Tables. SAP Thought Leadership Paper Human Capital Management Document and Data Retention Compliance Understanding and Addressing the Costs, Risks, and Legal Pitfalls. The yellow bar is missing in the standard reports. If you think it is important to see this, keep reading and you find out how to get an instant, complete overview of database space usage with minimal effort. Icons/Karriere/Icon_Stellenanzeige.png' alt='Claim Management Sap R/3 Pdf' title='Claim Management Sap R/3 Pdf' />Latest trending topics being covered on ZDNet including Reviews, Tech Industry, Security, Hardware, Apple, and Windows. Figure 1 BWo. H filling up more quickly than expected Make sure to keep an eye on all objects and tables. Most organisations running BWo. H do not have the right tools to monitor HANA database usage, manage the database size effectively and plan for future growth in a cost effective way. In this blog I describe a first step in getting better insight in database space usage. This solution is based on a script which you can run instantly, without having to configure, develop or customize anything. Running this script will give insight in the as is situation. SAP-Trainer-resume-sample-2.jpg' alt='Claim Management Sap R/3 Pdf' title='Claim Management Sap R/3 Pdf' />If you want to effectively plan for future growth then you will need some means of getting insight in historic growth as well. In my next blog I will describe how you can build out the solution with minimum development effort to a full blown database size monitoring application which allows for trend reporting. The result of running this ad hoc SQL should look something like this and will be available at HANA speed Within seconds and without any system development Figure 2 Output of running the ad hoc script. How Much Do World Rally Drivers Earnings here. From here it is a small step to clear insight and cool visualisations. This data can then be used to create some visualisations which provide great insight. Below are a few examples Figure 3a Only 6 tables take up 5. Figure 3b Surprisingly, Cubes in blue dont take up much space. DSOs Orange do, as does Master Data Grey. Figure 3c There seems to be something wrong with housekeeping on Basis tables. The solution part 1 A SQL script. Just like any other database, HANA stores all the metadata about tables in its own dictionary tables. Dragon Nest Speed Hack Detection Utility. You can find out the size of, say, an active table of a DSO or a fact table in a cube if you know which dictionary tables to look at. You have to have some understanding about table partitioning, row and column stores, memory usage and disk space to interpret the results. Luckily SAP is helping you because HANA comes with extremely useful database views on top of the dictionary tables which makes it easier to get a complete overview of table sizes. When you understand these views, you have half the job done. The other half is understanding how BW objects relate to tables in the HANA database. BW objects use several tables and to understand how database space is used it is important to evaluate BW objects rather than individual tables. The script in this blog combines the different dictionary views to get a complete view of all tables and then applies some further logic to put the tables in their BW context. Together, this results in a complete breakdown of database space size usage by BW object. Step 1 The dictionary views. The four views below are used to get an overview of memory usage, disk allocation and other storage parameters for each table in HANA. These are all fully documented on help. Technology Platform SAP HANA Platform SAP HANA Platform Core SAP HANA SQL and System views reference System Views ReferenceTable Name. Description. TABLESAll available tables. MCSTABLESRuntime properties of column store tables. MRSTABLESRuntime properties of row store tables. MTABLEPERSISTENCESTATISTICSPersistence file storage statistics for all tables. Note I am pretty sure that I dont actually need to use TABLES in my script and the reason it is still there is just because I dont want to break my code dont fix it if it aint broken. Please feel free to share your cleaner version of the SQL in the comment section of this blog. The information I use from these views are just the basic storage parameters Size of memory in Total main, delta and history Size of memory in Delta Disk Size and record count. The SQL for is quite straight forward. The only thing to bear in mind is that tables can be partitioned, so you have to use a group by and aggregate the statistics. Step 2 The BW groupings. Somewhere deep down in BW there might be a table or a number of tables where the relationship between a table name and an object type Cube, DSO, Info. Object, etceterar can be found. If such table exists, I have not been able to find it. Instead, I use the well documented naming convention BW uses for its tables. The code I have posted here is complete for the systems where I have used it. It has the BICA for DSOs, BICFfor cubes and a lot more. If you happen to use a system which uses different components for example BPC then you might have to add some elements. Unfortunately, PSA and Change Log tables are defined with the same prefix BICB To distinguish between the two, I look for specific strings in the description. This makes it a bit more complex, the coding may vary if it there is bespoke development in different languages and ultimately there is a risk that a table is not correctly classified. It then ends up in the list as a PSA table instead of a Change Log table or the other way around, which I believe is just a minor inconvenience. Structure of the code. I have tried to keep the ad hoc SQL script simple and as a result it is a bit longer than strictly necessary. There is a bit of complexity in interrogating the table names to derive the object type, but apart from that the code is quite easy to read. The price you pay for this is that the code comes in three parts, linked together through a union. The way the code is cut up is as follows Union part 1 BW Objects assumed to always be column store tables. Union part 2 Non BW Objects, column store tables. Union part 3 Non BW Objects, row store tables. There is duplication of code, but the coding is a lot simpler to understand compared to a solution or at least my solution where everything is brought together in one statement. Step 3 Run the code I promised you a solution which would not require any development but there is a small tweak you will need to make to the code that I provide in this post, unless your BW system happens to sit in schema SAPNW1. Just do a find and replace of SAPNW1 with whatever schema name of your BWo.