JCo RFC from a UTF-8 System to an MDMP SAP System

We have a non-SAP-based application which is using the JCo to connect to and interact with an SAP system. Today the non-SAP system is using the "Latin-1" and "Shift-JIS" code pages and the SAP system is also using the corresponding SAP code pages/languages in an MDMP mode. The non-SAP system is proposing to move its application, content, etc to a "Unicode" system based on UTF-8. I suspect SAP won't like that code page difference across the JCo. The non-SAP app is calling RFC-enable function modules, of course. Is there something that can be done to ensure the text is properly transmitted, captured, and stored in SAP?

Mick,
You have to ensure the function modules is in SAP if RFC enabled before you can calling it from outside SAP system. There are 2 types of connectors that you can use to achieve connection from non-SAP system.
DotNet Connection and Java Connection where the later is still supported by SAP on ongoing basis. You may refer here for the guide.
http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5c6a85b11d6b28500508b5d5211/content.htm
Cheers,
Andrew

Similar Messages

Procedure to call an RFC from another R/3 system

Hi ,
I am new to RFC, how can we do the following steps:
1.      Run a routine in Dev environment which calls an RFC which is in testing
2.      The RFC performs the task as written in it
3.      RFC passes the result to routine in Dev and
4.      We display the return in the end in Dev.
Do i need any authorization for that?
Regards,
Pooja

Hi,
I wanted to know how to call an RFC from one R/3 system to another R/3 system .
And what settings should be made to do a RFC in T code SM59?
what does the function module RFC_READ_REPORT do? Can i call any program through this?(As the documentation is not available I am not able to understand the functionality of this Function module)
Regards,
Pooja

Import RFCs from 3.1i system - Required authorisations

Hi,
I am trying to import some RFCs from a 3.1i system
However, I am getting the following error in XI when I try this :
Logon failed: You are not authorized to logon to the target system.
Can anyone tell me a list of all the authorisations required bearing in mind this is a 3.1i system so the XI roles will not exist as standard.
Cheers
Colin.

hi Colin,
the user which will be used to import the metadata
needs to have:
auth to these groups :
As of 3.1H
RFC1, SG00, SRFC, SUNI, SYST
from:
Authorizations to Read Metadata on
http://help.sap.com/saphelp_nw04/helpdata/en/25/76cd3bae738826e10000000a11402f/content.htm
XI roles have nothing to do with that
as you're using user in the r3 system and not the XI
Regards,
michal

Calling JCO RFC Server program from JCO RFC client

Hi,
I have an RFC registered server program which implements JCO.Server. It seems to be working fine, when called from SAP.
For testing purposes, I was trying to write a JCO client program which would take the place of the SAP client.
This program opens a connection to the RFC server and executes a function e.g.
JCO.Client client = JCO.createClient("xx.yy.com", "sapgw35", "MYPROGID");
client.connect();
client.execute(function);
The RFC server program receives the call fine, when I test with a simple function which has no table parameters. However when I tried a more complex function with table parameters, I get an serverExceptionOccurred from the RFC server program:
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: connection closed without message (CM_NO_DATA_RECEIVED)
    at com.sap.mw.jco.rfc.MiddlewareRFC$Server.nativeListen(Native Method)
    at com.sap.mw.jco.rfc.MiddlewareRFC$Server.listen(MiddlewareRFC.java:1368)
    at com.sap.mw.jco.JCO$Server.listen(JCO.java:6805)
I have tried to initialize the repositories in both server and client programs correctly, so that the function is in the cached function list and the table structures in the cached structures list before the function is invoked. But I am not sure if there is still something I am missing, so any ideas would be welcome.
Thanks,
Richard

JCO example 5 is a very good one for server side programming.
try the example,somethings you 'd better make clear.
1) JCO.server
2) repositories--data mapping
3) parameters: export import,table...
further topic:
1) JCO pool
2) tRFC,qRFC
After you have success in Client side programming,try example 5.
Regards

JCO RFC Provider problem

