This is an old post, but it describes well our problem.
As it's explained in the archiving documentation, the "tdinv7210m000" session archives inventory transactions comparing the transaction date (trdt) with the form parameter.
The "tdinv700" table is read sequentially for each item from the oldest transaction date to the newest, but once a transaction on a non-archived project is met, it jumps to the next item and doesn't analyse other transactions.
I don't understand the logic and it causes many problems in my company because we are re-using a production orders serie and it results in a melt of oldest and newest inventory transactions in the tdinv700.
Thank you in advance for sharing your experience on this session.