Skip to main content
Solved

ROUNDDIFF transactions only occured once

  • September 30, 2021
  • 5 replies
  • 490 views

MarieSkoldenborg
Sidekick (Customer)
Forum|alt.badge.img+9

Here I found a very good explanation of the logic for ROUNDDIFF transactions: 

However, we have only experienced ROUNDDIFF transactions created once (2021-06-30). Since then new parts are available with qty 0 and inventory value <> 0. No new ROUNDDIFF transactions have been created. Is there a setting whether to have these transactions created or not? Something we are missing?

Our problem when the transactions are created:  

We run the scheduled task “Aggregate inventory transactions per period”  on the 3rd day of each month (offset:3). The reason is that we want to be able to update date applied on the 1st and 2nd day before the statistics are updated.

So the inventory transactions for June were aggregated on July 3rd. Fine.

Then on August 3rd the inventory transactions for July were aggregated. Now also the ROUNDDIFF transactions were created for June since the statistical period of July was created in August. This causes postings dated 2021-06-30 but since the period of June is closed we don’t want to transfer them to Finance. 

Now the idea was to have the “Aggregate inventory transactions per period” running on the 3rd and the 4th of each period. Then the ROUNDDIFF postings would have been created on the 4th instead. 

However, now when we run the same job in our test environment, no ROUNDDIFF transactions are created. 

So is there something I should do in order to have the ROUNDDIFF transactions created, other than running the “Aggregate inventory transactions per period” with an offset within the current period? 

Please advise. 

Best answer by Vimukthi Mahakumbura

Hi @MarieSkoldenborg , yes, that is correct. ROUNDDIFFs are created in the end of a period.You seems having an offset of few days and you modify some transactions to the previous month, that is ok. As long as the previous period is open, the aggregation we run today should create ROUNDDIFFs for the previous period. Also based on Inactive days.  

 

View original
Did this topic help you find an answer to your question?
This topic has been closed for comments

Vimukthi Mahakumbura
Superhero (Customer)
Forum|alt.badge.img+19

What about the Inactive Days for Remaining Stock Value in the site?

 


Vimukthi Mahakumbura
Superhero (Customer)
Forum|alt.badge.img+19

Another possibility is, your Accounting Periods being closed at the time of the execution of the Aggregation job. 

When you run the job on 3rd, if the Accounting period of the previous month is closed, it will not create a ROUNDDIFF transaction too. 


Vimukthi Mahakumbura
Superhero (Customer)
Forum|alt.badge.img+19

Another small question while reading your specific problem. When you are running to aggregation on 3rd of August, upto which date are you aggregating?


MarieSkoldenborg
Sidekick (Customer)
Forum|alt.badge.img+9

Many thanks @Vimukthi Mahakumbura  for your responses. 

I think I have the full picture now: 

ROUNDDIFF transactions were created for June since June was open when the “Aggregate” function for the next period was executed. 

If we run the aggregate function on day 3, we set offset to 3 days. 

And the “Inactive days” is set to 0. 

So if we want ROUNDDIFF postings to be created for September we need to run the “aggregate” function for October as soon as possible, when September still is open, correct?


Vimukthi Mahakumbura
Superhero (Customer)
Forum|alt.badge.img+19

Hi @MarieSkoldenborg , yes, that is correct. ROUNDDIFFs are created in the end of a period.You seems having an offset of few days and you modify some transactions to the previous month, that is ok. As long as the previous period is open, the aggregation we run today should create ROUNDDIFFs for the previous period. Also based on Inactive days.  

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings