• Log In
  • Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • HomePage
  • About
  • Structure
  • Schedule
    • First Half of the Semester
      • Week 1: Introduction
      • Week 2: Business Process; Assertions
      • Week 3: Fraud, P2P Controls
      • Week 4: OTC Process, Types of Controls
      • Week 5: Inventory & Shipping Controls
      • Week 6: Invoicing & Collection Controls
      • Week 7: IT vs. SAP Controls, Security 1
    • Second Half of the Semester
      • Week 8: Security: Roles, Finance Process & Controls
      • Week 9: Security: User Management, Segregation of Duties
      • Week 10: Data, SOD/SAT Review
      • Week 11: Change Management, Development
      • Week 12: Auditing, Table Security, Risk / Control Framework
      • Week 13: SAP Futures, Special System Access
      • Week 14: Character vs. Controls
  • Assignments
    • SAP GUI Installation
    • Exercise 1: Procure to Pay
    • Exercise 2: Order to Cash
    • Exercise 3: Journal Entries
    • Exercise 4: Segregation of Duties (SOD)
    • Final Exercise: Risk-Controls Framework
    • Extra Credit Assignment
  • Roster / Schedule / Teams
  • Webex
  • Gradebook

Auditing Controls in ERP Systems - 2017

Temple University

Exam 2: Case

November 8, 2017 by Edward N Beaver 1 Comment

As discussed several of the questions on Exam 2 relate to this real-world like small business case. You are encouraged to pre-read, print, etc. this case prior to the Exam.

Filed Under: Exams Tagged With:

Reader Interactions

Comments

  1. Kevin Berg says

    November 12, 2017 at 6:14 pm

    2. In your company, do you use any blueprints as documentation?  Why are process blueprints important in the documentation?

    We use blueprint documents quite a bit. For networking, we use Visio to document all of our servers and computers (on-premis and off) and how they interact with each other. This allows us to know how our network runs from the internet demarcation point to the firewall to our DC’s etc. On top of that , the computers listed show us who uses them and what permissions they have for both our file server and our Microsoft NAV ERP. Having a baseline of what is going on security wise through a blueprint system allows for tighter security without being too secure. It also helps to look at our network and users and spoof a user to test security. For instance, a new employee is hired in marketing so I can look at a base user, bring them up in our diagrams and create the user and authorizations based off of the least privileged person, login as them and poke around. Once I am satisfied, I create the actual role based off of my testing.

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Primary Sidebar

Weekly Discussions

  • Assignments (12)
  • Exams (7)
  • General (6)
  • Real World Control Failure Presentations (3)
  • Week 01: Introduction (4)
  • Week 02: Business Process; Assertions (3)
  • Week 03: Fraud, P2P Controls (2)
  • Week 04: OTC Process, Types of Controls (3)
  • Week 05: Inventory & Shipping Controls (3)
  • Week 06: Invoicing & Collection Controls (1)
  • Week 07: General IT vs. SAP Controls, Security 1 (2)
  • Week 08: Security 2, Finance 2 (3)
  • Week 09: Security: User Mgmt, Segregation of Duties (2)
  • Week 10: Data; SOD/SAT Review (2)
  • Week 11: Change Management, Development (3)
  • Week 12: Table Security, Control Framework (2)
  • Week 13: SAP Futures, Special System Access (2)
  • Week 14: Character vs. Controls (4)

Copyright © 2025 · Magazine Pro Theme on Genesis Framework · WordPress · Log in