You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 10
Next »
You want to either prepare or analyze your SAP BW system to move to BW on HANA or BW/4HANA. You have now (one/several) of those challenges to:
- Identify Objects that are not needed anymore, to preserve effort and valuable memory space?
- Align with the functional business department how many of those tenths, hundredths, thousands of Queries should be taken over/are still needed?
- You need to reflect new requirements in data models. InfoProviders need to be adjusted?
- While you talk to your business department they want to take over (parts/all) of the old Queries, so they can continue work?
- You need to rebuild Data Flows and therefore need to understand complexities within flows and what actually happens?
There is not really an actual error beside the fact that many of those tasks above you have to do manually! Who likes to copy and paste information into Excel and stays focused doing that (without error) for hundreds of elements?! Of course errors can creep in here by doing mistakes in the manual steps. As this is too much of an effort you decide to go for the "supposedly" easiest way, by taking nothing/everything/doing nothing at all.
There is not really a good support for those activities above by SAP standard tools.
Use the Docu Peformer for example to:
| Phase | Activities | How to support them with the Docu Performer | Possible Saving
(on each Activity) |
|---|
| Analysis | - Create a basis for discussion with the Functional Department what is needed in terms of reporting
- Identify unneeded objects that can be deleted/cleaned up
- Check Data Flows for (also for nested ABAP/AMDP) logic that is not always immediately visible!
- Understand overall complexity in mapping for the whole data flow at once
- Identify Queries that haven't been used for a long(er) time.
- Understand the dependencies from one BW Object to nearly all other elements (including ABAP/AMDP)
- Understand what is on which system available. Are all Queries/InfoProviders/etc. transported and available in all Systems? All all emergency changes from PROD maintained in DEV as well?
| - /wiki/spaces/DPUM191/pages/439521177
- There are several Functions for that:
- /wiki/spaces/DPUM191/pages/439520820
- /wiki/spaces/DPUM191/pages/437979230
- /wiki/spaces/DPUM191/pages/439520859
- /wiki/spaces/DPUM191/pages/437979250
- /wiki/spaces/DPUM191/pages/437979280
- /wiki/spaces/DPUM191/pages/439520868
- /wiki/spaces/DPUM191/pages/439521188
- Use "Grid View" with "Column Chooser" and column "Last Used Date": /wiki/spaces/DPUM191/pages/437979007
- /wiki/spaces/DPUM191/pages/437979254
- Mass comparison: /wiki/spaces/DPUM191/pages/437979240. Individual comparison: /wiki/spaces/DPUM191/pages/437979266 (can be also triggered form the mass comparison for individual elements; mass detailed comparison coming soon)
| - 40%-60%
- 20%-50%
- 35%-45%
- 20%-40%
- ~5%
- 5%-15%
- 50%-80%
|
|---|
| Design | coming soon... If you have a good idea, please let us know how we can support you even more and create a feature request! |
|
|
|---|
| Implementation | - You need to take over data models to BW/4HANA or BW on HANA while still adjusting existing naming conventions.
- You want to take over (some/many/all) Queries to the new and adjusted data model to secure basic processes within functional/reporting departments.
- You need to translate elements in the Data Warehouse to reflect two/several languages using a dictionary instead of doing this manually.
- You want to use consistent Naming Conventions.
- Go through all DTPs and ensure that they are relevant for loading and are used/implemented in process chains.
| - /wiki/spaces/DPUM191/pages/439517267
- /wiki/spaces/DPUM191/pages/439517337
- /wiki/spaces/DPUM191/pages/439517271
- /wiki/spaces/DPUM191/pages/437979234
- Show DTPs used and not used in process chains: /wiki/spaces/DPUM191/pages/439521184
| - 80%-95%
- 80%-95%
- 50%-70%
- 5%-15%
- 50%-70%
|
|---|
| Testing | more coming soon... For Bug Fixing aspects - see also Phase "Support" If you have more good ideas, please let us know how we can support you even more and create a feature request!
|
|
|
|---|
| Deploy | - Use existing documentation and specifically added information (comments) for objects to understand additionally required procedures/impacts/etc. (special loading, activation order, etc.).
more coming soon... If you have a good idea, please let us know how we can support you even more and create a feature request!
| - /wiki/spaces/DPUM191/pages/437979101 + /wiki/spaces/DPUM191/pages/437978998 especially: /wiki/spaces/DPUM191/pages/437979140
| - ~5%
|
|---|
| Support | - Support general resolutions for data:
- You need to understand how mappings are done within Data Flows, to be able to identify errors.
- Here it is also important to understand what ABAP/AMDP routines do and
- if there are any relevant DTP/IP Filter and selections that influence processing or that has been changed due to singular events (testing, one time loading etc.) but have not been reversed.
| - /wiki/spaces/DPUM191/pages/439520868 - here especially:
- /wiki/spaces/DPUM191/pages/437979272
- /wiki/spaces/DPUM191/pages/437979293
- /wiki/spaces/DPUM191/pages/439521184
| - 15%-40%
- 20%-50%
- ~10%
- ~10%
|
|---|
| Documentation | - Preserve knowledge for later use, changes in team structure etc.
- Creating documentation for different target groups (Functional Department, Audits, IT, etc.)
| - /wiki/spaces/DPUM191/pages/437979101
- /wiki/spaces/DPUM191/pages/437978998 especially: /wiki/spaces/DPUM191/pages/437979140
| - at least 15% depending how well used later!
- 10%-40%
|
|---|
