1. eMARS 3.10 Upgrade Reporting User Group Meeting October 9, 2014

2. Agenda  Updated Migration Plan  Universe Compare  Getting Started  MRDB 2  Resources & Assistance 2

3. Updated Migration Plan

4. Migration Plan  Agency Report Folders were migrated from infoAdvantage to the new environment (EBI 4.1 Test) on October 1 4 Reports were NOT deleted from infoAdvantage

5. Migration Plan  October 15, 2014 – Reports residing in designated folders in infoAdvantage will be Migrated to new environment (EBI 4.1 Test) ‒ Report Lead’s Favorites ‒ Report Developers’ Favorites 5 Reports will NOT be deleted from infoAdvantage

6. Migration Plan  December 1, 2014 – Second migration from designated folders –Only new reports within the previously defined folders will be selected –Reports that were migrated on Oct 15 will not be selected  February 1, 2015 – Third migration from designated folders –Only new reports within the previously defined folders will be selected –Reports that were migrated on Oct 15 and Dec 1 will not be selected 6 Reports will NOT be deleted from infoAdvantage

7. Migration Plan 7 EBI Test 4.1 10/15/2014 - Drop 1 All reports in the Report Developer’s /Lead’s Favorites Folders are moved to new environment (EBI Test 4.1) 12/1/2014 – Drop 2 1) New reports migrated to EBI Test 4.1 2) Reports that were migrated during the first drop will not be moved 2/1/2015 – Drop 3 1) New reports migrated to EBI Test 4.1 2) Reports that were migrated during the 1 st and 2 nd drops will not be moved After a report is redeveloped, the report must be moved to the correct Agency Folder. 12/1/2014 Copy of agency folders/reports are moved to UAT 3/1/2015 Copy of agency folders/reports moved to UAT. infoAdvantage Production 12/1/2014 Agency users may begin testing reports that have been redeveloped 3/14/2015 Cutover activities begin the night before Go-Live 3/15/2015 Go Live EBI Production 4.1 EBI UAT 4.1

8. Universe Compare

9. Custom Universes  Custom Universes no longer needed ‒ PCARD_DTL ‒ Vendor ABA ‒ Proof of Necessity ‒ Cingular ‒ Document Phase Universe-KY ‒ Inventory  Replaced with new Universe ‒ KY Security & Workflow – 3.10 OADM Security & Workflow  Linked Universes/Combination of both ‒ KY Chart of Accounts – 3.10 FIN Chart of Accounts 9

10. Custom Universes 10

11. Linked Universe 11

12. Baseline Universe Compare  A detailed 3.6.03 to 3.10.01 comparison of each baseline universe will be available on the eMARS website as completed 12

13. Getting Started

14. Availability 14 EBI 4.1/eMARS Reporting Test will be available by October 15, 2014. An email will go out next week to let you know when you can log in and begin re-development.

15. Log In  URL to EBI 4.1 Test (eMARS Reporting)  Password  Single Sign-On will be available through eMARS 3.10.01 UAT at a later date 15 http://kyeasxebi41test.easdev.dslab.ky.gov:8080/BOE/BI today@1200

16. EBI 4.1/eMARS Reporting 16

17. MRDB 2

18. Purpose  Allow users to access financial data through data warehouse views as opposed to InfoAdvantage  Run queries as opposed to reports  Export data from Microsoft Access to Microsoft Excel

19. Current Views  O_DW.VW_FCT1_EXPENDITURE –Detailed expenditure information for accounting/budgeting needs  O_DW.VW_FCT1_REVENUE ‒ Detailed revenue information for accounting/budgeting needs  O_DW.VW_FCT1_CASH – Detailed cash information for accounting/budgeting needs  O_DW.VW_FCT1_SUMMARY_LEDGER – Summarized information for selected chart of account elements  O_DW.VW_FCT1_CHARGE ‒ Detailed charge information

