SAP Blogs: what is sap

Showing posts with label what is sap. Show all posts

Monday, July 2

A brief introduction about SAP

In this article you get information about SAP which helps smaller companies as well as larger companies to run better. From back-office to the boardroom, factory to store, PC to cellular phone, SAP encourages individuals and companies to work together more successfully and use organization understanding more successfully to stand above the competition. We do this by increasing the option program across on-premise set ups, on-demand deployments, and cellular phone devices.

We believe that the power of our individuals, items, and associates releases development and makes significant new value about SAP for customers, and, eventually, entire sectors and the economic climate at large.

Our objective is to help companies of all styles and sectors to run well. Our perspective is to help the globe run better.

About SAP

Headquartered in Walldorf, Malaysia, SAP is the market head in business program. Established in 1972, SAP (which appears for "Systems, Programs, and Products in Data Processing") has a rich history of advancement and development as a true head in the market. SAP applications and solutions enable more than 183,000 clients globally to work viably, adjust consistency, and grow self-sufficiently. With income (IFRS) of €12.5 million for the year of 2010, SAP has more than 55,000 workers and sales and development places in more than 50 nations globally. You can get more information about SAP by visiting our website, such as the Frankfurt inventory market and NYSE, under the icon "SAP."

Founded in 1972, SAP is the globe head in business applications in terms of programming and software-related service income. Based on market capital, we are the planet's third biggest separate program company. We have more than 183,000 clients in over 130 nations.

SAP markets and its goods and solutions mainly through a globally network of local subsidiaries, which are certified to spread SAP items to clients in described areas. Under their certificate contracts, the subsidiaries pass on to the licensor a certain amount of the income produced by circulating the items. Distributorship contracts are in place with separate merchants in some nations.

For a complete list of subsidiaries about SAP, affiliates, and other value investment strategies, see the Notices to the Combined Economical Claims area, Observe (35).

Our management confirming smashes our activities down into four segments: Product, Talking to, Training, and Sybase. For more information about our sections, see the Notices to the Combined Economical Claims area, Observe (29).

SAP is detailed on several deals, such as the Frankfurt inventory market and NYSE, under the icon "SAP."

Our business has obtained its international popularity as a head in the organization applications market for one reason alone. Before we launch our alternatives to our more than 183,000 globally clients, we first use what we have developed to help our workers successfully and successfully address our own functional needs. In short, to manage our organization and to work as a best-run organization, SAP operates SAP. This is the full information about SAP.

Leverage Our Solutions

Working about SAP latest alternatives for on-demand, on-premise, and on-device, SAP's lines-of-business power the IT applications and technology facilities that help them quickly accommodate promote requirements and drive market opportunities. About SAP Global IT team – consisting of program designers, support experts, organization users, and international IT professionals – is aware of best how SAP alternatives can help SAP workers achieve their goals, while reducing the corporation's operating costs and improving its daily performance.

SAP ABAP training

What is SAP ABAP

What is SAP Netweaver

Tuesday, June 26

SAP Jobs

ABAP Programmer Analyst Senior
Ashley Ellis - Burlington, MA

ABAP Programmer Analyst Senior
Client : West Boston. Well established, manufacturer of Medical equipemts
ABAP Analyst need to work hand in hand with department manager. You need to take lead in improving the process of MM and SD Modules.
****************************************************************************

SAP PP/APO Expert

Job Type	Permanent
Advertiser	Progressive Recruitment - Munich
Date Posted	26-Jun-2012
Last Updated Date	26-Jun-2012

Reference Code : 143727

Contact Name : Anika Sieverdin

Contact Telephone : +49 89 55 1 9797

**********************************************************************************************

Monday, June 25

SAP ABAP Training

INTRODUCTION TO SAP AND ABAP/4 LANGUAGE

ABAP/4 editor (Focus on the functionalities of
new ABAP editor)
Arithmetic operations
Check and value tables.
Control statements
Data Dictionary
Data element
Data types
Domain
Introduction SAP R/3 architecture, Introduction to
SAP ABAP/4
Open SQL –statements (insert, modify, delete,
update).
Output statements
Overall introduction to ERP
Parameters
Primary and foreign keys.
Search helps
Selection screens
Simple reporting
String operations
Structures
Table maintenance generator and T-code creation
Tables
Transaction code creation
Type Groups
Views
Writing small programs

