Copyright © 2012 SofOS, C.A. Reservados todos los derechos.

1
Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 2
This unit introduces you to the structure of the mySAP Business Suite family of solutions. Furthermore,
you are given a first overview of the integration and technology patform SAP NetWeaver. Finally, we
will deal with SAP’s release strategy.

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 3

The basic elements of SAP solutions are:
- SAP NetWeaver: is the technological infrastructure for all SAP solutions.
- mySAP Business Suite: bundles all cross-industry, SAP NetWeaver-based SAP solutions.
- SAP Smart Business Solutions: are SAP solutions 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 results in a different “mySAP All-in-One package”. This product is
suitable for customers with a few dozen to a few hundred end users. SAP Business One is a completely new
product that can be easily linked to existing SAP landscapes (by XML). The software is programmed in C++
and can be installed under various Microsoft Windows operating systems. SAP Business One contains functions
important for running your business, such as financial accounting, customer management, purchasing, and
warehouse management. Even the smallest companies can use this software profitably.
- SAP xApps: (Collaborative Cross Applications) allow you to integrate existing applications with each other by
accessing existing datasets and functions using open interfaces. This means that you can implement new
applications 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.

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 4

An SAP system consists of a database and one or more instances. An instance that combines with a
database to create a runnable SAP system is called the central instance. A central instance should be
configured in every SAP system. A central system exists if the system contains only a single instance,
and this is running together with its database on one server.

You can install two instances of a system or even of different systems on one server. When configuring
two systems (or their databases) on one server, you should ensure that the two systems are clearly
differentiated. If not, a conflict situation will eventually occur during the use of common resources (such
as program libraries), especially if one system is to be upgraded while the other is used with the same
release.

No SAP System IDs (SIDs) should be assigned more than once within a company. Performing a
meaningful data exchange with two systems with the same SID is very difficult (renaming the systems).
The three-character SID of the SAP system is always identical to the ID of the database used.

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 5

An SAP system instance is an administrative Unit in which the components of an SAP system that provide one or
more services are combined. The services provided are started and stopped together. All components of an instance
are provided with parameters using a common instance profile.

These components are currently the dispatcher, the work processes, the assigned main memory areas, and an
Internet CommUnication Manager (ICM), if one is configured.

An instance always has exactly one dispatcher. The start of an instance always begins with the start of the
associated dispatcher. A dispatcher requires a minimum of two dialog work processes. Otherwise it is not possible
to start it. Multiple dispatchers can be configured on one host, but must have different system (instance) numbers.
The default for the instance number of a dispatcher is 00. Port 3200 receives commUnication for this dispatcher. If
there are two instances on one machine, the port numbers 3200 and 3201 are usually assigned, and so on.

An instance is also called the application server in the software-oriented view of the client-server model. The
application server provides the rUntime environment for the business applications of the mySAP.com e-business
platform. The mySAP Technology application server is called the SAP Web Application Server (Web AS) and is
the Internet-oriented development of the previously used application server.

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 6

BC (Basis component) is a set of middleware programs and tools from SAP systems. SAP provides the
underlying base that enables applications (such as FI, CO, and SD, for example) to be interoperable and
portable across operating systems and database products. Offers a group of services that make possible
the work of the SAP applications. It works as between the applications and the SAP Netweaver
environment. Also, provides application programming interfaces for programming and handling of
distributed applications.

BC includes client/server architecture and configuration and a graphical user interface (GUI). In addition
to the interface between system elements. Also, BC components include a development environment for
SAP applications, and a data dictionary, as well as user and system administration and monitoring tools.

Since NW 2004, Basis administration changed to Netweaver administration.

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 7

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 8
Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 9
mySAP Business Suite offers many options for integrating your company-internal business processes
and, likewise, integrating business partners. systems. You can implement the integration of cross-
enterprise processes using different technologies, such as with Application Link Enabling, using
Electronic Data Interchange (EDI), through XML data exchange, or also using Collaborative Cross-
Applications (xApps) and Web Services.

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 10

