Types of Projects in SAP

1) Life cycle implementation or End-To-End Implementation

• Even implementation environment creating objects from scratch(beginning).

• Having an organization name is X and respective organization working with oracle
• Now it is going to SAP EC C 6.0
• From oracle to SAP EC 6.0 Technology
• As a ABAP Programmer you should check Oracle technology and requirements of the company X
• Once you came to know, you should maintain things in SAP
• For first time implementation that is END TO END Implementation
• That means implementing SAP for first time
• LIFE CYCLE IMPLEMENTATION is nothing but implementing SAP R/3 from scratch
• Apart from looking this example
• While working organization with sap

Objects are nothing but programming

2) SUPPORT Project:

• Making changing in existing SAP objects

• X-Company imagine implemented EC C 6.0 VERSION
• Computer found some objects are not supporting current requirements so those objects must be changed.
• Making changes in existing objects
• Presently maximum projects are upgradation projects only

                                           ( 3) UPGRADATION Projects:

• Version 4.7 , it is upgrading from 4.7c to v EC-C 6.0
• Upgrading SAP R/3 version to version
• Objects means programs, tables, applications is known as objects
• Which objects you are using
• In upgradation you should work in both (4.7 & 6.0), how many objects are supporting and not, if it is not supporting we need to create object again in 6.0 version
• Upgrading SAP version to version.

Based on these support & upgradation in projects in resume

1.)    ASAP: Accelerated SAP methodology

2.) ASAP is the implementation methodology for SAP and this is most usable method. 

1.)    ASAP: Accelerated SAP methodology

2.)     

            ASAP is the implementation methodology for SAP and this is most usable method.

·        This methodology provides a road map to implement SAP Projects

·        This methodology supports in SAP EC E and SAP R/3 VERSION

·        Acceralation to SAP methodology in SAP Solution manager is compatible EC C

·        Difference between SAP & SAP Solution manager is when as ASAP works an SAP EC-C & SAP R/3 where as

ERP CONSULTANTS:

1.     PWC

2.     KPMG

3.     DELOITE

4.     E&Y

BDC CONCEPT: Used to transfer data from SAP R/3 to non SAP.

FLOW CHARTS: Are nothing but EPC(enterprises process control diagram) EPC uses VISIO, ARIS tools for EPC diagrams.

ü      Project team contains 13-15 employees

Functional specks: Functional people will prepare it and forwarded to project leader of ABAP and in this area project leader convert function spek to technical spek and which can uses ABAP program.

SAP APPLICATION TYPES:

SAP APPLICATION TYPES:

1. Report application
2. GUI application
3. Business Document processing application
4. Data transfer application

Repository:

A position of database that is used to maintain SAP application components.

Ø                                          SAP provides a standard package or user defined packages in Repository

SAP Implementation life cycle: Life cycle or n-n is called SAP implementation from scratch to top.

Development	Testing/QA	Production
1. Project preparation 2. Business requirement analysis documentation is called i.) Business Read maps ii.) Business blue prints iii) client sign off iv) FIT GAP analysis 3.) Realization phase i.e. start doing on system.	4. Testing/QA	5. Go-live & support Deploy SAP Configure/test End-user training Finally gives ownership to organization Limited post production support

ABAPERS ROLE:

ABAPERS ROLE:

1.                  CUSTOMIZING:                  (i) Modifications

                                                            (ii) Enhancements

2.                  Reusability                             :Reuse the existing components.

3.                  Develop new application        : we can build new application using the

 components of existing application

           

 

CROSS APPLICATIONS:(Advance ABAP Features)

q       RFC(remote function call):

ü        provides communication between distribution SAP R/3 systems

Example:

·          having senders system i.e: SAP R/3 4.7

·          having receivers system i.e: SAP EC-C 6.0

q       BAPI(Business application programming interface) :

·        provides interface between SAP R/3 and third party front ends.

·        Having SAP EC-C Sys with users have:                                                      (i)user-x is working with java as front end.                                        (ii) another user-y is working with SAP technology

