RFC Adaptive Model,JCO destinations error

HI,
I created the tutorial application to get Flight List using RFC adaptive model.
I created the JCO destinations in web dynpro content administrator after configuring the SLD (after many problems though ).
Our Server is Web AS 6.4 ABAP + JAVA ,but no R/3 modules installed.
WD_FLIGHTLIST_MODELDATA_DEST-type application--single server connection
WD_FLIGHTLIST_RFC_METADATA_DEST-type Dictionary-load balanced
The JCo destinations status shows green.
The test for WD_FLIGHTLIST_MODELDATA_DEST is succesful but the test for WD_FLIGHTLIST_RFC_METADATA_DEST fails with the error:[code]
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=nwserver GROUP=PUBLIC R3NAME=NWS MSSERV=sapmsNWS PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR Group PUBLIC not found TIME Thu Nov 10 18:24:23 2005 RELEASE 640 COMPONENT LG VERSION 5 RC -6 MODULE lgxx.c LINE 3515 DETAIL LgIGroup COUNTER 2 [/code]
The ping fails and if i test it again,i get another error
[code]com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=nwserver GROUP=PUBLIC R3NAME=NWS MSSERV=sapmsNWS PCS=1 ERROR Group PUBLIC not found TIME Thu Nov 10 18:29:13 2005 RELEASE 640 COMPONENT LG VERSION 5 RC -6 MODULE lgxx.c LINE 3515 DETAIL LgIGroup COUNTER 1 [/code]
What is wrong?Any more steps required?
If i try to edit it,the type is still the same-Application with single connection.
How can i change it?Do i need to change it to type Dictionary in the first place? How to proceed.
Please guide.
Regards,
Siddhartha
Message was edited by: Siddhartha Jain
Message was edited by: Siddhartha Jain

hi Siddhartha,
You have to configure PUBLIC group using SMLG transaction
check these links out
http://help.sap.com/saphelp_nw04/helpdata/en/28/1c623c44696069e10000000a11405a/content.htm
hope this helps you
Regards
Rohit

Similar Messages

RFC Adaptive Model Questions

Hi all,
I have some questions about RFC Adaptive Model in Web Dynpro:
1)Can I add a new RFC into a Model without recreating that?
2)Theres a way to WebDynpro dont lost de mapped attributes like an input field thats mapped to an import parameter of a RFC? Because all the times that I change the Model and recreate that, my application lost the link between Controller and View and its generate a lot of work to redo this manually.
Thanks,
Manoel

About RFC models, if I have this schema:
RFCModels
-- ZRFC_A
-- ZRFC_B
-- ZRFC_C
If I want to add a new RFC to this model (ZRFC_D), I can't do that. In this case I want to create a new Model with the ZRFC_D right?
When I import a Web Services Model and I have made some changes in Web Services, I don't have a Re-import option enabled like RCC models. What can I do in this case?
Thanks,
Manoel

JCo destination error while executing the webservice model

