1. Identify unneeded objects that can be deleted. This also includes the search for inactive DTPs, because the depending process chains would fail (1c).
2. Identify Queries that have not been used for a long time.
3. When working with reporting objects and not being careful with transports it might happen that you accidentally generate objects with the same technical name but with different GUIDs. This leads to confusion and mistakes.
4. As you have identified the objects to be candidates for deletion you need to understand the dependencies from this specific SAP BW Object to nearly all other elements (including ABAP/AMDP).
5. Specifically for Queries, you can immediately check the structure of the query to evaluate the dependency and the type of usage (free characteristic vs. selection vs. filter, etc.).
6. You want to use consistent Naming Conventions.
7. Understand if there are any other implications for the objects you want to delete. In addition, you can preserve your knowledge for later use, changes in team structure, etc. so that colleagues don't have to go through the same process ("We cannot clean up this object because ...")
8. If you do not want to use any more queries that for example have complex definitions, or input ready, but should be (anymore), then you have to find all those different elements in your system.
9. Find ABAP "BreakPoints"/"Select Single"/"..." that could be a problem for SystemLog or Performance or...
10. Understand what is on which system available. Are all Queries/InfoProviders/etc. transported and available in all Systems? Are all emergency changes from PROD maintained in DEV as well? Can elements be deleted?

1. There are several functions for that:
   
   1. List InfoProvider without Data Flows
   2. Data Loads and Usages
   3. Inactive Entities
   4. Unused InfoObjects
   5. Variable Analyzer
2. Use "Grid View" with "Column Chooser" and the column "Last Used Date": Column Chooser
3. Redundant Reporting Elements
4. Usage of BW Entities
5. Analyze and Compare Elements
6. Naming Conventions
7. BW Commenting
8. Queries with specific Components
9. BW Code Scan
10. Mass comparison: System Comparison. Individual comparison: Analyze and Compare (can be also triggered from the mass comparison for individual elements; mass detailed comparison coming soon)

1. 20%-50%
2. ~5%
3. 5%-15%
4. at least 15% depending on how well used later!
5. ~5%
6. 5%-15%
7. ~5%
8. 10%-20%
9. 10%-15%
10. 50%-80%

If you have a good idea, please let us know how we can support you even more and create a feature-request!

1. While doing all the changes, you can easily add and preserve your results and special knowledge for later use. So when somebody is ill, on vacation or the team changes, everybody knows what to do and why things happen. So you avoid repeated work and save time and money.

1. BW Commenting

1. 10%-40%

If you have a good idea, please let us know how we can support you even more and create a feature-request!

For deployment procedures, e.g. what needs to happen before/after transporting, any special steps needed, etc., have a look at the documentation...

If you have a good idea, please let us know how we can support you even more and create a feature-request!

See documentation...

If you have a good idea in addition, please let us know how we can support you even more and create a feature request!

1. Just with a little added effort, you can create documentation for different target groups (Functional Department, Audits, IT, etc.) to inform about the different changes that happened through the cleanup.

1. BW Documentation especially: Scenarios

1. 10%-40%