SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.

ppt
Supplementary Presentation

SAP ECC 6.0 Basis Overview

Copyright
Copyright
© 2007
© Accenture
2007 Accenture
All Rights
All rights
Reserved.
reserved.
Accenture,
Accenture,
its logo,
its logo,
and and
HighHigh
Performance
Performance
Delivered
Delivered
are trademarks
are trademarks
of Accenture.
of Accenture.

Note to Faculty: Delivery of this presentation is optional. If participants in the

training session need more information about Basis, then plan to deliver all or as
much of this presentation as possible. If there is not time to deliver the presentation
in its entirety, be sure to refer participants to the presentation in their Bootcamp’s
Participant Workbook_Supplementary Presentations.pdf file.

Copyright © 2007 Accenture All Rights Reserved. 1

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

SAP Basis Overview - Agenda

• Context
• SAP NetWeaver Components
• Typical System Landscapes
• How Work is Performed within SAP
• Performance of the SAP System
• Change Control and Transports
• Security and Authorisations
• SAP Updates and Patches

Key Message(s):
Welcome to the SAP Basis Overview topic. This course provides overview on SAP
NetWeaver components, system landscapes, and other important SAP R/3 Basis
functions. This topic has been developed for multiple SAP program initiatives,
including SAP Financials, Human Resources and Opportunity Management.

This topic will cover various information; to begin with, the SAP NetWeaver will
concentrate on different NetWeaver components and its brief introduction, after
which we’ll cover system landscapes as well as introduce Basis roles in SAP R/3.

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 2

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

Context for Presentation

• When starting on an SAP project, what are the key
areas within the “Technical Realm” that I should know
about?
• What components are we implementing?
• What systems and clients are available?
• What will general processing and performance be
like?
• How are changes being tracked and controlled?

Key Message(s):
The context of this topic is to describe key areas within the “Technical Realm” and
identify SAP NetWeaver components we are implementing. You will also get a brief
overview on processing/performance as well as change management controls and
tracking details.

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 3

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

Context for Presentation (cont.)

• What security will be setup?
• What levels of SAP patches and fixes will be applied?
• Each of these questions – and the answers – will
impact the way you work within the system and
shape the overall solution

Key Message(s):
Then, we’ll cover SAP security, SAP patches and fixes levels. Each of these
questions and the answers will impact the way you work within the system and
shape the overall solution.

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 4

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

SAP BASIS Overview - Agenda

• Context
• SAP NetWeaver Components
• Typical System Landscapes
• How Work is Performed within SAP
• Performance of the SAP System
• Change Control and Transports
• Security and Authorisations
• SAP Updates and Patches

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 5

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

SAP NetWeaver Components

(1 of 8)
• What does the SAP NetWeaver Platform consist of?
SAP NetWeaver™
PEOPLE INTEGRATION
Multi channel access (MI)

Composite Application Framework (CAF)

…
Portal (EP) Collaboration

INFORMATION INTEGRATION
Bus. Intel. (BW)

Life Cycle Mgmt

Knowledge Mgmt

Master Data Mgmt (MDM) WebSphere

PROCESS INTEGRATION (XI)

Integration Business
Broker Process Mgmt

APPLICATION PLATFORM (Web AS) Microsoft

.net
J2EE ABAP

DB and OS Abstraction
6

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 6

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

SAP NetWeaver Components

(2 of 8)
SAP NetWeaver™
• Web AS (Application
PEOPLE INTEGRATION Server):
Multi channel access (MI) – A single, common
Composite Application Framework (CAF)

…
Portal (EP) Collaboration architecture
INFORMATION INTEGRATION – Both ABAP- and Java-
Bus. Intel. (BW)

Life Cycle Mgmt

Knowledge Mgmt
based capabilities are
Master Data Mgmt (MDM) WebSphere
supported and can
PROCESS INTEGRATION (XI) exist simultaneously
Integration Business
Broker Process Mgmt – Provides the base for
APPLICATION PLATFORM (Web AS) Microsoft all SAP modules (for
J2EE ABAP
.net
example, ECC, SRM,
DB and OS Abstraction CRM, etc.)

Key Message(s):
Web AS (Application Server) is a single common architecture that consists of
ABAP- and Java-based capabilities. This combination provides a base for all SAP
modules like ECC, SRM, CRM, XI, etc.

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 7

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

SAP NetWeaver Components

