Sicon Known Issues

13539 – Written off Subcontractor POs prevent WO being completed with Unconfirmed Costs

Version Reported In

Sicon Manufacturing v221.0.0

Detailed Description

This is an issue specifically to do with using Unconfirmed Costs, Subcontractor Purchase Orders on a Works Order, and the Write Off Incomplete Orders feature in Sage.

The situation is that on the Works Order, a subcontractor Purchase Order has been raised, despatched and received so that the works order line shows as issued.  However, if the subcontract Purchase Order is not fully invoiced, these continue to show as unconfirmed costs on the Works Order, and as a result it cannot be completed.

13539 - Written Off Subcontractor POs with Unconfirmed Costs - Image 1

If the purchase order is subsequently completed through the Write Off Incomplete Orders feature in Sage, the invoice cannot be processed and therefore the costs can never be confirmed, and the works order cannot be completed.

Impact: Low

  • Urgency | BP Workaround required; inconvenient.
  • Impact | Single User Affected.

Workaround

Write Off Incomplete Orders is typically used as a tidy up exercise for historic orders.  It is therefore deemed a low-risk issue that should not present an issue for most sites, as current Works Orders are unlikely to be impacted and unconfirmed costs are not recommended for use with Sicon Manufacturing.

If this issue has occurred on a customer site, this can be worked around but will require a partial fix in SQL.

First, update the purchase order header to be “Live” from within the POPOrderReturn table (DocumentStatusID).

Next, in Sage, once the purchase order is live, it can be fully invoiced, which in turn will confirm costs and allow the works order to be completed.

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