Documente Academic
Documente Profesional
Documente Cultură
INFORMATION SYSTEMS
ENTERPRISE RESOURCE PLANNING
Assignment
Enrolment number: MBISMCT13727119
Self Declaration
I declare that the assignment submitted by me is not a verbatim/photo static
copy from the website/books/journals/manuscripts.
MBA
INFORMATION SYSTEMS
ENTERPRISE RESOURCE
PLANNING
Enrolment number:
MBISMCT13727119
ERP Architecture:
ERP applications are most commonly deployed in a distributed and often
widely dispersed manner. While the servers may be centralized, the clients
are usually spread to multiple locations throughout the enterprise.
Generally there are three functional areas of responsibility that is distributed
among the servers and the clients. First, there is the database component the central repository for all of the data that is transferred to and from the
clients. Then, of course, the clients - here raw data gets inputted, requests
for information are submitted, and the data satisfying these requests is
presented. Lastly, we have the application component that acts as the
intermediary between the client and the database. Where these components
physically reside and how the processes get distributed will vary somewhat
from one implementation to the next. The two most commonly implemented
architectures are outlined below.
Two-tier Implementations
In typical two-tier architecture, the server handles both application and
database duties. The clients are responsible for presenting the data and
passing user input back to the server. While there may be multiple servers
and the clients may be distributed across several types of local and wide
area links, this distribution of processing responsibilities remains the same.
Three-tier Client/Server Implementations
In three-tier architectures, the database and application functions are
separated. This is very typical of large production ERP deployments. In this
scenario, satisfying client requests requires two or more network
connections. Initially, the client establishes communications with the
application server. The application server then creates a second connection
to the database server.
The SAP R/3 System architecture consists of three layers: Presentation,
Application, and Data Storage.
The following diagram illustrates the function served by each layer and how
the layers work together:
May 2015
Page 2 of 16
MBA
INFORMATION SYSTEMS
ENTERPRISE RESOURCE
PLANNING
Enrolment number:
MBISMCT13727119
Presentation
This is where users of the SAP R/3 System will submit input to the SAP R/3
System for the processing of business transactions. It is also where the
output from these transactions appears as output fields, reports, tables and
spread sheets.
On the desktop level, R/3 offers a user-friendly graphical interface called
SAPGUI. The system also integrates alternative interfaces for optimum
compliance with your requirements. This includes integrating common PC
applications. Information exchange is also carried out through the Internet,
Kiosk touch screen systems and telephone applications.
Application
May 2015
Page 3 of 16
MBA
INFORMATION SYSTEMS
ENTERPRISE RESOURCE
PLANNING
Enrolment number:
MBISMCT13727119
May 2015
Page 4 of 16
MBA
INFORMATION SYSTEMS
ENTERPRISE RESOURCE
PLANNING
Enrolment number:
MBISMCT13727119
The R/3 presentation software displays the graphical user interface using the
tools provided by the relevant presentation environment (frontend operating
system).
Database interface
Today, large amounts of data are usually administered using relational
database management systems (RDBMS). These systems store the data and
the relationships between the data in two-dimensional tables, which are
known for their logical simplicity. The definitions of the data, tables, and
table relationships are stored in the data dictionary of the RDBMS.
Within ABAP, SAP OPEN SQL is used to access application data in the
database, independent of the corresponding RDBMS. The R/3 database
interface converts the open SQL statements from the ABAP statements into
the corresponding database statements. This means that application
programs written in ABAP are database-independent. Native SQL commands
can be used in ABAP.
When interpreting open SQL statements, the R/3 database interface checks
the syntax of these statements and automatically ensures the local SAP
buffers in the shared memory of the application server are utilized optimally.
Data frequently required by the applications is stored in these buffers so that
the system does not have to access the database server to read this data. In
particular, all technical data such as ABAP programs, screens, and ABAP
Dictionary information, as well as some business process parameters usually
remain unchanged in a running system, making them ideal buffering
May 2015
Page 5 of 16
MBA
INFORMATION SYSTEMS
ENTERPRISE RESOURCE
PLANNING
Enrolment number:
MBISMCT13727119
To make the R/3 System independent of the database system with which you
use it despite the differences in the SQL syntax between various databases,
each work process on an application server has a database interface. The R/3
System communicates with the database by means of this interface. The
database interface converts all of the database requests from the R/3
System into the correct Standard SQL statements for the database system.
To do this, it uses a database-specific component that shields the differences
between database systems from the rest of the database interface. You
choose the appropriate layer when you install the R/3 System.
There are two ways of accessing the database from a program - with Open
SQL or Native SQL.
Open SQL
Open SQL statements are a subset of Standard SQL that is fully integrated in
ABAP. They allow you to access data irrespective of the database system that
the R/3 installation is using. Open SQL consists of the Data Manipulation
Language (DML) part of Standard SQL; in other words, it allows you to read
(SELECT) and change (INSERT, UPDATE, DELETE) data.
May 2015
Page 6 of 16
MBA
INFORMATION SYSTEMS
ENTERPRISE RESOURCE
PLANNING
Enrolment number:
MBISMCT13727119
Open SQL also goes beyond Standard SQL to provide statements that, in
conjunction with other ABAP constructions, can simplify or speed up
database access. It also allows you to buffer certain tables on the application
server, saving excessive database access. In this case, the database
interface is responsible for comparing the buffer with the database. Buffers
are partly stored in the working memory of the current work process, and
partly in the shared memory for all work processes on an application server.
Where an R/3 System is distributed across more than one application server,
the data in the various buffers is synchronized at set intervals by the buffer
management. When buffering the database, you must remember that data in
the buffer is not always up to date. For this reason, you should only use the
buffer for data which does not often change. You specify whether a table can
be buffered in its definition in the ABAP Dictionary.
Native SQL
Native SQL is only loosely integrated into ABAP, and allows access to all of
the functions contained in the programming interface of the respective
database system. Unlike Open SQL statements, Native SQL statements are
not checked and converted, but instead are sent directly to the database
system. When you use Native SQL, the function of the database-dependent
layer is minimal. Programs that use Native SQL are specific to the database
system for which they were written. When writing R/3 applications, you
should avoid using Native SQL wherever possible. It is used, however, in
some parts of the R/3 Basis System - for example, for creating or changing
table definitions in the ABAP Dictionary.
Operating system interface
The operating system views the R/3 runtime system as a group of parallel,
cooperating processes. On each application server these processes include
the dispatcher as well as work processes; the number of work processes
depends on the available resources. Work processes may be installed for
dialog processing, update, dialog free background processing and spooling.
In addition to these work process types (dialog processing (D), update (V: for
the German Verbuchung), lock management (E), background processing
(B), spool (S), the R/3 runtime system provides two additional services for
internal and external communication (below are the restrictions on the
number of work processes):
May 2015
Page 7 of 16
MBA
INFORMATION SYSTEMS
ENTERPRISE RESOURCE
PLANNING
Enrolment number:
MBISMCT13727119
May 2015
Page 8 of 16
MBA
INFORMATION SYSTEMS
ENTERPRISE RESOURCE
PLANNING
Enrolment number:
MBISMCT13727119
May 2015
Page 9 of 16
MBA
INFORMATION SYSTEMS
ENTERPRISE RESOURCE
PLANNING
Enrolment number:
MBISMCT13727119
Page 10 of 16
MBA
INFORMATION SYSTEMS
ENTERPRISE RESOURCE
PLANNING
Enrolment number:
MBISMCT13727119
Page 11 of 16
MBA
INFORMATION SYSTEMS
ENTERPRISE RESOURCE
PLANNING
Enrolment number:
MBISMCT13727119
Work structure
Organization structure
Product flow facility structure
Information flow facility structure
Management methods
Power and leadership structure
Risk and reward structure
Culture and attitude
Page 12 of 16
MBA
INFORMATION SYSTEMS
ENTERPRISE RESOURCE
PLANNING
Enrolment number:
MBISMCT13727119
Page 13 of 16
MBA
INFORMATION SYSTEMS
ENTERPRISE RESOURCE
PLANNING
Enrolment number:
MBISMCT13727119
Increased Efficiency
Resource wastage is a common source of increase production costs. Often
this is due to improper planning. A company that employs supply chain
management is able to achieve efficiency of its operations since only those
values adding activities are encouraged. This ensures that the organizations
processes flow smoothly and output keeps in line with the company's needs.
Increased Output
A company that employs supply chain management can foster close-knit
relationships with its suppliers and customers, ensuring the timely fulfillment
of orders. A company known for its timeliness and responsiveness will attract
more customers, and will grow as a result of increased output and sales.
Increased Profits
The SCM Systems gives the ability to quickly and effectively process orders
to ensure customer needs are understood and addressed quickly. It will
also provide the business with the flexibility to respond to ever changing
customer demands and market trends.
Improved Collaboration - A SCM system wired in to the latest software
allows you to know the position your raw materials and your finished
products are in by tracking both your suppliers and your distributors. These
companies can also track where you are at in receiving or sending those
materials. This knowledge can keep relationships between these businesses
strong. This system often includes the development of reports on how the
chain of goods progresses from supplier through distributor. These reports
help your businesses to determine potential areas of improvement.
Cycle Times - The cycle time can be defined as the time it takes your
business to turn over a product from raw materials, give it to your distributor
to sell and then make enough money to purchase new raw products to start
the cycle over. If at any point it takes too long to obtain these raw materials,
May 2015
Page 14 of 16
MBA
INFORMATION SYSTEMS
ENTERPRISE RESOURCE
PLANNING
Enrolment number:
MBISMCT13727119
production may have to stop which will slow down your organization. A SCM
system improves cycle times and ensures that raw materials are provided
when your business needs them so that you never have to stop production.
Response to Conflict - Unfortunately, a business cannot always run
smoothly and there are a number of factors that can lead to problems in the
production of a product. If an issue occurs with the suppliers of your
company, you may have to change how you produce your product. If the
distributor goes out of business, you will have to find another way to sell the
product. A SCM system lets your company better cope with problems at
either side of the production spectrum. You can quickly and easily figure out
a response to the problem instead of being surprised by it at a later time.
Additional advantages:
With the increased visibility into the supply chain and adaptive supply
chain network, it can be more responsive. We can sense and respond
quickly to changes and quickly capitalize on new opportunities.
By offering a common information framework that supports
communication and collaboration, SCM enables to better adapt to and
meet customer demands.
We can track and monitor compliance in areas as environment, health
and safety.
Information transparency and real-time business intelligence can lead
to shorter cash-to-cash cycle times. Reduced inventory levels and
increased inventory turns across the network can lower overall costs.
With SCM, we can lower operational expenses with timelier planning
for procurement, manufacturing and transportation. Better order,
product and execution tracking can lead to improvements in
performance and quality - and lower costs. We can also improve
margins through better coordination with business partners.
Tight connection with trading partners keep the supply chain aligned
with current business strategies and priorities, improving
organization's overall performance and achievement of goals.
May 2015
the
Page 15 of 16
MBA
INFORMATION SYSTEMS
ENTERPRISE RESOURCE
PLANNING
Enrolment number:
MBISMCT13727119
May 2015
Page 16 of 16