Skip to main content
Solved

Calculate Replenishment Parameters failed with error

  • 7 February 2024
  • 9 replies
  • 85 views

We are setting up and testing the “Calculate Replenishment Parameters” for certain items.  Not sure if we have missed some setting(s) in the Replenishment tab as the “Calculate Replenishment Parameters” process failed with a  message “IN Error:  InternalError: Sequence’s sorting order is wrong or it’s not sorted”.

Any suggestions would be really appreciated as this is our first time setup and try the Calculate Replenishment Parameters.  Please find attached the settings on the Replenishment Tab in one of the item, and also the Calculate Replenishment Parameters errors when we run the process.  Thanks...

9 replies

Kandy Beatty
Rank
Userlevel 7
Badge +16

HI @dngu 

Can you pull the trace error and see what that is saying?

Kandy ~ If a member helped you, please *Like* their post, and if a member provided an answer to your question, please mark it as *Best Answer*.
D
Rank
Userlevel 2
Badge

Hi @Kandy Beatty

I have attached the file ie. “Calculate Replenishment Parameters error” in my original message.  It’s the trace errors on some of the items that I exported from the error message.

 

K
Rank
Userlevel 5
Badge +1

Any news on this?
I encountered this for the first time today too.
Here is part of the trace:
 

 

D
Rank
Userlevel 2
Badge

Hi @krausef77  There is no further update on this topic yet.  We are still searching an answer.  Thanks...

jwaldron46
Rank
Userlevel 3
Badge +1

We ran into this today also.  Following this thread now...

Jeff Waldron
jeremyd45
Rank
Userlevel 5
Badge +1

We had a client run into an issue where they were unable to process because there was an invalid Date/Time parameter. It seemed to have happened related to an upgrade, but I can’t figure out why that would have mattered. 

Be the change you want to see
jwaldron46
Rank
Userlevel 3
Badge +1

Acumatica Support was able to find our specific issue.  For the two items that received this error, the “Periods to Analyze” were set to Zero instead of our standard periods we use.  Worked fine when I corrected the items.

Jeff Waldron
B
Rank
Userlevel 1

Hi all, to confirm what @jwaldron46 found, in testing I found the same. So against the replenishment class on the item (last column by default) must have non zero value to calculate (makes sense!).

jeremyd45
Rank
Userlevel 5
Badge +1

Acumatica also identified that if there is a leap year, the calendar may also break. 

Be the change you want to see

Reply


Terms & ConditionsCookie settings