Refresh RFC metadata

Hi,
I have an RFC connection from R/3 to XI and when i do a change in the structures of FunctIon Modules and import in XI , metadata are not change, because when i run the FM it sends the old structures of the interface
How can i update the metadata of FM in XI?
Thanks

Hi,
Do SXI_CACHE and also do Complete cache
Apart from that do some change in the CC in XI, like any description and activate now
REgards
Seshagiri

Similar Messages

RFC metadata change: how to refresh?

Hi everybody
I have a RFC in my model. If, after import, its metadata are changed, the new in/out parameters are ignored by VC.
How can I workaround this problem (i.e. cache refresh, force metadata import again, ...) without renaming the RFC?
Thanks
Vincenzo

Hai ,
I have an simillar problem even i changed my options to get latest . so i request to change the bapi name and reimport in to Vc then New updated bapi imported . but sometimes using get latest automatically bapi will be updated wht ever u change . so try get latest otherwise change bapi name and reimport ur problem will be solved .
Regards,
venkat

Logical systems for modeldata and RFC metadata

Hi All,
I want to know how I can display the my own created logical system names under the drop-down menu when i have to select the logical system names for modeldata and rfc metadata. I don't want to them to be written instead i want them to be one of the options in the drop down menu, as we have them in the FLIGHT_LIST_INIT example found in the sample applications and examples.
Thanks in advance
Srikant

Hi,
While creating SLD for your R/3 systems give the desired name of wht u want instead of logical name.
For configuring the same refer the link below :-
http://help.sap.com/saphelp_erp2004/helpdata/en/29/e0b75c2b7d40c5bfbda82e905b701c/frameset.htm
Regards,
guru

Invalidating rfc metadata cache

hi all,
i want to invalidate rfc metada cache through adaptive rfc metada cache invalidation tool in webdynpro console..
can any one plz suggest me the path to find that.
thanks in advane
seshagiri

hi juan,
it was very helpful solution to our problem that is invalidating rfc metadata.
after i gone through the pdf,i found it is for NW04S or 7.0 SP12
but v r using SP09
so i beleive upgraing is the only solution.right
or can u suggest any other solution.
thanks in advance
seshagiri

RFC metadata & model instance

Hi,
Could you explain why do we require RFC metadata & model instance in WD adaptive RFC model? What is purpose of these?
Krishna.

hi
Rfc metadata and modeldata logical system destnations to connect to backend systems used in configuration of JCOs .
we configure JCOs in ContentAdmin.
Meta data is the Dictionary data thats why you find Metadata destination in Dictionaries of your project.
Modeldata is the Application data,you can find logical system name of Modeldata in Properties of your Modelclass.
So Model data destination will fetch actual data while metadata destination will contain description of the data.
Regards
sowmya.

WHAT IS MEANT RFC METADATA?

Hi
What is meant by RFC METADATA?
BR
SAGAR

Hi Sagar,
Please google or search SCN before you ask this type of question. The answers are online.
How to use SCN search
Regards,
Jannus Botha

J2EE RFC Metadata cache refresh

Hi All,
I've searched a bit on this forum but can't quite find the answer I'm looking for...
Is it possible to perform a cache refresh without having to restart the server, after making changes to an RFC model and deploying it? It's a pain in the neck to have to keep restarting DEV, QA and PROD everytime we move something through the CMS that has changes to models.
I would have thought the assembly step from consolidation to production would have solved this problem but it doesn't.
Thanks,
Gareth.

> Hi Gareth,
> Several stacks like Web Dynpro, Metadata Interface,
> e, JCO etc read the ABAP metadata and cache it on the
> J2EE Engine. Hence the older metadata still remains
> cached.
> Solution:
> 1) If the interface of a function module is changed
> on the ABAP side, the restart of the J2EE application
> server updates the meta data caches on Java side. A
> restart of the ABAP application server is not
> necessary.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> 2) People think about a option to update the meta
> data cache without a restart of the J2EE application
> server. But nothing in detail is planned at the
> moment.
>
>
>
>
>
>
> Regards,
> Arun
Hi Arun,
I understand what is happening and how it works and why... I was simply asking if there is a way to refresh the J2EE cache without restarting the server?
I think this is something we really need included in future SP's as it is a pain. As mentioned, I would have throught the assembly/import step in the NWDI CMS would have done something to refresh the cache when an SC is imported into the Production system.
Gareth.