(3 of 8)
• SAP XI:
SAP NetWeaver™
– SAP XI is SAP’s EAI tool
PEOPLE INTEGRATION
Multi channel access (MI) – Provides capabilities to
Composite Application Framework (CAF)

… integrate disparate systems,

Portal (EP) Collaboration
including data transformation,
INFORMATION INTEGRATION mapping and translation tools
Bus. Intel. (BW) – Consists of pre-configured

Life Cycle Mgmt

Knowledge Mgmt

Master Data Mgmt (MDM) WebSphere adaptors to assist integrating

with different applications,
PROCESS INTEGRATION (XI)
databases and using different
Integration Business
Broker Process Mgmt messaging protocols and
Microsoft
services
APPLICATION PLATFORM (Web AS)
.net – Also provides Business
J2EE ABAP
Process Management
DB and OS Abstraction
functionality

Key Message(s):
Next in SAP NetWeaver hierarchy is XI (Process Integration) module. SAP XI is
SAP’s EAI tool. It provides a technical infrastructure for XML-based message
exchange in order to connect SAP components with each other, as well as with non-
SAP components.

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 8

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

SAP NetWeaver Components

(4 of 8)
SAP NetWeaver™
• SAP MDM:
PEOPLE INTEGRATION – SAP MDM provides the
Multi channel access (MI) capability to store and
Composite Application Framework (CAF)

…
Portal (EP) Collaboration manage master data in a
INFORMATION INTEGRATION central location and to
Bus. Intel. (BW) distribute to systems that

Life Cycle Mgmt

Knowledge Mgmt

Master Data Mgmt (MDM) WebSphere use this data (both SAP

PROCESS INTEGRATION (XI) and non-SAP)

Integration
Broker
Business
Process Mgmt
– Provides consistency of
master data within an
APPLICATION PLATFORM (Web AS) Microsoft
J2EE ABAP
.net enterprise
DB and OS Abstraction

Key Message(s):
SAP MDM (Master Data Management) enables companies to consolidate and
harmonize their master data within heterogeneous IT landscapes.

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 9

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

SAP NetWeaver Components

(5 of 8)
SAP NetWeaver™
• SAP BW:
PEOPLE INTEGRATION – SAP BW is SAP’s
Multi channel access (MI) Business Warehouse
Composite Application Framework (CAF)

…
Portal (EP) Collaboration solution
INFORMATION INTEGRATION – Includes business
Bus. Intel. (BW)
analytics, web-based

Life Cycle Mgmt

Knowledge Mgmt

Master Data Mgmt (MDM) WebSphere reporting and report

PROCESS INTEGRATION (XI) subscription
Integration Business
Broker Process Mgmt

APPLICATION PLATFORM (Web AS) Microsoft

.net
J2EE ABAP

DB and OS Abstraction

10

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 10

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

SAP NetWeaver Components

(6 of 8)
SAP NetWeaver™
• SAP EP:
PEOPLE INTEGRATION – SAP EP is the Enterprise
Multi channel access (MI) Portal solution
Composite Application Framework (CAF)

…
Portal (EP) Collaboration
– Based solely on Java stack
INFORMATION INTEGRATION
– Includes pre-configured
Bus. Intel. (BW)

Life Cycle Mgmt

Knowledge Mgmt
and coded iViews for
Master Data Mgmt (MDM) WebSphere
displaying content, and
PROCESS INTEGRATION (XI) pre-configured business
Integration Business
Broker Process Mgmt packages to allow
APPLICATION PLATFORM (Web AS) Microsoft
specialised web-based
J2EE ABAP
.net representation of SAP
DB and OS Abstraction transactions (from all
modules)
11

Key Message(s):
SAP EP is the Enterprise Portal solution, based solely on Java stack. It includes
pre-configured and coded iViews for displaying content and pre-configured business
packages to allow specialised web-based representation of SAP transactions.

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 11

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

SAP NetWeaver Components

(7 of 8)
SAP NetWeaver™
• SAP MI:
PEOPLE INTEGRATION – SAP MI (Mobile
Multi channel access (MI) Infrastructure) is SAP’s
Composite Application Framework (CAF)

…
Portal (EP) Collaboration mobile development
INFORMATION INTEGRATION platform
Bus. Intel. (BW)
– Provides functionality for

Life Cycle Mgmt

Knowledge Mgmt

Master Data Mgmt (MDM) WebSphere mobile computing and