REPORTING

Breakpoint creation.
Control Break Statements.
Conversion exits.
Creating and handling buttons.
Debugging techniques.
Monday, June 25, 2012
Declaration
Emphasize on the usage of New Debugger.
Events for classical reports.
Events for interactive reports.
For all entries and joins (inner and left outer).
Function modules.
Hide and hotspot.
Includes.
Internal tables.
Macros
Menu painter.
Message class creation & message types and
handling messages.
Modularization techniques.
Population.
Processing.
Subroutines.
Variants.
Watch point creation.

ABAP OOPS

Fundamentals of OOPS.
Global classes and interfaces.
Importance of Public, Private and Protected
sections.
Introduction to Local classes and methods
Simple reporting using local classes and methods.
Usage of global classes in the reports.
ALV
Adding new buttons in the ALV toolbar and
handling events.
Interactive ALV Reports.
Introduction.
Simple report to display simple ALV grid using
Function Modules.
Simple report to display simple ALV List using
Function Modules
Monday, June 25, 2012
Types of ALV
Usage of latest class library in ECC 6.0 for ALV.
Working with ALV using classes (List, Grid and
Tree).

DIALOG PROGRAMMING

Call Screen.
Creation of
Dynamic Screen.
Field validations.
Flow logic.
Introduction to screen painter and dialog
programming.
Leave Screen.
Leave to Screen.
Lock objects.
Normal Screens
PAI.
PBO.
POH.
POV.
Processing of list from transaction and vice versa.
Programming in object browser.
Screen designing.
Screen table and its fields.
Set Screen.
Sub Screens.
Tab Strips.
Table Controls.

INTERFACE PROGRAMMING

Application server.
Call transaction.
Customer master.
Different methods.
Error Handling in Call Transaction.
File Handling.
Monday, June 25, 2012
Flat file creation.
Handling Table Controls in BDC and Screen
Resolutions.
Introduction to BDC.
Legacy System Migration Workbench (LSMW)
Mass Updation.
Methods in BDC.
Presentation server.
Recordings.
Session method.
Steps to Create an LSMW Project.
Uploading data.
Vendor master.
Why Data Transfers
SAP Scripts
Introduction.
Layout Sets.
Modifying standard layout sets (by using
subroutines).
SAP Script Elements.
Uploading logo.

SMARTFORMS

Graphics management.
Output type configuration to standard orders.
Standard Texts.
Working with smart forms.
Writing print program and designing layouts.

ADOBE FORMS / INTERACTIVE FORMS (PDF)

Introduction
Overview on Form Interface and Layout sets

MISCELLANEOUS TOPICS

ABAP memory.
Correction and Transport System (CTS).
Monday, June 25, 2012
Field symbols.
Imports/ Exports.
Logical Database and Handling Events (LDB).
Merging Requests
MM flow.
Release Requests.
SAP memory.
SAP System Landscape.
SD flow.
SET/GET parameters.
Task Creation.
Transport Organizer.
Workbench Request.

CROSS APPLICATION

Basic.
Concepts of IDOCS.
Creation of IDOCS.
Creation of message types.
Creation of segments
Display IDOCS.
Extension.

IDOCS

IDOCS list.
Introduction to CA.
Monitoring tools of IDOC interface.
RFC destination.
Statistics.
Structure of IDOCS and Types.
Working with RFC function modules.

ALE

Defining logical systems used for ALE interfaces.
Outbound / Inbound processing.
Transferring of master data from one system to another system.
Distribution modal view.
Monday, June 25, 2012
IDOC filtering.
Segment filtering using filter objects.
Reduced IDOC.
Outbound using change pointers methods.

EDI

Overview and architecture.
BAPI and Business Objects
Introduction to BAPI
Overview of Business Objects.
Step By Step Approach followed to create BAPI.
ENHANCEMENTS
Introduction to enhancements.
Different Ways of doing Enhancements.
Types of User Exits.
Field Exits
Menu Exit
Function Exit.
Screen Exit

