SAP R/3

6.20
Upgrade

1
 Rationale for Upgrade
• First System Upgrade Since Fall 1999
• Part of Both Long-Term Strategy &
Original Purchase Decision
• Provides New Functionality
• Continued Maintenance & Support
• Support for Latest Technologies

2
 Upgrade Principles
• No Implementation of New Modules or
Functions
• Return to Standard R/3 Functionality,
Where Possible
• User Retraining Kept to a Minimum
• Freeze on New Initiatives
– Key Operational Initiatives Will Be Supported

3
 Upgrade Step One
• Many Users Already Have New Client
– Since January 2003
• Change Desktop Client
• Enhanced Appearance
• Same Functions & Transactions
• Goal: December 15 to Change All Desktops
• Communications Strategy
– Meetings with LAN Administrators
– Emails to All Users

January 21, 2003: new Windows client.

October 9, 2003: new Mac OS client.

4
5
6
 Client Upgrade
• SAPgui 6.20 for Windows & Mac OS
• Download and Install Instructions at
http://www.oit.duke.edu/techsupport/sap
• Many Users Already Have New Client
– Since January 2003
• Goal: December 15 to Change All
Desktops
• Email Notice to Be Sent to End Users

7
 Windows Minimum
Requirements
• Windows 98/ME/NT
– Pentium 200 Mhz
– 64 MB RAM
– Screen Resolution: 1024x768
• Windows 2000
– Pentium 200 Mhz
– 96 MB RAM
– Screen Resolution: 1024x768

8
 Windows Minimum
Requirements
• Windows XP
– Pentium 300 Mhz
– 128 MB RAM
– Screen Resolution: 1024x768

9
 MAC OS
System Requirements
• Different Versions for OS 9 and OS X
• OS 9
– G3 or Better
– 128 MB RAM
– Mac OS Runtime for Java 2.2.4 or Newer
• OS X 10.2
– G3 or Better
– 128 MB RAM
– Java Virtual Machine 1.3.1 or Better
(Included in OS)

10
 What to Expect
• Email Will Be sent to End Users
Announcing the Client Upgrade
• Training Sessions for LAN Administrators
– Nov. 3, 3:30 PM, 2002 Duke North
– Nov. 4, 10:30 AM, Carpenter Board Room
– Nov. 12, 2:30 PM, 130 North Building
• Goal for Upgrading All Copies of SAPgui
from 4.5B to 6.20: December 15, 2003

11
 Upgrade Step Two
• System Upgrade
• Target: April 2004
• New Appearance
• Enhanced Navigation & Improved Usability
– Example: “Favorites” Transactions List
• Comprehensive Communications &
Training Strategy
• Greatest Impact on Central Offices

12
Windows Installation

13
 Windows Installation

We’re showing how to install from PROMETHEUS using a NetWare

client. The steps are similar if downloading over FTP.
(If downloading, be sure to download the entire directory hierarchy, not
just a single file.)

14
15
16
17
BW will only be installed by user request and is not needed in most
cases.

18
19
20
21
22
23
24
25
26
27
SAPLOGON.ini - discuss implications

28
29
Mac OS X Installation

30
Mac OS X Installation

31
32
33
Bug in SAP-provided installer – doesn’t affect performance.

34
35
Can alternatively be put in /Applications – but must be an Administrator

36
37
38
39
Must be logged in as the user who will use R/3. Admin rights optional.

40
This will most often happen when Authentic Login is being reinstalled on an
OS X machine.

41
42
Required environment variables are set at the next login.

43
Congratulations!

44
 R/3 Printing
• Client Æ App Server Æ Network Printer
• Printers must be registered
http://www.r3.duke.edu, “Printer Setup” link
• Registration requires:
– IP address
– DNS name
– Manufacturer & Model
– Location
– Department

This slide describes the printing of reports and other data within R/3 -
see also Hardcopy printing later.
R/3 is compatible with a wide range of printers, especially:
PCL 5 compliant
PostScript level 2 compliant

45
 R/3 Printing
• Registration Produces Unique Output
Device Name
• User’s Default Printer Set Through su3
Transaction in R/3

Under “Defaults” tab:

– Complete “Output Device” field
– Check “Output Immediately”
– Check “Delete After Output”

These are standard settings.

A few users may need these settings modified (such as not checking
“Output Immediately”), but those cases are exceptional.

46
R/3 Printing in su3

47
 R/3 Printing
• Some users may need to print
screenshots
• (Journal entries, forms - not reports)
• Options Æ Hardcopy on Windows
• Options Æ Print on Mac OS
• Sends a conventional print job to the
user’s default printer (per OS settings)

48
 R/3 and Remote Users
• No IP restrictions
• Compatible with, but doesn’t require, VPN
• Works over slow connections (dial-up)
• Works with basic NAT firewalls.

Earlier versions of Authentic Login weren’t VPN-compliant

Previously, in cases in which a computer might have multiple IP
addresses (NAT, VPN, multiple NICs) logins would fail.
This has been corrected.

49
 R/3 and Firewalls
• Outgoing TCP ports:
– 3200-3202; 3299-3302; 3600-3605
• Incoming TCP port for printing:
– 515
• Outgoing Kerberos ports:
– 88; 749

Port 515 may need to be opened explicitly.

It can be limited to SAP application servers.

50
 R/3 and Firewalls
R/3 Hosts:
• prdn00.oit.duke.edu 152.3.101.66
• prdb00.oit.duke.edu 152.3.101.198
• prdas01.oit.duke.edu 152.3.101.67
• prdas02.oit.duke.edu 152.3.101.68
• prdas03.oit.duke.edu 152.3.101.69
• prdas04.oit.duke.edu 152.3.101.70
• prdas05.oit.duke.edu 152.3.101.71
• spoon.oit.duke.edu 152.3.101.92
• mashie.oit.duke.edu 152.3.101.93
• niblick.oit.duke.edu 152.3.101.94
• wedge.oit.duke.edu 152.3.100.17
• cleek.oit.duke.edu 152.3.101.13
• putter.oit.duke.edu 152.3.101.162

51
 R/3 and Firewalls
Kerberos Hosts:
• kaserv1.acpub.duke.edu 152.3.233.58
• kaserv2.acpub.duke.edu 152.3.233.67
• kaserv3.acpub.duke.edu 152.3.233.70

52
 R/3 User Training
• All users should attend “Introduction to R/3
at Duke”
• Other role-specific courses are offered on
a regular basis
• For more information on schedules and
specific course offerings:
http://www.r3.duke.edu, “Learning R/3”
section

53
 R/3 User Accounts
• Departmental User Administrators
request user access, privileges
• User Administrators are often business
managers or R/3 expert users within the
department
• User Administrator List:
http://www.r3.duke.edu, “Department
Listing” link

54
 R/3 User Accounts
• Health System: based on Dempo ID
• University: based on existing NetID
• Two parts to authentication:
– Kerberos principal proves identity
– R/3 ID grants access, stores profile
(permissions)
• R/3 ID’s are locked or removed after a
period of disuse

Because of the two-part authentication, sometimes users can

authenticate through Authentic Login / Kerberos Client and still can’t
use the R/3 system.
User Administrators can help in such cases.

90 days till inactive ID is locked

Another 90 till it’s removed

55
Questions?

56