1_day_sap__basis_intro_by_bob_panic

Date: 2 May 2014

Duration: 1 day

Welcome

Your name

Location – home office

Job role

How long with [industry, practice area,

community]

Something unique about yourself

SAP Basis FastTrak WAS 700 2

Housekeeping

Washrooms

Transportation/parking

No pagers or cell phones

Participation

Questions


Day 1: Objectives

At the end of day 1, you should be able to:

Define and analyze Enterprise Resource

Planning

Identify the different phases of SAP Project

Lifecycle

Explain SAP Basis Administration


Day 1: Module map

Module 1: Introduction to Enterprise Resource Planning (ERP)

Module 2: SAP Project Lifecycle

3 Module 3:SAP Basis Administration


Introduction to ERP Module 1

Module 1: Objectives

After completion of this module, you should be

able to:

Define an ERP

Relate SAP to an ERP

Understand the evolution of SAP

Identify the components of SAP.

Understand SAP Netweaver Concept.

Understand the various kinds of Client-Server

Architecture from SAP perspective.

Know SAP’s Release and Maintenance

Strategy


Module 1: Agenda

Topic 1: ERP: Definition

Topic 2: Relation between SAP and ERP

Topic 3: SAP evolution

Topic 4: Components of SAP

Topic 5: Features of Sap Netweaver

Topic 6: SAP client-server architecture

Topic 7: SAP release and maintenance strategy


Enterprise computing in the 70’s

Large corporations developed their software in-house.

These software aimed at automating functional

processes.

Advantages:

– Application tailored to Organization’s requirement.

Disadvantages:

– Systems could not be changed on demand.

– Excessive change made the applications difficult to

manage.

– Required large number of skilled in-house personnel to

maintain the systems.

– Very high cost of maintenance.


Make vs. Buy vs. Mix ‘n Merge


Make Buy Mix ‘n Merge

In-house

developed

applications

3rd Party

developed

applications

Packaged

Corporate

Applications,

such as SAP

& Oracle

Financials

1970’s 1980’s 1990’s

Enterprise Resource Planning (ERP)


ERP is the planning of how business resources (materials, employees,

customers etc.) are acquired and moved from one state to another.

Overview of SAP

The SAP system is software which is composed of different software and a

server as a whole and has the ability to perform standard business functions

for corporations.

SAP (pronounced ess-aye-pea ) is based in Walldorf, Germany .

It stands for Systems, Applications and Products in Data Processing.

Its an ERP Package.

SAP's foundation is built upon the concepts of specialization and integration.

It is world premier provider of client/server business solutions.

SAP products can be broken down further into modules portions of

functionality.


Evolution of SAP AG

SAP was founded in the year 1972 as Systemanalyse und

Programmentwicklung ("System Analysis and Program Development")

The acronym was later changed to stand for Systeme, Anwendungen und

Produkte in der Datenverarbeitung ("Systems, Applications and Products in

Data Processing").

In 1976 "SAP GmbH" is founded and the following year it moved

headquarters to Walldorf .

SAP AG became the company's official name in 2005 (AG is short for

Aktiengesellschaft).

In August 1988, SAP GmbH transferred into SAP AG (a corporation by

German law).

In 1995, SAP was included in the German stock index DAX and On August 3,

1998, the letters S-A-P appear for the first time on the Big board at the New

York Stock Exchange (NYSW).

Henning Kagermann became the sole CEO of SAP in 2003 till date.


Technical solutions

In 1972 the SAP R/1 solution was launched -the first

financial accounting software.

Seven years later, in 1979, SAP launched SAP R/2.

In 1981, SAP brought a completely re-designed

solution to market. With the change from R/2 to R/3

in 1992.


ERP packages

SAP ERP 6.0 from SAP

mySAP from SAP

SAP Business One from SAP

PeopleSoft from Oracle

JD Edwards EnterpriseOne & JD Edwards World

from Oracle


R/2 system

SAP R/2 is a real-time enterprise resource planning (ERP) software.

R/2 is SAP AG mainframe software that runs on IBM, Siemens, Amdahl, and compatible equipment.

R/2 can be linked to R/3 systems and share online data.

R/2 system is mainly targeted at enterprises with data intensive and centralized industries.

R/2 is the predecessor of the client/server R/3 system.

R/2 system offers comprehensive, fully functional business applications to satisfy the demands of mainframe users.


R/3 system and further on

