Answer / hari kiran vemula

There are mainly 4 types of RFC communication in SAP. They are
1.Synchronous RFC
2.Asynchronous RFC
3.Transactional RFC
4.Queued RFC

Synchronous RFC (sRFC) : In this type of RFC communication,
the calling program waits until the requested processing
step on the remote system has ended and then continues to
work locally.
In other words, both the systems involved must be available
at the time the call is made.

Asynchronous RFC (aRFC) : In this type of RFC communication,
the calling program gives the request to the remote system
and immediately continues to work locally. The requested
processing step is executed on the remote system in isolation.
If the remote system cannot be reached at the time of the
call, the asynchronous calls of the RFC client are lost

Transactional RFC (tRFC) : This type of RFC communication is
similar to asynchronous RFC but by allocating a transaction
id(TID) it guarantees that if a request is sent several
times because of network problems it is processed only
once. Unlike asynchronous RFC, in Transactional RFC the
remote system does not have to be available at the moment
the RFC client program start the call. The data is held in
the source system until the target system is available.
The report program RSARFCSE is called in the background at
regular intervals and tries to place the unsuccessful
requests, identified by their transaction id again.

Queued RFC (qRFC) : This RFC communication is an extension
to the transactional RFC. In this method, all the requests
are queued up(inbound queue and outbound queue) and are
processed in a sequence only if it is certain that all
preceding calls are processed correctly. This method
guarantees that all the requests are processed in the
sequence in which they are received.
This type of RFCs will be used in SCM (APO) systems for CIF
queues etc where requests have to be processed in an order.

Answer / rony

Transactional RFC: It is an advanced version of Async RFC
where the source systems process will not wait for the target
system resources and writes an entry in to ARFC tables. Where
a background scheduler “RSARFCSE” runs for every 60sec and
reads the ARFC tables to commit the transactions. QoS (Quality
of Service). It uses QoS (EO) Exactly Once to commit the
transactions.
Regular RFC:It provides communication mechanism between two
systems where acknowledgement is not required (eg: it is
similar to post card).

once a request is imported,is there any way to undo it? how about version management?

1 Answers  

---

If have 5 years of experience with JD Edwards (ERP), would it be like starting from scratch to learn SAP (ERP)? I have been told that my experience with JDE is not relative to working with SAP.

2 Answers  

---

While doing implementation do you get any issues?

0 Answers  

---

describe the procedure for java stack upgradation.

2 Answers   iGate,

---

Which are the most frequent errors encountered while dealing with transports ?

0 Answers  

---

---

you want to take sap backup using brtools. How would you do that?

0 Answers  

---

Can you create a table with fields not referring to data elements?

4 Answers   TCS,

---

How to solve if more swaps are occurred?

4 Answers   IBM,

---

What are the profiles that are maintained in the R3 system?

4 Answers  

---

Which table contains the details related to Q defined in SPAM? Is there a way to revert back the Q defined? If yes, How?

0 Answers   IBM,

---

How to selftest whether the Sap Application Server is installed properly or not through command prompt?what is the command to selftest ?

3 Answers  

---

How will monitor in CCMS

1 Answers   IBM,

---