Notes1

48
SAP Overview

description

sap notes

Transcript of Notes1

Page 1: Notes1

SAP Overview

Page 2: Notes1

SAP?

• Company

• ERP Software package– R/2– R/3

Page 3: Notes1

Why ERP

• Integration

• Best business practices

• Standardization

Page 4: Notes1

Why not ERP?

• Complexity

• Cost

• Inflexibility

Page 5: Notes1

SAP R/3 System Business Modules

Sales &Distribution

MaterialsMgmt.

ProductionPlanning

FinancialAccounting

Controlling

Fixed AssetsMgmt.

QualityMgmt.

PlantMaintenance

HumanResources

Workflow

IndustrySolutions

R/3Client / Server

ABAP/4 ProjectSystem

Logistical Financial

Page 6: Notes1

R/3 System: Hardware/Software Views

Page 7: Notes1

Typical Client Server Architectures

Central System

Two - tierDistributed System

Two - tierClient/Server

Three - tierClient/Server

Multi-layerCooperative

Client/Server

Presentation Application Database

Page 8: Notes1

Database and Application

R/3 System ConfigurationsCentral System

SAP2-Tier Configuration 3-Tier Configuration Web-enabled

Presentation

Database,

Application,

PresentationDatabase

Application

Presentation

Internet Transaction Service/Web Service

In a central R/3 System configuration, one host is responsible for all processing tasks.

Page 9: Notes1

Database and Application

R/3 System ConfigurationsCentral Systems

SAP2-Tier Configuration 3-Tier Configuration Web-enabled

Presentation

Database,

Application,

PresentationDatabase

Application

Presentation

Internet Transaction Service/Web Service

Two‑tier R/3 System configurations are usually implemented using special presentation servers that are responsible solely for formatting the graphical interface. Many R/3 System users use PCs with Microsoft Windows ‑installed, for example, as presentation servers.

Page 10: Notes1

An alternative two‑tier configuration is to install powerful desktop systems and to use these for presentation and applications (two‑tier client/server). This type of configuration is particularly useful for expensive applications (such as simulations) or for software developers.

Database and Application

R/3 System ConfigurationsCentral Systems

SAP2-Tier Configuration 3-Tier Configuration Web-enabled

Presentation

Database,

Application,

PresentationDatabase

Application

Presentation

Internet Transaction Service/Web Service

Page 11: Notes1

In a three‑tier configuration, you use your own host for the three tiers. Using data from the database server, several different application servers can operate at the same time. To ensure that the load on individual servers is as even as possible and to achieve optimal performance, you can use special application servers for individual application areas such as sales planning, distribution or financial accounting.

Database and Application

R/3 System ConfigurationsCentral Systems

SAP2-Tier Configuration 3-Tier Configuration Web-enabled

Presentation

Database,

Application,

PresentationDatabase

Application

Presentation

Internet Transaction Service/Web Service

Page 12: Notes1

Database and Application

R/3 System ConfigurationsCentral Systems

SAP2-Tier Configuration 3-Tier Configuration Web-enabled

Presentation

Database,

Application,

PresentationDatabase

Application

Presentation

Internet Transaction Service/Web Service

To web‑enable the SAP Applications, a Web Server and an ITS (Internet Transaction Server) are needed. The web‑service and the services for the ITS can run on one server or on two dedicated servers. The presentation in this configuration is provided by an Internet Browser. The new SAP Web platform is NetWeaver.

Page 13: Notes1

Basis System: Three-Tier Computer Hierarchy

Input / Outputof data to users

Access to Dataase:(Read / Write data)

Central Database(Storage of all data)

Database

Application

Presentation

Processing of datausing application logic

Presentation of theprocessed data tothe user

Page 14: Notes1

Client/Server Overview

Client

Server

LAN/WAN

TCP / IP

Page 15: Notes1

Client/Server Overview (Logical Structure)

Presentation

Data Storage

ApplicationLogic

Client

Server

Page 16: Notes1

SAP AG

R

What does an R/3 Database Contain?

R/3System

database

Repository ObjectsRepository Objects

Customizing ObjectsCustomizing Objects

ClientClient ClientClient ClientClient

Global SettingsGlobal Settings

Page 17: Notes1

SAP AG

R

What is a Client?

“A client is an autonomous unit in the R/3 System withregard to commercial law, organization, and data.”

ClientClient

Page 18: Notes1

Common Client Roles

CUST

QTST

PROD

Development &Development &CustomizingCustomizing

Quality AssuranceQuality Assurance

ProductionProduction

Configuring of client settings andcreation of new functionality

Functionality testing andverification of configuration

Productive activities and businessdata

Page 19: Notes1

Additional Client Roles

SAND

PPRD

SandboxSandbox

TestTest

TrainingTraining

Pre-productionPre-production

Sampling of customizingtransactions and settings

Testing of configuration settingswith data

Configured environment for theload of legacy data prior to thestart of productive activities

TRNG End-user customer trainingenvironment

TEST

Page 20: Notes1

Sample SAP System Landscape

Development Testing Production

DatabaseServers

ApplicationServers

PresentationServers

Page 21: Notes1

Object Migration

Program A

Table A

Screen A

Program A

Table A

Screen A

Program A

Table A

Screen A

Development QA Testing Production

Corrections and Transport

Page 22: Notes1

Object Migration

Program AVersion 1

Program AVersion 1

Program AVersion 2

Program AVersion 2

Program AVersion 3

Program AVersion 3

Program AVersion 1

Program AVersion 1

Program AVersion 2

Program AVersion 2