What is SAP ABAP ?

ABAP 4 is the programming language of the SAP R/3 system. It is used to develop or customize SAP R/3 system, ABAP stands for Advanced Business Application Programming. Main components of ABAP 4 programming language are:

ABAP 4 Data Dictionary

ABAP 4 Development Workbench

ABAP 4 Repository Information

SAP's development tools are accessed from the development workbench. R/3 repository stores the program developed using ABAP. Data dictionary contains tables, structures, domains, data elements. In general it contains the attributes and data upon which programs work. Developers of the SAP R/3 system use development workbench to write programs using ABAP language. ABAP is similar to many other programming languages. It consists of Source Code, Attributes and Text elements.

Transport and maintenance of ABAP code is done though a transport mechanism which is built into the SAP R/3 system. Every change that is done in a ABAP program gets stored into a Transport request which can be moved to QA and subsequently to PRD systems using the transaction SE10.

It consists of the following sub modules/applications/screens:

1. ABAP 00

2. ABAP Query

3. ABAP Workbench

4. ALE

5. ALV reporting

6. ASAP methodology

7. Business Connector

8. Business Server Pages

9. Business Workflow (BC - WF)

10. Data Dictionary

11. Dialog Programming

12. EBP

13. EDI

14. IDOCS

15. Internet Application Server

16. LSMW

17. Menu Painter

18. Mercator Report Painter

19. Report writer

20. Repository Information System

21. SAP Script

22. Screen Painter

23. Smartforms

Saturday, June 23

Function groups and now Objects in the new ABAP Objects language

The center of ABAP Objects are Objects. Any object oriented language focuses on objects and hence maps objects with the real world entities. After release 3.1 of SAP WAS ABAP, BOR or the business object repository contains objects. Examples of objects are customers, invoice, order etc. These are contained in the BOR as examples.

Function Groups and function modules were like objects in ABAP versions before ABAP objects was introduced. Function groups contain function modules. FMs can be treated as services or functions of the objects. Also the global data of function groups formed the attributes of the objects. For example: an FG which processes Sales orders has many FMs within it and global data declared. Global data can be accessed by the FMs within the FG. This ensures encapsulation. The data (global data) and the services (FMs) are combined within a FG.

ABAP programs hold a specific amount of memory art runtime. Similarly when a FM is called, it loads its corresponding FG and global data into memory. One ABAP program can call multiple FMs from several FGs and hence multiple internal ABAP sessions can run and memory occupied.

As already said, When a FM is called, its FG with global data is loaded into memory. This instance of FG can be treated as Object when we look at this from the Object orientation perspective. So the instance of function group is an interface between the user and function module. Function groups global data can be accessed via function modules only. If Function groups and function modules can be used for object orientation of a program then why ABAP Objects was introduced? The answer is below.

In classical ABAP, a program can work with many instances of different function groups.

But it is not possible to work on many instances of a single function group at a time.

ABAP Objects allow the user to work with many instances of a class.

For example : You are supposed to develop a ABAP program which can process many sales orders at the same time. It is not possible to do so with function groups philosophy. You would instead need a class and several objects of that class. Each object at that time would represent a Sales Order.

So now with the new ABAP objects, you can load multiple instances of the same Class using CREATE OBJECT statement. ABAP accesses the interface of the instance using Object’s reference.

Saturday, April 14

SAP Web dynpro ABAP Introduction Audio

Tuesday, June 28

Single Sign On for Non-SAP Applications

Single sign on is possible for external applications also. By external applications, I mean non sap Application. So the scenario is that a user wants to logon to a non sap application from SAP EP without entering user ID and password. Is this possible? The answer is yes. This is possible by implementing SSO for external usage.

There are 2 ways to implement SSO for external usage.

The Dynamic link library SAPSSPEXT is a very intelligent library. It can extract user id and password from the logon ticket issued by SAP EP. So by using this library logon to external or non sap applications is possible. This library has 2 interfaces viz: JNI Java Interface and a COM(Windows) interface. It is available to be downloaded on the sap service marketplace.

