The CDHDR and CDPOS table contains information related to changes of a specific entity. Using these tables you can track how many times the value of an entity has changed and especially to which value. Because the CDHDR and CDPOS tables contains alot of data it is advisable to restrict the table during data extraction.
Using a restriction on OBJECTCLASS you have the ability to only select those records related to a specific SAP entity for e.g. Sales Orders (VERKBELEG), Purchase Orders (EINKBELEG) or Handling Units (HANDL_UNIT). To determine which filter must be setup the table TCDOBT can be used. This table stores all object classes available in the system.
Tags: tables
Hidden InfoPackage monitor issue
This week I encountered an issue with the SAP GUI. When accessing the data load monitor of an InfoPackage I noticed that the request window wasn’t visible anymore. Luckily some of the SAP GUI specific settings are stored in SAP tables. This includes the width of the InfoPackage window.
The table which stores the InfoPackage monitor setting is called RSRADIOMON. For every known user a record is stored. As shown in the picture below the column THREEWIDTH is set to 29 which is resulting in a very small window. By changing the THREEWIDTH to a higher value (for e.g. 290) the InfoPackage monitor will be displayed in normal proportions again.
SAP tables related to transports
In some cases it might be interesting to know which SAP BW objects are attached to a specific transport for e.g. release management. Instead of copy and pasting object values mentioned in the SE10 transaction SAP tables can be used.
All information related to SAP transports is stored in E07* tables. An overview of these tables is shown below. Along with this information and this table overview you have the ability to compose an overview of objects (including their functional description) belonging to specific transport.
| Table | Description |
|---|---|
| E070 | Change & Transport System: Header of Requests/Tasks |
| E070A | Change & Transport System: Attributes of a Request |
| E070C | CTS: Source/Target Client of Requests/Tasks |
| E070CREATE | Change & Transport System: Creation Date of Request |
| E070CTV | Generated Table for View E070CTV |
| E070DEP | Change & Transport System: Dependencies of Requests |
| E070L | CTS: Index for Assigning Numbers to Requests/Tasks |
| E070M | CTS: Target Package/Layer for Requests |
| E070TC | Help Table for E070 for Client-Specific Imports |
| E070USE | Use of Current Requests by Users |
| E070V | Generated Table for View E070V |
| E071 | Change & Transport System: Object Entries of Requests/Tasks |
| E071C | Change & Transport System: Client-Specific Lock Flag |
| E071E | Lang. Transport: Positive List for Generic Object Selection |
| E071K | Change & Transport System: Key Entries of Requests/Tasks |
| E071KC | Change & Transport System: Key Entries of Requests/Tasks |
| E071KF | Change & Transport System: Nametab Info. on (CHAR)Key Fields |
| E071KFINI | Change & Transport System: Nametab Info. on (CHAR)Key Fields |
| E071K_30 | Change & Transport System: Key Entries of Requests/Tasks |
| E071K_KEY | E071K Key Fields |
| E071S | System-Specific Import Status of Objects |
| E071V | Generated Table for View E071V |
| E07T | Change & Transport System: Short Texts for Requests/Tasks |
| E07T_OLD | E07T Before TRKORR Extension |
Thanks to http://sapbasisanswers.blogspot.nl/ for supplying this helpful overview.
SAP Business Warehouse extractor and table analyzer
Building up a new dataflow can be very time-consuming, mainly when there is no data acquisition layer to extract data from. Setting up a proper data acquisition layer means considering which fields to extract towards the data warehouse system. Since not all fields of a table used in the source system it is advisable to first analyze which fields are useful. Extracting all fields results in empty and unused objects in the Data Warehouse system, which technically results in a bigger database.
In order to make everybody’s life easier I created the ABAP program “SAP Business Warehouse extractor and table analyzer”. This program can be used to analyze Business Content extractors (like 2LIS structures) or SAP tables.
Verify dimension sizes of InfoCubes
Maybe you are one of the lucky few who is currently working with BW on HANA and do not have to model InfoCubes anymore (from a performance perspective). But for those who still need to do this, ABAP program SAP_INFOCUBE_DESIGN could help you verify how well your InfoCubes are modelled in SAP Business Warehouse. This program collects data for every InfoCube in the BW system and counts the records available in the related dimension tables and fact table. The program then checks the ratio between the number of records in the dimension tables against the number of records in the fact table.
A ratio between 10% and 20% is considered as high cardinality and therefore indicated in red. In most cases you should avoid dimension tables larger than 10%. Of course this it all depends on how frequent the data is used in the mentioned dimension table. If possible use line item dimensions instead!
Note: The data which is used for this analysis comes from BW statistics, so be sure that if you want to analyze a specific InfoCube, statistics are created for it.