Hi,
I have explained what I have done so far and whats my issue right now.
My requirement is calling a PI interface (exposed as webservice) from webdynpro for java and setting some parameter value to the PI interface based on which our functional flow will continue.
Done so Far :
1. Created a webdynpro for java application using NWDI.
2. received the WSDL file of the PI interface and imported as "Adaptive webservice model" into webdynpro.
3. used the model and set the parameters to PI interface and executed the model.
4. I have created JCO destinations in the source system (where the application runs) to communicate to the PI system. A special user has been created and assigned in the connection for communicating.
5. Also I have created the "Dynamic Webseviceproxies" in visual admin with the same name as the JCO destinations. It had a property "URL" for which I have tested with providing both the PI server URL (Http://<Hostname>:<Port no>) and also the complete webservice URL (Which calls the WSDL file directly)
when I run the application, I get the following error.
1. Exception on creation of service metadata for WS metadata destination 'WD_RFC_METADATA_DEST' and WS interface '{<Interface Name>'. One possible reason is that the metadata destination 'WD_RFC_METADATA_DEST' has not been properly configured; check configuration.
after some exception the next error follows
2. Invalid Response Code 403 while accessing URL: <The URL which I have provided in the webservice proxy in Visual admin tool> Response Message: Forbidden.
after some lines of exception from PI server the next error follows.
3. Error: You are not authorized to view the requested resource
My Question :
1. Do I miss anything in Configuration?
2. Is my way of approach wrong?
3. Any additional authorization needed?
Kindly provide some ideas and inputs.
Regards,
Mahendran B.

Dear Mahendran
JCO destination will not used for the Web Service Model. While creating the webservice model, you need to use the logical destination which you have created in the Visual Admin.
Please refer to the Secured WebServices II and verify currently used webservice logical destination How To Reimport Web Service Models in Web Dynpro for Java
You can also refer to
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/900bbf94-a7a8-2910-e298-a651b4706c1e?QuickLink=index&overridelayout=true
Hope it will helps
Best Regards
Arun Jaiswal

RFC or Bapi RFC ? to import RFC Adaptive Model - Is the same one or other?

Hi:
I want to know if is exactly the same to import a RFC not a (BAPI marked as RFC) to use the model, since I'm getting this error:
[Info]: Creating Model: PepueModel
[Info]: Creating Model Class: Z_Psim_Ngc_Pep_Ue_Input
[Info]: Creating Model Class: Z_Psim_Ngc_Pep_Ue_Output
[Error]: RFC Import Failed. The import has been terminated.
[Fatal]: com.sap.mw.jco.JCO$Exception: The function module "DD_DOMA_GET" not released for 'remote' calls.
[Fatal]: com.sap.ide.metamodel.importers.rfcmodel.RFCImportFailedException: RFC Import failed. Cause: class com.sap.mw.jco.JCO$Exception:The function module "DD_DOMA_GET" not released for 'remote' calls.
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: The function module "DD_DOMA_GET" not released for 'remote' calls.
 at com.sap.mw.jco.rfc.MiddlewareRFC$Client.nativeExecute(Native Method)
 at com.sap.mw.jco.rfc.MiddlewareRFC$Client.execute(MiddlewareRFC.java:1221)
 at com.sap.mw.jco.JCO$Client.execute(JCO.java:3691)
 at com.sap.mw.jco.JCO$Client.execute(JCO.java:3136)
 at com.sap.mdi.ddtypes.DDFactory.execute(DDFactory.java:173)
 at com.sap.mdi.ddtypes.DDFactory.execute(DDFactory.java:164)
 at com.sap.mdi.ddtypes.DDDomain.<init>(DDDomain.java:45)
 at com.sap.mdi.ddtypes.DDDataelement.<init>(DDDataelement.java:59)
 at com.sap.mdi.ddtypes.DDFactory.analyseJCOReturn(DDFactory.java:451)
 at com.sap.mdi.ddtypes.DDFactory.getDDObject(DDFactory.java:434)
 at com.sap.mdi.ddtypes.DDFactory.getDDObject(DDFactory.java:372)
 at com.sap.mdi.ddtypes.DDFactory.getDDObjectWithSubtree(DDFactory.java:262)
 at com.sap.mdi.RfmParameter.getDDObject(RfmParameter.java:602)
 at com.sap.dictionary.types.mdi2metamodel.R3ToMetamodelDictionaryConverterWithNestedStructures.getDdicObject(R3ToMetamodelDictionaryConverterWithNestedStructures.java:206)
 at com.sap.ide.metamodel.importers.rfcmodel.DynamicRFCModelImporter.ImportRFC(DynamicRFCModelImporter.java:341)
 at com.sap.ide.metamodel.importers.rfcmodel.DynamicRFCModelImporter.doImport(DynamicRFCModelImporter.java:196)
 at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.ModelWizard$3.run(ModelWizard.java:706)
 at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
The tutorial:
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/11/e2bc3d9ecc6b3be10000000a114084/frameset.htm">click here</a>
says "not-released function modules with a yellow icon."
My RFC (NOT BAPI MARKED AS RFC) is display with a yellow icon.
Searching the error "DD_DOMA_GET" not released for 'remote' calls I found the SAP note: 717836, it says The function module DD_DOMA_GET should be changed to remote-enabled. Where Should I find this function? I guess that is at the R3 System, what should I do to make it remote-enabled?. The other note I found was the SAP note 672745. But I really don't know it those notes apply to my problem.
What is the meaning of: not released? what should be done to make it RELEASE?.
Who made it told me that can't make me a BAPI to bring me the data, he only can do a RFC to get the list I need. The RFC (NOT BAPI MARKED AS RFC) was tranported and can be executed without any problem inside the R3 4.6
The RFC has a parameter, but I think that at import time it doesn't care.
Thanks for the time and interest on this thread.

Rodrigo:
The yellow or green icon it doesn't have to be if its a RFC or BAPI, it have to be with the release state of the function (BAPI or RFC, in this case seems to be the same).
This is the documentation abut it (it's at my original post too) see: http://help.sap.com/saphelp_nw04/helpdata/en/11/e2bc3d9ecc6b3be10000000a114084/frameset.htm
Hope it helps you

JCO DESTINATION ERROR

Hi Everyone,
We created JCO RFC's between PORTAL and ABAP systems, they are working fine. we also created the JCO destinations for METADATA in web dynpro. While we are trying to test the JCO destination it is throwing the following error
<h4>com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=indhcm GROUP=SPACE R3NAME=E6M MSSERV=sapmsE6D PCS=1 ERROR service 'sapmsE6M' unknown TIME Tue Feb 21 17:57:28 2012 RELEASE 701 COMPONENT NI (network interface) VERSION 38 RC -3 MODULE nixxhsl.cpp LINE 776 DETAIL NiHsLGetServNo: service name cached as unknown COUNTER 1</h4>
Help me regarding this issue
Regards,
Mahesh

Hi Mahesh,
Please check
1. SPACE logon group is created in SMLG
2. Check if the below entry in maintained in services file in the system.
sapms<SID> 36$$/tcp # SAP System Message Server Port
$$ - is your instance number of the abap system.
What is the SID for ABAP and JAVA system.
Thanks
Jaianandh V

ESS/ MSS JCO destination error...

Hi All,
I have created all JCO destinations and when i test them , the result is successful
But once i click on ess/mss tab in portals, i get the error..
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'SAP_R3_HumanResources_MetaData' in the SLD. No such JCO destination is defined in the SLD.
But i have maintained SAP_R3_HumanResources_MetaData in the SLD.. Actually i have two SAP_R3_HumanResources_MetaData services one is active and another is inactive..
For SAP_R3_HumanResources -- i have used "Logon Ticket" and for SAP_R3_HumanResources_MetaData -- used userid & pwd.
Actually i have to do UserMapping as my portal userid and R/3 userid are different.. Then in this case am i creating JCO destinations correctly.. If not how to do..
Please throw some light into this problem by your valuable suggestions.
Thanks & Regards,
Mahesh.M.R

Hi
I am having the exact same problem (i think). I believe that the problem is caused by a failed connection to the SLD.
In my case, if I scroll the bottom of the error page, the 'Detailed exception chain' has the error:
TypeBroker failed to access SLD: Error while obtaining JCO connection.
The same error can be found in the DefaultTrace.
This ESS is on a nw2004s sandbox portal (trying to reach an ECC 6.0 sandbox), but being lazy I just reused the SLD in my Development environment.
This is however a Java WAS 6.40 and according to Note 954820 (Compatibility of SLD in the system landscape)
QUOTE
In general, the connection of systems to the SLD is released for SLD client applications with releases earlier than or equal to the SLD release (to be more precise: the AS Java release on which the SLD runs). Within a release, all Support Packages are released.
UNQUOTE
So, i'll try activating the SLD on a nw2004s JAVA WAS and use that instead.
Regards
Stig

RFC Adaptive model in web dynpro application gives mandatory parameter erro

Hi,
I need to check when we create model to call bapi from backend, are there any checks for the input data which are done by the model before the bapi is called ?
I am passing some input parameters and I get the following error on the screen. and the return structure is empty.
Mandatory parameter BFLUSHDATAGEN of method BAPI_REPMANCONF_CREATE_MTS missing
But if I pass the very same paramters directly in se37 transaction to the bapi, then this error is not seen. it gives some other error in return structure.
There fore I have a doubt is there any check which doesnt call the bapi at all if it doesnt find the parameters it is looking for. I know the paremeters are not correct but I expect to see the same error what is seen in se37 in the return structure of my modal context element.
thanks in advance for help.
r

hi, I have corrected my code and written the below code inthe controllers init method.
Bapi_Repmanconf_Create_Mts_Input parent = new Bapi_Repmanconf_Create_Mts_Input();
wdContext.nodeBapi_Repmanconf_Create_Mts_Input().bind(parent);
Bapi_Rm_Datgen input1 = new Bapi_Rm_Datgen();
wdContext.nodeBflushdatagen().bind(input1);
input1.setMaterialnr("100-400");
input1.setPdc_Number("100066");
parent.setBflushdatagen(input1);
Even this I getmandatory paramter missing eror
kindly help
Edited by: rita c on Nov 6, 2008 6:29 PM

Jco.JCO$Exception when create a new adaptive model in NWDS

HI friends:
when I create a new adaptive model in NWDS, error occurs:
Warning:Creating a connection with Metamodel language <zh_CN> failed. Continuing with language <zh>
Fatal: com.sap.mw.jco.JCO$Exception: Missing R3NAME=... or ASHOST=... in connect_param in RfcOpenEx
but when I used a existent model to reimport model , it has no error
Thank you in advance.
Yonk
Edited by: Yonk King on Nov 7, 2008 11:11 AM

Check whether you are providing the correct login credentials while importing the RFC.

Error when trying to create a JCO Destination

Hi
I receives the following error when trying to creat a JCO Destination, clicking on the button in the host:port/webdynpro/dispatcher/sap.com/tcwdtools/Explorer
I get the following error:
Error stacktrace:
java.lang.NullPointerException
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:880)
     at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:272)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:237)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)
     at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:223)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:274)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:555)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
     at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:620)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:263)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:740)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:350)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:640)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
     at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:391)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:265)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     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)
