Oracle R12 one year on: Harnessing the · PDF fileOracle R12 one year on: Harnessing the...
Transcript of Oracle R12 one year on: Harnessing the · PDF fileOracle R12 one year on: Harnessing the...
Oracle R12 one year on:
Harnessing the benefits
Ben Heath and Nik Sharkey
Finance Division
Wednesday 1 October 2014
R12 then – November 2013 to now
• Over 16,000 incidents raised in ten months.
• Over 650 changes raised in ten months.
• Currently 4,700+ users.
• Over 240,000 purchase orders raised.
• Over 390,000 payment documents raised.
• Nearly 1,900 new projects created.
• Over 150,000 reports run.
R12 – what went well
• We went live on time.
• We’ve paid the suppliers and our employees.
• We’ve invoiced and collected funds from customers.
• System unavailability has
been limited.
• Year end has so far been
successful.
R12 – what didn’t go so well
• Some aspects of project reporting.
• Some data migration.
• Approval hierarchies.
• Uptake of training before ‘go live’.
• Service level from Financial
Systems Support Centre
(FSSC).
Issues from user feedback
• The upgraded system is too complicated and too slow.
• Better guidance and improved training is needed.
• FSSC response times need to be faster.
• Specific issues:
• 31% more detailed report descriptions and better distribution.
• 27% - improved catalogue/ more items within purchasing
• 22% - better search function when purchasing
• 29% - resolution to VAT function issues.
R12 now – business as usual
• Around 250-300 incidents a week.
• Some of the fixes applied have reduced the number of
issues raised.
• Continuing to work with Oracle on more complex
issues that
cannot be resolved
in-house.
2014 priority: new supplier registration
• Change supplier set up form.
• Improve on the automation of this process.
• Better visibility of the request.
• Quicker for the Finance
Division to process.
2014 priority: improved shopping
experience
• People familiar with a range of online shopping tools.
• Looking at products that would create the more user-
friendly shopping experience in iProcurement.
• For example:
• increased search capability
• greater filtering functionality
• more detailed comparisons
2014 priority: iProcurement tax
personalisation
• iProcurement tax personalisation:
• reduce the number of errors users are experiencing
• remove the need to select ‘Yes’ on each line providing the
users with a greater user experience.
• 30 new reports/enhanced reports.
• Improve report distribution.
2014 priority: improved reporting
Planned development for 2015
• Document management (precursor to i-Expenses).
• i-expenses
• Budgeting tool
• Reporting
• XL Connect
All longer term developments are draft and subject to
working with the new Oracle departmental advisory
group
Improving our customer service
• Comprehensive review of Financial Systems Support
Centre
• Ensure correct resource and skills are
available to develop and support.
• Continuous customer service training
to ensure excellence in
customer service.
Questions or queries?
• Take a look at our web pages at
www.admin.ox.ac.uk/finance/support
• Call the Helpdesk on (2)84800