Now suppose you have a non-sap applications which is web based and it supports authentication using a HTTP header variable, Web Server Filter method of single sign on is the best for you. This filter studies the logon ticket using a public-key certificate and tries to extract the name of the authenticated user from the logon ticket. This name is then written in the HTTP header variable. Thats it !

Only few web servers support this method of logon. Some of them are Apache Web Server, Microsoft Internet Information Server (IIS), Sun Java System Web Server.

No Need to Remember SAP System Passwords - Implement SSO

What is SSO ?

As the name suggests, single sign on is a feature of SAP EP which enables users to logon to multiple systems during a sessions using only one username and password. SAP EP has various applications integrated into it and users can access those applications. These applications connect to various backend systems. Each system may have login credentials. But when a system is created in SAP EP and user is logged to SAP EP and tries to access data from a system, he not required to logon to that system again if single sign on is configured in the SAP Enterprise portal.

So how do we implement SSO in SAP EP?

There are 2 methods to do it:

1. Using User mapping and

2. Using logon tickets. Logon tickets method is recommended by SAP.

User mapping

User mapping can be used when the system is not able to accept the logon tickets. So the mapping is done between the portal ID and user-id and password of the target system. It is not necessary that portal logon id and ECC system logon id are same.

To create a SSO, you need to create a system in portal. Then you need to set various necessary properties of the system created. The logon method property of the system must be set to UIDPW. Also you need to set user mapping to access SAP ECC.

During single sign, secure information that is the user ID and password of the user are sent across network, so a secure protocol for the communication must be used. Recommended is secure socket layer protocol.

Logon tickets

Logon tickets are essentially ticket of user credentials and not the actual user credentials. They do not contain any passwords. This ticket is issued by the portal server after the user has logged in successfully. This ticket is stored in user’s local machine or client as a cookie. Then it can be used by the external applications like SAP systems to logon. Logon ticket may contain portal user ID and a mapped user ID for logging on to external applications. It contains the valildity period, it contains the information which identifies the system which issued the logon ticket. It also may contain digital signature.

Single Sign On for Non-SAP Applications

Related Posts :

Save Costs, Time, and Efforts-install Business Packages
What Is an Enterprise Portal?

Monday, June 27

Save Costs, Time, and Efforts-install Business Packages

Some basic information about business packages is provided in this post, Business packages are predefined content developed by SAP or third-party vendors that serve particular business requirements.

Business packages are a collection of roles, worksets, pages, or iViews.

By installing a business package, you can save costs, time, and efforts incurred in

implementation. Because it is created by either SAP or third-party vendors, a business

package does not require much development This results in savings. No licensing is involved for importing a business package as long as the customer has purchased licenses for the portal and the backend with which the business package will be integrated.

Depending on the customer’s requirements, you can deploy whole business package, or part of it. You can integrate SAP content in the back end with business package. For example, if SAP Human Resources Application (HR), SAP Sales and Distribution (SD), and SAP Business Information Warehouse (BW) etc are already installed, you can install the business package and integrate with the back end to create transactions through the Web.

You can install three types of business packages:

• Business packages for specialists

• Business packages for managers

• Business packages for end users

A business package may consist of:

• Portal content objects The roles, worksets, pages, iViews, business objects, and

system objects.

• PAR files Portal Archive (PAR) files include Java applications or configuration files

required for content management, collaboration modules and UWL.

• Web Dynpro applications Web Dynpro applications can be run in web dynpro iView.

• Other objects Visual Composer PAR files , Transport packages,Repository

Manager PAR files etc…

Scalibility - Distribution of Software and Hardware Components and Sizing

This post will discuss aspects related to scalability. How to implement

scalibility by adopting techniques such as distribution of software and hardware components and sizing etc.

What Is Scalability?

What if the user population increases suddenly, the geographical distance of the users from the portal increases, number of portal functionality increases, the number of objects in the portal content directory increase or the size of data used in the KM application increase. The portal’s performance should not be affected by all these factors. The measure of its strength to withstand all these adversities is called scalability.