Any ideas?
Regards
Kay-Arne

Hi,
Have you configured your SLD? Check JCO Destination error out or search for "com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus" in the SDN forums.
Best regards,
Vladimir

Rfc Adapter - commit work and wait

Hi,
Here is my problem:
I'm calling a BAPI specifying 'Commit' in Communication Channel. After this call, in BPM i call another RFC (or BAPI) that needs to modify or use objects created in the first call. The problem is that the work made by the first BAPI wasn't updated in the database yet, and i receive errors in next calls.
Is there anyway to wait for commit?
Jose Neves

Hi again,
Thanks for your attention...
Well i am using the 'WAIT' between Steps... But this is not how i would like to keep things... i can't assume how long i should wait and i don't want to have unneeded pauses during process (each process has about 18 calls to R3!).
The only solution i see everywhere is Wrap Wrap Wrap... unfortunately this implies changing every BAPI to Z...
I know that RFC Adapter uses JCO... I think in JCO you can start a transaction, using an identifier, passing this ID to every BAPI call, and call commit at the end, but i don't see anyway to do this in XI.
Another solution i have heard around, is about using ABAP Proxy... is that true that i can encapsulate many BAPI calls in a proxy, and execute all in the same session? We have some configuration problems, and we are not using ABAP Proxy so we can't try... But if this is the solution...

