...
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 Discuss with the functional business department how many of those tenths, hundredths, the tens, hundreds or thousands of Queries should be taken over/ are still needed and have to be considered for the migration?
- 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 besides 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 on 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 /or doing nothing at all.
Cause
There is not really good support for those activities above by SAP standard tools.
Solution
Use the Docu products of the Performer Suite for example to:
| Phase | Activities | How to support them with the Docu Performer Suite | Possible Saving
(on each Activity) |
|---|
Analysis
(System Scout) | - 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 emergency changes from PROD maintained in DEV as well?Matrix of Usage: InfoProvider Objects in Queries
| - /wiki/spaces/DPUM192/pages/512103569
- There are several Functions System Scout functions for that:/wiki/spaces/DPUM192/pages/512103645
- List InfoProvider without Usage in Data Flows
- Last Load and Usage Analysis
- /wiki/spaces/DPUM192/pages/512103518
- /wiki/spaces/DPUM192/pages/512103532
- /wiki/spaces/DPUM192/pages/512103536
- /wiki/spaces/DPUM192/pages/512103579
- Show inactive Objects
- Unused InfoObjects
- Variables Analyzer
- Data Flow Analysis
- Data Lineage of BW Entities
- Use "Grid View" with "Column Chooser" and column "Last Used Date": /wiki/spaces/DPUM192/pages/512102847
- /wiki/spaces/DPUM192/pages/512103555
- Mass comparison: /wiki/spaces/DPUM192/pages/512103472. Individual comparison: /wiki/spaces/DPUM192/pages/512103623 (can be also Column Chooser
- Usage of BW Entities
- Mass comparison: Compare Entities of Systems. Individual comparison: Comparison of Elements (can also be triggered form the mass comparison for individual different elements; detailed 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
(Migration Booster & Translation Steward) | - 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/DPUM192/pages/512103659
- /wiki/spaces/DPUM192/pages/512103866
- /wiki/spaces/DPUM192/pages/512103965
- /wiki/spaces/DPUM192/pages/512103501Migration Booster
- Copy Reporting Elements
- Translation Steward
- Check Naming Conventions of BW Entities with System Scout (also possible from transports)
- Show DTPs used and not used in process chains: /wiki/spaces/DPUM192/pages/512103615 Show DTPs and InfoPackages incl. Filters
| - 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
(Docu Performer) | - 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/DPUM192/pages/512103299 + /wiki/spaces/DPUM192/pages/512103241 BW Commenting + BW Documentation especially: Scenarios
| - ~5%
|
|---|
Support
(System Scout) | - 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/DPUM192/pages/512103579 Data Flow Analysis - here especially:
- /wiki/spaces/DPUM192/pages/512103599
- /wiki/spaces/DPUM192/pages/512103583
- /wiki/spaces/DPUM192/pages/512103615Mapping Analysis of InfoObjects
- Look-Up Analysis
- Show DTPs and InfoPackages incl. Filters
| - 15%-40%
- 20%-50%
- ~10%
- ~10%
|
|---|
Documentation
(Docu Performer) | - Preserve knowledge for later use, changes in team structure, etc.
- Creating documentation for different target groups (Functional Department, Audits, IT, etc.)
| - /wiki/spaces/DPUM192/pages/512103299
- /wiki/spaces/DPUM192/pages/512103241 BW Commenting
- BW Documentation especially: Scenarios
| - at least 15% depending on how well used later!
- 10%-40%
|
|---|
...