·        Respecytive users different Front-ends working with SAP technology

·        For that reason we are using BAPI’S concept

·        SAP GUI is SAP front-end that reason you can expect In-built communication. Communication we should maintain by BAPI’S concept

BAPI’S maintains communication between SAP and NON SAP Front-ends(example: Jave, .Net, VB etc.,)

(3) WORK FLOW

• It is equalant to email, like email, it have inbox, outbox

• Client created order
• Once client created order that workflow can transfer to manager
• Manager can check in workflow inblox
• Manager opens the inbox and he reads the order details
• Once he satisfies the orders, he approves the Order
• Now business transaction starts
• Workflow transfer documents across positions in SAP

CROSS APPLICATIONS used for distributed business activities

SAP ARCHITECTURE:

H/W Requirement Celeron / P IV

128/ 256 RAM, 10 GD HDD

(700-800 MB occupies)

PRESENTATION SERVER:

§                     under presentation server we can find SAP R/3 provided server nothing but sap r/3 GUI.

§                     Under application server u can find all SAP provided application i.e.: 13000 predefined servers

§                     ABAP Language can work within application server

Apart from application server

DATABASE SERVER:

§                     17000 predefined database tables

§                     It is a database independent

§                     We can use any database.

CLIENT

Client is nothing but group of user-ids

§                     If u look into SAP AG, SAP AG can supply SAP R/3 software with client 000 for any organization

§                     Client 000 is the Master client under SAP R/3 Environment. It can supply with client:000, This client is different from client server technology

§                     Client 000 can be called as master client (or) universal client

§                     Client 000 is accessible only to BASIS(i.e Administrator)

§                     Administrator can create Quality client and he can create finally production client and development client.

§                     No user can allow to SAP R/3 administrator client can create development client , quality client and production client.

§                     BASIS is copied client 000, he can create three clients:                                                                                                                                    (1.) Development client (2)test client (3) Production client

 

 

• ABAP programmers can access DEVELOPMENT, TEST CLIENTS
• Function consultants (i.e SD,MM,…) can access all the clients
• End users can access only Production clients( i.e Ene-Users=company employees)
  

DEVELOPMENT CLIENT:

• For creating objects( i.e tables) in SAP
• And to modify predefined objects(i.e applications)
• SAP Architecture have 3 layers (1) Presentation Server(Front –end SAP GUI) (2)Application Server (3)Database Server

APPLICATION SERVER:

• It have 11000 predefined application

     

 DATABASE SERVER

• DB server have 17000 predefined tables
• Each client have the 3 layers

• QUALITY CLIENT(test client)
  For testing objects designed by development client
  PRODUCTION CLIENT:
  
  
  §                     After testing is completed in quality client( test client)
  §                     Once I kept in production client
  §                     Finally object can be kept in production client
  §                     Objects can be maintained in production client
  
  
  v                                         As an ABAP PROGRAMERS can access these two clients only they are
• development client and (2) quality client

As a functional consultant can accessing client from the above first.

§                     End-users can find under production client

§                     U can find the number 100 in development client.

§                     U can find the number 200 in quality client.

§                     U can find the number 800 in production client.

ABAP work Bench :  Is an Integrated development environment used to develop SAP applications.

v                 ABAP Work bench is a set of tools that can generate components of SAP application.

Components of Work Bench :-

1.      ABAP EDITOR : TO CREATE ABAP programs.

2.      ABAP DICTIONARY : Used to create global dictionary objects like database tables, views etc

3.      SCREEN PAINTER :  Used to create GUI Screens for SAP applications.

4.      MENU PAINTER :  Used to create Menus for SAP GUI screens.

5.      FUNCTION BUILDER : Used to create function modules.

6.      FORM PAINTER : Used to create SAP business documents.

7.      MESSAGE CLASS BUILDER : Used to define ‘ALERTS’ These components are technically called as ‘ABAP OBJECTS’ these are stored in Database

Ex : To Create Sales (Components)

