Sicon Known Issues

13406 – Booked and Issued costs different on WO, causing differences in Project Enquiry

Version Reported In

Sicon Manufacturing v221.0.18

Detailed Description

A scenario has been reported where a Parent Works Order is showing a different booked in cost to the issued costs (and no variance postings have been made). If using Project Integration, this then leads to the Project Enquiry Stock tab showing the finished item costs at a different value to the total of the Works Order lines on the Works Order tab.

13406 - Booked and Issued costs different on WO, causing differences in Project Enquiry - Image 2

This seems to only be an issue where a subassembly(/ies) has been booked in at one cost, and the parent works order is displaying the issued cost differently.

A simple illustration to explain further:

  • Subassembly:
    • Components £10
    • Labour £10
    • Finished item booked into stock at £20
  • Parent
    • Components £50
    • Labour £50
    • Subassembly item £15 (rather than £20)

Parent finished item therefore booked in to stock as £115 (£50 + £50 + £15)
Works Order would show issued costs as £120 (£50 + £50 + £20)

Impact: Low

  • Urgency | Ability to work not affected; inconvenient.
  • Impact |Single User Affected.

Workaround

As this is predominantly a display issue there is no workaround at present, other than to rely on the Stock tab rather than Works Orders tab.  The booked stock value on the project is correct, and it’s simply the Works Order tab displaying an inaccurate issued figure.

We have been unable to replicate and are therefore unable to resolve this known issue at present.  If you are experiencing this issue and know the steps to replicate on demand, please send these to Sicon Support quoting known Issue 13406 and this can be investigated further.

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