Question

Accounting Period has defined incorrectly and mismatches with Statistic Period

K
Rank
Userlevel 2
Badge +4

Accounting period of 12 in Company 10 has been defined as Valid from/Valid Until (01/12/2022 to 30/12/2022) 

Statistic Period of 12  has been defined with begin/End date (01/12/2022 to 31/12/2022)

 

Due to this it is not possible to perform Aggregate Inventory Transaction  as it can not find accounting period which has 31/12/2022. it is giving an error in the background job.

 

If Company doesn't use any depreciation calendars and if No inventory transactions or any other GL postings are not available on 31/12/2022 , can we suggest that introducing New Period to include 31/12/2022 as a viable solution?

What consequence this involves? can you suggest what areas going to be affected with this change.

 

Thank you

 

 

3 replies

P
Rank

Hi,

In my opinion the best approach to this situation is to extend accounting period 12 to 31/12/2022. It is normal definition and everything should work. I wonder why it was set to 30/12/2022 in first place?

What is defined for 31/12/2022 in accounting periods now ?

Best Regards,

Pawel

 

K
Rank
Userlevel 2
Badge +4

Thanks Pawel . But it is not possible to amend existing accounting periods , IFS application will not allow this 

P
Rank

It was possible from application, but during the first setup process, when there was no next period defined. Now there is a need to analyse those situation deeper to redesign periods from the beginning. You should raise a ticket for Implementation Team to redesign the periods, next it will be possible only directly in the period table in the database.

Best Regards,

Pawel

 

Reply


Terms & ConditionsCookie settings