Sicon Known Issues

12432 – Booked Works Order cannot be allocated or issued to complete it

Version Reported In

Sicon Manufacturing v.221.0.80

Detailed Description

This is a specific issue when the Works Order setting to “Reduce Line Quantity when booking” is enabled, and a works order has lines that have not been issued.

If the works order has a part-issued line, this setting will reduce the line quantity to the quantity issued when booking, this is as expected.

However, if the works order has a line that has not been issued at all, this setting will not touch those lines.  This is where this issue occurs.

The setting allows the works order to still be booked, but it cannot be completed because there are lines that have had no components issued:

The problem is that it is not possible to allocate and issue the components through editing the individual works order as these options are greyed out in this situation:

Impact: Low

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

Workaround

There are a couple of options to work around this.

Configuration (recommended)

Select one of the options to Remove unused lines, or Zero unneeded lines when booking, so the system knows how to handle lines that have had nothing issued against them.

See the WOP Settings section of the Works Order Processing User guide for more information on these settings – https://www.sicon.co.uk/user-guide/works-order-processing-help-and-user-guide/#13-11.

Work around (for one works order at a time)

Alternatively, if the lines should be issued and the works order is already in a booked state, use the Process Works Order Screen to issue the lines instead.

Note, this will complete the works order without the need for an additional step to complete the booked works order.

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