End of Period Suite II

Configuration

1. Still logged in as the MSIADMIN for v77a, retreive copies of the sample configuration file and copy scripts from $ulib. Do not modify the originals in $ulib. Copy the scripts clear_data and copy_data into $ubin, and set their modes to 550. They should remain owned by MSIADMIN:MSIGROUP.

   	cp $ulib/clear_data $ulib/copy_data $ubin 
   	chmod 550 $ubin/copy_data $ubin/clear_data 
   		

   If you need to change them to make them writable, be sure to reprotect them when you are done.
2. Copy the configuration file sample from $ulib to your first environment where you wish to implement EOP Suite II. Set its modes to 660 for now, as it will neeed to be customized before use.

   	cp $ulib/eop_run.cfg $uetc 
   	chmod 660 $uetc/eop_run.cfg 
   		

   You can use what ever names your choose for the configuration files.
3. Edit the configuration file as appropriate for your site. Try to do your first test on a small test database to try different settings (see eop_run Configuration File for more information).
4. Make sure your test database environment is ready to run an End of Period.
5. To use EOP Suite II, you must set accruals and invoicing in the Portfolio Maintenance [U0212] update to run every day. To not run accruals or invoicing on a particular day, set ACCRUALS and INVOICES to N. You can associate different configuration files with eop_run and schedule these different versions to run at different times through cron, allowing you to determine when accruals and invoices are processed. Alternatively, you can provide a script to generate appropriate configuration files based on criteria you determine.
6. Once this is set up you can test it from the command prompt.
7. Log onto the server as the user who will submit and monitor the End of Period.
8. Execute the following:

   	eop_run –s environment-name $uetc/eop_run.cfg username password
   		

9. The logfiles used are $ueop/log/eop_run.log and $ueop/log/pport_status.log for each portfolio. Running tail –f on the portfolio log will allow you to watch the "heart beat" messages from the monitor program.
10. The same eop_run command can be executed from within a cron-driven script as well.