The current behavior consistent with the application as that is how delete works for other basic data. For example, the Fixed Assets Object Group, Fixed Assets Books is also working in the same way. If you define a new Object group and then connect it to FAP5 with control type FAC2, you can delete the Object Group even if it’s connected to the posting control. This is the same for Books as well. That is because in such situations the value for tax code, object group, Books are not passed to create postings from the posting control. Instead these values are used to fetch the account (for example) from the posting control.

And then if you try to delete the account it gives an error because as per the setting the account is used in the posting control to create postings.

---

Hi Rasangi, in addition to what Yoshini mentions, in this case you were able to delete it because no accounting transaction has been created yet with that tax code. Once this is included in a transaction, you can no longer remove it, the only way to avoid the use is changing the valid date and you can also put a warning for not selecting it in the tax code description,and also remove it from the posting control.

---