SAP R/3 is a client/server based application and it is designed to run

simultaneously across several separate computer systems.

The R/3 architecture allows distribution of the workload to multiple PC's

connecting in a network.

The SAP runtime system is designed in such a way that it distributes the

presentation, application logic and the data management to different

computers.

SAP R/3 is arranged into distinct functional modules. The most widely used

modules are Financials and Controlling (FICO), Human Resources (HR),

Materials Management (MM), Sales & Distribution (SD), and Production

Planning (PP).

By 1996, the company had earned 1,089 new SAP R/3 customers. At the end

of the year, SAP R/3 has been installed in more than 9,000 systems

worldwide.


SAP’s go-to-market-approach


Source: SAP

SAP product portfolio


Industry Solutions

IS- Aerospace & Defense

IS- Automotive

IS- Oil……

SAP xAPPS

SAP xAPP Resource &

Management

SAP xAPP Product Definition

•……

SAP Smart Business Solutions

mySAP All-in-One

SAP Business One

mySAP Business Suite

mySAP ERP

mySAP SCM

mySAP CRM

mySAP PLM

mySAP SRM

SAP NetWeaver

SAP Enterprise Portal

SAP Master Data Management

SAP Business Information Warehouse

•SAP Exchange Infrastructure

•SAP Mobile Infrastructure

•SAP Web Application Server

Basic elements of SAP solution

SAP NetWeaver: Technological infrastructure for all SAP solutions.

SAP Business Suite: Compromise of cross-industry, SAP Netweaver based

solutions.

SAP Smart Business Solutions: SAP solution for small and midsize

businesses.

The mySAP All-in-One solution is an SAP R/3- based system that has been

extended with business functions from other SAP solutions. This means that

each combination of functions result in a different mySAP All-in-one package.

SAP Packaged Solutions offer a similar approach. These solution are

packages of functions from different solutions of mySAP Business Suite

combined individually for each customer.


Basic elements of SAP solution

SAP xAPPS (Collaborative Cross Applications): Allow for integration of

existing applications with each other by accessing existing datasets and

functions using open interfaces. This means that new applications can be

implemented based on an existing infrastructure.

Industry Solutions provide business functions for selected industries. These

functions are implemented in an SAP R/3(Enterprise) System and are

available as Add-Ons.


SAP business suite

Previously known as mySAP.com.

It’s a complete spectrum of business solutions.

A technological infrastructure that combines openness and flexibility with maturity and stability.

Interfaces for integrating non-SAP products.

Components that can be adapted to meet multiple business requirements.

Numerous industry-specific functions.


SAP business suite (continued)

Comprises of the following solutions:

– SAP ERP (Enterprise Resource Planning)

– SAP CRM (Customer Relationship Management)

– SAP SRM (Supplier Relationship Management)

– SAP SCM (Supply Chain Management)

– SAP PLM ( Product Life-Cycle Management)

One of the major product is SAP NetWeaver.


Solutions and components

Many solutions for business

challenges are provided in context

of mySAP Business Suite.

Different solutions therefore

contain, in part, similar

components. Components refer

to, e.g. an SAP ECC system, an

SAP SCM system or also an SAP

Business Information Warehouse

system.


Source: SAP

Possibilities with SAP business suite


Possible Business Scenarios with SAP Business Suite

Source: SAP

Some key features of SAP NetWeavers

NetWeaver is a technology stack provided by SAP to support SAP Business

Suite and its SAP solutions and other SAP products.

SAP Netweaver allows the integration of non-SAP products.

Customers can make use of the SAP NetWeaver functions for a specific

solution.

SAP for Industry solutions, not only provide add-ons to SAP components but

also preconfigurations and best practices.

mySAP ERP (now SAP ERP 6.0) is available since March 2003.

SAP offered a bundle of components supporting ERP business processes.

SAP R/3 Enterprise was one of those components.

SAP ERP Central Component (ECC) is next step in this evolution.


R/3 / ECC Releases


Source: SAP

SAP NetWeaver

SAP NetWeaver is the technical basis of the solutions

from mySAP Business Suite and the Composite

Applications the SAP xAPPS.

It is also the core of the Enterprise Services Architecture,

SAP basic concept for Web Service solution.

It is the functionally successor of the SAP application

platform mySAP Technology and serves the basis for the

Enterprise Services Architecture, in order to meet

requests for flexibility and integration between systems,

