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