Binarycse

SAP R/3 ARCHITECTURE

As a ABAP PROGRAMMER in real time in SAP R/3

1.    LIFE CYCLE IMPLEMENTATION PROJECTS (OR) END TO END IMPLEMENTATION.
2.    UPGRADATION PROJECTS, AND
3.    SUPPORT PROJECTS

I.    LIFE CYCLE IMPLEMENTATIONS :

ORGANIZATION---MIGRATING to SAP R/3

IMPLEMENTING SAP R/3 NEWLY

II.    UPGRADATION :

WORKING WITH VERSION SAP R/3 4.73  TO ECC
SAP R/3 4.7 TO ECC

1st step is to find out WHICH OBJECTS SUPPORT ECC FROM BACK VERSION AND THEN CREATE NEW ECC.

III.    SUPPORT :

MODIFYING EXISTING OBJECTS
ASAP – ACCELERATED SAP

SAP R/3 ARCHITECTURE

SAP R/3 HAS
1.    PRESENTATION SERVER (FRONT END) (SAP GUI)
2.    APPLICATION SERVER (PREDEFINED APPLICATIONS) ABAP LANGUAGE works in this SERVER
3.    DATABASE SERVER (PREDEFINED DATABASE)

PRESENTATION SERVER

FRONT END = SAP GUI
VERSION 4.6 C

LOGON SCREEN

MASTER CLIENT 000 OR UNIVERSAL CLIENT CAN BE ACCESSED by Administrator Only.

CLIENT IS NOTHING BUT SET OF USER IDs.

MASTER CLEINT CAN BE ACCESSED by ADMINISTRATOR ONLY.

IN SAPR/3 47 FUNCTIONAL MODULES ARE THERE SUCH AS SD, MM ETC

END USERS CAN WORK WITH PRODUCTION CLIENT

FUNCTIONS OF DEVELOPMENT CLIENT

MODIFYING PREDEFINED OBJECTS AND CREATING NEW OBJECTS    

QUALITY CLIENT CAN BE USED AS QUALITY TESTING BY WAY OF CONDUCTING TEST.

ON PRODUCTION CLEINT END USERS CAN WORK

DEVELOPMENT CLIENT    :     LOGON DETAILS FOR USING DEVELOPMENT CLIENT
800                                    -    CLIENT NUMBER
USER                                  -    SAP USER
PASSWORD                         -    ABAP
LANGUAGE                          -    EN (ENGLISH)

Above is the DIMENSION OF SAP GUI

SAP MENU

OFFICE                                     -    WORK FLOW INBOX AND OUTBOX

LOGISTICS                               -    FUNCTIONAL PEOPLE (SALES & DIST, MM, PROD.)

ACCOUNTING                            -    FINANCE FUNCTIONAL PEOPLE

HUMAR RESOURCE                     -    HR FUNCTIONAL PEOPLE

INFORMATION SYS                    -    PREDEFINED ABAP REPORTS

TOOLS                                     -    ABAP PROGRAMMERS & Administrators are AUTHORIZED TO ACCESS INFORMATION SYSTEMS AND TOOLS OPTIONS UNDER    SAP R/3 – PRESENTATION SERVER.

TOOLS

I.    ABAP WORKBENCH

LIST OF OPTIONS AVAILABLE UNDER ABAP WORKBENCH.

1.    REPOSITORY BROWSER (SE80) Storing objects which are modified or created. Works like a directory for storing SAP Objects.

2.    ABAP DICTIONERY (SE11) It will handle R/3 database part.

3.    ABAP EDITOR (SE38) It is for handling programmes in ABAP language.

4.    FUNCTION BUILDER (SE37) It is for handling functions in ABAP Language.

5.    CLASS BUILDER (SE24) It is for handling object oriented ABAP.

6.    SCREEN PAINTER(SE51) It is for modifying predefined applications and for creating new applications.

7.    MENU PAINTER (SE41) It is for modifying predefined applications and for creating new applications.

All the above (1) to (7) are part of ABAP BOR (Business Object Repository).Names under dictionary is called as Transaction Code. SE 11 (SE means System Engineering)