Program AVersion 3

Program AVersion 3

Originals

Development QA TestingCorrections

andTransport

?

?

Page 23: Notes1

Geography-based Clients

R/3America

R/3Europe

R/3Japan

America Client 010America Client 010

Japan Client 030Japan Client 030

Europe Client 020Europe Client 020

Page 24: Notes1

Client Copies

Configuration

Development

Interface TestingQuality Assurance

User Training

Page 25: Notes1

ERP: Integration

Integrate people, data and business processes within and between organizations.

Collaboration, non-redundancy, consistency and internal process optimization.

Page 26: Notes1

Procurement ProcessOutlineAgreement

Demand

Purchase Requisition Vendor

Purchase OrderGoods Receipt

& Inventory Mgmt.

AccountsPayable Invoice

Verification

Scheduling Agreement

Page 27: Notes1

Production Process

Goods Issue Shop Floor

Goods ReceiptOrder Settlement

Schedule/Release

Page 28: Notes1

Sales Process — Trading Goods

Customer Order Picking

Goods IssueBillingAccounts Receivable

Packing

Page 29: Notes1

Sales Process Finished Goods

Customer Order

AvailabilityCheck

Goods Issue

BillingPartial PaymentFinal Payment

Page 30: Notes1

Sales Process Finished Goods

Customer Order

Availability Check - Insufficient -

IndependentDemand

MRP Run

ProductionScheduling

Purchasing

DependentDemand

Page 31: Notes1

Process Flow

Goods Issueto Shop Floor

GoodsReceipt

Production

Goods IssueBillingAccounts Receivable

Page 32: Notes1

Logging In

• Basics

Page 33: Notes1

Client

• This is a numeric field.

• This number defines a whole business entity.

Page 34: Notes1

User

• Every SAP user has a user name.

• Users of SAP system are client-specific, which means that having a user identification on one client will only allow access to that particular client.

Page 35: Notes1

Password Rules

• Letters

• Numbers

• Easy to remember

• 3-8 Characters long

• No 3 Characters can be the same

• Do not start with a ? or an !

• Do not use previous 5 passwords

Page 36: Notes1

Language

• SAP supports multi-national character sets and languages on the same system, at the same time.

• Default languages are English and German.

Page 37: Notes1

Field Types

• There are three types of Entry Fields

– Required– Default entry– Optional entry field

Page 38: Notes1

Sessions

• An SAP session is a window in which the user may perform a particular task.

• A User may have up to nine sessions open at one time.

Page 39: Notes1

SAP R/3 Resource Management: The Dispatcher

Data base

Application

Presentation

BuffersWorkProcess

WorkProcess

WorkProcess

Dispatcher

SAP GUI

Communications

Page 40: Notes1

SAP Memory BufferSAP Memory Buffer

Relational database systemRelational database system

SAP GUISAP GUI

SAP R/3 Resource Management: Data Flow

Data base

Application

Presentation

WorkProcess

Dispatcher

TerminalProcess

Request queuesRequest queues

11

33

22

4455

66

77

Roll

Page

Page 41: Notes1

SAP Dispatcher

SAP R/3 Resource Management: Work Processes

1 2 3 4

5 6 7 8 9 10 11

12 13 14 15 16 17 18

19 20 21 22 23 24 25

26 27 28 29 30 31

1999

Background Jobs

Spool

Enqueue

Dialog Update MessageSold to party: C100

Item Material Qty10 6301 1020 6412 1030 1507 25

O r d e r

Sold to party: C100

Item Material Qty10 6301 1020 6412 1030 1507 25

O r d e r

Sold to party: C100

Item Material Qty10 6301 1020 6412 1030 1507 25

O r d e r

Sold to party: C100

Item Material Qty10 6301 1020 6412 1030 1507 25

O r d e r

M

Gateway

R/2

R/3

G

AABB

CC

Page 42: Notes1

SAP R/3 Resource Management: Lock Management by the Enqueue Work Process

WorkProcess

Update

WorkProcess

Enqueue

Dispatcher

WorkProcess

Update

WorkProcess

Enqueue

Dispatcher

Lock table in

main storage

MessageServer

Instance A

Instance B

Page 43: Notes1

SAP R/3 Resource Management: R/3 Instance

Dialog . . . . Update SpoolBack-

groundEnqueue

Dispatcher

DatabaseInstance

DatabaseInstance Message

Server

MessageServer

SAPGateway

SAPGateway

Instance Profiles(parameters)

Instance Profiles(parameters)

SAP BuffersSAP Buffers

Startor

Stop

Startor

Stop

Central Instance

Page 44: Notes1

SAP R/3 Resource Management: Distributed SAP R/3 Processing

Dialog Update Enqueue Spool

Dispatcher

Mess-age

Gate-way

Instance 01

Enqueue Dialog . . .

Dispatcher

Instance 02

DialogBack-

ground Enqueue

Dispatcher

Instance 03

Page 45: Notes1

Reporting

• Three basic steps to running a report

– Access the report– Enter selection criteria– Execute the report

Page 46: Notes1

System MessagesSystem Messages

E - Error – An invalid entry has been made. – The cursor moves to the field where the error has occurred.

W - Warning– A possible error has been made. –The user can continue without changing.

I – Information– Feedback from the system.

Page 47: Notes1

Customizing - Modeling the Business

– Organizational Structures in each module

– Master Data - Customers, Materials, …

– Rules - required entries, tolerances, …

Page 48: Notes1

Mapping

– Assignment of organizational structures to reflect the enterprise model

– Establishes integration among modules