RFC -File Sync Async bridge RFC Adapter Exception

Hi
I am using sync async bridge to send a response back to rfc.
Although there is no error in sxmb_moni as well as the auditlog shows that the response was sent successfully to rfc.. still the RFC adapter gives the following error with no response sent to RFC..
Error in processing caused by: com.sap.aii.af.rfc.RfcAdapterException: failed to identify XML document:java.lang.Exception: javax.xml.parsers.FactoryConfigurationError: Provider com.sap.engine.lib.jaxp.SAXParserFactoryImpl not found
please help

Solved the problem..
The problem could be due to the following..
1. the response structure was just a single character..while i was sending a whole string..
2. I restarted the server...probably the problem
javax.xml.parsers.FactoryConfigurationError: Provider com.sap.engine.lib.jaxp.SAXParserFactoryImpl not found
system property must have set mismatch for the SAXFactoryImpl.... by deploying modules before in which i was using SAX parser.. may be the i set the system property earlier to other provider dont remember...
Hope this information will be useful to someone in future using Sync/Async bridge

RFC adapter not responding

Hi guys,
We are facing the following problem:
We have a receiver RFC adapter that executes some RFC functions on a SAP R/3 system connected to XI. When the R/3 system is down (e.g. for maintenance reasons) the RFC adapter (communication channel) has a red "error" status in Communication channel monitor (that could not connect to R/3), which is ok. However, when the R/3 system goes up, the RFC communication channel remains in the same error status, irrespective of the fact that the R/3 is now up. Morever, it needs some manual stop and start from CC monitor in order to be able to "see" that the R/3 is now up. This has an impact on our interfaces that it may be the case that sometimes the administrators, fail to notice this and the corresponding interfaces that make us of the RFC adapter, fail for no reason.
Is there a way to avoid this undesirable situation?
Best Regards
Evaggelos Gkatzios

Hi Gkatzios,
we also facing same problem as your,,when the R3 system is down for some maintenance reason at the same time XI expects something from R3 ,in this situation RFC adapter is going to error state,when R3 is up RFC adapter works fine but CC still shows error status.but some times we have to stop and start CC manually.
everytime when we open the CC monitoring particular CC always in error state eventhough it is working fine..
If you find any solution for this please let me know.
Thanks for your time.
Regards
Rao

How to Maintain Jco Destinations ( using ARFC2 )

