cancel
Showing results for 
Search instead for 
Did you mean: 

Adaptive RFC Field values

Former Member
0 Kudos

Hello All,

I have a WD Project using the aRFC, new change request from customer to add three more fields.

We have added these fields in RFC SAP R/3 system and reimported model and mapped the fields, but the problem is these field values are not showing,

I am unable to fetch particularly newly added fields in Web dynpro.

Please help on this.

Thanks and Regards,

CSP

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi,

After the reimport and the restart of the server, bind the new attributes to the model node.

Right click on the model node and select Edit Model Binding. Select the new attributes. Rebuild and deploy.

Regards,

Kartikaye

Former Member
0 Kudos

Hi,

You must restart the server to refelect the changes done in RFC.

if it is local development in your machine, just restart the j2ee engine.

if it is in the portal, you need to restart the portal server.

regards,

Former Member
0 Kudos

Hi,

Try to invalidate the meta data cache through webdynpro console for the newly imported model.

After invalidating the model through webdynpro console still if you are facing the same problem you have to restart the server once.

Go through the link

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10465350-b4f5-2910-61ba-a58282b3...

If you restart the server it will surely work, we have faced this problem may times..

Hope this helps you..

Regards,

Saleem

Former Member
0 Kudos

Hi,

You need to remport the model at WebDynpro side.

After reimport you can get the new fields at design time.

Before deploying the reimported model you have to refresh the Adaptive RFC cache. If not you will get the runtime error.

Follwo the procedure in below document to invalidate the adaptive RFC chache:

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10465350-b4f5-2910-61ba-a58282b3...

After invalidating cache through this tool, still if you are facing the issue: the final resolution is


Restart portal server

Regards,

Charan