Monday 21 March 2011

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.

No comments:

Post a Comment