Dear Mark,
Well I have two answers
1. Use your NON post project in the Journal entry.
This will not update project again.
2. Enter the batch using the projectid to reverse out the Expense entries (do not release it)
open up query analyzer and on the gltran records for the batch, update the pc_status to a 2
a 2 indicates the batch has already gone over, and no need to transfer.
update gltran set pc_status = '2' where batnbr = 'XXXXXX'
then you can go and release the batch.
Although I don't quite understand what you mean "We changed the sub-account in Project Set up and that seems to have moved the related expenses to the correct place in project." as I don't see that changing the project subaccounts will impact any already released expenses in the system. In other words, changing the project subaccount on its master record doesn't change the subaccount previously used by the project in the pjtran table.
However, I can see allocator backing out the allocation from the sub to the new sub if you ran a recalculation.
Jana MacDonald
Microsoft SL Support
