-
Financials
-
Commercials
-
Manufacturing
-
- 11591 - Auto allocate across multiple bins doesn't automatically select traceable numbers
- 11653 - Auto Select Traceable Items selectable when Issue Full Batch disabled
- 11367 - Scrollable View button not working on Sicon Works Order List
- 11432 - Build Time Enqury view is not exporting to Excel
- 10993 - Sort order on WO history tab
- 10307 - Error when creating WO for SO with no requested delivery date
- 10308 - Multiple finished item cost split % default calculation
- 9711 - Work in Progress variance postings when Stock > Nominal Integration is turned off
- 9633 - All Modules | Sicon fields not cleared when saving stock item
- 10636 - Works Order Comments not saving when added before WO creation
- 10856 - Not prompted to update Operations on Process WO Screen
- 9779 - Works order list doesn't retain edits to column order or sizing
- Show all articles (8) Collapse Articles
-
Sicon Approvals
9633 – All Modules | Sicon fields not cleared when saving stock item
5 - Development Priority Level
1 rating
5 | 100% | |
4 | 0% | |
3 | 0% | |
2 | 0% | |
1 | 0% |
Version Reported In
Sicon v221.001
Detailed Description
On the “Enter New Stock Item” form, we have a Sicon tab to hold Sicon module specific data. The specific options list in the tab will be dependent on the Sicon modules installed & enabled.
On completion of creating a new stock item, when you press “Save”, the Enter Stock Item Form should clear – i.e. revert to an empty form, ready for you to enter the next stock item.
Certain of our Sicon tabs however don’t – they retain their entries:
It is technically possible therefore that the user could not notice this and accidentally set this information against the second stock item.
Impact: Low
- Urgency | Ability to work not affected; inconvenient.
- Impact | Single user affected.
Workaround
After saving a stock item, clicking into another Sicon tab & then back into the one with retained data will force a refresh & empty the fields.
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;
- Not causing any problems – not a priority.
- It’s annoying, but not causing too many problems – not a priority.
- Would be nice to be fixed, but not essential – not a high priority.
- It would be helpful to have this fixed – fairly high priority.
- Really needs to be fixed as soon as possible – high priority.
5 - Development Priority Level
1 rating
5 | 100% | |
4 | 0% | |
3 | 0% | |
2 | 0% | |
1 | 0% |