Hi Justin,
this is a functional gap at the kernel level. So there cannot be a standard aproach so far. But let me share my ideas.
1. Delete triggers before and recreate triggers after the archiving run
Can you ensure that the archiving run is no productive data/transaction is execute during the archiving run - you can delete the trigger before the run and recreate it afterwards. The result: triggers cannot record and archive deletes will not cause a delete on the HANA system.
Deleting triggers can be executed via expert funtions on the SLT system at transaction LTRC.
2. Define a transformation rule, that exclude deletion
You could define a rule that check the operations, a if it is a delete you can skip this from processing. This rule has to be defined before you start the archiving run, but again you have to ensure that no productive data is delete (that do not belong to the archiving run)
Both options require manual steps. So we are looking to improve it - but due to the fast that this is a core kernel story - it is not a enhancement that can be achieved asap.
Best,
Tobias
