10308 – Multiple finished item cost split % default calculation

Version Reported In

Sicon Manufacturing v.221.0.58

Detailed Description

Sicon Works Order Processing allows you to add multiple finished items to a works order. If doing so, it’s necessary to decide on a split of how the cost of the works order should be split – how much should be apportioned to finished item A, and how much to finish item B.

The cost split is done on the “Finished Products” tab of the Works Order. Here, the user is able to enter the cost split on either a percentage basis or an exact cost basis.

On initial adding of a second finished item to a works order, the system should calculate a default cost split based on the average buying price of each finished item; i.e. if works order is to build 3 of item A (average buying price £20) and 4 of item B (average buying price £10), the default cost split should be 60% to item A (calculated as total cost for item A 3 * £20; over total cost of full works order 3 * £20 + 4 * £10); and 40% to item B.

This is a default split only – and is designed so the user can override / enter a new split.

There have been occasions where users have reported that this initial default split is calculating incorrectly (note – exact replication steps to make it calculate incorrectly are unknown).

Impact: Low

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

Workaround

The default cost split is designed only to be a suggestion, and should never be automatically relied upon. Instead, when using multiple finished items on a works order, the user should always review the cost split before booking in a finished item (and there is a pop-up prompting the user to do so). Even if default calculation is incorrect therefore, user should enter the correct split before booking in any finished items.

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.