2 weeks ago - last edited 2 weeks ago
Hello SAP Community,
We are currently running SAP BW 7.5 and have plans to migrate to SAP BW/4HANA 2023. Our strategy is to perform the migration step by step and module by module. Additionally, our SAP ECC 6.0 EHP8 system will continue to serve as a source system during this process.
I have a few questions regarding this migration and integration scenario:
Module-by-Module Migration:
Integration with ECC 6.0 as a Source:
Best Practices & Tools:
Any shared experiences, resources, or guidance on this phased migration approach would be greatly appreciated. Thank you in advance for your insights!
Best regards,
Amir
Request clarification before answering.
Hello Amir,
You wrote "Our plan is to continue operating our current BW system alongside BW/4HANA during the migration". For me this leads to the following question: What migration path are you intending to use? InPlace Conversion or Remote Conversion?
My first answer was more for an InPlace Conversion. That means you migrate your objects within the current system (SID remains the same), supported by modes: Compatibility, B4H, R4C. In the end a technical system conversion "upgrades" the system to BW/4. In this approach, DataSources are "switched" to ODP when running the tasklist. The datasource connection is either SAPI or ODP. (=> when using the toolbox for conversion and delta queue cloning)
A remote conversion means a parallel landscape is created and objects are transferred from the existing system to BW/4. This is a totally different approach.
In this approach, objects are transferred to BW/4. On the way of this transfer the objects will be converted. The existing landscape remains nearly unchanged. When DataSources are part of this scope they will be connected as ODP DataSources in BW/4 (incl. delta-queu-cloning to ODP).
As the existing system remains unchanged, the extraction logic (SAPI) will continue in the existing landscape. After the transfer to BW/4 in BW/4 the extraction is done via ODP. So, from a source system point of view there are two targets for the DataSource: SAPI to the "old" system and ODP to BW/4.
Best Regards,
Eduard
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Amir,
A conversion to BW/4 needs to be prepared very well.
To 1:
One important step is to decide how to "slice and dice" your BW system to create scopes (you call it "module") to convert the objects into BW/4 compatible objects. This means it has to be analyzed how objects can be grouped to convert as a package. You start with start objects which collect dependent other objects, e. g. a CUBE will collect the MPROs on top of it, because the MPRO can not contain ADSO. When selecting start objects you have to keep in mind that there are BW objects which are collectors on its own, e. g. Dataflow object or Process Chain. If you use them as a start object, the toolbox will collect all dependent objects, e. g. a process chain contains of ODSO activate, so the ODSO will be collected to, and the transformations into the ODSO and the DTP into the ODSO, etc. So be careful with the selection of the start objects.
To 2:
The ECC system can remain as source system for BW/4, but it has to be switched to an ODP source system type. DataSource have to be made ODP enabled and the toolbox will support the "switch" from SAPI extraction to the ODP framework. Delta initializations will remain ("Delta queue cloning"); no new initialization is required. After the conversion of the datasource the objects are transferred: InfoPackage -> DTP and delta loading can be continued (with new objects) but within the ODP framework.
The conversion guide and SAP Note 2383530 gives you more information.
Best Regards,
Eduard
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Eduard,
Thank you for your previous insights regarding the conversion process and grouping of BW objects.
I have an additional question related to the extraction setup during our phased migration. Our plan is to continue operating our current BW system alongside BW/4HANA during the migration. For instance, we intend to extract data from the 2LIS_03_BF_TR data source using two methods concurrently:
My questions are:
Concurrent Extraction Support:
Can we extract data from the same ECC data source (2LIS_03_BF_TR) simultaneously using both the legacy extraction method and the ODP framework without conflicts?
Configuration Considerations:
Are there specific configuration steps or best practices to ensure that enabling ODP on this data source does not interfere with the delta handling or data consistency for the legacy extraction process?
Monitoring and Delta Handling:
What recommendations do you have for monitoring the delta queues or initial load processes to ensure that both extraction paths (legacy and ODP) operate smoothly side by side?
Your guidance on setting up and validating this dual extraction scenario would be greatly appreciated as we work through the module-by-module migration.
Thank you in advance for your help!
Best regards,
Amir
Hi Amir
I think the following documents contain answers to most of your questions:
2383530 Conversion from SAP BW to SAP BW/4HANA
Also look for consulting notes with the short text "BW4SL", as they contain additional information for specific topics and object types.
Besides this, there are also some blogposts available in the topic like:
br
Roland
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
60 | |
10 | |
8 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.