APPLICATION SERVER

Dialog Service: It provides interface between application server and presentation server.

Update Service: Provides interface between application server and database server.

Message Service: Error handling in SAPR/3.

Gateway Service: For R/3 Distributed Environment (workflow, RFC and BAPIS).

Spool Service: (Printer or Fax) Provides interface between SAPR/3 and external systems such as printers and fax.

ENQUE SERVICE FUNCTIONALITY

It Maintains a data integrity in SAPR/3.

Data Integrity in SAPR/3 is maintained by Enque Service.

Based on quantity with reference of product we have to apply Lock and Unlock.

Background Service: It is for processing ABAP Programme in background.Executes in foreground and background.

Foreground: requires user interaction and executes immediately.

Background: Not requires user interaction and executes on later date.For running long run programme use background service.

DATABASE SERVICE: It can store data permanently in R/3 Database.

Naming Conventions in SAPR/3.

If it is user defined object the name should starts with Y or Z.
Apart from Y and Z the remaining letters are reserved for SAPR/3.

Introduction To ABAP

ERP--> Enterprise Resources and Planning.

Leading applicable products available in market are:

--> 1) Oracle Applications --> Oracle Finance

--> Oracle Management

--> Oracle HRMS.

 

--> 2) People Soft

--> 3) SAP R/3 – System Applications Products Release for 3 tier Architecture

-->  4) RAMCO

-->  5) BANN

Difference between ERP & NON-ERP.

Example:-

For NON-ERP is Oracle, VB
In this user defined databases applications are stored.

For ERP is SAPR/3.
In this predefined databases and applications are stored i.e., not created by user.

Scenarios in ERP:-

Vendor: BANN is suitable for this vendor it is for manufacturing business.

Financial Consultant: RAMCO is suitable for this financial consultant.
-->  In RAMCO nearly 80% predefined tables and applications are there.
-->  BANN and RAMCO are mid range ERP’s.  These are used in small scale or medium scale industries.
-->  ORACLE applications, People Soft and SAP R/3 are for MNC’s (Multi National Company).

SAP R/3  -- ABAP Language Functionality

ABAP stands for Advanced Business Application Programming.

In SAPR/3 we have 17000 predefined database tables.

In SAPR/3 we have 13000 predefined application.

ABAP CONCEPTS:

1.    ABAP TRANSACTIONS
2.    BDC (Batch Data Conversion)
3.    ABAP REPORTS
4.    SAP SCRIPTS

1. ABAP TRANSACTIONS: ABAP Transactions purpose is for modifying predefined applications as per requirements as well as create new applications.
2. BDC(Batch Data Conversion): BDC can transfer the data from NON-SAP to SAP i.e., ORACLE TO SAPR/3.

3.    ABAP REPORTS: It is used for designing reports in SAP R/3 system.
4.    SAP SCRIPTS: Vendor is business partner to the organisation.

Organisation has to procure raw materials from vendor.  For this order created in SAPR/3 for raw material procurement.  After that this order is transferred to vendor

through Fax or E-mail.  Then the vendor can supply raw material.  So that based on raw materials data, finance department can make payments.

-->    i.e., scripts provides interface between SAP R/3 and Business Partner (Vendor).

-->   ABAP is not a syntax language it is only a business language.

Pre Requirements for handling ABAP Language:

-->    SQL Statements
-->   Tables creation in ORACLE
-->   By value and By reference
-->   Object Oriented.

SAP R/3 Versions:
4.0A, 4.0B, 4.5B, 4.6B, 4.6C, 4.7 and 4.7EE
4.7 version is equal to 4.7 EE i.e., 4.7 = 4.7 EE

Where EE stands for Enterprise Edition.  It is latest version of SAP R/3.
In maximum organisations, we can find SAPR/3 with versions 4.6C and 4.7.

SAPR/3 Softwares:
IDES stands for International Demo Educational System

It is SAPR/3 authorized edition.
It is example for application practice and database practice.
Production Software  -  It is for organisations.

For Installation of SAPR/3.

SAPR/3 -->  4.7 -->IDES
Space – 100 GB
RAM – 1 GB

