How to do RFC

In our example there are 3 System with following configuration –

DEV ( client 200,300,400 ; H1/192.168.0.1 )

QAS ( client 200,300,400 ; H2/192.168.0.2 )

PRD ( client 200 ; H3/192.168.0.3 )  

       Task ->  DEV(Source) wants to talk to QAS (Target)

Steps :-

1.Login to source (DEV).

2.Execute SM59.

3.Select R/3 connection and click on the create button.

4. Select Connection type 3

5. Provide a description for the destination as below- 

6. Save it.

7. Now we will show the technical details like

 (target host should be ip address

 or host name. system number is 00 in this example)

8.Then provide logon details (In this example)

    Language en;

    Client 200;

    User aleada;

    Password pass;

      

9.Then click to save it.

10. Then click on Test connection.

11.Then look for successful message. 

12. After it authorization test

RFC (Remote Function Call)

RFC is the call of a function module that is running in a different system . It is used to maintain the communication between SAP or NON-SAP system with SAP system.

There are 4 types of RFC present in SAP –

1.Synchronous System :- For direct combination between different system and between SAP system. Both system should be active at that time.

2.Asynchronous System :- For direct combination between different system and for parallel processing of selected task. System can be active or not.

3.Transaction RFC :- The main problem with asynchronous rfc is that when we send data in it, same message can be send one or more time. So removing this type of inconsistency we send an id with that data. With the help of this id receiving of same message more than 1 time will be rejected.

4.Queue RFC :- It is extension of TRFC. That type of RFC maintain a queue. It also ensure that individual steps are processed in the sequence.

5.Background RFC :- It is successor to TRFC and QRFC.

 

“DEVBMGS(XX)”

D(DIALOG) :- It is responsible for all interactive task for the system ,every business process executed in it .If there are no DIALOG free any time then system will not up.It execute one DIALOG at one time. rdisp/wp_no dia is the profile parameter used In it.

E(ENQUEUE) :- Responsible for lock management system and it is used  to ensure data integrity .Commonly  only 1 enqueue work process for single SAP system .Configure up to 4 enqueue work process for better performance .rdisp/wp_ no_eng  is the profile parameter used in it.

V(UPDATE) :-It is used to modify the database requested by DIALOG .For better performance we keep data on server. rdisp/wp_no_vb and rdisp/wp_no_vb2 show number of number of update work process for V1 and V2 respectively. for V1 is time critical process and V2 is less time critical process.

B(BACKGROUND) :- It is used to running a long and time consuming job where large data retrieval is required .It is basically used for batch job scheduling. rdisp/wp_no_btc  is the profile parameter used in it.

Client in SAP

A client is defined as a legally and organizationally independent unit within the R/3

 system, Client create a virtually partition of the SAP system.Main objective of client is to keep data isolated. Data in  a client can be visible on that particular client.

   SAP comes with three standard clients :000,001 and 066.

Client 000 contains client-independent settings .It include parameters for all applications ,standard settings.

Client 001 is a copy of the 000 client ,its setting are client-dependent .It doesn’t behave like 000.SAP customer usually used this client as a source for copying other new clients.

Client 066 is reserved for SAP access to its customer’s system to perform the Early Watch service. When the loads of individual clients differ, the buffer manager of the application service is able to respond and allocate resources appropriately.

Directory structure of R/3 systems

Life of T-CODE

v BACKGROUND JOBS ADMINISTRATION :-

       SM36 - Define Background Job

       SM36WIZ – Job definition wizard

       SM37 - Background Job Overview

       SM39 - Job Analysis

       SM49 - Execute External OS commands

       SM62 - Maintain Events

       SM64 - Release of an Event

       SM65 - Background Processing Analysis Tool

       SM69 - Maintain External OS Commands

Life of T-CODE

v USER ADMINISTRATION :-

      SU 01 - User Maintenance

      SU 02 - Maintain Authorization profile

      SU 05 - Maintain Internet Users

      SU 10 - User Mass Maintenance

      SMLG - Maintain Logon Group

v CLIENT ADMINISTRATION :-

      SCC1 – Local Transport import

      SCC3 –Check Client Copy Log File

      SCC4 –Client overview/creation

      SCC5 –Client Deletion

      SCC7 – Client Import Post Processing

      SCC8 – Client Export

      SCC9 – Remote client Copy

      SCCL – Local Client Copy 

vDATABASE ADMINISTRATION :-

       DB01 - Analyze exclusive lock waits

       DB02 - Analyze tables and indexes

       DB12 - DB Backup Monitor

       DB13 - DBA Planning Calendar

       DB15 - Data Archiving: Database Tables