I am not entirely convinced that the linked thread is a suitable match for this specific case.
The archived thread is about modifying condition values in existing order items, while here the OP is deleting order items.
From what I read in 366265 - How should I fill the BAPI parameters?, p.3 a) for deleting items you just need to pass information in BAPISDITM, BAPISDITMX, BAPISDH1X and the order number, there is no mention that you have to delete conditions in the bapi on top of that (and even when you modify items you might not be able to delete all conditions).
When I followed the steps for deleting items from this note, the KONV entries were removed after bapi_transaction_commit.
hevanderson.maria , as a part of the troubleshooting try this:
1. starting point order with items 10, 20.
2. delete via bapi item 20 and commit.
3. check the outcome.
4. add item 20 via bapi and commit.
5. check the outcome in konv.
---
Then make another test:
1. starting point order with items 10, 20.
2. delete via bapi item 20, add via bapi item 30. commit.
3. check the outcome in konv.
Edit: the reason why I suggested these tests is because making simple examples (without complicating the case with additional pricing modification in condition handling) are easier to troubleshoot especially if your pricing procedure is complex. After you ensure that these two tests are successful, you will only need to investigate what you pass in conditions (if you made any adjustments there via the bapi).