interfaces, users and processes.

It connects information, business processes and people

across system and organizational boundaries.

It the central tool for reducing TCO of complex system

infrastructure.


Source: SAP

NetWeaver: A snapshot


Integration Layer Who would use it? What is it? Which Component?

People

Integration

Information

Integration

Process

Integration

Application

Platform

All users

Managers, Power users,

Administrators &

Developers

Administrators &

Developers

Administrators

& Developers

Linking various

systems in a unified UI

Preparation &

consolidation of data

& data views

Modeling processes,

disturbing & grouping

data

Core technology on

which all NetWeaver

components are built

Enterprise Portal,

SAP Mobile Infrastructure

Master Data

Management,

Business

Warehousing

XI

Web Application

Server

Integration Levels of SAP NetWeaver

SAP NetWeaver provides core functions for the technical infrastructure of

your business solutions in four integration levels.

– People Integration: This ensures the employees to have the information and

functions that is required to perform their work as quickly and efficiently as

possible.

– Information Integration: The Information Integration level provides access to all

structured and unstructured information in the company.

– Process Integration: Process Integration ensures that business processes run

across system boundaries in a heterogeneous system landscape.

– Application Platform: With SAP Web Application Server, the Application Platform

has J2EE and ABAP runtime environments. Thus it supports Web applications and

Web services in an open development environment.


Integration Levels of SAP NetWeaver

SAP NetWeaver also supports cross-application software, so-called

composite applications or xAPPs. (xAPPs connect heterogeneous systems in

continuous cross-function processes so that the underlying applications can

be more or less ignored).

Different software interfaces ensures full interoperability of applications that

are running on Microsoft .NET and IBM WebSphere.


Components of SAP NetWeaver


Source: SAP


SAP system architecture and WebAS

Source: SAP

SAP system architecture and WebAS (continued)

The SAP classic system architecture requires a database server, one or more

application servers, and one or more (typically hundreds or thousands of)

front-end presentation servers.

Many of SAP products (including ECC) are build upon powerful platform

called Web Application Server, or WebAS.

WebAS offers an "open" front-end.

Uses the most popular computer communication languages HTML, XML, Web

Services, and traditional "SAP."

It is very helpful for the programmers for customizing.

WebAS provide an "open" back-end.

A company deploying it, can navigate a number of different roads.


Client / server environment

A standard client/server environment connects workstations, printers, and other client devices to a server.


Source: SAP

Three-tiered architecture


Source: SAP

Three-Tiered architecture (continued)

The three layers are:

Presentation layer:

– The PC-based GUI interface that is used by the end-user community.

Application layer:

– The SAP application servers that service requests for data and manage the

interface to the presentation layer.

Database layer:

– The actual DBMS that communicates with the application servers to fulfill their

requests for data.


Three-Tiered architecture (continued)

Advantages of Three-tier Architectures:

– 1. Scalability: Add machines in middle tier to support more users

– 2. Portability: It is possible to use different platforms at all levels.

– 3. Interoperability and openness: Middleware serves as platform to integrate and

interact with third-party products.

– 4. Nice GUIs: Presentation servers can interact with Microsoft Word, Excel, etc.


The SAP Web as a fixed component of SAP systems


Every SAP system is based on the SAP Web as a runtime environment

Source: SAP

SAP Web Application Server (SAP Web AS)


Source: SAP

SAP Web Application Server (SAP Web AS) (continued)

SAP Web AS is the logical result of further development of the SAP.

Application Server Technology (formerly also known as SAP Basis), with

particular attention being paid to Web-based applications.

SAP Web Application Server offers:

A reliable and thoroughly tested runtime environment, evolved over more

than ten years.

A framework for executing complex business processes that meets the

highest security standards.

A reliable and user-friendly development environment.

Support for open technical standards, such as: HTTP, HTTPS, SMTP,

WebDAV, SOAP, SSL, SSO, X.509, Unicode, HTML, XML, and WML.

High scalability, inherited from SAP Basis.

Support for various operating systems and database systems.


SAP’s release and maintenance strategy

SAP’s release and maintenance strategy defines how SAP delivers and

maintains SAP applications and SAP NetWeaver.

SAP’s release strategy assures the following:

– Aligned availability

– Availability of country, language, and platform versions

– Possibilities for you to participate in different phases of shipment

– Well-defined upgrade paths

SAP’s maintenance strategy provides the following:

– Aligned maintenance between SAP applications and SAP NetWeaver

– A three-phase maintenance model to satisfy different customer needs

– Well-defined timelines for different maintenance phases


Release strategy

The release strategy is based on the following principles:

You can obtain the entire mySAP Business Suite, individual SAP applications

or SAP NetWeaver.

SAP applications and SAP NetWeaver have their individual release cycles.

Usually, SAP delivers a new release of SAP NetWeaver first, and shortly

afterwards, new releases for SAP applications of mySAP Business Suite

follow synchronously.

SAP always gives you access to the current release of an SAP application

and to procedures to upgrade to the current release.

A new release of an SAP application can always be integrated with any

release of any other SAP application that is still in mainstream and extended

maintenance.

This approach offers you maximal flexibility for continuous improvement.


The Ramp-Up

Ramp-Up process is SAP’s process of introducing new application releases to the market.

Ramp-Up program provides a risk-free way for you to implement new SAP software as soon as it becomes available.

At the beginning of the Ramp-Up process, SAP identifies target industries as well as customers who then implement and use the new release in closely monitored and documented projects.

During the Ramp Up, the software is only available for limited circle of customers, customers “apply” at SAP to participate in Ramp-Up.

The Ramp-Up servers to take customer wishes into consideration before the respective SAP software is generally available (“unrestricted shipment”).

Participants in Ramp-Up are given direct contact to the SAP development and are provided with wide support in implementing the SAP software.


Maintenance strategy

The maintenance strategy for cross-industry applications is based on the following principles:

SAP offers three successive maintenance phases: mainstream maintenance, extended maintenance, and customer-specific maintenance.

SAP provides support packages during mainstream maintenance and extended maintenance. The delivery frequency of support packages is dependent on the maintenance phase.

SAP also provides legal changes to adapt the SAP application to new or changed legal requirements during mainstream and extended maintenance.

As part of its release strategy, SAP announces the planned period and scope of mainstream maintenance for a release as soon as the release is announced

5-1-2 maintenance strategy.


Maintenance strategy (continued)


Source: SAP

The SAP software maintenance strategy for SAP R/3 and

mySAP ERP


Source: SAP

Module takeaways

The SAP system is software which is composed

of different software and a server as a whole and

has the ability to perform standard business

functions for corporations. Its stands for

Systems, Applications and Products in Data

Processing.

SAP has evolved from a R/2 to R/3 type

architecture.

SAP Web Application server opens up a variety

of new opportunities.

SAP follows a release and maintenance strategy.


Questions and Answers


Module 1: Summary

Having completed this module, you should now be

able to:

Define an ERP

Relate SAP to an ERP

Recognize the evolution of SAP

Identify the various components of SAP

Put in your own words the underlying features of

SAP Netweaver

Categorize various kinds of client-server

architecture from a SAP perspective

Analyze SAP’s release as well as maintenance

strategy


Day 1: Module map



3 Module 3: SAP Basis Administration


SAP Project Lifecycle Module 2


On completion of this module, you should be

able to:

Describe the different phases of SAP

Project Lifecycle


Module 2: Agenda

Topic 1: SAP Project Lifecycle


SAP project lifecycle


Evaluations Project

Preparation

Business

Blueprint Realization Testing

Final

Preparations Go live Sustain/

Support

A typical new SAP implementation lifecycle

Sustain Sustain Evaluation Realization Testing Final

Preparation

Go live

Sustain

A Typical Multiphase SAP Implementation

The stages of SAP project lifecycle

The stages are described briefly below:

– Evaluation: This may be a decision to choose between different software vendors

or selection of products from a single vendor.

– Project Preparation: Since a SAP implementation intends to map the

organization processes to the ones defined by SAP, the implementation needs to

be have on-board people with complete knowledge of the organization business

processes. The project preparation phase, amongst other things, aims to identify

this team.

– Business Blueprint: What modules of the SAP product would be used and the

mapping of the existing business processes to the processes provided by SAP.

– Realization: The actual work of adapting the SAP software to be aligned with the

organizations business processes is done is this phases. This would include

customizing the software and also development of new objects based on

requirement.


The stages of SAP project lifecycle (continued)

– Testing: The changes made in realization phase need to be tested in isolation as

well as in a consolidated manner using real life like data. This is done in the testing

phase

– Final preparation: The production system is prepared using the changes from the

realization & testing phases. Certain activities need to be done directly in the