Hi Friends
I call ARFC2 setting WD_MODELDATA_DEST and WD_RFC_METADATA_DEST.
... then get error message.
com.sap.conn.jco.JCoException: (106) JCO_ERROR_RESOURCE: Destination WD_RFC_METADATA_DEST does not exist
 at com.sap.conn.jco.rt.DefaultDestinationManager.update(DefaultDestinationManager.java:195)
 at com.sap.conn.jco.rt.DefaultDestinationManager.searchDestination(DefaultDestinationManager.java:344)
 at com.sap.conn.jco.rt.DefaultDestinationManager.getDestinationInstance(DefaultDestinationManager.java:96)
 at com.sap.conn.jco.JCoDestinationManager.getDestination(JCoDestinationManager.java:61)
 at com.sap.tc.cm.arfc2.metadata.RFMParser.<init>(RFMParser.java:78)
 ... 74 more
I wnat to Maintain the demo01's JCo Destinations, but the page is null.
Where can I create WD_MODELDATA_DEST、WD_RFC_METADATA_DEST.
thx.

Hi BenChen,
You need to create JCO Destination in the SAP Portal >> Content Administration >> Web dynpro >> Maintain Jco Destinations.
If "Create" button not active,then you need to check SLD running or not and SLD data supplier.
Please refer to below documents will helps
[System Landscape Directory Process and JCo Configuration|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0c1d495-048e-2b10-babd-924a136f56b5?quicklink=index&overridelayout=true]
[JCO Destination Errors|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0019b1a-775f-2910-beb8-d81f27d0d8d0?quicklink=index&overridelayout=true]
[How to Configure the JCo Destination Settings|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/user-interface-technology/wd%20java/7.0/portal%20integration/how%20to%20configure%20the%20jco%20destination%20settings.pdf]
Hope it will helps
Regards
Arun Jaiswal

Jco error RFC adapter field PT F not defined

Hi Experts,
I am in a strange situation as I have become clue less on this issue
It is a file to XI to RFC scenario.. runs fine in dev environment
When I change the parameters in teh rfc communication channel to point to QAS it throws
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling Z_TRAX_PO_CHG_IV in remote system (RfcClient[CC_QAS]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Field selection PT F not defined:
There is no such field as PT F and besides the version of the bapi in QAS is in sync with the dev..
pls help me ou ton this
Edited by: Ravindra Teja on Feb 27, 2011 8:45 AM

Hi,
First of all, can you please elaborate what you want?
secondly, why don't you transport your developments to QAS?
Third, what is the reason behind changing the receiver RFC adapter parameter to QAS?
4th, do you want to post data to QAS, if yes, did you transported the RFC to QAS ? Please re import the rfc to your swcv from QAS system.
Please check communication channel if you getting any error?
Regards
Aashish Sinha

Error in Adaptive RFC 2 Model

Hi Expert,
I am developing one webdynpro application in CE 7.1.1 (EHP1).
Created Model and import RFC to model.
I am trying to execute RFC from controller like :
Doc_Allocation nw_Model=new Doc_Allocation();
lock_Input=new Z_Apip_Enqueue_Dequeue_Barcode_Input(nw_Model);
lock_Input.setIv_Flag("4");
lock_Input.setIv_Userid(tl_User.getUniqueName());
lock_Input.setIv_Barcodeid(barcodeid); wdContext.nodeZ_Apip_Enqueue_Dequeue_Barcode_Input().bind(lock_Input); wdContext.currentZ_Apip_Enqueue_Dequeue_Barcode_InputElement().modelObject().execute();
I am getting error for execute method. There is no mehtod to execute RFC.
wdContext.currentZ_Apip_Enqueue_Dequeue_Barcode_InputElement().modelObject().execute();
How to execute RFC without execute method. Please any one provide sample code to execute RFC
This same code is working for Adaptive RFC Model(But this is deprecated in EHP1). I am trying to migrate same application in EHP1.
Regards,
Satya.

Hi Ayyapparaj,
Thanks for replying...
If i create new application in EHP1 IDE it is working fine.. no problem...
But I am trying to migrate applications which are developed in CE 7.1 SP5 to EHP1, i am getting this type of errors. In ".wdmodel" file of model it is showing Adaptive RFC2, but i am getting error in code(for execute()).
<Core.Reference package="com.sap.tc.cm.arfc2.modeltype" name="AdaptiveRFC2" type="ModelType" path="ModelSettingDefinition:connectionScope"/>
in Error Log of webdynpro application :
com.sap.tc.cm.arfc2.gci.ARFC2TypedModelClass cannot be resolved to a type
How to resolve this problem..
Regards,
Satya
Edited by: Satya on Dec 19, 2008 4:57 PM

RFC Adaptive Model,JCO destinations error

Similar Messages

Maybe you are looking for