Sicon Known Issues

15140 – Average Buy Price does not update the Future Buy Price on an existing works order

Version Reported In

Sicon Manufacturing v221.0.91

Detailed Description

When creating a works order for the first time, the system cycles through some decision points to determine the “future buy price” for each component (see section 16 of the Works Order Processing Help and User Guide).

This future buy price is used to calculate the estimated cost of the works order, and where the source is average price, this is based on the average price at the point of creating the works order and doesn’t automatically update. This then means that if a stock item’s average price has since been revalued (for example, using Sage’s revaluation feature, or stock received in at a different cost), this is not updated in the estimated cost, even when using “calculate cost” on the works order.

In the example below, the unit cost (1) of PRJ-Bolts-10mm started off as 0.51463 (x4 = £2.06).  On the stock item behind (2), the average price has since been recalculated to 0.50983 (x4 = £2.04).

15140 - Image 1

Impact: Low

  • Urgency | Ability to work affected; workaround available.
  • Impact | All users affected.

Workaround

As soon as a component is issued, the correct price will be used (average, FIFO etc).  But if un-issued, the system will revert to the future buy price set at the point the Works Order was created.

It is possible to manually update the cost of the component on the works order, which will then be taken into account when using the Calculate Cost button on the Works Order (again, stock will still be issued at the actual price).

15140 - Image 2

Development Priority Voting

Please let us know your development priority for this Known Issue by providing us with a star rating based on the below;

  1. Not causing any problems – not a priority.
  2. It’s annoying, but not causing too many problems – not a priority.
  3. Would be nice to be fixed, but not essential – not a high priority.
  4. It would be helpful to have this fixed – fairly high priority.
  5. Really needs to be fixed as soon as possible – high priority.
0 - Development Priority Level
5 0%
4 0%
3 0%
2 0%
1 0%
5
Please Share Your Feedback
How Can We Improve This Article?
Contents