PROCESS INTEGRATION (XI) related access to SAP

Integration
Broker
Business
Process Mgmt
functionality
APPLICATION PLATFORM (Web AS) Microsoft
.net
J2EE ABAP

DB and OS Abstraction

12

Key Message(s):
SAP MI (Mobile Infrastructure) is SAP’s mobile development platform.

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 12

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

SAP NetWeaver Components

(8 of 8)
• SAP CAF:
SAP NetWeaver™
PEOPLE INTEGRATION
– SAP CAF (Composite
Multi channel access (MI) Application Framework) is
Composite Application Framework (CAF)

… SAP’s custom development

Portal (EP) Collaboration
platform
INFORMATION INTEGRATION
Bus. Intel. (BW)
– Enables custom applications

Life Cycle Mgmt

Knowledge Mgmt
to be built on Web AS (ABAP
Master Data Mgmt (MDM) WebSphere
and/or Java) that can be
PROCESS INTEGRATION (XI) totally independent of other
Integration
Broker
Business
Process Mgmt
“core” SAP functionality
– Custom developments may
APPLICATION PLATFORM (Web AS) Microsoft
J2EE ABAP
.net also reference and combine
DB and OS Abstraction
data from multiple SAP
components into a single
application 13

Key Message(s):
SAP NetWeaver CAF provides a toolset and runtime for developing, running and
efficiently managing composite applications using SAP's enterprise SOA.

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 13

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

SAP BASIS Overview - Agenda

• Context
• SAP NetWeaver Components
• Typical System Landscapes
• How Work is Performed within SAP
• Performance of the SAP System
• Change Control and Transports
• Security and Authorisations
• SAP Updates and Patches

14

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 14

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

SAP System Landscape

• The “system landscape” usually refers to:
– The SAP instances/systems that make up the solution
– The architecture of the SAP solution
– The SAP clients used within each system

15

Key Message(s):
The “system landscape” refers to the SAP instances/system, the architecture of
SAP solution and the SAP clients. A client in SAP is a self-contained unit of an SAP
R/3 system residing within an instance that contains its own separate master
records and set of tables. Clients are defined by a 3-digit number.

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 15

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

SAP System Landscape –

Systems
• An example system landscape is shown below.
• The typical uses for each of these systems are outlined in the table below:

Sandpit Test / prototype development or configuration. Standalone system

that is often refreshed or overwritten. (May or may not be part of the
landscape, depending on the size/scope of the implementation.)
Development Where configuration and development is performed and unit tested.
QA/Test Where integration testing occurs, along with other testing cycles.
Pre-Production Where regression testing occurs and often production support. May
also serve as a failover for production or for performance testing.
(Very important for large implementations or implementations involving
multiple staged or parallel releases. Otherwise, may not be included.)
Production The “live” system, accessed by users.

• It is important to understand the overall system landscape strategy in order to be aware of

what functions are performed within each system and also what setup/configuration is
required in each.
16

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 16

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

SAP System Landscape -

Architecture
• The underlying architecture for a SAP
system is typically implemented as a “2-tier”
or “3-tier” architecture that contains the
following layers:
– Presentation Layer
– Application Layer
– Database Layer
– Presentation Layer
– Central Layer
– Presentation Layer
– Central Layer
• The decision between 2 and 3-Tier
architecture is often driven by the technology
platform chosen (ie. IBM vs. Microsoft), the
size of the system being implemented and
the business usage requirements.
17

Key Message(s):
• The Presentation Layer represents how users will access the system. This can
have an impact on the configuration & setup needed within the application.
• The Application Layer relates to servers whose primary function is to process
the functionality of the application.
• The Database Layer relates to a server dedicated to performing database
functions (i.e.. database queries, updates etc).
• The Presentation Layer represents how users will access the system. This can
have an impact on the configuration & setup needed within the application.
• The Central Layer relates to a server that performs both application and
database processing.
• The Presentation Layer represents how users will access the system. This can
have an impact on the configuration & setup needed within the application.
• The Central Layer relates to a server that performs both application and
database processing.
• The decision between 2- and 3-tier architecture is often driven by the technology
platform chosen (i.e., IBM vs. Microsoft), the size of the system being
implemented, and the business usage requirements.

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 17

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

SAP System Landscape – Clients

