ESS User Account Automation

We would like to rewrite our existing process entirely in ProcessFlow but have not had time to do so. In the meantime we are still living with the quick-n-dirty process we put in place at implementation ... in 2009.
Process Flow 1 reads HR11 and writes a file of Lawson employees with job info, etc.
Process Flow 2 reads the RMID's and writes a file of Lawson people info.
Then we have an Access database that reads these two interfaces along with a third interface from Active Directory. The active directory file is what provides the "link" between the employee number, RMID, and the AD account. The Access database analyzes for RMID adds, changes, and inactivations and builds the userload file. It recognizes movement from employee to manager or vice versa in order to apply the correct groups and roles. The Access db has as failsafe that doesn't write out the userloadfile if there are more than 50 change records in a day - to prevent a failed interface from inactivating all of our accounts ;-)
Process Flow 3 uploads the userloadfile to the application server and executes the loadusers command.
It's very klugy, but works great.

I have a process that has been working for years using PFlow and sending it to AD. My Pflow after the ad account is created creates all of my lawson security for a user and there are smart notifications which go out to the various departments. So when a user gets created in HR I do not need to create anything. I am bound to AD. if you need more information please email me.

We have a nightly process that creates an XML file in the format that the "loadusers" utility is expecting. Our process looks for new employee records, and generates the XML file. Then we run loadusers to load it including the employee identity. But if you are hosted, sounds like you may need a couple of extra steps, like ftp-ing the file to them and they run the loadusers utility. If you need an example of the xml, send me an email - lisa.hodges@rivhs.com.