For handling ABAP language:
Working with ABAP or ABAP/4 here 4 stands for 4th generation.
ABAP does not have any versions only SAP has versions.
SAP R/3 is the product of SAP AG (Limited).  SAP AG is german based organisation.
SAPR/3 is released in 1992.
Behind SAP R/3 work functionality is RDBMS functionality.

Advantages of SAPR/3:
1.    SAP R/3 is platform independent i.e., we can install SAPR/3 in any operating system.
2.    SAP R/3 is database independent.

ABAP Language

ABAP Language design is based on ‘C’ Language i.e., source for ABAP is C.

Organisation – X
In MM Department 2 positions are there.  Those are Assistant Manger and Manager.  Assistant Manager for creating orders.  Manger is authorized for approving order what ever approved by Assistant Manager.

Assistant Manager creates order and then sent to Manager through work flow.  Work flow is worked as email like inbox and outbox.  After sending manager, he looks into work flow and approves the order i.e., between Assistant Manager and manager we can apply work flow functionality work flow is equally to email.  Once the manager is approving the order then that order details will be forward to finance department.

Here both MM Department and FI Department are SAP R/3 systems.  The data is transferred from one SAP R/3 system to another SAP R/3 system.  We can use interface between them.  That interface is called as RFC.

RFC stands for Remote Function Call.

RFC provides interface across SAP R/3 systems.

In finance department we have User A and User B.  User A working with a front end VB.  User B working with SAP R/3 provides front end.  It is nothing but SAP GUI.  It is SAP R/3 provided front end.User A will allocate funds that order which are forwarded by Manager of MM Department or which are received by Finance Department.Here finance department is SAP R/3 front end and user A is VB front end.  So we want one interface between SAP R/3 and Non SAP R/3 front end i.e., BAPIS.

BAPI’s stands for Business Application Program Interface.

BAPI’s provides interface between SAP R/3 and Non-SAP R/3 front end.

Scenarios in SAP:-

1.    New Dimensional Products:-
a)    SAP-BI: Where BI stands for Business Intelligence.
It is equivalent to SAP-BW.  Here BW stands for Business Ware Housing.  SAP-BW latest version is 7.0 it is data ware housing product.

b)    SAP-ECC: Where ECC stands for Enterprise Component.  It is latest version and is also 7.0.
c)    SAP-Net Weaver: It is web based product under this we can find sub products:-
i)    SAP-XI : XI stands for Exchange Infrastructure.
ii)    SAP-EP : EP stands for Enterprise Portal.
iii)    SAP-Web As Portal : WebAs stands for web application server.

SAP-XI is equivalent to MQ Series.
SAP-EP is the front end of SAP – Netweaver.
SAP – WebAs is web server in SAP R/3.

It is for web applications.

 

Introduction To ABAP

ERP--> Enterprise Resources and Planning.

Leading applicable products available in market are:

--> 1) Oracle Applications --> Oracle Finance

--> Oracle Management

--> Oracle HRMS.

 

--> 2) People Soft

--> 3) SAP R/3 – System Applications Products Release for 3 tier Architecture

-->  4) RAMCO

-->  5) BANN

Difference between ERP & NON-ERP.

Example:-

For NON-ERP is Oracle, VB
In this user defined databases applications are stored.

For ERP is SAPR/3.
In this predefined databases and applications are stored i.e., not created by user.

Scenarios in ERP:-

Vendor: BANN is suitable for this vendor it is for manufacturing business.

Financial Consultant: RAMCO is suitable for this financial consultant.
-->  In RAMCO nearly 80% predefined tables and applications are there.
-->  BANN and RAMCO are mid range ERP’s.  These are used in small scale or medium scale industries.
-->  ORACLE applications, People Soft and SAP R/3 are for MNC’s (Multi National Company).

SAP R/3  -- ABAP Language Functionality

ABAP stands for Advanced Business Application Programming.

In SAPR/3 we have 17000 predefined database tables.

In SAPR/3 we have 13000 predefined application.

ABAP CONCEPTS:

