Showing results for 
Search instead for 
Did you mean: 

Adaptive RFC

Former Member
0 Kudos

Dear EP Community,

I have some questions! What is adaptive RFC? How it is diiferent from RFC. One more question, What is Client side eventing, Iview Eventing, and Portal Eventing. How do they differ?? Can somebody please help me.

Thanks in advance.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos


Adaptive RFCs are those for which we dont want to re import the model if the underlining structure changes. Thats why its called adaptive..(adaptive to changes).

The following are the advantages of adpative RFC

Data types

If a data type is edited in the back-end system, the structure used for the Web Dynpro application remains valid and no runtime error occurs.

Customer enhancements and adjustments

If a field length is changed in the back-end system or a customer enhancement field is created, the field values are still valid at runtime. The enhancement field remains visible even without a subsequent manual adjustment of the structure at design time.

Release-specific structures

If a structure changes in the back-end system due to a new release – for example, if the application developer adds a new field – no runtime error occurs in the Web Dynpro application.

Different structure definitions in different back-end systems

Restriction: No fields or structures may have been deleted in any of these systems.


Client side eventing are those events which are triggered by client. for eg Button click.

Sever side eventing are those events which are triggered at the server side like time out.

Eventing in the portal usually refers to EPCF ie triggering an event in an iview by another iview. In this eventing we can transfer data in between using Data bag.

Hope this Helps


Answers (3)

Answers (3)

Former Member
0 Kudos


Thanks to Pooja, Vinod, George for your help. Now I have the real understanding of the issues. Keep it up. great work.

Former Member
0 Kudos


The <b>Adaptive Remote Function Call (Adaptive RFC)</b> is a technology that enables the Web Dynpro application developer to use the business functions encapsulated in Business APIs (BAPIs) even after a structure modification, without having to provide the new data using a second back end or a new structure with subsequent regeneration of the proxies.

This new RFC model shows adaptive behavior. This means that the RFC proxies do not use the original design time structure definition at runtime. Instead, this Web Dynpro model automatically adapts the data of the structure passed in the Java proxy generation to the current data – that is, a structure definition in the back-end system that may have been modified.

Generated structures are used for the context definition; the context ensures type-specific access to the attributes, as they are valid at runtime. However, the context attribute does not create the structure attributes until runtime and can therefore automatically take any changes made a later stage into account.

All structures, fields, and data types are maintained by the Java Dictionary runtime. A memory is available for this, which acts like a virtual machine: Load definitions are automatically loaded from the back end on demand.

The Web Dynpro context therefore shows adaptive, non-static behavior. At runtime, not just those fields are visible that were generated at design time.

<b>Client side eventing</b> is a portal service that allows event driven manipulations on the web client without causing a server event.

When a business application uses more than one iview you need <b>portal eventing</b> service(EPCF) to communicate between iviews and to transfer data. There is a Java object, called client data bag, that serves as transient data buffer on the browser.

Hope this helps.



Former Member
0 Kudos

hi nagaraju..

In a broader sence adaptive RFCs helps web dynpro developers to use bsiness functions in BAPI's.

For more details you can refer the link

The explanation for difference between these eventings can be found at the following link