Phase | Activities | How to support with the Performer Suite | Time-saving potential (with 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 have not been used for a long(er) time.
- Understand the dependencies from one BW Object to nearly all other elements (including ABAP/AMDP). The usage must also be checked in frontend objects (BO, SAC) to find out which Queries are relevant for the migration as they are used as data sources.
- Understand what is on which system is 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
- There are several System Scout functions for that:
- List InfoProvider without Usage in Data FlowsFlow
- Last Load and Usage Analysis
- Show inactive ObjectsData Loads and Usages
- Inactive Entities
- Unused InfoObjects
- Variables Variable Analyzer
- Data Flow Analysis
- Mapping analysis in the data flow for individual IOBJs:
Data Lineage Analysis for all IOBJs - Use "Grid View" with "Column Chooser" and column "Last Used Date": Column Chooser
- Usage of BW Entities
- Mass comparison: Compare Entities of SystemsSystem Comparison.
Individual comparison: Comparison of ElementsCompare BW Entities
| - 40%-60%
- 20%-50%
- 35%-45%
- 20%-40%
- ~5%
- 5%-15%
- 50%-80%
|
---|
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 Queries to the new and adjusted data model to secure basic processes within functional/reporting departments. Before that, it must be clarified with the business user which Queries should be considered for the new BW/4HANA system.
- 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.
| - Migrate InfoProvider & InfoObjects
- Collect & import objects from a data flow
- Renaming and remodeling of objects
- Export modeled objects to SAP
- Copy Reporting Elements and optionally create a backup of a Query, which can be restored at a later point in time in the new BW/4HANA system.
- Translate the newly created objects
- Check Naming Conventions of BW Entities with System Scout (also possible from transports)
- Show DTPs used and not used in process chains: Show DTPs and InfoPackages incl. Filters
| - 80%-95%
- 80%-95%
- 50%-70%
- 5%-15%
- 50%-70%
|
---|
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.).
If you have a good idea, please let us know how we can support you even more and create a feature request!
| - 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 have been changed due to singular events (testing, one-time loading, etc.) but have not been reversed.
| - Data Flow Analysis - here especially:
- Mapping 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.)
| - BW Commenting
- BW Documentation especially: Scenarios
| - at least 15% depending on how well it is used later.
- 10%-40%
|
---|