1. e~Print - Innovative Ways We Use It
Presented by: Bruce Knox
University of Arkansas, Division of Agriculture
April 4, 2006
8:30 am – 9:30 am
Evaluation Code 182

2. Introduction Purpose: Automate Report Generation for e~Print
Benefits: Improved Reporting with Reduced Costs

3. Topics of Discussion/Agenda
Secure Distributed Reporting
Our First Efforts
Server Side Automation
A Month End Example
Monitoring the Automation

4. Secure Distributed Reporting
We needed a way to deliver timely reports to a geographically distributed management team.

5. We Have Faculty in Every County of Our State.

6. e~Print Delivers Our Reports
A Secure Web Server
Page Security by Fund/Orgn (Banner Security)

7. Our First Efforts At First, We Used Only MS Access Reports
Users Developed and Ran the Reports
WS-FTP Transferred the Report Files

8. This Was Great For IT After Some Minor Setup,
We Handed It All to a Super User

9. Why We Replaced The Original Reports
Our Super User Created a Lot of Reports
More Reports Than She had Time to Run

10. Time For Server Side Automation
We Use Pass-Through Queries With MS Access
That Made Reverse Engineering The Reports Easy

11. Summary, Detail, Period End Reporting
YTD Summary Reports Run Every Hour
YTD Detail Reports Run Twice A Day
Summary, Detail, and Month End Each Evening

12. A Month End Example
This is Typically all I see of this Application: An Run Notice

13. A Month End Example
This is Typically all I see of this Application: An Run Notice

14. The Managers See Only Their Reports

15. Our Month End Reports Are Run Automatically

16. This is Done Using the Banner Calendar
A cron run shell script runs a SQL*Plus script to check if the Month End Closed Today.
SPOOL fspd_closed.run
SELECT
'HOST fspd_run_closed_reports.shl', 'Closed: '||FTVFSPD_ACTIVITY_DATE||' for',
'FSPD', FTVFSPD_FSPD_CODE FSPD,
'FSYR', FTVFSYR_FSYR_CODE FSYR
FROM FTVFSYR,FTVFSPD
WHERE FTVFSPD_COAS_CODE = FTVFSYR_COAS_CODE
AND FTVFSPD_FSYR_CODE = FTVFSYR_FSYR_CODE
AND FTVFSPD_PRD_STATUS_IND = 'C'
AND FTVFSPD_PRD_END_DATE < SYSDATE -- Keeps Closing Date in the Past
AND TRUNC(FTVFSPD_ACTIVITY_DATE) = TRUNC(SYSDATE);
SPOOL OFF
START fspd_closed.run

17. Check if the Month End Closed Today
AND FTVFSPD_PRD_STATUS_IND = 'C'
AND FTVFSPD_PRD_END_DATE < SYSDATE
-- Keeps Closing Date (and Time) in the Past
AND TRUNC(FTVFSPD_ACTIVITY_DATE) = TRUNC(SYSDATE);

18. We LOG The CRON Job Tue Jan 17 21:32:00 CST 2006
fspd_closed.shl beginning
fspd_closed.shl Control Month End Reporting Scripts
fspd_closed.shl ending18
(evening before the closing)

19. Then The Closing Wed Jan 18 21:32:00 CST 2006
fspd_closed.shl beginning
fspd_closed.shl Control Month End Reporting Scripts
HOST fspd_run_closed_reports.shl
Closed: 18-JAN-2006 for FSPD 06 FSYR 06
(evening of closing)

20. Finally, The Reports fspd_run_closed_reports.shl beginning
Run The YTD Summary and The MTD Detail Reports for Month End
Wed Jan 18 21:32:00 CST 2006
fspd_run_closed_reports.shl ending

21. The Drill Down Gives Each Month

22. Each Month End Report Stores Multiple Copies

23. Each Month End Report Stores Multiple Copies

24. YTD Summary

25. YTD Summary

26. YTD Summary

27. Run: Date-Time and Report Name

28. MTD Detail

29. MTD Detail

30. MTD Detail

31. e~Print – Defining Reports

32. Defining Reports

33. Defining Reports

34. Naming the Report for e~Print

35. Naming The Report for Users

36. Where is the Title on the Report?

37. Place the Date and Time on the Menus

38. What to do with the 1st Blank Page?

39. Page Security - ORGN

40. Page Security - FUND

41. Optional email Notification

42. The Shell Scripts – Let’s See How Simple
Each Report has a Shell Script
All Report Shell Scripts are Run as One Job

43. Report Shell Script Example– Part I Setup
#!/bin/ksh
# dbr01_cp.shl
# Closed Period Reports Run 01: Orgn Summary Daily
# Run orgsumm_dbr.sql to create extract, dbr01.pco to create report,
# ftp the dbr01.lst report as 100gbsumm, then
# ftp 100gbsumm.done to e~Print dbrd Repository
print
date
print dbr01_cp.shl beginning
PATH= ...
export PATH
export ORACLE_SID=PROD
ORAENV_ASK=NO
. /usr/lbin/oraenv

44. Report Shell Script - Part II Extract and Report
# dbr01_cp.shl continued
echo "START orgsumm_dbr.sql"
#INSERT Extracted Records into Table DBR_01
run_pw_mgr.shl userid orgsumm_dbr.sql
echo beginning dbr01.pco
dbr01
echo dbr01.lst Report Complete

