1 / 20

eMARS 3.10 Upgrade Reporting User Group Meeting July 31, 2014

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. Agency Report Leads. Each agency should have a Reporting Lead identified

callum-levy
Télécharger la présentation

eMARS 3.10 Upgrade Reporting User Group Meeting July 31, 2014

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. eMARS 3.10 UpgradeReporting User Group MeetingJuly 31, 2014

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

  3. 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: http://finance.ky.gov/services/statewideacct/Pages/agencydelegationandcontactinformation.aspx • Contact Finance Customer Resource Center (Finance.CRC Group@ky.gov) with updates

  4. 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

  5. Report vs. Query • Report • Created and Published in a central location • Available to multiple users • Intended to be runand/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

  6. 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

  7. eMARS and EBI EBI CDW / CACS-G FAS3 CHFS KYTC KHRIS eMARS KBUD etc…

  8. Agency Folders within EBI • Agency Folders are at a higher level within EBI

  9. Where We Have Been • 2006 – eMARS 3.6.01 • BO 3.0 – 3.6.01 Universes • 2008 – eMARS 3.6.03 • BO 3.0 – 3.6.01 Universes • 2010 – eMARS 3.6.03 • BO 3.1 (Deski to Webi conversion) – 3.6.01 Universes • 2012 – eMARS 3.9.01 • BO 3.1 – 3.6.01 Universes

  10. 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

  11. Where Are We Going • March 2015 -- eMARS 3.10.01 • BO 4.1 -- Universe upgrade to 3.10.01 • Improves our ability for future upgrades • Improves our ability to keep universes in sync with eMARS

  12. 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 Reports will NOT be deleted from infoAdvantage

  13. 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 Reports will NOT be deleted from infoAdvantage

  14. Procurement Document Chain Universe

  15. 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 I Need a Name 

  16. 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 • MajProg/Prog/Prog Period • Send to Finance.CRCGroup@ky.gov

  17. 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 Finance.CRCGroup@ky.gov

  18. 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, 2014 Report Leads/Developers remember not to leave reports in your Inbox! These get deleted the first of every month.

  19. 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

  20. Questions ?

More Related