How to refresh XI RFC Metadata Repository?

Hi everyone,
I would like to know how to refresh the XI RFCadapter Metadata Repository.
I had a scenario RFC(R/3) -> XI -> Legacy System. I made some changes in RFC on R/3 environment, adding some fields, but unfortunately these fields are not appearing in XI.
I imported and activated the RFC in "Design:Integration Builder" but XI still not receiving these new fields.
Thanks for your attention.
Best Regards,
Gabriel Santana
Message was edited by: Gabriel Sant'Anna

Hi,
Thank you for your replies.
Chris, I followed the guide you sent me, very helpful, but unfortunately when I tried to realize "Single Repository Object Cache Refresh" to object type "AdapterMetaData", the following error appeared:
Method fault! Message : Plain exception:null com.sap.guid.GUIDFormatException at com.sap.guid.GUID.parseHexGUID(GUID.java:814) at com.sap.guid.GUIDGenerator.parseHexGUID(GUIDGenerator.java:111) at com.sap.aii.utilxi.misc.api.GUIDFactory.parseHexGUID(GUIDFactory.java:120) at com.sap.aii.ibrep.server.abapcache.HmiMethod_CacheRefresh.process(HmiMethod_CacheRefresh.java:62) at com.sap.aii.ib.server.hmi.HmiServiceImpl.invokeMethod(HmiServiceImpl.java:132) at com.sap.aii.ib.server.hmi.HmiServer.process(HmiServer.java:248) at com.sap.aii.ib.sbeans.hmi.HmiBean.process(HmiBean.java:62) at com.sap.aii.ib.sbeans.hmi.HmiLocalLocalObjectImpl10.process(HmiLocalLocalObjectImpl10.java:144) at com.sap.aii.ib.web.hmi.HmiServlet.processRequestByHmiServer(HmiServlet.java:281) at com.sap.aii.ib.web.hmi.workers.ExternalClient.doWork(ExternalClient.java:78) at com.sap.aii.ib.web.hmi.HmiServlet.doWork(HmiServlet.java:560) at com.sap.aii.ib.web.hmi.HmiServlet.doGet(HmiServlet.java:704) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37) at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162) Stack trace: com.sap.aii.utilxi.hmi.api.HmiMethodFault: Plain exception:null com.sap.guid.GUIDFormatException at com.sap.guid.GUID.parseHexGUID(GUID.java:814) at com.sap.guid.GUIDGenerator.parseHexGUID(GUIDGenerator.java:111) at com.sap.aii.utilxi.misc.api.GUIDFactory.parseHexGUID(GUIDFactory.java:120) at com.sap.aii.ibrep.server.abapcache.HmiMethod_CacheRefresh.process(HmiMethod_CacheRefresh.java:62) at com.sap.aii.ib.server.hmi.HmiServiceImpl.invokeMethod(HmiServiceImpl.java:132) at com.sap.aii.ib.server.hmi.HmiServer.process(HmiServer.java:248) at com.sap.aii.ib.sbeans.hmi.HmiBean.process(HmiBean.java:62) at com.sap.aii.ib.sbeans.hmi.HmiLocalLocalObjectImpl10.process(HmiLocalLocalObjectImpl10.java:144) at com.sap.aii.ib.web.hmi.HmiServlet.processRequestByHmiServer(HmiServlet.java:281) at com.sap.aii.ib.web.hmi.workers.ExternalClient.doWork(ExternalClient.java:78) at com.sap.aii.ib.web.hmi.HmiServlet.doWork(HmiServlet.java:560) at com.sap.aii.ib.web.hmi.HmiServlet.doGet(HmiServlet.java:704) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37) at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162) at com.sap.aii.ibrep.server.abapcache.HmiMethod_CacheRefresh.process(HmiMethod_CacheRefresh.java:68) at com.sap.aii.ib.server.hmi.HmiServiceImpl.invokeMethod(HmiServiceImpl.java:132) at com.sap.aii.ib.server.hmi.HmiServer.process(HmiServer.java:248) at com.sap.aii.ib.sbeans.hmi.HmiBean.process(HmiBean.java:62) at com.sap.aii.ib.sbeans.hmi.HmiLocalLocalObjectImpl10.process(HmiLocalLocalObjectImpl10.java:144) at com.sap.aii.ib.web.hmi.HmiServlet.processRequestByHmiServer(HmiServlet.java:281) at com.sap.aii.ib.web.hmi.workers.ExternalClient.doWork(ExternalClient.java:78) at com.sap.aii.ib.web.hmi.HmiServlet.doWork(HmiServlet.java:560) at com.sap.aii.ib.web.hmi.HmiServlet.doGet(HmiServlet.java:704) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37) at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162) Root cause : null
Details: No details available
My path for this service is:
http://mslsr08:50000/rep/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=RM&type=AdapterMetaData&guid0=&guid1=
How could I solve this issue and finally refresh the cache?
Best Regards,
Gabriel Santana

