615260 Enterprise Systems SAP Stream Wednesdays

1
615-260 Enterprise Systems SAP Stream
(Wednesdays)
L4 What is SAP R/3? (Five views of R/3 views 2
and 3a(i) today)
2
SSLC needs you!!

• Why? The Staff-Student Liaison Committee needs
  you to
• represent this subjects students to the lecturer
• participate in 2 informative meetings
• (Week 5, Tues lunchtime Week 10 Tues 5.30 PM)
• feedback information to your fellow students.
• This will enhance your CV by
• demonstrating involvement in student life
• demonstrating leadership skills to employers
• working towards having good reference letters
  from lecturers.
• Please consider volunteering!
• More information at
• www.dis.unimelb.edu.au/undergraduate/sslc.html

3
Lecture Plan What is SAP R/3?

• Revision
• Plan for the SAP Stream this semester (different
  views of R/3)
• PEAS must be configured
• Five different views of SAP R/3
• V1 Management view
• V2 User view
• V3 Technical view
• V3a. Implementation-team view
• i. Configuration

4
What is SAP R/3?
Revision
This is the old picture
5
SAPs client-server architecture
Revision
Internet
Client PC running SAP SAPgui
Server in Queensland running SAP R/3 4.7
gui graphical user interface
Database server (Oracle)
3-tier
6
User view of R/3
Revision

• We use server S03 at QUT
• We use clients 200 and 400.
• A client is a separate organization using R/3,
  not a client as in client/server.
• Clients 200 and 400 share the same servers and
  instance. As a user, you are never aware of the
  other clients presence.

7
Logging on
Revision

• To logon, click the yellow man icon
• You get a window like
• (This menu is defined in a file called
  SAPlogon.ini that you download to your Windows
  directory from sap.fit.qut.edu.au)
• Select server
• S03 R/3 Enterprise 4.7 (UM/USA)
• Click Logon

8
Logging on (2)
Revision

• Change the client code to 200 or 400
• Enter username and password
• Language defaults to English
• Click the green tick, or press Enter
• The first time you logon, you will be asked to
  change your password

9
The product is immensely powerful

• Many of the worlds largest global companies use
  SAP R/3
• IBM, Microsoft, Apple, General Motors, Chrysler
  Daimler, BMW, CocaCola, Nestle, Colgate
  Palmolive, Guiness, DuPont, Dow Chemicals, Bayer,
  Woolworths, Reebok, Exxon, Shell, Mobil, Disney
• BHP, Coles Myer, Western Mining, Toyota, National
  Australia Bank?!, Optus, Southcorp,

10
2. Plan for SAP stream this semester
11
3. PEAS must be Configured

• Organizations invest in PEAS to gain access to
  powerful computer-based information systems more
  cheaply than through custom-built software
  development.

12
What the organization gets is

• a highly configurable software product,
• containing solutions to the needs of many of the
  vendors existing customers,
• that impounds deep and detailed knowledge of many
  good and less good ways of conducting a wide
  range processes in a broad range of industries
• Are these best practices? Not necessarily!

13
The problem for the licensing organization is to
achieve fit

• Find the right combination of processes for its
  own changing needs,
• Configure the software to meet those needs, and
• Implement the new processes in its own
  organization.

Consider fit for a pair of jeans. They can be too
tight, too loose, or just right. But if you put
on weight, they wont fit. Likewise for
organizations.
14
Changing PEAS Options range from Configuration
to Customization

• Configuration
• Screen masks (e.g., 3 screens into one)
• Workflow programming
• Extended reporting
• User exits
• ERP programming (e.g., ABAP/4)
• Interface development
• Code Modification (Customization)

Discussed later in this lecture
Source Brehm, Heinzl, and Markus, Tailoring ERP
Systems A Spectrum of Choices, 2000
15
Is our IDES R/3 system at QUT configured or
customized?

• The software we use this semester is configured,
  for a company called IDES, but not customized (
  vanilla SAP).
• Configuration specifies company names,
  organizational structure, chart of accounts,
  etc., which clearly differ from organization to
  organization.
• Configuration is achieved by entering values in
  tables using the Implementation Guide (IMG) part
  of R/3.

16
(No Transcript)
17
Why is achieving fit difficult?

• Changing processes in organizations is hard
  (TQM/BPR, change management)
• Customizing the software is hard (programming)
  and causes problems for software upgrades.
  (Recall, customizing is heavy-duty change, not
  just configuration.)
