| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
...
For the migration from BW to BW/4HANA there is a concept of Compatibility Views. They can be used for migration e.g. of DSOs to ADSOs. The concept is that a view with the name of the old DSO table (e.g. /BIC/AMY_DSO00) is created. That view selects on the new ADSO table (e.g. /BIC/AMY_ADSO1). With this concept, you do not have to change your code where you do lookups or other reads on tables of your old InfoProviders. We do not support this concept and we think that also the code should be migrated. These leads to advantages like clear names of DDIC views and it is sustainable.
With the Docu Performer, you can do an ABAP Scan to identify the places where an InfoProvider table is used in the code. These places should be adjusted manually.
Queries
Modeling does not support the generation of Hierarchies.
So before copying a Query with the Docu Performer, you should create corresponding Hierarchies in target systems.