You could have SAW export the data needed to create the PO to a delimited file and then trigger a VI import job, this would be the easiest to implement. 

Next up would be having SAW execute a script file or SAW's scripting feature (think it uses some variant of Visual Basic) that contains the code to create the PO through sage 100's BOI. This will require knowledge of working with the BOI, you can search this forum for examples and search either this forum or the knowledge base for scripting.docx for a good starter doc. There should also be a course on SageU.

You could have SAW export the data needed to create the PO to a delimited file and then trigger a VI import job, this would be the easiest to implement. 

Next up would be having SAW execute a script file or SAW's scripting feature (think it uses some variant of Visual Basic) that contains the code to create the PO through sage 100's BOI. This will require knowledge of working with the BOI, you can search this forum for examples and search either this forum or the knowledge base for scripting.docx for a good starter doc. There should also be a course on SageU.

Thank you. Found out the request is for Sage 100 Premium so it sounds like that's an advantage. Appreciate the feedback.

DO NOT attempt to write back via SQL, you will bypass crucial logic only handled by the business objects. You MUST go through VI or the BOI.

Thank you good to know as this is my first encounter learning about this. Really appreciate it!

Be careful with direct data edits through SQL.  This bypasses all the important Sage business logic implemented through BOI.  I limit direct SQL edits to simple things like UDF field updates.  Creating a PO directly in SQL is not recommended at all.  David's suggestion of a VI job is the safest approach, but you can use a UDT instead of CSV if you prefer.