Introduction to
Enterprise Systems,
Enterprise Computer
Models and SAP / R3
Lecture Overview





Summary of today’s enterprise computing
ecosystem
Demystify the “Cloud”
Summary of enterprise systems and
topologies
Summary of the SAP enterprise system
SAP introductory demonstration
The Enterprise Ecosystem

We have traditional on premises computer
systems


SAP / ORACLE / Dynamics
We utilize “the cloud”


Clouds are categorized as public or private
We run various types of services on these
clouds

SaaS, PaaS, SOA, Web services
A Taxonomy of the Cloud

Public clouds



Pay as you go model for computing resources
No control of vendor-supplied hardware or
performance
Limited to no long term contracts


https://aws.amazon.com/products/?nc2=h_ql_ny
_livestream_blu
Private clouds

Always single tenant dedicated to a company
Cloud Stack
Infrastructure as Service (IaaS) - 1


Physical or virtual computing infrastructure (servers,
storage, networking) are outsourced to external
companies
We manage the operating system and applications
running on these servers
 Risks
 HIPPA, ITAR, gaming compliance
 Benefits
 Cost reductions, hardware expansion /
contraction flexibility
Infrastructure as Service (IaaS) - 2

Amazon EC2 provides hosted servers




We can purchase SAP HANA instances on the EC2
We can purchase Windows instances on the EC2
Microsoft Azure provides hosted Windows and
SQL Server instances in the cloud
Rackspace provides similar services
Platform as a Service (PaaS) -1

Platform as a Service (PaaS) is a paradigm for
delivering operating systems and associated
services over the Internet without downloads
or installation

We extend Salesforce.com through their
application programming interfaces (APIs)


https://help.salesforce.com/HTViewHelpDoc?id=i
ntegrate_what_is_api.htm
We talk to Facebook through its APIs

https://developers.facebook.com/
Software as a Service (SaaS) - 1


SaaS provides access to specific application
software through the cloud
Salesforce.com is built on this model



We access the software entirely through the
Web
UNR is adopting workday for their financial
systems
Apprenda.com
Software as a Service (SaaS) -2

Google Apps is akin to a web-based version
of Office


http://www.google.com/enterprise/apps/busines
s/
Office 365 is office in the cloud

http://office.microsoft.com/en-us/
Characteristics of
Enterprise Systems


They are some of the most complex systems
in use today
They are typically

N-tier systems made up of



clients
an application / business logic layer
a data layer
The SAP Enterprise System


You access the SAP R3 program on a PC via a
software program known as NetWeaver
The database and application lives on
virtualized servers at Chico State University
The SAP Ecosystem
SAP Clients


You run a program called NetWeaver on your
PC or Windows computer
NetWeaver allows you to connect to an
application server


There are several at Chico State
You communicate with these application servers
via the SAP Easy Access Menu
SAP NetWeaver Login

You use NetWeaver
to connect to the
application servers
at Chico State
SAP NetWeaver (Easy Access)

Drill-down Easy Access menu to run
transactions)
The SAP Application Server (1)
The SAP Application Server (2)



The dispatcher accepts transactional
requests and hands them off to work
processes for actual execution
These work processes, in turn, record
changes to the central DBMS
Roughly speaking this process is called a unit
of work

A logical unit of work has a transaction code
Logical Unit of Work
(Introduction)

The unit of work concept ensures
transactional integrity


A sequence of database operations are
completed in their entirety or not at all
An accounting transaction cannot end up
“partially recorded”, which would lead to an out
of balance G/L
Logical Unit of Work
(Illustration)
LOW (Example)


This example demonstrates the transaction to
purchase supplies for cash
The transaction code is FB50
LOW (Example)

Screen 1 (Enter Document)
LOW (Example)

Screen 2 (Simulate Transaction)
LOW (Example)

Screen 3 (Post)
The Data Layer




The database contains about 25000 tables
These tables store ALL application data
As mentioned HANA, ORACLE, SQL Server
can be used as the database
We can use the Data Browser to look at these
tables
The Database (Example)

The transaction that you just recorded caused


An accounting header record to be recorded to
the database table named BKPF
Transactional records were written to the table
BSEG
The Database (Example)


The accounting
header record
Table BKPF
The Database (Example)

The transactional entry has two records (DR
and CR
The Database (Example)

Debit and credit transactional records
Organizational Data

Organizations are usually structured
hierarchically

Company ( table T001)




Accounting
Finance
Credit granting
Divisions


Plants and warehouses
Sales and marketing office
Organizational Data (SAP)

An organization (enterprise) runs on a client



The SAP term really has a unique meaning in
this context
Think of the client as the server or server
clusters (instance) (enterprise)
A client can have multiple companies

Roughly speaking, a company produces
independent financial statements
Organizational Data
(Company)

Table T001 contains the master company
records

Global Bike has two companies
Organizational Data (SAP)

A company can have many facilities


Plants create goods and services
Distribution centers store goods
(warehouses)


In SAP, a distribution center is a type of plant
A company can have many purchasing
organizations and sales organizations


A purchasing organization buys goods
A sales organization sells them
Organizational Data (Plant)


The table T001W contains the list of plants
The table T001K associates plants with
companies
The Global Bike
Organizational Structure
Global Bike Group
Global Bike Inc. US00
Dallas
Miami
San Diego
Enterprise
Global Bike Germany GmbH DE00
Heidelberg
Hamburg
Companies
Locations
(plants)
Types of SAP Data

SAP data is categorized into two types

Master data describes entities used across
business transactions (long-term data)



Customers buy goods again and again for
example
We buy goods from vendors
Transactional data reflects the consequences
(outcomes) of executing process steps
(transactions) related to master data
Types of Master Data

Materials (MARA)



Customers (KNA1, KNB2, KNVV)


Used in manufacturing
Purchased from vendors and sold to customers
(trading goods)
Buy goods from us
Vendors

Sell goods to us
Transactional Data

Transactional data records the outcome of a
process

Goods movement



Shipment documents
Transfer of goods between warehouses
Financial documents


Sales (Invoice and payment receipt – accounts
receivable)
Purchase (PO to payment – accounts payable)