SAP System Architecture and Organization Structure Flashcards
ERP System Architecture Policies
Usable world-wide
* Open policy with respect to data access and
functionality – i.e. open source system
* Support distributed applications and interfaces
to other systems
ERP System Architecture Policies
* Enterprise System (ES) Architecture:
– technical structure of the software
– Way that users interact with the software
– Ways the software is physically managed on
computer hardware
ERP System Architecture Policies
Most modern ES have:
– 3-tier Client-Server Architecture
– Service-oriented architecture
SAP Architecture
Client/Server Environment
– Client – hardware/software environment that can make a request
for services for a central repository of resources
– Server – hardware/software combination that can provide services
to a group of clients in a controlled environment
Client-Server Architecture
Think of a desktop application – e.g. Excel
* These applications consist of three components, or layers:
– Interaction (menus, selecting)
– What it allows (e.g. formula/chart creation)
– Data storage (e.g. hard drive, other drive)
* These layers are actually called:
– Presentation layer (or GUI)
– Application layer
– Data or Database layer
SAP Architecture
Three – Tier Structure
– GUI
* Graphical User Interface or
Web Interface
– Application Server
* One or more, help distribute
work load
– Database Server
* One single data repository
Database Layer
- The database layer consists of a central database system containing all of the data in the System
- SAP does not manufacture its own database for
ECC and previous versions; however, it does for S/4 HANA - Supported database
– ADABAS D
– DB2
– INFORMIX, Microsoft SQL Server, ORACLE
– SAP Hana only runs on an SAP-supported d’base
Four Categories of Data in SAP
- Code
– Programming codes to support all the functions or
performance - Configuration data
– SAP consultants - Master data
– Data that does not change often
– E.g., Rutgers - Student (Name, ID, Home address) - Transaction data
– Happened daily/actively
– E.g., purchase order
SAP Database
- Contains the master data and transaction data
from your business applications, and all data for
the entire System - Contains the control and customizing data that
determines how your System runs - Contains the program code for applications
– Applications consist of program code, screen
definitions, menus, function modules, and various
other components
Application Layer
- The application layer consists of application
servers and message servers - Each application server contains a set of
services used to run the System - Not all application servers will provide the full
range of services
– One server can serve multiple functions
– Multiple servers can serve one function
Presentation Layer
- The presentation layer contains the software
components that make up the SAP GUI
(Graphical User Interface) - This layer is the interface between the system
and its users - The presentation layer sends the user’s input to
the application server, and receives data for
display from it
Advantages of Multi-Tier Architecture
- Load Distribution
– Software is distributed over three layers. This leads to better
system performance.
– It separates program execution from the tasks of processing user
input and formatting data output.
– It allows application layer and database layer, which are subject
to a very heavy load when the system is running, to be separate. - Scalability
– Software components of the system can be distributed in almost
any configuration across various hosts.
– It is particularly valuable in the application layer.
Bullwhip Effect
- A slight motion of the handle of a bullwhip can make
the top thrash wildly at up to 900mph. - Increasing demand variability as you move upstream.
- Most demand distortion is caused by the supply chain
itself, not by the customer. - Results in:
– excessive inventory investment
– poor customer service
– lost revenues
– misguided capacity planning
– ineffective transportation
– Ineffective production schedules.
Structure Drives Behavior:
Causes of the Bullwhip Effect
- Lack of visibility
- Long lead time
- Many stages in the supply chain
- Lack of pull signals
- Order batching
- Price discount and promotions
- Forward buying
Other Behaviors that Cause the
Bullwhip Effect
- Over-reaction to backlogs
- Neglecting to order to reduce inventory
- Hoarding customers/consumers
- Shortage gaming for customers
- Demand forecast inaccuracies
- Attempts to meet end-of-month metrics
Ways to Mitigate the Bullwhip Effect
- Reduce lead times
- Use/sharing of POS data
- Smaller orders
– Work with suppliers on more frequent deliveries of smaller
order increments - Use stable pricing, “everyday low prices”
– Levels out customer demand - Allocation based on past sales