production system as well- these are done during the Final preparation phase.

– Go-live: Releasing the productive system to the end-users. The go-live may be

done in a Big Bang (all modules at one go) or in a phase-by-phase manner.

– Sustain / support: The project now moves into the sustain & maintain phase,

where end-users issues would be resolved & ongoing maintenance of the system

would be taken care of.


Module takeaways

A SAP project lifecycle consists of various

stages starting from evaluation to the projects

subsequent support.




Module 2: Summary

Having completed this module, you should now

be able to:


Lifecycle


Day 1: Module map



3 Module 3: SAP Basis Administration


SAP Basis Administration Module 3


After completion of this module, you should be

able to:

Recognize the basic tasks related to SAP basis

administration

Interpret how to navigate though the SAP

Interface

Explain SAP GUI Frontend

Describe a logon group

Explain how to access help in SAP

Categorize the important SAP administrative

tasks


Module 3: Agenda

Topic 1: Relation between basic task and

SAP basis administration

Topic 2: Navigation though the SAP interface

Topic 3: SAP GUI frontend

Topic 4: Logon group

Topic 5: Access help in SAP

Topic 6: Important SAP administrative tasks


SAP basis administration


System

Architect Transport

Adminis-

trator

Batch

Adminis-

trator

Security

Specialist

ABAP

Specialist DDIC

Manager

SAP DBA

System

Adminis-

trator

Interface

Analyst

Solutions

Specialist

BASIS

Consult-

ant

The symphony


Transport Admin

Change Control Across SAP Landscape

System Architect

Sizing SAP Systems Design SAP Landscape

Interface Analyst

Analyse and Monitor Interfaces within SAP Landscape

System Administrator Maintain System Health Monitor and Tune System Performance

SAP DBA Manage integrity of SAP Database Objects Manage Backups and Restore

DDIC Manager Manage Changes to SAP Data Dictionary

Batch Admin

Create and Manage Batch Jobs across Landscape

Security Specialist

Design Monitor and Manage Access to SAP Landscape

ABAP Specialist Troubleshoot and Tune ABAP Programs Apply correction to Programs as per SAP Notes

Solutions Specialist Installation of AP/Add-On Migrate OS/DB Upgrade SAP version Archiving of SAP Data

SAP administrator's frequently used transactions


Source: SAP

NAVIGATION in SAP

Command field The command field is used to enter transaction codes to call a

task without having to choose menu options for navigation.

Find button This button is used to perform a search for data on the screen in

which you are currently working.

Create Session button Open a new session by clicking this button.

Alternatively, execute /O in the command field, overview of the current

session will pop up with option to Generate and End Session.

Customizing of Local Layout button This customizing button allows a user to

customize SAP GUI display options


SAP GUI (Graphical User Interface)

It is also known as presentation interface enables the user to interact with the

SAP system

It implements the graphical user interface using the functions provided by

relevant presentation environment..

The following types of SAP GUI are available:

– SAP GUI for Windows environment- written in C or C++, runs o Windows-based

platforms and supports all transactions in SAP system. The volume of data

transferred for each change is generally a few KB hence user can easily connect

presentation servers over WANs.

– SAP GUI for Java environment is written in Java and is platform independent. It is

similar to SAP GUI for Windows.

– SAP GUI for HTML consists of Internet Transaction Server (ITS) on the server and

Web browser on client end. ITS converts SAP GUI data flow from SAP Web

Application Server into HTML and vice-versa. It does not support all the functions

in SAP system. Almost no installation is required for SAP GUI for HTML.


SAP GUI (Graphical User Interface)

Each time you connect to SAP via the SAP GUI user interface you begin a

user session.

You can have multiple sessions open with multiple SAP components such as

SAP ECC, R/3, CRM, and so on or you can open one or more sessions with a

single system.


Session number

Navigation using mouse

Navigation Using the Keyboard

– Menus can be selected with the mouse or by using the keyboard. To select menu

paths using your keyboard, press F10 (to activate the menu bar), and then use the

navigational arrow keys on your keyboard to select and display the menu.

– You choose a function by highlighting it with the arrow keys and then pressing

Enter.


To select a menu, single-click on the menu to display the various options listed underneath that menu.

Different types of SAP GUI


ITS- internet transaction server required to convert SAP GUI data flow from

SAP Web Application Server into HTML and back.

Java environment

Windows PC + Browser for SAP GUI for HTML