Scalability is important because by conducting appropriate load tests, you can determine aspects such as how many incoming HTTP requests can be processed in an hour, how many concurrent users can use the portal without significant performance degradation, and how many transactions can be executed in SAP R/3 from the portal.

How can scalability be implemented ?

This can be done by adding new hardware, such as servers, RAM, and hard disks, to maintain the portal’s performance at satisfactory levels with increasing loads. Also you can distribute portal components to different physical machines so that enough resources are available.

Sizing for Performance and Scalability

Sizing the various components is very important part of portal infrastructure design so that performance and scalability are good under heavy load conditions. Sizing determines the hard disk, memory, CPU, I/O, and network load requirements so that the response time is satisfactory.

Portal can be implemented in phases ranging over say 2 to 5 years. Is sizing is ok, performance will not suffer when system load increases due to increased users, increased workload activity, and other factors.

Sizing determines the success or failure of the project so it must be done ahead of the project start. But the factors which affect scalability and sizing are very dynamic in nature. They can increase of decrease during the implementation cycle also or after the portal has gone live, so sizing has to be kept in process. It is an ongoing activity and it part of portal maintenance.

Important - Proper sizing ensures that the portal performance does not suffer due to increased load.

The factors that influence sizing are database versions, portal software versions, customer-related factors and operating system versions.

customer-related factors can be the workload on the system, the nature of users in terms of the intensity of use of applications, number of users, geographical distribution of users,the amount of customizing involved.

Factors that can affect sizing are :

• Number of top-level menus in top-level navigation (TLN)

• Number of nodes in the detailed navigation iView

• Layout of the portal desktop and the portal framework page

• Number of iViews in the content area of the portal desktop

• Number of Java iViews that use Java Connector Remote Function Call (JCO RFC)

• Number of iViews that fetch data from SAP and non-SAP backend systems

• Custom navigation iViews and the programming model used to create those iViews

• Number of roles and groups created in the UME database

• Number of concurrent users using the portal

• Think time between two successive clicks

Etc…

It is very important that data about the above stated factors is gathered during the requirement gathering phase and thought is given to it well ahead. This will result in smooth operations after go live.

Sunday, June 26

Introduction to SAP NetWeaver Enterprise Portal

In this post, we address what ancha enterprise portal is and how it differs from an

ordinary website. We then discuss the business benefits involved in implementing

an enterprise portal. In the next post, as part of the introduction, we deal with the

SAP NetWeaver Portal in particular and analyze the various components that constitute

the portal.

We also look at the SAP NetWeaver technology stack and analyze the role of the SAP

NetWeaver Portal in the stack. We then address some of the benefits of using the portal,

such as navigating intuitively, drag and relate functionality, branding and personalization,

integration using iViews, role-based personalization, securing the portal, single sign-on, and

ready-made implementation of content using business packages.

Another important component of the SAP NetWeaver Portal is the Knowledge

Management (KM) component that is used for integrating unstructured content. This is

accomplished using two major components—namely, Content Management and TREX.

Knowledge Management provides functionality such as discussion forums, content

workflow, and classification. Sitting on top of KM is the collaboration functionality of

the portal, which provides functionality such as the collaboration room, the Collaboration

Launch Pad, real-time collaboration, and third-party integration.

Why SAP NetWeaver Portal?

One of the first few questions that needs to be answered during a portal implementation is

how do we stand to benefit by implementing a portal? Is it really important to use a portal,

or is it something that can be avoided? A portal provides a means by which we can improve

the business efficiency of a process. For example, by implementing a portal, a company can

provide the right information to the right person at the right time. Based on this information,

the person can make a decision that is not only correct, but also quick.

By implementing an enterprise portal, you can provide the right information in the right

format to the right person at the right time.

The portal provides the required information in one place. Not only does the portal

increase the productivity of an employee, it also reduces the turnaround time of a given

business process. By implementing a portal, a customer service representative can quickly

attend to customer complaints, or a sales representative can place an order at a customer

site and answer customer inquiries regarding pricing.

related post :
What Is an Enterprise Portal ?

SAP Blogs

Pages