The CRfcTransApp Class and Transactional RFC

The CRfcTransApp Class and Transactional RFC

The CRfcTransApp Class is a direct descendent of the CRfcServerApp Class It is an abstract class not to be used as is. It encapsulates the initialization, running and termination of a transactional RFC server application. This application is available in R/3 version 3.0 and onward. A transactional RFC server application (built with the framework provided by the class library) must have exactly one object of a class derived from CRfcTransApp. We will call this the "transaction application object.

This class inherits the following from the CRfcServerApp class:

the encapsulation of the main server processing loop

the management of the server function list

the dispatching of requests from R/3 to appropriate server function objects

In addition there are four virtual functions specific to transactional RFCs that must be overridden by the user.

These four virtual functions are similar to the four callback functions you implement and install in the RFC C-API. They are:

OnCheckID: This function is called when a local transaction starts. It must be used to check whether the transaction is already running or has already been completed.

OnCommit: This function is called when the local transaction ends. It commits the transaction locally.

OnRollBack: This function is called if the local transaction fails because of an error during the processing inside the RFC library. It should be used to roll back a failed local transaction.

OnConfirmID: This function is called when the local transaction is confirmed. All information stored locally about this transaction can be deleted.

These four function are automatically called at runtime by the RFC Class Library when appropriate.