• Ø                                          Sap application are build on component model.
  Ø                                          Each tool is responsible for creating a components all there components are ABAP objects.
  Ø                                          All these components are directly stored in database.
  Ø                                          Component model gives reusability.

SAP AG(since AG means LTD) PRODUCTS

SAP AG(since AG means LTD) PRODUCTS

1)                                          SAP R/2: First ERP product released in 1970, language is Cobol.

2)                                          SAP R/3: Second ERP product released in 1993, works on RDBMS and based an ABAP language this is based on ‘C ‘ language.

·        SAP R/3 means Real time Three Tier Architecture

·        This is the product

·        Latest version of SAP R/3 4.7

·        This is not NETWEAVER Technology means does not support web environment technologies

3)                                          SAP(EC-C) products

·        From SAP AG point of view SAP R/3 product must upgrade to SAP EC-C (ENTERPRISE CENTRAL COMPONANTS 6.0) before 2011

·        To install EC-C version

hard disc  400 GB

RAM         4GB

4)                                          MYSAP.COM: used for e-business solutions language is ABAP.

5)                                          SAP mins/SMB: Small scale or medium scale business, language is ABAP.

6)                                          IS(Industries Specific): IS-oil, Textiles, Sales.

NEW DIMENSIONAL PRODUCTS FROM SAP AG:

1)                  SAP XI(Exchange Infrastructure)

·        It is a Netweaver components means supports to web environments

 

• XI is a converter, and it is a middle ware technologies

1)                  SAP-Web AS(Web Application Server)

• It is also Netweaver component
• This is equalant to JAVA web server or any web server.
• In SAP we have to install SAP webserver.

2)                  SAP-EP(ENTERPRISE PORTAL)

• It is also a Netweaver component
• This is to design, Front-end application in Netweaver Technology
• if u see the website of railway reservation it may be developed SAP-EP
• JAVE knowledge is must for this

Note: if we are more than 3 years gap in our academic then learn this application or SAP –BI

3)                  SAP-BI(business Intelligence)

• It is also a Netweaver component
• Dataware housing product

4)                  SAP-BW (or) B/W: (Business information Warehousing: it is data warehousing technology for forecasting analysis.

5)                  SAP-APO’s(Advanced Planes and Optimizers): it is supply chain management technology(scm)

6)                  SAP-SEM(Strategic enterprise management)

7)                  SAP-SRM(Strategic relationship management)

8)                  SAP-CRM(Customers relationship management

9)                  SAP-NETWEAVER

SAP FEATURES

SAP technical features:

1.                                          Platform independent

2.                                          Database independent

3.                                          Based on III tier Architecture

4.                                          Open system.

5.                                          Multi language support.

1.                              Platform independent: It can work in any type of platform

2.                              Database Independent: it can use any type of database Ex: SQL, .NET.

Ø                                                      Open SQL:           it can work for any RDBMS

Ø                                                      Native SQL:         It can work for respective a native usage.

Ø                                                      SAP has its own DBMS inbuilt.

3.                              Based on III tier Architecture: because of III tier architectures faster and that will not effect the change in one layer.

4.                              Open system: Open system is without changing source codes we can develop 70% of SAP remaining 30% we can customize.

5.                              Multi language support: it can support more than 75

PACKAGE:  Already developed application 40% code is predefined.

Example: bill generationg

Application can be customized.

FUNCTIONS OF OPERATING SYSTEM

RESOURCE	MANAGEMENT
Ø      Memory Ø      Processors Ø      Information Ø      Devices	Ø      Keep track of resource Ø      Identify jobs that need resources Ø      Enforce a policy to allocate Ø      Allocate Ø      Deallocate.

There many functions allocated for one user means III tiers

III TIER ARCHITECTURE:

Ø                                          Client server architecture called as II tier architecture.

Ø                                          Client is presentation layer/server.

Ø                                          Server is Backend server.

III TIER:

Interfaces to communicate each other

Advantages of III tier technology:

1)      Load balancing

2)      Scalability(we can increase application server according to our requirements

3)      Availability (if any problem in one as we can remove that place it a new one without effecting

4)      Reliability.