WD Java RFC metadata cache invalidation without recycle JAVA

Since we are in a high availability production system, we cannot recycle or CE instance. There are times were the RFC metdata invalidation does not work and the only things that forces it is a recycle of the CE system.
This is contrary to what SAP has publicized, so is there a process in NWA or a single process (and NOT the server0 process) that we can refresh without stopping and starting the java engine.
Much like Visual Administration is there a single service we can stop and start to ensure the engine stays up and running and available?
Thanks
Weyland Yutani

Hi Weyland ,
did you check the guide ?
Metadata Cache Invalidation for Adaptive RFC Models
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/10465350-b4f5-2910-61ba-a58282b3b6df
There's a solution in this guide which explains how to proceed to avoid engine restart in case of ARFC.
(I don't know your engine release, but if it is >= 711, then you may welcome this guide as well:
Using an Adaptive RFC 2 Model in Web Dynpro Java
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50f7192d-2808-2d10-189b-df3fa5f71abf )
I hope this helps.
Best Regards,
Ervin

Refresh Idoc Metadata in PI 7.31 Java Only

Hello experts,
We are facing issue to refresh the Idoc metadata every time when we change Idoc structure in ECC for Idoc outbound scenario.
We have imported the latest Idoc structure in ESR and assigned that to MM,OM and IFolw. Still in message monitoring we can see the old Idoc structure.
Is there anywhere else to import Idoc metadata like it used to be in Dual Stack idx2 ??
Regards,
Suman

Hi Suman,
If you are new with Idoc in PI you try with the sap.help documentation: http://help.sap.com/saphelp_nw73ehp1/helpdata/en/50/980951964146f1a7f189b411796bae/content.htm
Regards

Caching of BAPI/RFC metadata

When calling an RFC from VC, the meta data seem to be cached somewhere. When I change the RFC interface, this is not reflected in VC. How can I delete this cache?

Hi Hartmut,
If you are using EP6 or later, there is a way of clearing the PCD cache (which includes cached metadata from RFC, JDBC or web service connections).
If you navigate to System Administration > Support > Portal Content Directory > PCD Administration, you will see a screen which allows you to either remove specific objects from the cache, or to flush the entire PCD cache.
This is also mentioned in SAP Note 868887.
Regards,
Sascha

Refresh RFC funcion Data service

Hi,
I have created an iView whose data service is RFC function.
I have changed the function interface in the R/3, but I can't see the changes to the interface in the visual composer.
How can I refresh the Interface of this function in the visual composer ?
Thanks,
Ofir.

Hi Ofir Kadosh,
1. First check after setting the below property in VC:
Goto Visual Composer menu --> Tools --> Options --> Compiler Tab --> Change Data service retrieval to Do not cache data services(get latest).
2. Second try to clear the cache in the Portal
Clear the Portal cache. May be the below document help you in clearing the Portal cache.
http://help.sap.com/saphelp_nw04s/helpdata/en/1c/3f1c409ce22402e10000000a1550b0/content.htm
3. If still your problem persists, copy the RFC with some other name and activate it. Then call this data service. This is not the proper way. But workaround to your issue.
Thanks,
Ramakrishna

RFC metadata import error - Couldnu0092t find the branch for version with id

