16695 – Using backflush to book in a Sicon Works Order is causing committed WOP-COS transactions to remain

Version Reported In

Sicon Manufacturing v221.0.91

Detailed Description

When backflushing a works order that is linked to a sales order, and Sicon project integration is enabled, committed WOP-COS postings are being left behind on the stock tab of the project enquiry screen.

In this case, the Sicon-Umbrella was booked via backflush, while the WHB-Sensor-Core-L2-SA was manually booked through the works order form. The WOP-COS transaction should have been replaced by the COS transaction.  The WOPISS entry is reversed by the SOPALLOC transaction.

Impact: Low

• Urgency | Ability to work unaffected; workaround available.
• Impact | All users affected, but only if using the feature as described above.

Workaround

Avoid using backflush to book the top-level works order. It’s fine to use backflush for subassembly works orders, but the top-level must be booked manually via the works order form to ensure accurate transactions on the project.

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.