Hi Rafi,
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. The following modification scenarios show the support offered by the Adaptive RFC in detail:
· 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.
Field Access
The visibility of enhancement fields using the Adaptive RFC model is achieved by using the generic get/setProperty on the model class.
For the visibility of enhancement fields from within the context use IWDNodeInfo or IWDAttributeInfo. All fields are copied using WDCopyService. To access the enhancement fields, use get/setAttributeValue on the model class.
Example
The following is a code example for a field access:
String getCustomerName()
String getCustomerID()
String getOrderID()
String getQuantity()
BigDecimal getPrice()
String getDiscount()
Object getAttributeValue(“CustomExtension”)
Or
A normal RFc model do not show adaptive behaviour i.e If there is a new entry in your structure and if you try to deploy the application it will give you an error whereas an Adaptive RFC model is flexible to that and it will adapt to changes in your structure(BAPI/RFC).
Adaptive RFC Model is exclusively used for connecting to R/3 System using BAPI'S. they show an adaptive behaviour that is they are flexible to the structure modification
Regards
Vijay Kalluri
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.