SLO clients into HANA

[Former Member]

We have 2 BW clients in 2 different BW systems.

We want to use SLO to transform the 2 clients into 1 client in HANA.

Could you please share your experience on how to achieve this?

Thanks!

[Former Member · Accepted solution]

Hi,

I assume you will use the news system as productive system.

To achieve that I would recommend 2 steps:

1.) Merge the both BW client into one client with a tool based apporach (SLO tool)

2.) Replicate the data into HANA DB.

With this approach you can test the correctness of the client merge and then start the HANA project.

Best Regards,

Axel

[Former Member · Accepted solution]

Axel, can step 2 (replicate the data into a HANA DB) be done using a SLO tool? Or is it essentially an activity carried out by DMO/SUM technologies/processes?

Thank you in advance.

[Former Member · Accepted solution]

SLO has a product called SLT replicator which specifically caters to this requirement.

It can replicate data from any DB to HANA. This SLO tool is meant for pure DATA replication.

SUM is another tool which is used to during SP upgrades.

Regards,

Farheen

[axel_marschall2 · Accepted solution]

Hi

If you have already consolidated your both BWs into one single BW, you can use standard methods ( f.e. DMO; DMO+PCA,..) to migrate the whole new BW system to HANA. I assume that all housekeeping tasks have been done during the consolidation of the 2 BW systems.

Regards,
Axel

[Sandeep_Kumar]

Hello,

This seems to be an interesting use case for SLT replicator.

As far as i know, you will not be able to achieve the client merge scenario using SLT replicator as it is.

You can get more details on the same by creating an OSS ticket in component: BC-HAN-LTR

Cheers,

Sandeep

[Former Member]

Then could you tell me how to use SLO to copy one client into HANA?

We did TDMS copy but the target was a regular DB.

Thanks!

[Sandeep_Kumar]

You can do some investigations on the usage of SLO replicator for copying/real time replication in HANA machine.However, the usage here is different from that of client copy.

See SAP note : 1605140