20. Current Views  O_DW.VW_FCT3_BUDGET_OPERATING –Single record for each 2 nd level budget reflecting the current budget amount.  O_DW.VW_FCT3_BUDGET_GRANT –Single record for each 2 nd level budget reflecting the current budget amount.  O_DW.VW_FCT3_BUDGET_CAPITAL_EXP ‒ Single record for each 2 nd level budget reflecting the current budget amount.  O_DW.VW_FCT3_BUDGET_CAPITAL_REV –Single record for each 2 nd level budget reflecting the current budget amount. 20

21. O_DW.VW_FCT1_EXPENDITURE FIELDS

22. O_DW.VW_FCT1_EXPENDITURE  Includes the following Closing Classifications: ‒ 10 Cash Expenditures ‒ 11 Accrued Expenditures ‒ 12 Encumbrances  Should Include: –All Coded Chart of Account Elements and Names –Most Rollups of Central Chart of Account Elements –Document and Referenced Document IDs

23. O_DW.VW_FCT1_REVENUE- FIELDS

24. O_DW.VW_FCT1_REVENUE  Includes the following Closing Classifications: ‒ 14 Collected Revenue ‒ 15 Billed Revenue  Should Include: –All Coded Chart of Account Elements and Names –Most Rollups of Central Chart of Account Elements –Document and Referenced Document IDs

25. O_DW.VW_FCT1_CASH FIELDS

26. O_DW.VW_FCT1_CASH  Includes the following Closing Classification: ‒ 5 Cash  Should Include: –All Coded Chart of Account Elements and Names –Most Rollups of Central Chart of Account Elements –Document and Referenced Document IDs

27. O_DW.VW_FCT1_SUMMARY_LEDGER FIELDS

28. O_DW.VW_FCT1_SUMMARY_LEDGER  Includes ALL Closing Classifications except: ‒ 6 Accounts left in old year  Should Include: –Select chart of accounts, their names and rollups –See Field List for elements included

29. O_DW.VW_FCT1_CHARGE FIELDS

30. O_DW.VW_FCT1_CHARGE  Includes the following Posting Codes: ‒ XXP3 – Standard Charge Non Reimbursable ‒ C001 – Standard Charge  Should Include: –All Coded Chart of Account Elements and Names –Most Rollups of Central Chart of Account Elements –Document and Referenced Document IDs

31. O_DW.VW_FCT3_BUDGET_GRANT-FIELDS

32. O_DW.VW_FCT3_BUDGET_GRANT  Includes a single record representing the current budget amount for level 2 of Budget Structure 39

33. O_DW.VW_FCT3_BUDGET_OPERATING-FIELDS

34. O_DW.VW_FCT3_BUDGET_OPERATING  Includes a single record representing the current budget amount for level 2 Budget Structure 3

35. O_DW.VW_FCT3_BUDGET_CAPITAL_REV-FIELDS

36. O_DW.VW_FCT3_BUDGET_CAPITAL_REV  Includes a single record representing the current budget amount for level 2 Budget Structure 42

37. O_DW.VW_FCT3_BUDGET_CAPITAL_EXP-FIELDS

38. O_DW.VW_FCT3_BUDGET_CAPITAL_EXP  Includes a single record representing the current budget amount for level 2 Budget Structure 43

39. How to access data  Contact Security Lead ‒ email Donald Sweasy with request to MRDB 2 Views within EMIAFP  Tools ‒ Microsoft Access ‒ Microsoft Excel ‒ SQL Developer ‒ Other Oracle Tools Requires Oracle Client 11 or 12c Requires TNSNAMES.ora file

40. Resources & Assistance  eMARS Upgrade Page –Report Developer’s Guide –Baseline Universe Compare –Presentations  Report Development Workshops –State Office Building – Purple Parlor –CRC and CGI resources available to help with report re-development –Schedule to be issued next week 40 Remember to use FY2013 data for testing reports.

41. What’s Next  Name Your Report Developers ‒ EBI security role would be eMARS Advanced ‒ Send to Finance.CRCGroup@ky.gov  Agency users should be evaluating Favorites –Send reports to be migrated to Report Lead or named Developers –Delete any unnecessary reports –Next migration date October 15, 2014 41

42. Questions ? 42