SAP NetWeaver

SAP NetWeaver is the latest advancement in the SAP Technology.

Net Weaver in simple words is an application and Integration platform in which Web Services play a major role and which is open for Non-SAP applications and platform.

For example, If you want to connect SAP to Java or to Dotnet or whichever language,
you will be having connectors/adapters to have a provision for that.

Net Weaver in simple words is an application and Integration platform in which Web Services play a major role and which is open for Non-SAP applications and platform. It is used by organizations to improve productivity and enhance efficiency by making all the resources that are available in an enterprise to work collectively. The SAP customers to bring heterogeneous environments at one platform use SAP NetWeaver. In addition, it enables customers to use the already existing systems without putting in much investment. Further in the near future, the various corporate sectors and Organizations have to take a decision for some common platform; could be Microsoft .NET, IBM WebSphere or SAP NetWeaver. Irrespective of the choice that they make, SAP NetWeaver is the one that integrates with all the three technologies
SAP NetWeaver attains the process of integration by integrating all the available heterogeneous resources of the existing system and unifying them into a homogeneous form. This integrated information forms the basis of total, comprehensible  focused solution as desired in an enterprise.

You can combine various information coming from different sources in a single window.
Portal is a one of the component of SAP NW which provides role based( Manager or team member) access to services.

SAP R/3 (R means Response/real time and 3 - 3 tier architecture) - Was not web-enabled whereas mySAP ERP - Web enabled
mySAP ERP has SAP Web Application Server- NetWeaver
mySAP is an integrated Business Suite, Its totally based on web/NetWever/JAVA Platform.
It supports online transaction. it includes SRM, CRM, APO BI etc.

Code Inspector

The Code Inspector is a tool for checking Repository objects regarding performance, security, syntax, and adherence to name conventions.


Memory Inspector

The Memory Inspector is a tool that is used to display and analyze memory snapshots.

We can use the Memory Inspector to:
· Display memory snapshots in various ways
· Compare memory snapshots and display the results in various ways
· Save memory snapshots on the presentation server and load them from there

Starting the Memory Inspector 

There are two ways of calling the Memory Inspector:
       1.      Calling the transaction S_MEMORY_INSPECTOR
       2.      Choosing the function Memory Analysis ® Compare Memory Snapshots in the ABAP Debugger

Runtime Monitor

The Runtime Monitor is an instrument that supports the recording of information on user-defined events that can occur during runtime of an ABAP program. For example, the information can consist of a test name and a text, which are recorded and stored with the time stamp and frequency of the event. Because this information is collected directly in the main memory, the runtime behavior of the program is barely influenced.
The events are mainly triggered by ABAP programmers and recorded using system classes. However, they can also be directly triggered by the runtime system (SAP kernel). The collected information of all application servers involved is transferred to the database at regular intervals. The Runtime Monitor includes the following functions. Use the links provided to call up more detailed descriptions of these functions.
The Runtime Monitor collects information on user-defined events that are triggered by ABAP programs at runtime. This information is first recorded in the main memory and then transferred to the  database in regular intervals. There it can be adjusted and asynchronously evaluated at any time. The Runtime Monitor provides system-wide information on the current program statuses and their frequency.
The Runtime Monitor also provides functions for defining, activating, and deleting test cases. The tests can be assigned to specific application servers and are then executed on these servers only. The log records can subsequently be displayed in different views and, if necessary, deleted.
Using the Maintain Tests function, you can edit individual tests. Using the Administration function, on the other hand, you can change entire system log records or settings, for example - irrespective of a particular test.

Runtime Analysis in ABAP

The runtime analysis provides an overview of the duration and performance of your source code, from individual statements up to complete transactions.
The runtime analysis tool allows you to examine the performance of any ABAP programs, such as reports, subroutines, function modules or classes, that you create in the ABAP Workbench. It saves its results in performance data files, which you can display as lists. You can use these results to identify runtime-intensive statements, to combine table accesses, and show the hierarchy of program calls.

Transaction SE30 to start the runtime analysis. In the initial screen, we see the four main functions of this tool, which can be activated by pushing the corresponding button.
·         Measurement in dialog status
·         Measurement of external session
·        Selection of measurement restrictions
·         Evaluation of measurement results
With large applications, it is advisable to first analyze the entire application and then check details in the hit lists.

Use the runtime analysis tool to measure the runtime of complex program segments or complete transactions.  
·       Excessive or unnecessary use of modularization units 
·       CPU-intensive program functions
·        User-specific functions that could be replaced with ABAP statements
·        Inefficient or redundant database access.

ABAP Debugger