• Knowing what processes are best for your
  organization is hard (the best placed person to
  guide this is the process owner)
• Over time, both business needs and the software
  evolve. The goal is on-going fit.

18
4. Five Different Views of SAP R/3

• V1 Management view (Monday stream)
• V2 User view (Process, Data, Screens)
• V3 Technical view
• V3a. Implementation team view
• Configuration
• Customization
• V3b. Software developers view
• V4 External Observers view

19
(No Transcript)
20
User View
21
User View Screens
22
User View

• In this subject, the Accounting module lectures
  (L8, 10, 12, 14) and Practical modules 1-6
  (including Project 2, 20) will give you a user
  view of SAP R/3 version 4.7.
• Ultimately, of course, what users do with the
  system is the reason for its existence.
• Initially, users have a huge amount to learn
  about how to use their configured version of R/3.

23
Detailed Subject Outline, 2004 (p.9)
24
User View Client

• From a users point of view, the client code,
  e.g., 200, defines their organization.
• As mentioned earlier, the client we specify as we
  log in is not the same as client in
  client/server.

25
4. Five Different Views of SAP R/3

• V1 Management view (Monday stream)
• V2 User view (Process, Data, Screens)
• V3 Technical view
• V3a. Implementation team view
• Configuration
• Customization
• V3b. Software developers view
• V4 External Observers view

26
Technical view architecture
27
Technical view Basis, Applications
Since 2002 Basis is called Web Application
Server. We are using WAS 6.20.
28
Technical view of R/3 Instance

• A central R/3 System consists of a single
  instance that is essentially all the code and a
  single database for R/3 (usually on one database
  server and one or more application servers)
• Compare when you start up MS-Word on your PC,
  you start up an instance of Word.
• We have two clients running on the one instance
  (clients 200 and 400).
• Compare you can edit more than one document in
  MS-Word.

29
Tools, ABAP Workbench, Overview, SE16-Data
Browser, table T000
30
Here we see the two clients on the one instance
31
4. Five Different Views of SAP R/3

• V1 Management view (Monday stream)
• V2 User view (Process, Data, Screens)
• V3 Technical view
• V3a. Implementation team view
• Configuration
• Customization
• V3b. Software developers view
• V4 External Observers view

32
V3a. Implementation Team View

• In this subject, the Configuration lectures
  (L16, 18, and 20) and Practical module 9
  (including Project 3, 20) will give you an
  implementation team view of SAP R/3 version 4.7.
• The implementation team has a much more technical
  view of R/3 than the users. They think of R/3 in
  terms of parameter tables, procedures, database,
  and transports from the development to
  production version of the system.

33
Detailed Subject Outline, 2004 (p.9)
34
Implementation team view Achieving Fit
Assess and explore the PEAS
Changes to the PEAS
Agree on Redesigned Processes
Changes to Org. Processes
Assess and explore Org. Processes
Kirchmer, Mathias. Business Process Oriented
Implementation of Standard Software How to
achieve competitive advantage quickly and
efficiently. Berlin, New YorkSpringer-Verlag,
1998
35
Implementation team view Configuration to
Customization
Funkies

• Configuration
• Screen masks (e.g., 3 screens into one)
• Workflow programming
• Extended reporting
• User exits
• ERP programming (e.g., ABAP/4)
• Interface development
• Code Modification

PWC speak
ABAPers
Source Brehm, Heinzl, and Markus, Tailoring ERP
Systems A Spectrum of Choices, 2000
36
Configuration

• I will use the term configuration to refer to
  changing parameters in tables in SAP R/3
• SAP promises that configuration specifications
  will transfer without problems to later versions
  of their software
• (Confusingly, SAP calls configuration
  customization!)

37
Tools, Accelerated SAP, Customizing, SPRO Edit
Project, SAP Reference IMG
1
2
Configuration
38
Defining company codes (you configure the SD
module for IDES in Module 12)
3
4
39
These are all companies in the one client, client
200.
40
(No Transcript)
41
(No Transcript)
42
(No Transcript)
43
SummaryFive Different Views of SAP R/3

• V1 Management view (Monday stream)
• V2 User view (Process, Data, Screens)
• V3 Technical view
• V3a. Implementation team view
• Configuration
• Customization
• V3b. Software developers view
• V4 External Observers view

44
Plan for SAP stream this semester