The following processes are required for operating business application software:
- •Presentation processes (for example, for displaying screens)
- •Application processes (for example, for executing application programs)
- •Database processes (for example, for managing and organizing database data)
When you are configuring an SAP system, you need to decide how you are going to distribute the
required processes among the available hardware. There are various ways of doing this, some of which
are described in more detail below. Configurations are either single-level or multilevel, depending on the
number of computer layers used (see the following slide). The SAP R/3 system is an example of business
application software.

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 11

- In central system (or single-tier) configurations, all processing tasks (database, application and
presentation processes) are performed by one computer. This is classic mainframe processing.

- Distributed presentation is a common configuration. The server manages the database and application
tasks. Presentation tasks are executed by SAP GUI.
•
- Two-tier configurations are usually implemented using special presentation servers that are responsible
solely for formatting the graphical interface. For example, many SAP users run SAP GUI processes.
•
- In a three-tier configuration, each layer runs on its own host. Many different application servers can
simultaneously work with the data of a database server.

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 12

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 13
The plattforms, databases and product life cycles are defined by the Product Availability Matrix (PAM).
It bundles technical and release planning information on SAP product versions for quick reference. You
will find information on the availability of SAP product versions, maintenance end dates and upgrade
paths, as well as technical release information (DB-platforms, JSE-platforms, operating systems etc.). A
SAP product version is structured into instances. An instance is a bundle of technically dependent
software component versions to be installed on one single logical system. The technical release
information is displayed per instance.

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 14

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 15
All SAP solutions are accessible using a general front end program, the SAP GUI (SAP Graphical User
Interface). For the sake of simplicity, further descriptions refer to the SAP GUI for the Windows
environment.

The SAP GUI program connects the front end computer with SAP systems. Theoretically you can specify
the SAP system required at the command-line level when calling the SAP GUI; in practice, you never
need to do this. For starting SAP GUI, SAP provides another program: SAP Logon. When you call up
SAP Logon, it displays a list of SAP systems for which you can start the logonprocess. This list is taken
from a file on the front end: saplogon.ini. This file is usually centrally preconfigured and provided for end
users.

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 16

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 17
- The command field lets you start applications directly by entering their transaction code.
- The Menu bar is the top line of any dialog window in the SAP system. The menus shown here depend
on which application you are in. These menus may also contain cascading menus.
- The pushbuttons in the standard toolbar are shown on every SAP screen. If they are not available in an
application, pushbuttons that you cannot use on that screen are deactivated.
- The title bar is the function that you are currently in.
- The application toolbar shows the pushbuttons available in the application that you are currently in.
- The Status bar displays information on the current system status, such as warnings and errors. You can
also change the display variant to show, for example, the transaction code of the transaction you are
currently in.
- Within a field group check boxes allow to select several options at the same time.
- With radio buttons you can only select one option.
- A tab organizes several subscreens to improve clarity.

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 18

You can use the F1 key to display an explanation of fields, menus, functions and messages. The
F1 help also displays technical information on the relevant field. There you will find the
parameter ID that you can use when setting user-specific default values for input fields that are
also linked to the parameter ID. You can also display interesting information by, for example,
calling the F1 help for the command field.

You can also use other buttons in the Performance Assistant dialog box to display information
on the selected field. One of the most important pieces of information, besides the link to the
context-sensitive Application Help, is the link to the Technical Information. Choose this to
display detailed information, such as the parameter ID assigned to the field. You can use
parameters to set defaults for frequently used input fields; to do this, the parameters are stored
with the desired values in the user master record.

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 19

You can choose F4 to display possible input values. You can also call up the F4 help for a field
using the button immediately to the right of the selected field. If a field contains a checkmark
symbol, you can only proceed to the next step in that application after entering a permitted
value (required entry). You can use transaction or screen variants, or Customizing to mark fields
as mandatory or optional, hidden or filled with hidden standard values.

