Hi,
Obviously it is not possible to show error message ‘Period 2022 -XX is not open for user group XX in Company XXXX’ right from the start, when postings are created and validated, because at this stage you so not know what is the user and user group selected for transfer, and it is transfer creating actual voucher. 

From the other hand, looking at the transaction in posting analysis, you can see the used id of the person who created transaction - but no information about the person who runs the transfer to finance. 

I think there’s something else that could justify the existing behavior - in case of problems with accounting period status, transfer job gets stopped, and the error is not handled as exception - not stored to a posting error field on posting. Handling it as exception would require much longer processing time, as this kind of error is common for ALL TRANSACTIONS valid for transfer, so it would change status from 2 to 99 for all of them (potentially thousands of lines) and then same time to regenerate postings and validate them again - on all transactions. Alternatively the error could be stored in just one transaction, first on the list - but what could we gain from it?

We’re getting a similar error “Financial period 5-2022 in company xxxx is closed for user group AC”.  The puzzling piece is we are doing transactions that are current (April 2023) and there are no dates that we can see that references May 2022!

Are you sure, @heather.will , that you do not have  not transferem transaction with date applied one year old (May 2022)?

@Adam Bereda Hi Adam, I’m not sure that we don’t have a “not transferem transaction” with a May 2022 date.  What is that and where do I look for it?

Please look in ‘Distribution and Manufacturing Postings Analysis’ for all lines not transferred (status <> 3). you can order results by accounting date - perhaps this one year old line will lad as first one

In my experience, the most common cause of this error is when someone re-opens a previously closed shop order and attempts to make changes to it.  It can and will create transactions that are dated in the past whether they added material to it or changed hours or whatever.  Then the next time you try to do the transfer job for month end or even just on a daily basis, you will see this error.

We had a group of engineers that were dumping parts onto old shop orders rather than creating new warranty orders as a short cut.  Tracing the the error through the analysis screen will lead you to the user who is doing the work….

Thanks for your suggestions.  It was a purchase order created in 2023 (not a shop order) so it is extra strange that the message is for a period closed May 2022.  Our Finance team has asked us if we can repost to a different period, but I don’t know how to change the postings.  Suggestions?

Well it turns out we weren’t reading the financial period correctly in IFS.  It wasn’t a transaction from that long ago afterall, just aweek ago.  We changed the register direct delivery date to “today’s date” and were able to proceed without needing to reopen last month’s accounting period.