Abstract
We have seen many articles and publications about SAP Datasphere in terms of features, connections and greenfield implementation, but many customers have been asking what can be done to save the investments which were already done on their c...
Abstract
This blog intends to provide an overview about the end-to-end process of the Remote Conversion to SAP Datasphere, BW bridge. For a deep dive into the details of all activities involved, check our SAP Datasphere, SAP BW bridge Runbook which c...
Hi Jonas, are you migrating via Shell or Remote? Usually you can finalize or delete the task list run which is not needed. Maybe you can share the error message/screenshot.Kind regards, Felipe
Hi Vishwa,
Thanks for the feedback.
1)BW bridge is a component of Datasphere and it is not temporary. So after the transfer (Shell or Remote), BW bridge stays (the receiver system) - its space can then be consumed/exposed to Datasphere. What is pos...
Hi Rejin, the source system notes should be implemented in your "old" ERP system - the one connect to your actual BW system from where the Shell Conversion will run. The xml file with the notes (Source_System_for_SAP_BW4HANA_[last_update].xml) should...
Hi Tanuj,
When having a SAP Datasphere, BW bridge landscape with more than one tenant (e.g. one development and one productive tenant), it is assumed that you wish to populate this productive tenant with the same data from your SAP BW productive sys...
Hi Pablo,
Thanks for the question. Data selectivity based on time is a feature available for BW NetWeaver migrations, however not yet functional in the Conversion Cockpit for BW/4HANA or BW bridge migrations. This has been internally discussed at SA...