Terminal Client

IITS

Windows PC

SAP GUI SAP GUI SAP GUI

ITS

Dispatcher Application Layer

Presentation Layer

Terminal server

Workstation PC

SAP logon program


Version number Advance Log-on Configuration

System ID

Create connection using a log-on group

Manually define a new connection

Create connection to a specific instance

SAP logon program (continued)

When logging on to an SAP system, you will be prompted to enter the user

and password, among other things.

If you have implemented a Single Sign-On (SSO) solution, you may not need

to enter this information.

You also have the option of specifying a client when logging on; the client field

usually already contains an appropriate default value i.e. 000, 001, 066.

When logging on, you can select a logon language supported by that system.

SAP systems can support a large number of languages, the minimum being

English and one other selected language.

On the logon screen, you also have the option of using the New password

pushbutton to change your password, at the most once per day.


Configuring the SAP logon pad


Meaningful description

Host name or IP address

Two digit number i.e. 00

Three character SID

Log-in screen


Force password change is asked by SAP after initial Log-in.

Calling up functions

You have several options for

navigating in an SAP system:

– By entering transaction codes

in the command field

– By choosing items from menus

in the menu bar

– By choosing items from the

favorites list or from the user

or SAP menus


SAP Easy Access and Favourites

Menu

Command

field

Example: Calling up functions

/n to cancel the current transaction

/nXXXX to call transaction XXXX directly from another transaction.Without the

prefix you can only call XXXX from the SAP Easy Access screen.

/o to display an overview of sessions

/oXXXX to call transaction XXXX in a new session directly from another

transaction

/nend to end the logon session with a confirmation dialog box

/nex to end the logon session without a confirmation dialog box

/i to delete the session you are currently using


Favorites management

The favorites list contains SAP system functions or links to Internet content or

to files on the end user's front-end computer.

The favorites list, which is initially empty, can be edited by each end user in

accordance with his or her preferences. You can only view your own favorites

list.

The Favorites menu gives you the option of adding a function from the user

(or SAP) menu to your personal favorites list by selecting the function and

choosing Favorites→Add.


Using logon group

You can use the ‘Groups’ button (for group selection) to create a new

connection to a system.

This connection uses the logon groups concept, meaning that the message

server always assigns a new logon to the instance with the best performance

in the selected logon group.

The configuration file ‘sapmsg.ini’ is evaluated to display the systems

available for selection.

The message server of the selected system is queried to discover the

available logon groups.

So that the connection to the message server of the system specified in

sapmsg.ini works, it is necessary for the Microsoft Windows file services to

specify the correct message server communication port for the selected

system ID.


Using logon group (continued)

A connection is then created to the relevant host and the message server

running on it using the information from sapmsg.ini and services.


Source: SAP

Without the use of logon group

A typical program buffer for each of the 8 instances (refer to the figure in last

slide), looks like this.

Buffer data will be populated with data of all area.


Source: SAP

Program buffer with the use of logon group


More SD programs

More FI programs

Source: SAP

Accessing help

Sometimes, you might find yourself on a particular SAP screen, wondering

what a particular field is used for.

In these cases, rather than launching a browser session and logging in to

the sap service marketplace, you can instead select the menu path help,

extended help from the screen that you have questions about.

Your online documentation application launches with topic-specific help

related to your current sap screen.


Accessing help (continued)

F1 Help.

You can access field-specific help by positioning your cursor in an SAP field and pressing the F1 key

For example run the transaction PFCG (Profile Generator), click on the Role filed any if there is any confusion in understanding the field press F1.

Performance Assistant will open up to provide for Application, Technical and various other options.




Application

help

SAP help portal

Technical help

Glossary Print


The Technical Information button provides SAP-specific details regarding the

Screen Data (current report name, program name, and screen number), GUI

