Dear all,
I understand if the RFC changed at ABAP side, I will need to re-import the RFC and invalidate the cache, or the RFC result will be incorrect mapped.
But after many try, I just cannot fix that without a server restart, please let me know what I am missing, below listed what I tried before restart:
1) Re-import the RFC
2) Invalidate all JCo relate to the WebDynpro
3) Click "Don't cache" option for all JCo relate to the WebDynpro (Only click the meta data at first but it don't work so...)
4) Rebuild and deploy the WebDynpro
5) Run the deploy WebDynpro once
After that I also tried to:
6) Create the missing context for the new add field in the structure
But still fail, and everything back to normal after a server restart.
Did server restart is the only way to go or I still missed something in the procedure?
Regards
Bill
Bill
Server re-start has been one of the tested way, out of the box functionality
to fix the RFC metadata cache..
However with 7.0, there is a tool which can help invalidate the cache.
You would do it thru Web Dynpro Content Admin...
Sandip
Hi Sandip,
Thanks for the prompt reply.
As I state in point 2 and 3, I already used the tools to invalidate the cache, but it just cannot solve the problem, that's why a started this question.
I can always solve it by restart the server, but it just take too long.
Regards
Bill
hmm thats bit strange the tool didnt help. What server version and SP are you on?
Well if the tool doess not work, go for re-start..you probably wouldn't need it frequently, unless the RFCs/BAPIs are changing frequently.
Sandip
Hi Sandip,
We are on 7.00 SP25, thanks for the reply, at least I know the procedure should be correct.
Regards
Bill
Bill
May be some bug with the Tool in SP25, I have used it in SP12 and it used to work.
You want to check with SAP via OSS message.
Sandip
Hi Sandip,
Thanks for all the effort, as no one point out I have missed anything, I will open a message in OSS to see if it is a bug.
Thanks for the suggestion.
Regards
Bill
Ok great..Do keep us posted if you get reply back from SAP.
Thanks
Sandip
Hi,
OSS confirmed 7.00 SP25 have problem on the tools, and it is fixed at 7.01 SP5.
Regards
Bill
Bill
That's good to hear...in the mean time, go ahead with the server re-starts
sandip