ERO system: implementation, audit and control risks

• Abstract:
  
  • 3.1. The architecture of ERP project
    
  • 3.2. ERP implementation phases ............................................................... ......11
    
  • 4.1.3.1. Visibility
    
  • 4.1.4.2. Lack of focus
    
  • 4.3. Required Action
    
  • 5.1. Introduction
    
  • 5.1.1.1. About CEGID ERP System
    
  • 5.2. Review management process 40
    5.2.1. Audit services
    
  • 1. Introduction
    
  • 2. ERP System Implementation 2.1. What is an ERP System?
    
  • 3. Implementation of ERP System
    
  • 3.1. The architecture of the ERP project
    
  • 3.1.1. Change management
    
  • 3.1.2. Technical structure
    
  • 3.2. ERP System implementation phases
    
  • 3.2.1. launch phase
    
  • 3.2.1.1. Build the project and release means
    
  • 3.2.1.2. Confirm the objectives and identify the open questions
    
  • 3.2.1.3. Initiate information systems mapping
    
  • 3.2.2. Design phase
    
  • 3.2.2.1. Validate options and close open questions
    
  • 3.2.2.2. Define scope and structures
    
  • 3.2.2.3. Identify and address specific risk
    
  • 3.2.2.4. Defining strategy and technical means
    
  • 3.2.3. Implementation of the solution
    
  • 3.2.3.1. Coordinate sub-projects
    
  • 3.2.3.2. Organize the deployment
    
  • 3.2.3.2.1. A deployment plan
    
  • 3.2.3.2.2. Deployment teams organization
    
  • 3.2.3.2.3. Training
    
  • 3.2.3.2.4. Anticipate Actions
    
  • 3.2.3.3. Upgrading existing repositories
    
  • 3.2.4. Integration phase
    
  • 3.2.4.1. Prepare toggle plan
    
  • 3.2.4.2. Validate integration
    
  • 3.2.5. Production phase
    
  • 3.2.5.1. Prepare the structure
    
  • 3.2.5.2. Simulate actual operation These operations simulate the final production scale.
    
  • 4. ERP System Audit and Control Risks
    
  • 4.1. Reasons for an ERP System Audit
    
  • 4.1.1. Increased Risk
    
  • 4.1.2. Higher Levels of Regulation
    
  • 4.1.3. Efforts to meet new regulatory requirements
    
  • 4.1.3.3. Efficiency
    
  • 4.1.4. Common mistakes 4.1.4.1. Poor planning
    
  • 4.1.4.2. Lack of focus
    
  • 4.1.4.3. Competency of Auditors
    
  • 4.1.4.4. Reliance on technology for the solution
    
  • 4.2. What should be reviewed?
    
  • 4.2.1. Hardware
    
  • 4.2.2. Network
    
  • 4.2.3. Software
    
  • 4.2.4. Processes
    
  • 4.2.5. Users work
    
  • 4.3. Required Action
    
  • 5.1.1. AS-Solar, CEGID and evolution of the implementation 5.1.1.1. About CEGID ERP System
    
  • 5.2.2. Audit Purchases Department
    
  • 5.2.3. Audit Sales department
    
  • 5.2.4. Recommendations
    
  • 5.3. Implementation phases 5.3.1. launch phase
    
  • 5.3.3. Implementation of the solution
    
  • 5.3.3.1. Coordinate sub-projects by service
    
  • 5.3.3.2. Integration of two new module
    
  • 5.4. Management process of AS-Solar company after ERP implementation
    
• Conclusion