The Debugger is a programming tool that we can use to execute ABAP programs, by line or by section. With this tool, we can display data objects and check the flow logic of programs.
At the moment, two types of debugging are possible: Debugging with the classic Debugger for release levels prior to 6.40 or debugging with the new Debugger, which is available for all releases after 6.40.
 The main differences between the classic and the new ABAP Debuggers are described below:
  • The new ABAP Debugger is executed in its own external mode (Debugger), while the application to be analyzed (debuggee) uses a second external mode. So far, the application to be analyzed and the debugger itself shared the same roll area of an external mode. For this reason, each action of the Debugger could influence the program flow of the application. Therefore, the classic Debugger cannot use any ABAP statements for designing the user interface. The path for designing modern UI techniques is not available for it.
· With the classic Debugger it is generally not possible to analyze programs in debugging mode that run in an ABAP processor unit and are called recursively from a subordinate unit. For example, a conversion exit cannot be analyzed using the Debugger if it runs within a WRITE statement. However, with the new Debugger this is possible.
  • The new Debugger provides the user with a flexible interface that can be configured as required and has more than eight desktops. Here it is possible to place and arrange up to four tools - depending on the user's selection. For example, it is possible to display source texts or structures. In this way, the user can design the Debugger interface according to his own individual requirements.
There are plans to make the new Debugger the default option as soon as it contains the following functions, which are currently not available:
  1. Watchpoints
  2. Debugging special types (http, BSP, RFC, update task)
  3. Display of memory consumption
  4. Display of system areas

The Transportation in SAP

The Transport Organizer

The Transport Organizer provides you with functions for organizing software development projects. It is designed to support projects of all sizes, whether they are carried out centrally or in a distributed environment.
We use the Transport Organizer to move applications from the development system to the production system. The Workbench Organizer also provides version control and tracking. When you work with the Workbench, you will encounter safeguards provided by the Transport Organizer.
 A brief overview of these checks and how they affect the development process is provided in Development in a Team Environment .

The Package Concept

At present, the SAP System contains more than 300 000 development objects (programs, tables, screens, BAPIs, function modules, types, and so on). These objects are grouped in over 1700 development classes stored in a flat structure.
Any developer can use any object. A developer can hardly set up a protection for his own development objects. He can also only with difficulty mark the development objects that he would like to make available to others. The technical modularization options open to developers on a small scale – for example, using module pools, function groups, or classes – are very limited. Whether on a large or small scale however, there are no mechanisms for technical modularization.
The package concept was developed to address these issues. Packages are a further development of the current development classes with new additional semantics. 
They are designed to help developers modularizeencapsulate, and decouple units in the SAP System.


A package is a container for objects that logically belong together; for example, all of the objects in an application. A package is also a type of development object.An example of a package might be ZSD,ZMM etc
When you create a new object or change an existing object, the system asks you to assign the object to a package.

Storing Development Objects

The SAP system stores development objects in the Repository, which is a part of the database.
When you complete work on a development object like a program, screen, or menu, you generate a runtime version of the object. This runtime version is stored, along with the object, in the Repository. An application consists of several runtime objects that are processed by the work processes in the SAP System.
In a standard SAP installation, development and live operation take place in separate systems. New applications are created in the development system and transported to the production system. Daily work takes place in the production system which uses run-time versions created in the development system.
The division between production and development systems is recommended because changes to an existing ABAP application take immediate effect. To prevent disturbances in daily work flow in the production system, all developments are carried out in development systems designed especially for this purpose.
Existing development classes are simply containers for development objects with a transport layer that determines how the objects will be transported. Packages extend the concept of development classes with the addition of new attributes: nesting, interfaces, visibility, and use accesses.
· Nesting allows you to embed packages in other packages.
· Visibility is a property of package elements. Elements may be visible outside their package. However, they are always visible to other elements in the same package and always invisible to embedded (sub-)packages within their package. For an element to be visible outside the package, it must be contained in at least one package interface.
· Use access is the right of one package to use the visible elements in the interface of a second package (but not the other way round).
Packages use interfaces and visibility to make their services known to other packages. All the visible elements in a package can, potentially, be sued by other packages. In contrast, invisible elements cannot be used by other packages as well. This allows the package to encapsulate its contents and protect its elements from being used by unspecified external packages.
Use accesses restrict the use of the visible elements of other packages’ interfaces. Not all visible elements can be used. A package can only use the visible elements of the provider package after the use access to the latter’s interface has been created.
Nesting allows you to split up larger units of the SAP System and structure them in a hierarchy. The interplay between interfaces and use accesses allows the elements of a package to be hidden simply, and thus protect them from unintentional use.
The package concept also offers the option of splitting and encapsulating the SAP System into technical units (the packages), reducing high levels of dependency and thus decoupling the system on a large and small scale.
(Source From



All about contents or data or information taken from or other sap related web sites which are available on the Internet for this BLOG.
If you find any doubts or mistakes please refer the other SAP/ABAP related sites .