Hi All,
When re-importing RFC meta-data, system returned following error message Couldnt find the branch for version with id = <version id>
I am not able to delete the existing (already imported) RFC meta-data. However, I am able to import the same RFC into a different Software Component.
The error is described in SAP note 710998, unfortunately, this note only references XI 2.0
Is there anyway other than these-
1) Deleting a new SWCV and importing it and then import the RFC and make Release transfer from new SWCV to Old SWCV. If so, is there any impact on my QA systems and Productions systems during transport.
2) Deleting the existing SWC and Reimporting from SLD and trying to import the RFC again and redoing all the design
3) Exporting the current SWC and deleting it and importing the same file and then trying out the RFC import.
These options I just thought as an workaround solutions. Because i am not able to try these, as i don't have any test systems for this. Let me know any suggestions on these.
Thanks in advance,
Regards,
Moorthy

Yes, the used structures were imported from an old XI system. But I created the mapping new on the PI and put the used externel definitions manually to the mapping. That worked fine but now everytime when saving the mapping this error occurs. Btw both structures are used in other mappings, too, and they can be modified without any problems.
Which jdk version do you mean? Client or server?
Regards.
Oliver.

Load balancing and rfc metadata repository in reciever rfc communication ch

hi.
i want to know the purpose of load balancing and rfc meta data repository in RFC communication channel.
and can u send me any examples on this load balancing.
waiting for your response.
bye.
regards.
seeta ram.

Hi Seeta Ram,
Load distribution is handled by the message server (there is one message server in an SAP System). When a user logs on, the message server assigns him or her to the application server that currently has the smallest load.
Well now you can understand that we use load balancing for better performance by distributing the work to different processes to balance or maintain the work load in SAP system.
For more information refer to this link
http://help.sap.com/saphelp_nw04/helpdata/en/28/75153a1a5b4c2de10000000a114084/content.htm
Regards
Sumit Bhutani

Error:No Jco RFc metadata found

Hi Moderator,
Pls don't block this question ,previously also ,I have closed the questionin another forum but you blocked here.
Closed the questionin another forum as I think that this is appropriate forum.
=========================================================
Hi All,
We are using ESS MSS on SAP EP 7.0 SP 15 and using ERP 6.0 EHP 3 .
In Portal while navigating to ESS -> leave_>apply leave we are getting this error
The initial exception that caused the request to fail, was:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: no jcoMetadata found for RFC function 'PT_ARQ_ACCOUNTS_GET_CE'! Please verify, that your model is consistent with the ABAP backend:
Detail information
==============
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: failed to create or init instance of model 'com.sap.xss.hr.lea.model.LeaveRequestAdaptiveModel' in scope APPLICATION_SCOPE with instanceId 'null'
at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getOrCreateModelInstanceFromScopeMaintainer(WDModelFactory.java:341)
at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getModelInstance(WDModelFactory.java:155)
at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getModelInstance(WDModelFactory.java:102)
==============
These are the details:
WebDynpro Content
SAP_ESS 603 SP3
SAP_MSS 600 SP14
SAPPCUI_GP 603 SP3
Business Package
BP_ERP5COM 1.31 SP3
BP_ERP5ESS 1.31 SP3
BP_ERP5HRA 1.11 SP7
BP_ERP5MSS 1.31 SP3
These are the details of ABAP backend
SAP_HR 600 29 SAPKE60029
EA-FINSERV 603 2 SAPK-60302INEAFINSRV
EA-HR 603 3 SAPK-60303INEAHR
EA-APPL 603 2 SAPK-60302INEAAPPL
Pls suggest how to resolve this.Is this related to Version mismatch of support packs.
I have checked the Jco RFC.All are working fine.
Regards
Ajay

Hi Ajay,
I am facing the same issue and am trying to follow the note that you had suggested. The note says to create the dummy RFCs "PT_ARQ_ACCOUNTS_GET_CE", "PT_ARQ_REQLIST_GET_CE" and PT_ARQ_READ_CE_SWITCH, But doesn't say which package I should save the RFC/structures/table types in. I tried saving them in EA-HR, but got the following error. "EA-HR cannot be extended."
Please help.
Regards,
JS.

Refresh RFC metadata

Similar Messages

Maybe you are looking for