How to avoid a deletion/update/insert of a record
whenever a deletion of a record is detected within the source system, SLT will execute the same operation also on the target. In some scenarios you would like to avoid exectly this behaviour. This can be achieved via a transformation rule.
The same logic can also be used if you want to avoid/modify any other operations like inserts or updates.
This example is based on DMIS2011 SP5 – for DMIS SP6 it is the same, just the UI (LTRS) for the rule definition will look a little bit different.
1.) IUUC_REPL_CONTENT / LTRS
You see that the operation ‘D’ referes to deletion. For any other specific user case you can also use ‘I’ (insert) or ‘U’.
Maybe you would like to store the information that the record was deleted on the source system. If so, just create a new field for the target table. Within the rule you will fill this field with an ‘X’ and in addition you would not use SKIP_RECORD, instead you would change the <öv_operation> into ‘U’ that the information will be populated within the target.
3) Result: 15 records in HANA
14 records in ECC
Interesting document.. Thanks for sharing
In one of my system when ever there is any change in source system, SLT is not overwriting it in Target system, it is add a new value in the system.
If the value was 1000 and now it is changed to 2000, SLT should overwrite that in Target system, but it is not happening, SLT is adding a new value in the table and both the values can be seen in target system.
Thanks & Regards
We are using 1 tables in hana & loading data from 4 different country differentiating using a key.
The product is up & running for 5 months now, Application(Oracle team) is planning to archive the data.
I checked lot of blogs, couldn't find the code for user specific archiving request to be excluded.
Can you please help us with code(We dont have a abap developer in our project) , how to exclude the records which are deleted by a user(Archiving user in our oracle database).
Thanks & Regards,