45. Report Shell Script – Part III Transfer to e~Print
# put dbr01.lst e~Print Repository dbrd dbr01_cp.shl continued
print ftp put dbr01.lst 100gbsumm
echo > 100gbsumm.done
ftp -n -i <<eof
user dbrd pw
ascii
put dbr01.lst 100gbsumm
put 100gbsumm.done 100gbsumm.done
quit
eof
rm -f dbr01.lst
rm -f 100gbsumm.done
print
date
print dbr01_cp.shl ending
# end of dbr01_cp.shl

46. Logging the Run dbr01_cp.shl > dbr01_cp_cron.log 2>&1
dbr01_cp_cron.log will contain any Run messages

47. Log Snippets - Part I Extract
Wed Jan 18 21:32:01 CST 2006
dbr01_cp.shl beginning
START orgsumm_dbr.sql
FSPD 06 FSYR 06 Run Date 18-JAN-2006
orgsumm_dbr extract beginning
2987 rows created.
Commit complete.
orgsumm_dbr extract complete

48. Log Snippets - Part II Report and FTP
beginning dbr01.pco
dbr01 CONNECTED TO ORACLE.
dbr01 completed
dbr01.lst Report Complete
ftp put dbr01.lst 100gbsumm
Wed Jan 18 21:32:17 CST 2006
dbr01_cp.shl ending

49. Report Shell Scripts are Run as One Job
#!/bin/ksh
#fspd_run_closed_reports.shl Run The YTD Summary and The MTD Detail Reports for Month End
# This .shl file is intended to be run ONLY by fspd_closed.shl/fspd_closed.sql
print
date
print fspd_run_closed_reports.shl beginning
echo Run The YTD Summary and The MTD Versions of Detail Reports for Month End
PATH= ...
export PATH
export ORACLE_SID=PROD
ORAENV_ASK=NO
. /usr//ora
# Set Values in Run_Dates Table was done in fspd_closed.sql run by fspd_closed.shl

50. Adding a New Report is Simple
at -q b > fspd_closed_reports_at.log 2>&1 <<EOF
dbr01_cp.shl > dbr01_cp_cron.log 2>&1
dbr02_cp.shl > dbr02_cp_cron.log 2>&1
dbr03_cp.shl > dbr03_cp_cron.log 2>&1
dbr04_cp.shl > dbr04_cp_cron.log 2>&1
dbr09_cp.shl > dbr09_cp_cron.log 2>&1
dbr05_cp.shl > dbr05_cp_cron.log 2>&1
dbr14_cp.shl > dbr14_cp_cron.log 2>&1
dbr13_cp.shl > dbr13_cp_cron.log 2>&1
dbr06m_cp.shl > dbr06m_cp_cron.log 2>&1
dbr07m_cp.shl > dbr07m_cp_cron.log 2>&1
dbr08m_cp.shl > dbr08m_cp_cron.log 2>&1
dbr10m_cp.shl > dbr10m_cp_cron.log 2>&1
dbr11m_cp.shl > dbr11m_cp_cron.log 2>&1
dbr12m_cp.shl > dbr12m_cp_cron.log 2>&1
dbr15m_cp.shl > dbr15m_cp_cron.log 2>&1
dbr16m_cp.shl > dbr16m_cp_cron.log 2>&1
dbr17m_cp.shl > dbr17m_cp_cron.log 2>&1
EOF

51. The Audit Script – Snippet I
# Any Errors?
awk '{print FILENAME, $0}' dbr??_cron.log | awk 'length >15' > dbr_audit_combined_logs.txt
egrep -i 'A file or directory in the path name does not exist.|ksh*not found.|netout: write returned 0?| 0 rows created.' dbr_audit_combined_logs.txt > dbr_audit_error_checking.txt

52. Audit Script – Snippet II
# Chose the Subject Text
if [ -s "/home/common/dbr_audit_error_checking.txt" ]
then
mail -s "dbr_audit.shl - Errors Detected" < dbr_audit_summary_plus.txt
else
mail -s "dbr_audit.shl - No Errors Detected" < dbr_audit_summary_plus.txt fi

53. Monitoring via

54. oops! From: <common@edison.uaex.edu> To: <bknox@uaex.edu>
Date: 2/15/ :18:36 PM
Subject: dbr_audit.shl - Errors Detected
Audit Report of dbrnn Logs
. . .

55. Summary e~Print Can Deliver More Than You Can Report
Simple Automation Can Bring Great Rewards
Label Your Report Pages
Use a Simple Modular Design
Automate Your Monitoring

56. Questions?

57. Please complete the on-line Evaluation Form
Thank You!
Bruce Knox
Please complete the on-line Evaluation Form
Evaluation Code 182

58. Without limitation, SunGard, the SunGard logo, Banner, Campus Pipeline, Luminis, PowerCAMPUS, Matrix, and Plus are trademarks or registered trademarks of SunGard Data Systems Inc. or its subsidiaries in the U.S. and other countries. Third-party names and marks referenced herein are trademarks or registered trademarks of their respective owners.
© 2006 SunGard. All rights reserved.