Sicon Known Issues

13684 – SOP016 – Error when creating a B2B for a SO with a build item

Version Reported In

Sicon Enhancement Pack v221.0.62

Detailed Description

If you have created a Sales Order from a Purchase order that includes a stock item, you will receive an error. This is because SOP016 will try to create a Sales Order for that build item although it is manufactured internally.

Please note – For this you will need to have Sicon Manufacturing installed.

1. Within the Sage 200 menu, go to Enhancement Pack > Settings.

13684 - Image 1

2. Go to the SOP tab and enable SOP016.

13684 - Image 2

3. Create a new Sales Order, this can be done by going into Sales Order Processing > Sales Orders > Enter New Order – Full.

13684 - Image 3

4. Within the Sales Order, add a stock item for a built item. And then select the Save button.

13684 - Image 4

5. Message will appear asking if you would like to create a back-to-back PO for the sales order, select the Yes button.

13684 - Image 5

6. A pop up will appear to ask you to create a Work Order for the item, select the Create Works Order button.

13684 - Image 6

7. On the Sub assembly, if applicable, select the Finish button.

13684 - Image 7

8. A Works Order will then be created in the contact of SOP016, however, this will error.

13684 - Image 8

Impact: Low

  • Urgency | Ability to work not affected; workaround available.
  • Impact | All users affected.

Workaround

Currently, SOP016 is not fully supportive of works orders which why this error is present. We recommend you create the Works Order through Sicon Works Orders > Works Order List rather than doing it while creating a Back-To-Back. We recommend on step 6 you select the Close button.

13684 - Image 9

More information on how to create a Works Order can be found inside the Works Order Processing help and user guide.

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