Day 1 - SAP R3 Architecture

Name: Day 1 - SAP R3 Architecture
Uploaded: 2017-08-24T12:26:44.000Z
Duration: 1 h 34 min 54 s
Description: SAP R3 Architecture - 3 layers of SAP Presentation Layer Application Layer Database Layer

SAP System Architecture

In this section, the speaker explains the architecture of the SAP system and how to log in.

SAP System Architecture

The SAP system consists of two servers: one for applications and one for interacting with the database management system.

The application layer interacts with the database layer to provide functionality.

The speaker provides a diagram of the architecture that can be used for reference.

Logging into SAP System

To log in, you need to use the SAP Logon icon, which is a software called SAP GUI software.

You need to install this software on your system and get an entry from your base system.

You can download this software from your company network or talk to local tech support guys like windows admins.

Once you have installed it, you will see an empty screen where you need to type in entries such as application server name, instance number, system ID, etc.

After entering these details, select the entry and click on "log on" to enter into the system.

Logging into SAP System Continued

In this section, we continue learning about logging into the SAP system.

Entering User Credentials

After logging in using your credentials (user ID and password), you will see a home screen that every user sees.

User Interface

The interface may not be user-friendly at first glance but becomes easier with time.

Java applications look more like websites than traditional interfaces.

SAP System Architecture

In this section, the speaker explains the architecture of the SAP system and how it works.

Development and Testing

The development team creates new developments, R&Ds, etc. in the development system.

Programs are tested in the quality system before moving to production to avoid data loss.

There are three systems for each department: development, quality, and production.

SAP System Structure

The SAP system is built like a human body with different parts that work together.

A new medicine is invented and tested on rats first before being tested on monkeys and then humans.

Similarly, programs are tested in development before moving to quality and then production.

Landscape of Systems

The landscape refers to the total number of applications, teams, and environments (development, quality, production).

Each department has its own set of systems for finance (FD1 FQ1 FP1), sales (SD1 SQ1 SP1), HR (HD1 HQ1 HV1), CRM (CD1 CQ1 CP1).

History of SAP

SAP was founded by former IBM employees who wanted to introduce a new software package to businesses.

They created a ready-made package of software that could be delivered to businesses.

R1 Architecture

In this section, the speaker explains what R1 architecture is and how it relates to SAP.

Real Time Database

R1 stands for real time.

They named it as a real-time database.

If you are really working and if you really have a manager, you will see a manager name. That is why they call it a real-time database.

SAP Landscape

There could be different environments under each landscape.

The client has a homony department and how many applications you are using. You need to talk about the total number of users basically.

This is a mandatory question in SAP landscape.

Non Technical Questions

In this section, the speaker discusses non-technical questions that may come up during an interview.

Internet Banking

Nowadays these questions have become more in interviews.

In India, internet banking was not there until 2000, 1998 and 1995.

Interview Preparation

The interview preparation starts from day one not after the completion of course.

Be ready to face these questions when you join some arc and when you are going for an interview.

#sandbox, test system, and other environments

In this section, the speaker explains that there are different types of environments under each landscape.

There could be something called as a sandbox.

After development, there could be something called as a test system.

This variable from company to company.

SAP Growth in India

This section discusses the growth of SAP in India and how it started.

History of SAP Growth

In 1992, SAP's growth started becoming more comfortable to use.

Intelli Group was the first company to bring SAP projects to India.

After Satyam fell down in 2008, clients went to other companies like Accenture and Capgemony which led to their growth.

Application Layer

The application layer consists of processes and services.

Processes reveal what software is running on the system.

There are five types of processes in the SAP application layer, including dialog, background, spool, update, and enqueue.

Dialog Process

The dialog process is responsible for two-way communication between users and systems with a threshold limit of 600 milliseconds.

Long duration activities are handled by the background process while recurring tasks are managed by the spool process.

Updating Database and End Queue

In this section, the speaker explains updating database and end queue. The process of creating, modifying or deleting data is called updating database. End queue is related to following queue when updates are being done.

Updating Database

Whenever you create, modify or delete data in SAP system, you are directly impacting the database.

This process is called updating database.

End Queue

When database updates are being done, it's important to follow a queue.

If you don't follow the queue, there will be a deadlock situation where no work can be done ahead.

If there is no end queue, there will be a rush in the updates which can lead to a deadlock situation or impact system performance.

End queue takes care of ensuring that updates are being done one by one.

Message and Gateway Services

In this section, the speaker explains message and gateway services. Message service is used for load balancing among application servers while gateway connects SAP system with another SAP/non-SAP system.

Message Service

There are two types of services - message and gateway.

Message service is responsible for distributing users equally into servers when they log in.

This ensures that no server gets overloaded which helps maintain high performance.

Gateway Service

Gateway connects SAP system with another SAP/non-SAP system for incoming/outgoing traffic.