1.    ABAP TRANSACTIONS
2.    BDC (Batch Data Conversion)
3.    ABAP REPORTS
4.    SAP SCRIPTS

1. ABAP TRANSACTIONS: ABAP Transactions purpose is for modifying predefined applications as per requirements as well as create new applications.
2. BDC(Batch Data Conversion): BDC can transfer the data from NON-SAP to SAP i.e., ORACLE TO SAPR/3.

3.    ABAP REPORTS: It is used for designing reports in SAP R/3 system.
4.    SAP SCRIPTS: Vendor is business partner to the organisation.

Organisation has to procure raw materials from vendor.  For this order created in SAPR/3 for raw material procurement.  After that this order is transferred to vendor

through Fax or E-mail.  Then the vendor can supply raw material.  So that based on raw materials data, finance department can make payments.

-->    i.e., scripts provides interface between SAP R/3 and Business Partner (Vendor).

-->   ABAP is not a syntax language it is only a business language.

Pre Requirements for handling ABAP Language:

-->    SQL Statements
-->   Tables creation in ORACLE
-->   By value and By reference
-->   Object Oriented.

SAP R/3 Versions:
4.0A, 4.0B, 4.5B, 4.6B, 4.6C, 4.7 and 4.7EE
4.7 version is equal to 4.7 EE i.e., 4.7 = 4.7 EE

Where EE stands for Enterprise Edition.  It is latest version of SAP R/3.
In maximum organisations, we can find SAPR/3 with versions 4.6C and 4.7.

SAPR/3 Softwares:
IDES stands for International Demo Educational System

It is SAPR/3 authorized edition.
It is example for application practice and database practice.
Production Software  -  It is for organisations.

For Installation of SAPR/3.

SAPR/3 -->  4.7 -->IDES
Space – 100 GB
RAM – 1 GB

For handling ABAP language:
Working with ABAP or ABAP/4 here 4 stands for 4th generation.
ABAP does not have any versions only SAP has versions.
SAP R/3 is the product of SAP AG (Limited).  SAP AG is german based organisation.
SAPR/3 is released in 1992.
Behind SAP R/3 work functionality is RDBMS functionality.

Advantages of SAPR/3:
1.    SAP R/3 is platform independent i.e., we can install SAPR/3 in any operating system.
2.    SAP R/3 is database independent.

ABAP Language

ABAP Language design is based on ‘C’ Language i.e., source for ABAP is C.

Organisation – X
In MM Department 2 positions are there.  Those are Assistant Manger and Manager.  Assistant Manager for creating orders.  Manger is authorized for approving order what ever approved by Assistant Manager.

Assistant Manager creates order and then sent to Manager through work flow.  Work flow is worked as email like inbox and outbox.  After sending manager, he looks into work flow and approves the order i.e., between Assistant Manager and manager we can apply work flow functionality work flow is equally to email.  Once the manager is approving the order then that order details will be forward to finance department.

Here both MM Department and FI Department are SAP R/3 systems.  The data is transferred from one SAP R/3 system to another SAP R/3 system.  We can use interface between them.  That interface is called as RFC.

RFC stands for Remote Function Call.

RFC provides interface across SAP R/3 systems.

In finance department we have User A and User B.  User A working with a front end VB.  User B working with SAP R/3 provides front end.  It is nothing but SAP GUI.  It is SAP R/3 provided front end.User A will allocate funds that order which are forwarded by Manager of MM Department or which are received by Finance Department.Here finance department is SAP R/3 front end and user A is VB front end.  So we want one interface between SAP R/3 and Non SAP R/3 front end i.e., BAPIS.

BAPI’s stands for Business Application Program Interface.

BAPI’s provides interface between SAP R/3 and Non-SAP R/3 front end.

Scenarios in SAP:-

1.    New Dimensional Products:-
a)    SAP-BI: Where BI stands for Business Intelligence.
It is equivalent to SAP-BW.  Here BW stands for Business Ware Housing.  SAP-BW latest version is 7.0 it is data ware housing product.

