Welcome Robert! You are diving right into the deep end!
oof… Scheduling via BPM is not for the faint of heart. There are so many methods called and secret sauce injected, it is hard to reproduce the epimagic for this particular task.
First you need Jose’s trace parser to help make sense of the traces (you dont strictly NEED it, but it helps!). Trace Helper Utility for Epicor ERP 10 - Epicor ERP 10 - Epicor User Help Forum
Next run your trace again, and reproduce the methods you want to trace. If you are scheduling a job, turn on tracing before you open Job Entry. This should give you a more complete view of all the methods and the parameters they used.
Next you need to start reproducing these methods in a BPM. I often find that we need to use GetDatasetForTree, before I call any methods, then I have to use an update table by query to make changes to the data before finally doing the update method. Here is a recent BPM example where both of the above are needed: How to unengineer a job using a BPM? - Epicor ERP 10 - Epicor User Help Forum
Good luck!
Nate