SAP Implementation Risks
Content
Inadequate AS IS Documentation
Requirements Not Clear
Vendor Software Problems
No Scope Verification
Test Tools Not Used
Ambiguous Capacity Testing Requirements
Loss Of Key People
Disconnected Transport Management Tool
Undocumented Assumptions
Neglecting The End User
Deficient Regression Testing
Hidden Scope Statement
Diluted Sign Offs
Poor Project Governance
Unclear Documentation Standards
  SAP Implementation Risks

(Submitted by: Jose Fajardo, Company: )
 
Neglecting The End User
Page 10 Of 15
 
  1. Neglecting the end user

Symptoms: One of the most overstated attribute of an ERP system is the promise of real-time integrated data. However one of the biggest nightmares that end users find with an ERP system is integrated data. When closely examined we see that the promise of integrated data can deprive end users from making data adjustments or on the fly changes that were common with legacy applications.  

Other common problems that ERP end users face is finding data, producing the right reports, increased complexity, mis-configured workflow,  ill-defined processes for performing critical tasks, recording of data in different places, etc. 

ERP systems can drastically revamp the work of end users and adversely affect a company’s mission critical processes when the end user input is ignored.  

Symptoms: Involve the end user early on during the requirements gathering phases and confirm with end users that requirements have been correctly captured and understood. Elaborate understanding of requirement with flow process diagrams. Obtain end user sign off and approval on captured requirements before proceeding to design a solution.  

For complex business functionality to be replaced with the ERP solution hold prototype sessions to demonstrate the systems’ capability, ease of use, and conformance to business rules and requirements. Solicit feedback from end users during the prototype sessions and ensure that all end users concerns and questions are addressed in order to minimize impact of the proposed solution in production.  

Additionally provide pre-selected User Acceptance Testing (UAT) participants with integrated test scenarios which allow peer reviews. The objective is to include the UAT participants early during the design phase and not just turn over a system that will be blindly tested during UAT.  

 
Stats Box
Vendor Listings (9)
Jobs (3)
Resumes (3)
Tutorials (18)
Articles (22)
Code Snippets (1)
CBTs (17)
Books (4)
Online Training (15)
Latest 5 Articles
Comment from December 1999
Comment from December 2000
Comment from October 2002
Almarai SAP Reference
Invoice Verification automation using SAP Workflow
 
Copyright © 2007 SapDox.com. All rights Reserved.