You can use the BM_Production_Bus object to write production entries.  However, there isn't an event that you can attach a script to in order to catch when the picking sheet is printed.  You can however attempt to replace hide the default quick print picking sheet button and put a custom button over it in which you call the oUIObj.BT_QPPicking method and followed by your code to create the production entry where you can check the value of PickingSheetPrinted$ before you create the production entry (depending on SO Options, you may need to reread the sales order in order to get the value for PickingSheetPrinted$).

Thanks David,

Related to the above...
I have a UDF in the lines with 3 options, I am trying to update a UDF on the header if any line has a value in the UDF.
It seems simple but I cant get it to work.
Any suggestions?

I tried a pre-write/post-write/post-validate on the detail, but I am not sure how to get it to look through all the lines and IF any of them have that UDF filled out to set Header UDF to "Y"

Pre-Totals, and loop through lines.

Set oLines = oSession.AsObject(oBusObj.Lines)

retVal = oLines.MoveFirst()

do until oLines.EoF

' do stuff…

retVal = oLines.MoveNext()

loop ' oLines

If your script is on the detail object, there should be an oHeaderObj object that you can use with the SetValue method to set the UDF on the header.  A pre-write on the detail or a post validate on the detail UDF should work to trigger this and this would work fine for flagging the header UDF but it would be a one way street.

If the header UDF would ever need to be reversed then you are better off using a pre write event on the header and then loop through the lines until you find a line with the detail UDF set.  You could even use the detail object's GetResultSets method with a filter on your UDF and if the method returns a 1, a record was found matching your filter.

I'd personally do this as a line button script, for greater control on the creation of Production Entries.  Having it as a BOI script is risky for exceptions to the usual processes (like reprints of picking sheets... changing quantities...).

Yeah,

I think its gonna end up being a button script on the Prod Entry to look through the SO lines and pull the needed info.

I think creating the production entry should be triggered by a button but setting the header UDF should be fine with the table event script.

Agreed.  (The suggestion for the button script was a reply to the original post).

You might want to consider a VI import (based on ODBC) instead of a script (for pulling data from SO).

I currently have a VI import to do this and its set to run at a specific time towards the EOD.
Now that I have the information I need from the S/O I will be setting it using ODBC.
Ideally we would like this to be automatic or at least a push of a button.