Hi!
We are having some problems in 2 PI 7.1 SP7 Development and Project
systems. Both have the same problem... We cannot see JCO RFC Provider
connections and we cannot create new JCO RFC connections.
Our Project system is copy of development and JCO connections are being
registered on Development causing some problems in proxy connections.
the problem is that we cannot change the JCO RFC connections on both
systems.
If I try to create a new JCO RFC Connection or even a dummy JCO connection it gives the error "The Program ID already exists. Type in an other name."
These systems are a SAP PI 7.1 upgrade from SAP XI 3.0. In version XI 3.0 the connections were OK.
In quality Assurance and Production we don't have this problem.
I've applied the latest AS Java patches but didn't changed the strange behaviour.
Have any one notice

In the default trace file we've found something like
"com.sap.engine.services.jmx.exception.JmxSecurityException: Caller <(>
<<)>some generated user id> not authorized, required permission missing"activate the UME super user, delete the deleted users, deactivate the UME super user and restart the system.
For further information you should see note 1261071

Error while importing an RFC from R/3

Hello,
I am getting the following error while importing an RFC from an R/3 system in the Repository:
***Ready for import***
Import started...
/XXX/YYY_CREATE_NOTIFICATION:
+ com.sap.aii.ibrep.sbeans.upload.RemoteUploadException: PERMISSION_ERROR
Import failed with 1 error
Does any one know what is required? Is it missign authorizations on the R/3 side or on the XI side?
Thank you,
Sumant.

Hi,
please check your User (used for importing RFC) authorizations,
it should have RFC authorization .
Thanks,
Madhav
Note: Points If Useful.

Third party system (JCO) ---RFC--- PI ---RFC--- ECC

Hello all,
We are trying to implement the following scenario:
Third party system (JCO) -RFC-> PI -RFC-> SAP ECC
The third party system connect to PI via Java Connector API with a know user id in PI. After that third party system tries to obtain the RFC that is already implemented and remote enabled in SAP ECC environment. But at this step there is something wrong in third party system software because we are not able to obtain the RFC interface and metadata from PI repository.
1. This step is working correctly. Connection is OK.
            JCO.Client mConnectionPI = JCO.createClient("100", // SAP client
                                                                                "user_id", // userid
                                                                                "********", // password
                                                                                "pt", // language
                                                                                "10.x.x.x", // application server host name
                                                                                "01"); // system number
            mConnectionPI.connect();
2. This step is not working correctly:
            JCO.Repository repository = new JCO.Repository("TestRep", mConnectionPI);
            IFunctionTemplate ftemplate = repository.getFunctionTemplate("Z_RFC_XXX"); - not found exception
We would like to know if there is something missing in any environment that we have to configure or implement in order to fix this issue. Thanks a lot.

Hi Primini,
couple of stupid-but-necessary questions:
1) have you imported the RFC model in PI Repository?
You don't need to have the RFC metadata in PI ABAP stack (there is no point in doing that), but rather in the PI Repository/ESR, within the SWCV you've created.
Check the "Activities" session of this link for more details:
http://help.sap.com/saphelp_nw70ehp2/helpdata/en/2b/a48f3c685bc358e10000000a11405a/frameset.htm
2) if you have done 1), have you configured the RFC Sender scenario properly?
I mean, have you ran the configuration wizard to create the agreements & determinations, setting the RFC interface as both the sender and the receiver interface? Of course, the systems would be different: as the sender system, you'll have a Business Service representing the legacy/JCo system; as the receiver, you'll have the ERP Business System.
This should make your scenario work.
If it doesn't, try one more thing: in the JCo code, just for the metadata repository connection, use a connection to the ERP system. But for the actual call, use the PI system.
Let us know the results.
Best regards,
Henrique.

JCO RFC Provider: "Bean not found" when calling EJB from ABAP via RFC

Hello,
I'm having trouble calling an EJB in a CE 7.1 system from ABAP via RFC. I'm trying to use the JCO RFC Provider service, which mean that I want to expose an EJB so that it can be called via Remote Function Call.
I have documented everything, including the code and the deployment descriptors I wrote, in this thread in the CE forum: Jco RFC Provider: Bean not found
If there's any chance you can help, please do me a favour and look into the problem.
Thanks a lot!
Thorsten