Data (comprised of the GUI's program name and status), Field Data

(comprised of the table and field names, and data element), and the Field

Description for Batch Input (comprised of the screen field).

The Edit Documentation button allows users with this special access the

capability to update and maintain F1-specific documentation.

The Glossary button provides a glossary of terms. Like Application Help,

though, your System Administrator must set it up.

The SAP Help Portal button opens a browser window and connects you to

http://help.sap.com (assuming you have an Internet connection).

It tells about the possible entries in a field value say role in Role field., desired

value can be copied to text box by clicking check mark (green).




F4 Help: It tell about the possible entries in a field value say role in Role

field., desired value can be copied to text box by clicking check mark (green).

Important SAP administration tasks

User list:

– The user overview (transaction SM04) displays all users logged on to the local

instance. Various administration functions are available here. For example, logging

off a user, or displaying an overview of main memory resources requested by

individual sessions.

– The global user overview (transaction AL08) on the other hand, does not provide

any editing functions, but simply displays a list of all users logged on to the

system, sorted by instance.


Display application servers

Transaction SM51 displays all instances that are currently active in your SAP

system. You can not only access numerous other transactions from here, but

also execute them for an application server you have selected from the

display.

Goto→ Server information → Queue Information displays a simple and

informative overview of the current status (particularly the available capacity)

of request queues managed by this instance.


Background job overview

Transaction SM37 provides an overview of background jobs that are either

planned or have already been executed in the system. You can select these

jobs in a variety of ways, for example, using the name of an ABAP program

that run in one of the job steps.

Note that you can use the change layout... push button to adapt the quantity

of information displayed to your own requirements.


Manage work processes

Functions provided in transaction SM50 and transaction SM66 is very similar,

global work process overview (SM66) and local work process overview

(SM50).

The local work process overview (SM50) provides comprehensive information

on the work processes configured on an instance, such as their current status,

the amount of

CPU time required since they started and administration functions (restarting

a work process, trace functions).

Work processes should always be configured to restart automatically: value

.Yes. in Start column.


Manage work processes (continued)


Manage lock entries

Transaction SM12 enables you to view and manage entries in the lock table.

The lock table is normally managed by the enqueue work process, in

exceptional cases, the administrator may need to intervene.

SM12 displays all entries in the lock table, with a flag in the appropriate

column to denote shared locks. Use the Details push button to display

additional information, such as the transaction that set the lock.

You should only delete locks manually in SM12 in exceptional circumstances

and after thorough checks.

Locks owned by update work processes are displayed in blue.


Profile generation and role maintenance

The Profile Generator, available since SAP R/3 3.1, is used for the structured

creation and assignment of authorizations via roles. Apart from the direct user

assignment, the indirect user assignment is also supported by means of

Organizational Management.


Change roles. modify authorizations

Manage update records

In transaction SM13, you have various options for switching to update

administration (SM14). SM13 also enables you to reprocess update records if

the process was not successful initially. You should not use this option for

update records of type V1 ( because V1 is used for critical updates.


Analyze system log

Transaction SM21, ( SysLog) enables you to analyze system messages that

are recorded in a log file. A distinction is made between messages, warnings,

and errors. Entries are correspondingly color-coded. The SysLog allows you

to identify the user that triggered the problem, the transaction they were using,

and other details.


System log

Send system messages

Transaction SM02: System messages enable you to pass on important

system-related (or general) news to the people affected. System messages

are displayed for each user the next time they interact with the system, on

condition that the messages expiry date has not yet been reached. When

creating system messages, you can not only specify an expiry date, but a

client or server. This means that these messages will either be displayed for

all users in that client or on that server, or for all users in the whole system.


Monitoring

The Computing Center Management System

(CCMS) provides a number of important

administration functions (RZ20):

– System administration (start, stop, reconfigure the

system)

– Background processing and job scheduling

– Printer landscape configuration

– System tuning

– Database administration (backup and

management)

– System profile management

– Dynamic load balancing

– System monitoring


System monitoring with transaction RZ20


Virtual monitoring tree element

Monitoring object

View current system status / open alerts

Module takeaways


The SAP Basis Administrator needs to

perform some transaction for regular health

check up.

The various transactions for checking

system log, ABAP dumps, update records,

batch jobs have been described to you.

You can use SAP Help when you stuck at a

menu.



Module 3: Summary

Having completed this module, you should now be

able to:

Topic 1: Relation between basic task and SAP

basis administration

Topic 2: Navigation though the SAP interface

Topic 3: SAP GUI frontend

Topic 4: Logon group

Topic 5: Access help in SAP

Topic 6: Important SAP administrative tasks


Day 1: Summary

At the end of day 1, we see that you are now able

to:

Define and analyze Enterprise Resource

Planning


Lifecycle

Explain SAP Basis Administration


1_day_sap__basis_intro_by_bob_panic

Documents

sap products

sap release

sap system

evolution of sap ag

sap perspective

overview of sap

sap gmbh

sap evolution topic