Hi,

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

/wp-content/uploads/2014/03/1_404322.png

2.) Include

/wp-content/uploads/2014/03/2_404323.png

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

/wp-content/uploads/2014/03/3_404348.png

14 records in ECC

/wp-content/uploads/2014/03/4_404349.png

Best,
Tobias

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. akella phani kishore

    Dear Tobias,

    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,

    Phani

    (0) 

Leave a Reply