(1 of 3)
• There are typically multiple clients set up within each
SAP system. The exception to this are APO, BW, XI
and Enterprise Portal, which are all single client
systems.
• A client contains its own set of data and configuration
/customisation. Different clients within the same
system cannot “see” or change data or configuration
in another client.

18

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 18

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

SAP System Landscape – Clients

(2 of 3)
• All clients in a system share repository information –
i.e., programs, tables and data structures, and some
client-independent configuration.
• Configurers must therefore be aware of any client-
independent settings, as these will affect all clients
within the system. Likewise, developers must be
aware of the impacts of all code/table changes.

19

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 19

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

SAP System Landscape – Clients

(3 of 3)
• Typical clients that are often set up are outlined below:
Clients Typically Set Up Typically Set
Up Within…
Configuration/Development Master – A client where “correct” Development
configuration and development is entered. No master data or transaction
data is normally entered in this client, to provide a “clean” configuration-
only environment. Configuration is transported to other clients.
Unit Test – Where unit testing of configuration and development occurs. Development
Playpen – An environment to test/trial configuration. Development
Integration Testing – An environment to perform integration testing. QA/Test
Conversion Testing – An environment for the Data Conversion Team to Development or
test uploads/conversion routines. QA/Test
Cutover Testing – An environment to test the “cutover” to the production QA/Test or Pre-
system. Production
Production – The “Live” environment, accessed by users. Production
20

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 20

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

SAP BASIS Overview - Agenda

• Context
• SAP NetWeaver Components
• Typical System Landscapes
• How Work is Performed within SAP
• Performance of the SAP System
• Change Control and Transports
• Security and Authorisations
• SAP Updates and Patches

21

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 21

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

How Work is Processed Within

SAP (1 of 3)
• Whenever a “request” is made to the SAP system,
the actual processing work will be performed by one
or more of the configured work processes. Each SAP
system provides a configurable number of work
processes to handle the processing load.

22

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 22

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

How Work is Processed Within

SAP (2 of 3)
• There are different types of work processes for specifically
performing different “types” of work. The key processes are:
– Dialog processes: Process interactive user commands and
requests.
– Update processes: Handle actual updates to the database.
– Batch processes: Process requests/functionality that occurs in
background (i.e., non-interactive).
– Spool processes: Process printing/output requests.
• Different systems are set up with different configurations of
work processes depending on functionality and processing
requirements.

23

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 23

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

How Work is Processed Within

SAP (3 of 3)
• While the majority of processing is
generally performed by dialog
work processes (as they handle
user requests), it is important to
understand how functionality
performs. For example, some
functions are able to use multiple
dialog work processes in parallel
to speeding up process. Others
are able (or recommended) to run
in background using batch
processes.
• Understanding these processes
will also help in understanding the
impact/best use of system
resources.
24

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 24

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

SAP BASIS Overview - Agenda

• Context
• SAP NetWeaver Components
• Typical System Landscapes
• How Work is Performed within SAP
• Performance of the SAP System
• Change Control and Transports
• Security and Authorisations
• SAP Updates and Patches

25

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 25

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

Performance of the SAP System

• The performance of a SAP system is often a talking point. Acceptable performance
is crucial in the “live” environment, but it is equally important in other systems to
enable the project or support to perform their work effectively
• Performance is most often referred to in terms of “response time,” i.e., how long it
takes to receive a response from the SAP system after initiating a request

Performance Description
Factor
Hardware An obvious impact to performance is the hardware. More CPUs / faster CPUs and
more memory can facilitate faster processing. There are, however, other related areas
that can impact performance, including network bandwidth and disk I/O (i.e., time
taken to read/write data to and from the disk storage).
SAP System Each SAP system contains a large number of “profile parameters.” These
Technical Setup configurable parameters determine many settings that can influence performance,
including buffer memory sizes and number of each type of work process. In particular,
the number of each type of work process can be very important. If there are not
enough dialog work processes available, then users will need to wait until a work
process is free before processing can begin, which can result in long response times.

26

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 26

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

Performance of the SAP System

(cont.)
Performance Factor Description
Custom Development Custom developments are often the worst performing functions within the
SAP system. Care must be taken on how the database is accessed and
how general programming concepts (e.g., looping, SELECT statements
and conditional statements) are implemented.
Database Requests Requests to the database are often large contributors to the overall
response time. It is often a function on how the request is made – for
example, sequential database reads take more time that direct database
reads. The overall size of the database also impacts performance.
Related to hardware, the database needs to have sufficient capacity to
handle all of the requests being made.
Application Configuration The way the SAP system is configured can also impact performance.
Complex configuration settings can result in complex processing
requirements that have long response times.