It acts as a point from where all incoming/outgoing traffic of a system happens.

R3 and HANA Architecture

In this section, the speaker explains R3 and HANA architecture. R3 architecture contains three layers while HANA architecture has only two layers.

SAP is currently using R3 architecture which contains three layers - presentation layer, application layer, and database layer.

A new architecture proposed by SAP is called HANA architecture which has only two layers - application layer and database layer integrated together.

SAP's own database called HANA will be used from 2020 onwards instead of third-party databases like Oracle or DB2.

Clients using three-tier architecture will have to shift to the HANA architecture by 2020.

Application Layer

In this section, the speaker provides an overview of the application layer.

The application layer consists of servers where users log in through the presentation layer and enter commands that enter through these servers.

The servers interact with databases to get updates.

SAP System Login

In this section, the instructor explains how to log in to the SAP system using the SAP Logon icon and GUI software.

Installing SAP GUI Software

To log in to the SAP system, you need to install the SAP GUI software on your system.

The latest version of the software is 740.

You can download it from your company network or ask your local tech support team for assistance.

Adding an Entry

Once you have installed the software, you will see an empty screen with no entries.

To add an entry, click on "New" and fill in all details such as application server name, instance number, system ID, and description.

Click "Finish" to save the entry.

Logging In

Select the entry you want to log in with and click on "Log On."

Enter your user ID and password when prompted.

Once logged in, you will see a home screen where you can enter SAP commands into a white box.

Understanding SAP Commands

In this section, the instructor explains that using SAP is all about knowing commands and how to use them.

Commonly Used Commands

There are around 30 to 40 commands that security personnel should know.

On a daily basis, only 10 to 20 of these commands are used.

The remaining commands are used rarely or never.

Using Commands

To use a command, simply enter it into the white box on your home screen.

For example: SU01 is used for creating a user while SM50 shows a list of processes running on the system.

Understanding SAP Landscape

In this section, the instructor explains what is meant by "SAP landscape."

Definition

SAP landscape refers to the overall structure of an organization's SAP systems.

It includes all hardware, software, and network components that make up the system.

Example

For example, if you are working for a client called BMW, which is supported by Accenture, the SAP landscape would include all hardware and software used by BMW as well as any additional components provided by Accenture.

BMW Landscape

In this section, the speaker explains the landscape of BMW and how it is structured.

Systems and Applications

The landscape of BMW consists of different systems and applications such as SAP FICO for finance, SAP HR for human resources, SAP SD for sales, SAP MM for materials management, and SAP CRM for customer relationship management.

There are also technical teams such as basis, security, and map teams that are required to install systems and create users. These teams are common to all modules.

Production systems like sales production system store data on sales done in a financial year. Customizations or developments are not done directly in production but in a separate development system to avoid downtime or loss of data.

Naming conventions follow a specific pattern where the first character indicates the type of system (e.g., E for sales), followed by D for development, Q for quality, and P for production.

Development Process

This section covers the development process used in BMW.

Testing Process

All customizations or developments are tested first in a separate development system before being tested in production.

In real-time scenarios, there is an additional quality system where new developments can be tested before being implemented into production.

The testing process is similar to how new medicines are tested on rats before being tested on monkeys and eventually humans.

System Interconnectivity

Data is moved from one interconnected system to another after it has been created.

Purpose of Quality System

This section explains the purpose of the quality system in BMW.

Testing Process

The quality system is used to test new developments before they are implemented into production.

The testing process is similar to how new medicines are tested on rats before being tested on monkeys and eventually humans.

Naming Conventions

This section covers the naming conventions used in BMW.

System Naming Convention

Naming conventions follow a specific pattern where the first character indicates the type of system (e.g., E for sales), followed by D for development, Q for quality, and P for production.

SAP Landscape and Environments

In this section, the instructor explains the different types of environments in SAP landscape and emphasizes the importance of being prepared to answer non-technical questions related to client details.

Understanding Environments

Environments in SAP landscape include development environment, quality environment, production environment, sandbox, and test system.

The number of environments may vary from company to company.

Sandbox is an experimental box where all experiments are done. It is like a playground where people play with their ideas.

Importance of Client Details

When explaining your board to a client, you need to talk about the total number of users, security team size, total teams available, your manager's name, TL name, client headquarters and IT company CEO.

Non-technical questions related to client details can reveal whether you are a real-time consultant or not.

It is important to be aware of client details as they may be asked during job interviews.

Conclusion

In this section, the instructor concludes by emphasizing the importance of being prepared for non-technical questions during job interviews.

Being Prepared for Job Interviews

Non-technical questions are gaining importance in job interviews as they can put candidates in trouble.

To avoid such troubles during job interviews, it is recommended that candidates have at least two clients' details ready with them along with answers to common non-technical questions.

Being prepared for job interviews starts from day one and not after the completion of the course.