Hi Vladimir,
Thank you very much, your help was immensely valuable.
I just had to add the function declaration to the Home Component interface, everything else was correct, and now it works.
Cheers,
Thorsten

How to debug a RFC function module remotely from another R/3 system?

Hi experts,
   I have RFC function module in one R/3 system. I am calling this from another R/3 system that is cross apps (Xapps).
   This function module is Synchronous.
Is it possible to debug this function module from cross apps?
Can somebody give me the steps?
Thanks & Regards
Gopal

Hi Shree,
   Can you explain it bit more?
   Do I have to call the function module with "IN BACKGROUND TASK"?
   Or is it that I have to just put external breakpoint in the function module?
   Please help
Thanks
Gopa

Services in JCo RFC not getting started after Changing the client from 001

Hi SAP Stars,
I have recently Installed Quality and Production servers with PI 7.1 on windows 2003, Sqlserver 2005, when I'm doing Post Activities(http://host:port/nwa) in which I try to change the client from 001 to 300(newly created) in JCo RFC(4 services) and start the service it is throwing error when I again change it to 001 client and start the service it is getting started, Could anyone help me in solving this issue same issue I facing in PI 7.1 Quality and Production
Thanks In Advance
Anil Kumar

Hi Anil,
All these JCo RFCs are client specific RFCs.
Please logon your PI NWA
Choose Configuration Management - Infrastructure- JCo RFC Provider
Then, Select the RFC
Under Details -> Choose Repository Configuraton
Change the client name to 300 (your new client)
Save
And repeat the same for all JCo RFC that you want to work for your newly created client.
Please ensure that you are using SAPJSF user & correct password for all these RFCs.
Ideally, these rfcs shuould work now if now please restart your PI (mostly Java alone also do)
I hope this helps you.
Regards
Sekhar
Edited by: sekhar on Dec 17, 2009 11:39 AM

Sender RFC from Third Party System

I have a vendor who is actually communicating through RFC from third party Application to SAP R/3. Now we are trying have XI in between. Where as with minimal impact on both sides.
Solution.
1. Have the RFC made as ZRFC in XI. Let the vendor call the RFC in XI ABAP and internally make an RFC call through XI Interface to R/3 as Sync Interface. Because we need to report the information back to the system where the request initiated.
2. Have RFC INI file copied as SAP Suggests under one of the folders. Develop the regular RFC to RFC Interface via XI.
Is there any other alternatives other than the above mentioned solutions? Or out of those 2, which one will provide the best performance
Appreciate any feedback. Please advice