27

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 27

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

SAP BASIS Overview - Agenda

• Context
• SAP NetWeaver Components
• Typical System Landscapes
• How Work is Performed within SAP
• Performance of the SAP System
• Change Control and Transports
• Security and Authorisations
• SAP Updates and Patches

28

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 28

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

Change Control and Transports

(1 of 3)
• Change control within SAP refers to how changes to
the application, i.e., predominantly configuration and
development changes, are propagated through the
various SAP systems…DEV → QA → Production,
etc.
• SAP’s primary tool to enable and control this
propagation is the TMS (Transport Management
System).

29

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 29

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

Change Control and Transports

(2 of 3)
• Key change control and transport points are listed below:
– Changes to all repository objects are retained within SAP as previous
versions. Full version control is enabled.
– When a change is made to configuration or a repository object, SAP will
always prompt you to enter a “transport” (change request) to associate
the change with. A transport is the mechanism by which SAP controls
all changes. It is essentially a container for all objects/data values that
are changed.
– Transports must be “released”, i.e., marked as complete, before they
can be moved to the next system.
– A transport is then “imported” into the next system, effectively
implementing the change in that system.
– Configurers/developers are often responsible for creating and releasing
transports, but the Basis team is usually responsible for actually
importing them into subsequent systems. 30

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 30

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

Change Control and Transports

(3 of 3)
• This window displays when creating a new transport:

• It is important to understand the change and transport strategy of the

project to ensure that configuration and development is performed and
controlled appropriately.
31

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 31

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

SAP BASIS Overview - Agenda

• Context
• SAP NetWeaver Components
• Typical System Landscapes
• How Work is Performed within SAP
• Performance of the SAP System
• Change Control and Transports
• Security and Authorisations
• SAP Updates and Patches

32

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 32

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

Security and Authorisations

• Security within SAP uses the concept of authorisation
roles and profiles. Each user is assigned a number of
roles, which contain profiles that grant access to
specific SAP transactions and data.
• The security concept is such that access to a function
must be specifically granted, i.e., you must be
assigned access to a specific function in order to run
that function.

33

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 33

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

Security and Authorisations

(cont.)
• Authorisations within profiles can be controlled at three levels:
– Transaction level: Every function has a transaction code
assigned to it. Access must be granted to that transaction code
for the user to be able to run the function (i.e., access the initial
screen).
– Access Type level: Once a user has initiated a transaction,
further controls can be specified to determine the access type
allowed, i.e., Create, Change, Display, Delete, etc.
– Data level: With the transaction and access types, restrictions
can also be made at a data level. For example, access only to
specific company codes, purchasing organisations or cost
centres

34

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 34

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

SAP BASIS Overview - Agenda

• Context
• SAP NetWeaver Components
• Typical System Landscapes
• How Work is Performed within SAP
• Performance of the SAP System
• Change Control and Transports
• Security and Authorisations
• SAP Updates and Patches

35

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 35

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

SAP Updates and Patches

• SAP provides support and fixes/patches for bugs in one of two
ways:
– OSS Notes (advance corrections)
– Support Pack Stacks

36

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 36

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

OSS Notes (Advance Corrections)

• OSS Notes are released as fixes for specific errors and are often individual
corrections to SAP code. They are also usually contained within a given
Support Pack Stack (see next slide).
• Individual OSS Notes can be applied directly to the SAP system through
the transaction SNOTE.
• OSS Notes can be searched for within the SAP Service Marketplace
(service.sap.com). An OSS ID is required to logon and search for OSS
Notes.

37

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 37

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

Support Pack Stacks

• Support Pack Stacks are released per SAP application (for example, SRM or CRM).
• They contain an often very large collection of individual bug fixes (OSS Notes) as
well as a number of technical/system-related updates.
• They can have a large impact on system functionality and are usually applied in a
very controlled and planned manner.
• They are released by SAP to a specified schedule – a sample is shown below:

38

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 38

SAP ECC 6.0 Basis Overview SAP ECC 6.0_Basis Overview.ppt
Supplementary Presentation

Questions

39

Key Message(s):

Additional Information:

Copyright © 2007 Accenture All Rights Reserved. 39