Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA (Application Component) Cross-Application Components⤷
ARCH_IMG (Package) Data Archiving Guide and Corresponding Tools
IMG Activity
| ID | ARCH_IMG_TABANALYSIS | Table Analysis |
| Transaction Code | S_ALR_87100564 | (empty) |
| Created on | 19991007 | |
| Customizing Attributes | ARCH_IMG_DEFAULT | Default Attributes for Data Archiving Guide |
| Customizing Activity | ARCH_IMG_TABANALYSIS | Table Analysis |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ARCH_IMG_TABANALYSIS |
You use this function to analyze database tables. During the analysis, specific field value combinations are assigned the number of corresponding entries. This involves the use of analysis variants that contain the corresponding field lists. For more information, see the SAP Library and the example below.
For certain tables the analysis variant ARCHIVE is used, which is tailored to the special requirements of archiving. You can use the generated analyses to determine which archiving object is required and which selection criteria may greatly affect archiving. This allows you to prevent the system from analyzing archiving objects or organizational units that only contribute a minimal amount of data. The following are notes on how to use table analysis most productively within data archiving:
- The table analysis generates an extract; additional data is generated. The amount of data is proportional to the number of lines displayed in the analysis. Therefore, only execute an analysis when necessary (this is particularly important within data archiving).
- Execute those analyses described in detail in application documentation. These details include how to interpret the results. It may be too early for executing table analyses. If necessary, run table analyses later.
- You can also use table analyses to determine the best selection criteria for archiving. This allows you to determine, for example, whether data is available for a particular fiscal year. The actual selection of criteria should only be carried out in conjunction with the particular departments in the company.
Example of table analysis:
Table BKPF uses analysis variant ARCHIVE, which contains the fields BUKRS, GJAHR, and BLART. The analysis determines the number of entries in table BKPF. The result is a list of the table entries by MANDT, BUKRS, GJAHR, and BLART. (The system automatically adds MANDT.
MANDT BUKRS GJAHR BLART Number
000 0001 1999 ZP 40,723
000 0001 1998 AB 13,237
000 0001 1999 AB 10,973
000 0001 1999 SA 9,239
... and so on ...
This list indicates there are 40,723 entries in table BKPF that have the value 000 under MANDT, the value 0001 under BUKRS, the value 1999 under GJAHR, and the value ZP under BLART. For MANDT 000, BUKRS 0001, GJAHR 1998, and BLART AB, there are 13,237 lines, and so on.
The list is sorted by number of entries. The field value combinations with the largest influence on the amount of data are listed first. Use the ALV Grid Control functions to format the list to your needs.
Business Attributes
| ASAP Roadmap ID | 899 | not to be assigned |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| IMGDUMMY | D - Dummy object | TAANA |
History
| Last changed by/on | SAP | 20000128 |
| SAP Release Created in | 46C |
