In Hibernate Envers it is possible to have a separate audit table. Similarly, is it possible to log into tables other than the entity’s table using Spring Data JPA auditing?
The auditing feature of Spring Data JPA just fills attributes in the entity you are persisting. How and where these attributes get persisted is controlled by you JPA implementation and of course your database.
JPA offers @SecondaryTable
to map fields to a second table.
If this isn't flexible enough for you, you can always employ database tools to achieve the effect by mapping the entity to a view which via triggers distributes the data however you want.