cancel
Showing results for 
Search instead for 
Did you mean: 

Transformation to look up tables in SLT

Former Member
0 Kudos

Hi,

   We are replicating tables from SAP ECC to HANA using SLT. There is a requirement to add a new column to a table Tab1 by looking up in to another table Tab2. Both Tab1 and Tab2 are getting replicated.

    Is there a better way to do it without writing a remote function module in SLT that reads the Tab2 from ECC for the look up? Can we store the Tab2 data in SLT, so instead of a remote functional call to ECC,  I can do a local look up?

Regards,

Ajay.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

I had thought of this before but never implemented it.  Given your requirement what you could do is create a table in your SLT environment that contains the fields you need from Table2.  (using SE11)

Then create an Include program that you put on the replication for Table2.  All this program does is insert / modify that table on your SLT environment.

Basically you are using the SLT configuration from ECC to HANA to also put a copy of the record on your SLT environment.   If it is a huge table, then you could have space problems on your SLT box, but you can control that.

Now when you are doing your replication for Table1, you can write an include program that reads your copy of the table on the SLT box and populate the new field.

Another option would be to write a Stored Proc/Trigger that runs in HANA that populates the column on Table1

Answers (3)

Answers (3)

Former Member
0 Kudos

Thank you for the responses, but...

Gopi,

   I should have made it clear in my original post. I need the field persisted in the table because I want to use it to filter my data in the calculation views. So, joining the 2 tables in HANA calculation views does not help.

Frederic,

    It is not a field to field join between the tables, I need to do the look up based on a derived value. So, I cannot create a view in SE11.

Regards,

Ajay.

gopinath_kolli
Active Participant
0 Kudos

Hi Ajay,

The reason you have mentioned for persistence will not be compromised if you create a calculation view.

Create a separate calculation view of joining the tables. And you can use this calculation view in pace of table.

Also please note that HANA is know for calculations on the fly, and is not recommended to store aggregates or any calculations.(Unless in some exceptional cases)

Hope this helps.

Thank you,

Gopinath.

FCI
Active Contributor
0 Kudos

Hi Ajay,

An alternative would be to replicate a view on the 2 tables. There are a lot of threads on the subject (view replication).

Regards,

Frederic

gopinath_kolli
Active Participant
0 Kudos

Hi Ajay,

Create a calculation view using both tables and join according to your requiremen. And use that cv wherever you need the combination.

thanks,

gopinath.