You can choose F4 to display possible input values. You can also call up the F4 help for a field
using the button immediately to the right of the selected field. If a field contains a checkmark
symbol, you can only proceed to the next step in that application after entering a permitted
value (required entry). You can use transaction or screen variants, or Customizing to mark fields
as mandatory or optional, hidden or filled with hidden standard values.

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 20

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 21
SAP systems can be used with a variety of operating systems and databases made by different
manufacturers. The application data in the SAP system is accessed in the ABAP stack via platform-
independent ABAP programs. But the data is stored database-specifically. Hence, the database queries
from the ABAP programs have to be translated into the respective dialect of the database. This is taken
care of by the database interface.

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 22

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 23
The ABAP Dictionary describes the logical structure of the objects used in application development and
shows how they are maaped to structures in the underlying relational database. It makes central
description of all data used in the system without redundancy possible.

The ABAP Dictionary provides a logical view on the application data and the organization of this data in
the underlying database system.

The ABAP Dictionary is an integrated and active data dictionary. Integration in this case means that the
ABAP Dictionary is completely embedded in the ABAP Development Workbench. Also, it is actives in
the run environment.

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 24

The ABAP Language (Advanced Business Application Programming) is a programming language
developed by SAP. The majority of the business applications of an SAP system are written in ABAP. An
ABAP program consists of individual statements.

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 25

Tools:
- Write ABAP or Java code
- Design screens
- Create user interfaces
- Test applications for efficiency
- Check applications for errors
- Use predefined functions
- Access development objects
- Create and access database information
- Create Internet services

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 26

The Repository is the central store for all ABAP Workbench development objects. Is cross-client and
contains all Dictionary objects (tables, data elements, domains) and all ABAP programs, menus, and
screens. Because of the Repository’'s cross-client nature, any Repository objects developed or changed in
any one client are used in exactly the same form in every other client in that system.

Repository objects are grouped together to form packages. Packages are containers for semantically
linked development objects (programs, tables, and so on). Packages are characterized by the properties
nesting, interfaces, visibility and use accesses. The ABAP Repository contains packages from all
software components.

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 27

An SAP system consists of different software layers, also called software components. All of these layers
are regularly updated using Support Packages; that is, errors are corrected and new functions are provided
using Support Packages. The SAP system should always be kept at the current correction status so that
errors in the standard release are preventatively removed.

An error correction that is not yet included in any Support Package is to be imported in accordance with a
SAP Note using the SAP Note Assistant.

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 28

A client usually represents a company in an SAP system. This means that if an SAP system has several
clients, then several companies can be represented and simultaneously active in that system. The client
has a corresponding key field in the tables of the database for that SAP system. If you are logged on to a
specific client, then you can only access data for that client. Clients therefore correspond to independent
business entities.

Has its own set of user master data, application data, and Customizing based on a table key ranges. All
users must log into a specific client within an SAP System. Application data (master and transaction
data) belongs only to one specific client.

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 29

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 30
The base SAP instance comes with two clients: 000, 001 and 066. All the base or subset data is
contained in client 000. Also, client 000 is where the administrator executes some maintenance activities
like configure or patching. Client 001 is a template for future copies. Client 066 is used by SAP for
EarlyWatch Alert auditory.

Clients 000 and 001 comes with SAP* and DDIC users by default. Client 066 only have
EARLYWATCH user.

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 31

The system landscape should enable you to:

Protect aplpication data using:

- Client roles
- Authorization concepts

Perform development, quality assurance and production activities in separate environments to ensure:
- Consistency of repository objects
- A secure and stable production environment

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 32

To ensure smooth production operation, an SAP system landscape should contain the three SAP systems,
the standard clients, and any required additional clients.

A three-system landscape is recommended and meets the needs of most customers:

- Development takes place in the development system. Changed objects are then released to the quality
assurance system.
- In the quality assurance system, you can test new developments without affecting the production
environment. A quality assurance system enables you to integrate development efforts and to check
the validity and consistency of transported objects before moving the objects into production.
- All objects imported into the quality assurance system can also be delivered to one or more production
systems.

The three-system landscape is also a basis to perform a release upgrade.

SAP systems in the same system landscape require unique system names.

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 33

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 34
- Answer the questions

Copyright © 2012 SofOS, C.A. Reservados todos los derechos. 35