b)    SAP-ECC: Where ECC stands for Enterprise Component.  It is latest version and is also 7.0.
c)    SAP-Net Weaver: It is web based product under this we can find sub products:-
i)    SAP-XI : XI stands for Exchange Infrastructure.
ii)    SAP-EP : EP stands for Enterprise Portal.
iii)    SAP-Web As Portal : WebAs stands for web application server.

SAP-XI is equivalent to MQ Series.
SAP-EP is the front end of SAP – Netweaver.
SAP – WebAs is web server in SAP R/3.

It is for web applications.

 

How To Create Web Dynpro Application

Create a Simple Web Dynpro Component

 

Development Objectives

In this step-by-step tutorial we will create a simple Web Dynpro component, which consists of one view.

For the view, you will create a view context, which is linked to a table element on the view layout and which contains the data from table SFLIGHT.

This table will be displayed in the browser at runtime.

Furthermore, you will create a Web Dynpro application for this simple Web Dynpro component, which can be run in the browser.

 

Creating a Web Dynpro Component

 

1. Start ABAP Workbench (SE80) and select Web-Dynpro-Comp./Intf. From the available object list.

 

 

2. To create a new Web Dynpro component, enter the name ZZ_00_SFLIGHT

for the new component in the selection dialog of the object list, and select Display.

 

 

3. In the dialog box that appears, you can enter a description of the new object and select as type Web Dynpro Component. In this dialog you also have the chance to maintain the name of the default window.

 

 

Assign the component ZZ_00_SFLIGHT to package $TMP.

 

As a result, you can now see the newly created Web Dynpro component ZZ_00_SFLIGHT object tree, which contains the objects component controller, component interface (which contains the entries interface controller and interface views) and windows. You can access the objects using double-click.

 

 

 

Creating a new View and Assigning the View to the Window

 

1. Click on the Web Dynpro component ZZ_00_SFLIGHT in the object tree and open the context menu to create a new view.

 

 

2. Create a view MAINVIEW.

 

 

The View Editor will be started on the right side of the Workbench window. In order to open the Layout tab and the View Designer,

a popup appears asking for user and password for

the SAP Web Application Server.

Use the same user/password which you used for logon to the SAP system.

 

3. Save the view MAINVIEW.

 

After saving the view MAINVIEW, it appears in the object tree of the Web Dynpro component under entry Views.

 

4. Now open window ZZ_00_SFLIGHT by clicking on Windows and double-clicking on ZZ_00_SFLIGHT. Switch to change mode.

 

5. Now open the view structure and move the view MAINVIEW inside the window structure on the right hand side by Drag and Drop.

 

Open the window structure on the right hand side and you will see the embedded MAINVIEW.

 

6. Save your changes.

 

 

Creating a View Context for MAINVIEW

 

1. Open the View Editor for view MAINVIEW and switch to tab Context. Create a context node SFLIGHT_NODE in the View Controller by opening the corresponding context menu.

 Maintain the properties according to the screen shot below. Select SFLIGHT as Dictionary Structure and “0…n” for the Cardinality.

Select button Add Attribute from Structure and select all components of structure SFLIGHT.

Press OK.

 

The result should look like this:

 

 

We have now created a context node SFLIGHT_NODE which refers to the data structure of table SFLIGHT and which can contain 0 to n entries at runtime. The context node has been created in the view context, since no data exchange with other views is planned. Therefore, the component controller context usage is not necessary.

 

2. Save your changes of view MAINVIEW.

 

Creating a corresponding UI Element for the context node SFLIGHT_NODE

...

1. Switch to tab Layout of view MAINVIEW.

 

2. Insert a new UI element of type table under ROOTUIELEMENTCONTAINER and assign the properties in the given table.

 

The name of the table is SFLIGHT_TABLE.

3. Create the binding of SFLIGHT_TABLE with context node SFLIGHT_NODE, select Text View as Standard Cell Editors and activate bindings for all cells.

 

 

 

Select context node SFLIGHT_NODE and press Continue.

 

Make sure that the binding for all context attributes is enabled (all checkboxes are activated) and press Confirm Entry (Enter).

 

 

The result should look like this:

 

 

4. Modify the property text of UI element Caption_1 to value Flights.

 

 

5. Save your changes