Enterprise Resource Planning Design and Implementation IST 346 BUS 326

1
Enterprise Resource Planning Design and
ImplementationIST 346 / BUS 326
Mid-Term Review10/02/2006
2
Exam Format

• Total points 75
• Time 75 minutes
• Accounts for 25 of total grade
• Format
• Written
• Two 15 point questions 30 points
• Three 10 point questions 30 points
• Fifteen 1 point questions 15 points

3
08/23

• Roots of ERP
• What is ERP
• Advantages, disadvantages of an ERP System

4
08/25

• Supply Chain Management
• Finance, Marketing and Production
• Right stuff, place, time and price
• Horizontal vs. vertical integration

5
09/05

• Re-engineering, value chain, process model
• ERP System Development
• Plan business, technology rationale
• Design customization vs re-engineering
• Implement data migration, interfaces etc

6
09/05

• Implementation risks
• Technology -
• Organization BPR vs Configuration
• People IT, users

7
09/11

• Main Phases
• Planning scope, goals, objectives, project
  organization, strategy
• Realization configuration, interfaces
• Preparation user support
• Productive - optimization
• Overall Phases
• Training
• Project Control
• Risk Management
• Change Management

8
09/11

• Implementation Strategies
• Step-by-step
• Big bang
• Roll Out
• ASAP, Value SAP, Solution Manager

9
09/13

• SAP Architecture Policies world-wide usage,
  open policy for data access, interfaces with
  external systems
• Basis
• Set of tools and programs to interface with OS,
  DB, communication interfaces and presentation
  interface
• Enables all functional modules to work in the
  same way
• Independent layer that guarantees integration

10
Logical View of R/3 System
11
Basis Components

• Kernel and basis services
• ABAP workbench
• Presentation component

12
Kernel and Basis

• The kernel and basis services component is a
  runtime environment for all R/3 applications that
  is hardware, OS and DB specific
• Functions
• Running applications - all R/3 applications run
  on the basis system
• User maintenance - R/3 multi-user environment,
  and each user can run several independent
  applications

13
Kernel and Basis

• Database access R/3 applications connect to the
  database and its management system via Basis
• System Admin and Monitoring monitor and control
  R/3 system
• Communication communicate with other R/3 and
  non-SAP systems. Also aids accessing R/3 from
  other systems visa BAPIs

14
ABAP Workbench

• Development environment for applications in the
  ABAP language
• Create, edit, test, and organize application
  developments
• Fully integrated in the R/3 Basis system
• Written in ABAP (like other R/3 applications)

15
Presentation Component

• Responsible for the interaction between the R/3
  System and the user
• Desktop component integration

16
Software View of the R/3 System
17
Basic Architecture Concepts

• Transaction
• Dialog Step
• Logical Unit of Work
• Instance
• Client

18
Transaction

• Operation that allows changes to the database
• A sequence of related steps known as dialog steps
• SAP Dispatcher handles the sequence of the steps
• Lock mechanism
• Transaction code

19
Dialog Step

• An R/3 screen represented by dynpro (dynamic
  program)
• Dynpro has field definitions, screen layout,
  validation, processing logic
• Dynpro controls tasks for PBO (Process Before
  Output) and PAI (Process After Input)

20
Logical Units of Work (LUW)

• List of logical steps in a transaction for its
  correct execution
• Defined as an elementary processing step working
  as a locking mechanism to protect transactions
  integrity

21
Instance

• Instance administrative unit which combines all
  the components of the SAP system
• Services are commonly started and stopped
• SAP System
• One DB
• One or more instances
• Referred to as central instance

22
Service Oriented Architecture

• Service-oriented architecture (SOA) is the
  underlying structure supporting communications
  between services
• An SOA solution consists of a composite set of
  business services that realize an end-to-end
  business process
• Separating business functions into
  subroutines/methods subroutines can exist in
  any machine

23
09/15 to 09/27- Organization Structure

• FI Company, company code, controlling area,
  chart of accounts, fiscal year variant, credit
  controlling area
• MM plant, storage locations, purchasing
  organization, purchasing group, shipping and
  loading point
• SD sales organization, distribution channel,
  division, sales area, sales office, sales group