16581 – Unconfirmed Costs Display Incorrect or Negative Values After Multiple Book and Unbook Actions

Version Reported In

Sicon Manufacturing v221.0.200

Detailed Description

This issue occurs exclusively when unconfirmed costs are enabled and the finished goods item is traceable under a costing method other than Actual, such as FIFO.  Sicon strongly recommends avoiding the use of unconfirmed costs due to the complexity and risk of confusion. In this scenario, unbooking a works order records the transaction at zero cost, and if the order is then rebooked and completed, the displayed cost may appear negative or incorrect.

In the example below, a works order has been booked and unbooked three times before the fourth and final booking. This is a simplified example of an expected cost of 20.00:

At the point of completing the works order, the complete routine calculates all booking costs correctly for stock and nominal postings, but presents an updated incorrect cost on the booking transactions window:

This negative value continues to increase with the number of unbookings.

Although this can look concerning, the underlying financial postings and stock valuations are accurate. The issue is purely visual:

As outlined in Sicon’s guidance on unconfirmed costs, the greater the number of transactions involved, the more complex it becomes to track and interpret the nominal bookings.

This will impact environments where unconfirmed costs are enabled for traceable items without Actual costing.

Impact: Low

• Urgency | Ability to work not affected; workaround available, visual issue only.
• Impact |All users affected, but only if using the features described above.

Workaround

Use Actual costing with a traceable built item and avoid enabling unconfirmed costs. No alternative workaround has been identified in the reported version.  To date, this issue has only been observed in a single environment. Changes to this functionality affect a high-risk area of the product, and enhancements are already scheduled as part of the roadmap for a future release.

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.