That's exactly what we are trying to achieve here. By Eliminating direct connection R/3, we are placing XI in between. But with the budget/timeline constraints from the Partner side, we are trying to have minimal change on the partner side. They might not change something to web service etc...
Here is the text about INI file
You can configure the non-SAP RFC client to connect to the sender communication channel in the following ways:
■ By defining the parameters PROGID, gateway-host, and gateway-service within the saprfc.ini-file using RFC-SDK.
■ By using appropriate parameters in the function RfcOpenEx.
If you use the saprfc.ini-file, the respective RFC destination has to be of type R.
All the parameter values used within the saprfc.ini-file or with the function RfcOpenEx should match the entries maintained within the corresponding sender communication channel.
Example for the saprfc.ini-file is as follows:
DEST=RFCCLIENTEXT
TYPE=R
PROGID=P106646.HKExternalClient
GWHOST=pwdf2153
GWSERV=sapgw40
Please check the following link, for the same text on RFC Sender
[Help.SAP|http://help.sap.com/saphelp_nw04/helpdata/en/67/6d0540ba5ee569e10000000a155106/content.htm]
Using the same Sender RFC for non-SAP System, please share any ideas

Import RFCs from 3.1i system - Error in SAP MetaDataInterface

Hi,
Trying to import some RFCs from a SAP R/3 3.1i system.
However, getting an error in XI :
Error in SAP MetaDataInterface: java.lang.NullPointerException
#7 10:23:59 [AWT-EventQueue-0] ERROR com.sap.aii.utilxi.swing.toolkit.ExceptionDialog: Throwable
Thrown:
MESSAGE ID: com.sap.aii.upload.sap.rb_exception.MDI_ERROR
com.sap.aii.ibrep.sbeans.upload.RemoteUploadException: Error in SAP MetaDataInterface: java.lang.NullPointerException
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceBean.openSAPSource(UploadServiceBean.java:79)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceRemoteObjectImpl0.openSAPSource(UploadServiceRemoteObjectImpl0.java:240)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceRemoteObjectImpl0p4_Skel.dispatch(UploadServiceRemoteObjectImpl0p4_Skel.java:196)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Serialized server exceptions:
MESSAGE ID: com.sap.aii.upload.sap.rb_exception.MDI_ERROR (serialized)
com.sap.aii.upload.sap.SAPConnectionException$MDIError: Error in SAP MetaDataInterface: java.lang.NullPointerException
     at com.sap.aii.upload.sap.SAPUploadSource.init(SAPUploadSource.java:187)
     at com.sap.aii.upload.sap.SAPUploadSource.<init>(SAPUploadSource.java:152)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceBean.connect(UploadServiceBean.java:87)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceBean.openSAPSource(UploadServiceBean.java:73)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceRemoteObjectImpl0.openSAPSource(UploadServiceRemoteObjectImpl0.java:240)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceRemoteObjectImpl0p4_Skel.dispatch(UploadServiceRemoteObjectImpl0p4_Skel.java:196)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
MESSAGE ID: com.sap.mdi.ObjectFactoryException (serialized)
com.sap.mdi.ObjectFactoryException: java.lang.NullPointerException
     at com.sap.mdi.ObjectFactory.setConnection(ObjectFactory.java:5145)
     at com.sap.mdi.ObjectFactory.<init>(ObjectFactory.java:3137)
     at com.sap.aii.upload.sap.SAPUploadSource.init(SAPUploadSource.java:181)
     at com.sap.aii.upload.sap.SAPUploadSource.<init>(SAPUploadSource.java:152)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceBean.connect(UploadServiceBean.java:87)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceBean.openSAPSource(UploadServiceBean.java:73)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceRemoteObjectImpl0.openSAPSource(UploadServiceRemoteObjectImpl0.java:240)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceRemoteObjectImpl0p4_Skel.dispatch(UploadServiceRemoteObjectImpl0p4_Skel.java:196)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#6 10:23:59 [Pool-Thread-4] ERROR com.sap.aii.ibrep.gui.tools.r3import.SAPNavigationPane: Connection failed
Thrown:
MESSAGE ID: com.sap.aii.upload.sap.rb_exception.MDI_ERROR
com.sap.aii.ibrep.sbeans.upload.RemoteUploadException: Error in SAP MetaDataInterface: java.lang.NullPointerException
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceBean.openSAPSource(UploadServiceBean.java:79)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceRemoteObjectImpl0.openSAPSource(UploadServiceRemoteObjectImpl0.java:240)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceRemoteObjectImpl0p4_Skel.dispatch(UploadServiceRemoteObjectImpl0p4_Skel.java:196)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Serialized server exceptions:
MESSAGE ID: com.sap.aii.upload.sap.rb_exception.MDI_ERROR (serialized)
com.sap.aii.upload.sap.SAPConnectionException$MDIError: Error in SAP MetaDataInterface: java.lang.NullPointerException
     at com.sap.aii.upload.sap.SAPUploadSource.init(SAPUploadSource.java:187)
     at com.sap.aii.upload.sap.SAPUploadSource.<init>(SAPUploadSource.java:152)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceBean.connect(UploadServiceBean.java:87)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceBean.openSAPSource(UploadServiceBean.java:73)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceRemoteObjectImpl0.openSAPSource(UploadServiceRemoteObjectImpl0.java:240)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceRemoteObjectImpl0p4_Skel.dispatch(UploadServiceRemoteObjectImpl0p4_Skel.java:196)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
MESSAGE ID: com.sap.mdi.ObjectFactoryException (serialized)
com.sap.mdi.ObjectFactoryException: java.lang.NullPointerException
     at com.sap.mdi.ObjectFactory.setConnection(ObjectFactory.java:5145)
     at com.sap.mdi.ObjectFactory.<init>(ObjectFactory.java:3137)
     at com.sap.aii.upload.sap.SAPUploadSource.init(SAPUploadSource.java:181)
     at com.sap.aii.upload.sap.SAPUploadSource.<init>(SAPUploadSource.java:152)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceBean.connect(UploadServiceBean.java:87)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceBean.openSAPSource(UploadServiceBean.java:73)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceRemoteObjectImpl0.openSAPSource(UploadServiceRemoteObjectImpl0.java:240)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceRemoteObjectImpl0p4_Skel.dispatch(UploadServiceRemoteObjectImpl0p4_Skel.java:196)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#5 10:19:57 [AWT-EventQueue-0] ERROR com.sap.aii.utilxi.swing.toolkit.ExceptionDialog: Throwable
Thrown:
MESSAGE ID: com.sap.aii.upload.sap.rb_exception.MDI_ERROR
com.sap.aii.ibrep.sbeans.upload.RemoteUploadException: Error in SAP MetaDataInterface: java.lang.NullPointerException
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceBean.openSAPSource(UploadServiceBean.java:79)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceRemoteObjectImpl0.openSAPSource(UploadServiceRemoteObjectImpl0.java:240)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceRemoteObjectImpl0p4_Skel.dispatch(UploadServiceRemoteObjectImpl0p4_Skel.java:196)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Serialized server exceptions:
MESSAGE ID: com.sap.aii.upload.sap.rb_exception.MDI_ERROR (serialized)
com.sap.aii.upload.sap.SAPConnectionException$MDIError: Error in SAP MetaDataInterface: java.lang.NullPointerException
     at com.sap.aii.upload.sap.SAPUploadSource.init(SAPUploadSource.java:187)
     at com.sap.aii.upload.sap.SAPUploadSource.<init>(SAPUploadSource.java:152)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceBean.connect(UploadServiceBean.java:87)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceBean.openSAPSource(UploadServiceBean.java:73)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceRemoteObjectImpl0.openSAPSource(UploadServiceRemoteObjectImpl0.java:240)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceRemoteObjectImpl0p4_Skel.dispatch(UploadServiceRemoteObjectImpl0p4_Skel.java:196)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
MESSAGE ID: com.sap.mdi.ObjectFactoryException (serialized)
com.sap.mdi.ObjectFactoryException: java.lang.NullPointerException
     at com.sap.mdi.ObjectFactory.setConnection(ObjectFactory.java:5145)
     at com.sap.mdi.ObjectFactory.<init>(ObjectFactory.java:3137)
     at com.sap.aii.upload.sap.SAPUploadSource.init(SAPUploadSource.java:181)
     at com.sap.aii.upload.sap.SAPUploadSource.<init>(SAPUploadSource.java:152)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceBean.connect(UploadServiceBean.java:87)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceBean.openSAPSource(UploadServiceBean.java:73)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceRemoteObjectImpl0.openSAPSource(UploadServiceRemoteObjectImpl0.java:240)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceRemoteObjectImpl0p4_Skel.dispatch(UploadServiceRemoteObjectImpl0p4_Skel.java:196)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#4 10:19:57 [Pool-Thread-5] ERROR com.sap.aii.ibrep.gui.tools.r3import.SAPNavigationPane: Connection failed
Thrown:
MESSAGE ID: com.sap.aii.upload.sap.rb_exception.MDI_ERROR
com.sap.aii.ibrep.sbeans.upload.RemoteUploadException: Error in SAP MetaDataInterface: java.lang.NullPointerException
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceBean.openSAPSource(UploadServiceBean.java:79)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceRemoteObjectImpl0.openSAPSource(UploadServiceRemoteObjectImpl0.java:240)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceRemoteObjectImpl0p4_Skel.dispatch(UploadServiceRemoteObjectImpl0p4_Skel.java:196)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Serialized server exceptions:
MESSAGE ID: com.sap.aii.upload.sap.rb_exception.MDI_ERROR (serialized)
com.sap.aii.upload.sap.SAPConnectionException$MDIError: Error in SAP MetaDataInterface: java.lang.NullPointerException
     at com.sap.aii.upload.sap.SAPUploadSource.init(SAPUploadSource.java:187)
     at com.sap.aii.upload.sap.SAPUploadSource.<init>(SAPUploadSource.java:152)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceBean.connect(UploadServiceBean.java:87)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceBean.openSAPSource(UploadServiceBean.java:73)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceRemoteObjectImpl0.openSAPSource(UploadServiceRemoteObjectImpl0.java:240)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceRemoteObjectImpl0p4_Skel.dispatch(UploadServiceRemoteObjectImpl0p4_Skel.java:196)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
MESSAGE ID: com.sap.mdi.ObjectFactoryException (serialized)
com.sap.mdi.ObjectFactoryException: java.lang.NullPointerException
     at com.sap.mdi.ObjectFactory.setConnection(ObjectFactory.java:5145)
     at com.sap.mdi.ObjectFactory.<init>(ObjectFactory.java:3137)
     at com.sap.aii.upload.sap.SAPUploadSource.init(SAPUploadSource.java:181)
     at com.sap.aii.upload.sap.SAPUploadSource.<init>(SAPUploadSource.java:152)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceBean.connect(UploadServiceBean.java:87)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceBean.openSAPSource(UploadServiceBean.java:73)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceRemoteObjectImpl0.openSAPSource(UploadServiceRemoteObjectImpl0.java:240)
     at com.sap.aii.ibrep.sbeans.upload.UploadServiceRemoteObjectImpl0p4_Skel.dispatch(UploadServiceRemoteObjectImpl0p4_Skel.java:196)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#3 10:15:36 [AWT-EventQueue-0] FINE AutoLog.created.com.sap.aii.ib.core.service.TypeNotRegisteredException: com.sap.aii.ib.core.service.TypeNotRegisteredException: Type "TypeConntestObj" is not registered in the service class Type Service - Type Information
     at com.sap.aii.ib.core.service.ServiceBase.getServiceImpl(ServiceBase.java:71)
     at com.sap.aii.ib.bom.gen.TypeServiceImpl.getTypeInformation(TypeServiceImpl.java:82)
     at com.sap.aii.ib.gui.xiitem.services.InternalXiItemService.getTypeInfo(InternalXiItemService.java:23)
     at com.sap.aii.ib.gui.xiitem.services.InternalXiItemService.createEmptyXiItem(InternalXiItemService.java:92)
     at com.sap.aii.ib.gui.xiitem.services.XiItemServiceProvider.createEmptyXiItem(XiItemServiceProvider.java:97)
     at com.sap.aii.ib.gui.xiitem.InternalXiItemServiceForNameNamespaceObjects.addType(InternalXiItemServiceForNameNamespaceObjects.java:68)
     at com.sap.aii.ib.gui.xiitem.InternalXiItemServiceForNameNamespaceObjects.<init>(InternalXiItemServiceForNameNamespaceObjects.java:55)
     at com.sap.aii.ib.gui.applcomp.StartupCodeEntry.guiStartup(StartupCodeEntry.java:151)
     at com.sap.aii.ib.gui.applcomp.StartupCodeEntry.startup(StartupCodeEntry.java:108)
     at com.sap.aii.ib.core.applcomp.IStartupCodeEntry.startupIfNotAlreadyDone(IStartupCodeEntry.java:33)
     at com.sap.aii.ibrep.gui.applcomp.StartupCodeEntry.startup(StartupCodeEntry.java:68)
     at com.sap.aii.ib.core.applcomp.IStartupCodeEntry.startupIfNotAlreadyDone(IStartupCodeEntry.java:33)
     at com.sap.aii.ib.core.applcomp.ExplicitApplicationComponentImpl.startup(ExplicitApplicationComponentImpl.java:116)
     at com.sap.aii.ib.core.applcomp.ExplicitApplicationComponents.startup(ExplicitApplicationComponents.java:383)
     at com.sap.aii.ib.core.applcomp.ApplicationComponent.startup(ApplicationComponent.java:209)
     at com.sap.aii.ib.gui.login.SplashLoginFrame$6.run(SplashLoginFrame.java:429)
     at java.awt.event.InvocationEvent.dispatch(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)
#2 10:15:36 [AWT-EventQueue-0] DEBUG AutoLog.created.com.sap.aii.ib.core.service.TypeNotRegisteredException: Type "TypeConntestObj" is not registered in the service class Type Service - Type Information
#1 10:15:36 [AWT-EventQueue-0] FINE AutoLog.created.com.sap.aii.ib.core.service.TypeNotRegisteredException: com.sap.aii.ib.core.service.TypeNotRegisteredException: Type "versConflList" is not registered in the service class Type Service - Type Information
     at com.sap.aii.ib.core.service.ServiceBase.getServiceImpl(ServiceBase.java:71)
     at com.sap.aii.ib.bom.gen.TypeServiceImpl.getTypeInformation(TypeServiceImpl.java:82)
     at com.sap.aii.ib.gui.xiitem.services.InternalXiItemService.getTypeInfo(InternalXiItemService.java:23)
     at com.sap.aii.ib.gui.xiitem.services.InternalXiItemServiceBase.<init>(InternalXiItemServiceBase.java:44)
     at com.sap.aii.ib.gui.xiitem.CommonInternalXiItemService$ForVersionConflictList.<init>(CommonInternalXiItemService.java:326)
     at com.sap.aii.ib.gui.applcomp.StartupCodeEntry.guiStartup(StartupCodeEntry.java:147)
     at com.sap.aii.ib.gui.applcomp.StartupCodeEntry.startup(StartupCodeEntry.java:108)
     at com.sap.aii.ib.core.applcomp.IStartupCodeEntry.startupIfNotAlreadyDone(IStartupCodeEntry.java:33)
     at com.sap.aii.ibrep.gui.applcomp.StartupCodeEntry.startup(StartupCodeEntry.java:68)
     at com.sap.aii.ib.core.applcomp.IStartupCodeEntry.startupIfNotAlreadyDone(IStartupCodeEntry.java:33)
     at com.sap.aii.ib.core.applcomp.ExplicitApplicationComponentImpl.startup(ExplicitApplicationComponentImpl.java:116)
     at com.sap.aii.ib.core.applcomp.ExplicitApplicationComponents.startup(ExplicitApplicationComponents.java:383)
     at com.sap.aii.ib.core.applcomp.ApplicationComponent.startup(ApplicationComponent.java:209)
     at com.sap.aii.ib.gui.login.SplashLoginFrame$6.run(SplashLoginFrame.java:429)
     at java.awt.event.InvocationEvent.dispatch(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)
#0 10:15:36 [AWT-EventQueue-0] DEBUG AutoLog.created.com.sap.aii.ib.core.service.TypeNotRegisteredException: Type "versConflList" is not registered in the service class Type Service - Type Information
Any ideas ?
Kind regards
Colin.

Hi Colin,
Check this thread..
Re: Support of RFC and IDOC adapters
Regards
Anand

How to call the RFC from XI system

Dear Friends,
My requirement is RFC to RFC scenario i.e SAP to XI to Third party system.
I have the BAPI_EUQI_CREATE rfc, this RFC is available in ECCsystem, that RFC I imported in XI system, so third party system how to call this RFC.
please give me the suggestion it is very helpful.
Regards,
Shalini Shah

Hi Shalini,
You have create a RFC in the 3rd party system and import that RFC in XI System using 3rd party adapter.Do the necessary mapping and configure the sender RFC Adapter and at receiver side configure 3rd paty Adapter.
The 3rd party adapters must be installed via Deploy Tool or JSPM. But u should have a sda file with the adpater content.
see here for more details on JSPM
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5006901f-925c-2910-5f98-9ae26cc07eca
For more info:
If you still want to do it,
1. Import the RFCs of sender and of receiver.
2. Do the necessary mapping.
3. Configure sender and receiver RFC adapters.
Before that check if you have RFC destination for the RFC adapter. If not You should establish it. To establish an RFC destination for the RFC adapter.
1. Call the transaction Display and Maintain RFC Destinations (SM59).
2. Select an existing RFC destination of type ABAP Connections (for example, ABAP_Old) by double-clicking it.
3. Choose Destination ® Copy and copy the RFC destination using a new name (for example, ABAP_New).
4. Save the new RFC destination (ABAP_New) and delete the old RFC destination (ABAP_Old).
5. Create a new RFC destination (for example, RFC_Adapter) of type T (TCP/IP connection) as the RFC destination for the RFC adapter.
6. Select the registration type Registered Server Program and in the Program ID field enter the corresponding program ID from the configuration of the sender RFC adapter.
7. In the Gateway host and Gateway service fields, enter the gateway host and gateway service from the configuration of the sender RFC adapter.
8. If the sender system is a Unicode system, define the RFC destination as Unicode.
9. Using the name of the old ABAP connection (ABAP_Old), create a new RFC destination of type L (logical destination with reference entry).
10. In the Reference Entry field enter the RFC destination (RFC_Adapter) for the RFC adapter.
For more details take a look at this link. http://help.sap.com/saphelp_nw70/helpdata/en/25/76cd3bae738826e10000000a11402f/content.htm
Dont forget to Reward points if this helps
Regards
Pragathi.
Edited by: Pragathi on May 24, 2008 7:21 AM

Import RFC from SAP System to XI

Hi
It is taking more time ( 5 to 10 mins) to list the RFC from SAPsystem ,When i try to Import RFC from SAP System to XI.
Please let me know your ideas on the same
Regards
Madhan D

Hi,
Could you pls check the following sap notes..
SAP Notes 718320,767091 and 212011 for a better idea on difference in performance while extracting data from R/3 backend.
Regards,
Madhu

PI System Copy (JCO RFC destinations missing)

Hi,
We are doing a Homogeneous System Copy of a PI 7.0 system:
- Source system --> PI 7.0 Production system ("PIP")
- Destination system --> PI 7.0 Development system ("PID")
We are executing the specific POST activities for a PI system (point 5.2.3.2.4 in the "System Copy for NW2004s SR2 Abap+Java" guide). In point 5.2.3.2.4.2, PI RFC destinations must be adapted in both Abap (SM59) and Java (Visual Administrator, JCO RFC Provider). The problem is that in all PI abap RFC destinations (AI_RUNTIME_JCOSERVER etc) the program_id is pointing to our PI
Production system ("AI_RUNTIME_PIP"), is it OK?
Besides, in Visual Administrator (JCO RFC Provider service), all the required RFC listeners for PI ("AI_DIRECTORY_PIP", "AI_RUNTIME_PIP", etc.) are missing after the system copy (???). Must these RFC listeners be manually created? How can we do it? Must we create them with the development SID ("AI_RUNTIME_PID") or with the production SID ("AI_RUNTIME_PIP")? Perhaps PI configuration wizard must be executed after the system copy of a PI system so that these JCO RFC destinations are created, but we are afraid executing the wizard could harm the PI configuration...
Thanks in advance.
Jon Larrucea

Hi Jon
Probably the best thing to do is just create these destinations manually. You will need to do this in SM59 and the Visual Administrator. See the link below:
Creating RFC Destinations in the ABAP and Java Environments
http://help.sap.com/saphelp_nw70/helpdata/en/be/6e0f41218ff023e10000000a155106/content.htm
Regards
Mark

JCo RFC from a UTF-8 System to an MDMP SAP System

Similar Messages

Maybe you are looking for