eMARS 3.10 Upgrade Reporting User Group Meeting July 31, 2014

Agenda  Recap  eMARS and EBI  Where We Have Been  Where We Are Going  Timeline  Procurement Document Chain Universe  Query Tool  Next Steps 2

Agency Report Leads  Each agency should have a Reporting Lead identified  The Reporting Lead will be the primary contact for all information related to the reporting upgrade  Confirm your Reporting Lead on the Agency Contact List at: cydelegationandcontactinformation.aspx  Contact Finance Customer Resource Center (Finance.CRC with updates 3

Report Developers  Report Developers are those individuals responsible for creating, publishing and maintaining the reports to be utilized by the agency users  Agencies need to identify these individuals – the EBI security role would be eMARS Advanced 4

Report vs. Query  Report –Created and Published in a central location –Available to multiple users –Intended to be run and/or printed by multiple users  Query –One time or limited data retrieval –Looking for raw data, not necessary a “pretty result” –Export to Excel may be preferred 5

eMARS and EBI  EBI is a consolidated Business Objects environment which allows multiple applications from multiple agencies to share resources  eMARS is a “tenant” of EBI  eMARS reporting upgrade is independent of EBI –Upgrade would occur regardless of EBI 6

EBI eMARS and EBI 7 KBUD KHRIS FAS 3 CDW / CACS-G eMARS KYTC CHFS etc…

Agency Folders within EBI  Agency Folders are at a higher level within EBI 8

Where We Have Been  2006 – eMARS –BO 3.0 – Universes  2008 – eMARS –BO 3.0 – Universes  2010 – eMARS –BO 3.1 (Deski to Webi conversion) – Universes  2012 – eMARS –BO 3.1 – Universes 9

Where We Have Been  eMARS Reporting had only one Update –Deski to Webi in 2010  There have been NO Universes changes since eMARS go-live in 2006  Upcoming Upgrade much needed 10

Where Are We Going  March eMARS –BO Universe upgrade to  Improves our ability for future upgrades  Improves our ability to keep universes in sync with eMARS 11

Timeline  September 2, 2014 – Reports residing in designated folders in infoAdvantage will be “Migrated” to new environment (BO 4.1 Test) ‒ Report Lead’s Favorites ‒ Report Developers’ Favorites ‒ Agency Folders 12 Reports will NOT be deleted from infoAdvantage

Timeline  December 1, 2014 – Second “migration” from designated folders –Only new or updated reports within the previously defined folders –Reports will be placed in a separate location in new environment to distinguish from previous migration  March 6, 2015 – Third “migration” from designated folders –Only new or updated reports within the previously defined folders –Reports will be placed in a separate location in new environment to distinguish from previous migration 13 Reports will NOT be deleted from infoAdvantage

Procurement Document Chain Universe 14

MRDB Revisited  Method for non report developers to connect to the eMARS data warehouse tables to create database queries using query tools of their choice (Access)  Requires Oracle Client (11 or 12C)  Requires TNSNAMES file  “FCT” like tables to be included ‒ Expenditure ‒ Revenue ‒ Cash ‒ Budget ‒ Accounting Journal 15 I Need a Name

What’s Next  Send us your thoughts on Statewide Reports –Remember these reports are built at a statewide level using statewide COA elements Fund Dept Unit Function OBJ/REV/BSA Maj Prog/Prog/Prog Period  Send to 16

What’s Next  Name Your Report Developers –Create, Publish, Maintain Reports to be run/printed by multiple agency users –Not someone who just needs to query data— “We have an APP for that!”  EBI security role would be eMARS Advanced  Send to 17

What’s Next  Agency users should be evaluating Favorites –Send reports to be migrated to Report Lead or named Developers –Delete any unnecessary reports  First migration date September 2, Report Leads/Developers remember not to leave reports in your Inbox! These get deleted the first of every month.

What’s Next  Begin Re-build of reports ‒ Use FY2013 data as it is static and will make a good comparison from infoAdvantage to new environment The BO 4.1 Test environment is a copy of production from a few months back so FY2014 is not a full year 19

Questions ? 20