1 / 16

Ramesh Kumar eAlliance Corporation www.eAlliancecorp.com

Complete Trusted Guaranteed. How Not To Do an R12 Upgrade Project. Ramesh Kumar eAlliance Corporation www.eAlliancecorp.com. R12 Upgrade Challenges?. A Typical R12 Upgrade Implementation. DBA Team Delivers First Release of R12 Instance Development Team Fixes Code Breaks

portia
Download Presentation

Ramesh Kumar eAlliance Corporation www.eAlliancecorp.com

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. Complete Trusted Guaranteed How Not To Do an R12 Upgrade Project Ramesh Kumar eAlliance Corporation www.eAlliancecorp.com

  2. R12 Upgrade Challenges?

  3. A Typical R12 Upgrade Implementation • DBA Team Delivers First Release of R12 Instance • Development Team Fixes Code Breaks • End-less Email Chains • ‘UAT’ • R12 Go-Live

  4. Typical R12 Project Outcomes Today …. • Costly Project Overruns • Business Flow Disruptions • Frustrated Users • Negative Impact on Overall Business Can you afford this in today’s economy?

  5. Problem #1: Functionality Surprises • Confession from an Operational Manager – Finance & Systems, after their R12 Upgrade Project • What Could Have Gone Better? • “We could have been more prepared at the start of the project around the nature and scale of changes coming in with R12” after R12 Go-Live Surprise! Surprise !! Surprise !!!

  6. Approach: Tackle Changes Ahead of the Project • Explain what R12 changes mean to users before starting the project. For ex. TCA, Supplier Master, Payments, Collections, GL • Review and document key business process flows with to understand the R12 impact • Don’t Deliver Training 1.0 in a Training 2.0 World • Classroom training (Training 1.0) doesn’t cut it. • Instructional Videos. • Create a Knowledge Vault of recorded videos for on-demand retrieval. • Training 2.0 possible with Enterprise Social Network. • Leverage tools like UPK

  7. It’s Starts With The Process ….

  8. Step #2: Collaboration

  9. Collaboration Technologies Today ….. According to McKinsey Global Institute Business and Economics Research Arm of McKinsey & Company

  10. The Social Network Built for the R12 Upgrade Project

  11. The Social Network Built into the End-User Workflow

  12. Culprit #3: Underestimating CEMLI Impact • Do Not Underestimate the impact of CEMLI objects

  13. Invest Time and Effort in R12 Technology Changes • Train Developers in New R12 Tools • Utilize automated tools for the CEMLI Migration to R12

  14. Step #4: Testing Practices • “Testing is the single most aspect of ERP Upgrade Projects” – AMR Research • “Plan to have the same testing phase as you would in a new install, including formulating test cases, checking results, and retesting as needed” – Director of IT/ERP Project Manager after R12 Go-Live Surprise! Surprise!!! Surprise !!!

  15. Solution: Establish a Solid Test Strategy • Document business processes as a basis for testing • Testing just a few steps is NOT a “Testing Strategy” • Entering an order • Shipping an order • Creating an invoice and collect money • Whole lot of other stuff need to be tested • Develop Test Scripts and try to automate the process • Leverage tools such as Oracle Automated Testing Suite (OATS)

  16. Summary: How to Save Money on R12 Upgrades Upgrade 1.0 Upgrade 2.0 • Training 1.0 -- Late  Training 2.0 – Early • Email/Phone  Collaboration 2.0 • CEMLI Migration  Technical Training Upfront • Testing  Automated Testing Tools

More Related