Import RFC/IDOC error

Hi all,
I am following "How to...push data in to BW from XI."
In the 5th step in the document it is given
Choose "Import RFC/IDOC" in the context menu of "Imported Objects" and enter your user data to logon to the BW system.
Select the function module /BIO/Q16ASENDXMLDATATOBW_RFC
Press "continue"
Press "Start"
But when I do this I am getting a java nullpointer exception error com.sap.aii.ibrep.sbeans.upload.remoteuploadexception:jsva.lang.nullpointerexception
I am using jre1.4.2_10 and java web start version 1.4.2
Please help me in resolving this issue.
Regards,
Aanand

Hi Anand,
Can you pls make sure that no other users have this same RFC imported into your XI integration builder and is waiting to get their change list activated. In that case also we get the error in importing...
check these links also.
Error importing RFC / idoc despite following note 769356
Cheers
JK

Similar Messages

Error importing RFC / idoc despite following note 769356

We have been experiencing a number of problems where we cannot import RFC / idocs in the integration repository. The BASIS team have followed note 769356 and originally this solved the problem but meant that we reverted back to old screens in the Integration Builder and some German texts in the Integration Repository.
Current patch version is Support Stack 4
To get to this point the following steps were followed:
Undeployed com.sap.xi.repository
Deployed the install version of com.sap.xi.repository.
In order to correct the problems with the incorrect screens etc.. The following steps were carried out:
Undeployed com.sap.xi.repository
Deployed the Support Stack 4 version of XITOOLS (includes com.sap.xi.repository)
Applied Support Stack 5 for the Abap kernel
Applied SAPXIAFC04P_1-20000272 and SAPXITOOL04P_1-20000274 via SDM
This fixed all of the problems with German texts etc.. but now we cannot import RFC / idocs again. In the Java Web Start Log (attached) we still get the error message
mentioned in note 769356. We have deleted the Web Start Cache on the client hosts (several restarts of the machine and deletions of the cache). The BASIS guys are going to undeploy and redeploy the repository again but failing that we are running out of ideas.
Does anyone have any suggestions?
Here is the entry in the log file:
java.lang.AbstractMethodError: com.sap.aii.ibrep.sbeans.upload.UploadServiceRemote_Stub.openSAPSource(Lcom/sap/aii/utilxi/misc/r3Connect/SAPConnectionData;Lcom/sap/aii/utilxi/misc/r3Connect/SAPLoginData;Lcom/sap/aii/ib/bom/gen/VersionContext;)Lcom/sap/aii/ibrep/sbeans/upload/SourceID;at com.sap.aii.ibrep.clsif.upload.RemoteUploadClient$ConnectionImpl.connectBean(RemoteUploadClient.java:107)at com.sap.aii.ibrep.clsif.upload.RemoteUploadClient$ConnectionImpl.<init>(RemoteUploadClient.java:91)at com.sap.aii.ibrep.clsif.upload.RemoteUploadClient.getSAPUploadConnection(RemoteUploadClient.java:66)at com.sap.aii.ibrep.gui.tools.r3import.wizard.SAPLogonPage.connect(SAPLogonPage.java:94)at com.sap.aii.ibrep.gui.tools.r3import.wizard.R3ImportWizard$LoginTask.run(R3ImportWizard.java:456)at com.sap.aii.utilxi.misc.thread.ThreadPool$ThreadPoolThread.run(ThreadPool.java:321)

Dan,
you are almost there!
If you religiously follow note 769356, you should not have this problem.
Just do the following as the note suggests:
- From SDM, undeploy only the com.sap.xi.repository
- Unzip SAPXITOOL04P_1-20000274.SCA.zip
- The file ExchangeRepository.sda will be one of the extracted files
- Only import the ExchangeRepository.sda. Do not import the entire ZIP package.
- Restart the J2EE engine.
- Delete Webstart Cache
- From the XI admin page:
http://XIhost:50000/rep/support/admin/status.html
Re-Initialize the Jars for resigning.
- Wait for 5 minutes for the jar signing to finish. Sometimes, the jar signing gets interrupted, you have to let it finish.
The above steps worked for me.
thanks,
Manish

Problem importing RFC/IDOC

Hi All,
While importing RFC/IDOC, there are 3 steps
1. Logon
2. Choose Objects
3. Execute imports
After giving the reqd info in logon, I can go to the next step, but here when I click on RFC or IDOC, I am not able to see the RFCs or IDOCS, IR is not responding, the screen goes blank and I have to close the application(IR).
Any help is appreciated.
Thanks,
Jai Shankar

>>wasn't it 3 that felt like 15 ?
No i guess it is a 15 actually.
>>do you have many Zidoc - ZRFC ?
Yes. This is a IDES system I am connectin to. So lot of them.
Thanks,
Jai Shankar

Can not modify/import RFC/IDoc

After I import design object to IR, I can't import IDoc from SAP system.
there I can not change system, client, information.
Why?

hi
Just double click on the software component and check whether the radio button Import of RFCS and IDOCs interfaces from SAP systems Permitted. Then you give R3 applicaiton server name and the system number as 00 and give your userid and password.
You can also get your R3 applicaiton server name from the SAP logon pad. Open SAP Logon pad select the R3 system which you want to connect and click on Change Item. There your application server name is given. So cross check once again whether this one and the one you are giving are the same. Then proceed further. It should work.
Note: reward points if solution found helpfull
Regards
Chandrakanth.k

RFC destination error while importing a client request

Dear Experts,
We are trying to import a Client Export from our Prd system to Development System and we are unable to import the request as it pops up a RFC destination error.
We have checked the RFC in the Dev QAS and PRD related to TMSADM and all of them are working fine
FYI, We are able to release the transports from the development system and it can be moved till qas and prd . So the TMS Configuration is also good.
The data file and co file in the backend of development is the same size as that of the Prd system.
I am really stuck . Kindly suggest a solution . Please find the screenshots while importing
Regards,
Suratharajan .S

Hi Suratha,
Goto STMS->system overview and select the Communication tab.
Maintained the Instance number of the ASD system.
Once you maintained the instance number , you will able to see it in the RFC ASD.DOMAIN_ASD.
Also distribute the configuration after entering the instance number.
With Regards
Ashutosh Chaturvedi

Error while importing the IDOC

Hi,
When I am Trying to import the Idoc the following error is dispalyed.
Pl go through it and reply me asap.
"**Ready for import**
Import started...
HRMD_A.HRMD_A06:
+ com.sap.aii.ibrep.sbeans.upload.RemoteUploadException: Documentation DE.OBJEKTID | urn:sap-com:document:sap:docu is already locked in another change list by user gopaln
Import failed with 1 error"
Thanks,
Srini

HRMD_A.HRMD_A06:
+ com.sap.aii.ibrep.sbeans.upload.RemoteUploadException: Documentation DE.OBJEKTID | <b>urn:sap-com:document:sap:docu is already locked in another change list by user gopaln</b>
>>> another user is already editing the onject... you will have to ask him to activate his changes. Also make sure the Idoc is released.

Error in importing an idoc

hi friends,
i am new to xi.when importing an idoc say from ecc5 to xi for a file to idoc scenario,I am getting this message-'System ECC is running on the specified application server. However, source system sapecc50 is specified in software component version FILE_TO_IDOC_COMP , 3.0 of sap.com Do you want to disconnect?' - Could anyone help me out.Thanks in advance

hi karthik,
this is just a message.. you can say yes and give the necessary details to connect to the system and import the idoc.
when you double click on your SCV, there is a system that is specified there.. i guess, the idoc you are trying to import is from another. hence, you can give the details of the system you want to import idoc from.

Import of IDOC from R/3 to XI system

Hi All,
I created RFC destination, port and partner profile in R/3 system and RFC destination and Port in XI system and Remote Logon is working on both the systems. Now i want to import an IDOC from R/3 system SAPECC6 to XI system, there i got specify the Application Server, System Number Logon data to the R/3 system, but it give the error like i.e.
"Unable to establish connection to R/3 system SAPECC6 (system=01, client=200) Troubleshooting tips:
Is the target system online?
Check the connection data (note that server names and groups are case-sensitive)
Tips for administrators (see the configuration guide for more details):
Does the user have the required authorizations in the target system?
Is the target system configured correctly in "etc/services"?"
Any body came across this situation, Please send the solution asap.
Thanks & Regards,
Nagarjuna.

Hi nagarjuna,
1 . First check this at your R/3 System.
While logon window, check the
Client No
2 . Second, when you import, you will give the details like application server, system no, user name and password. But you can fine the client no is different at this place.
Please change the settings according to that and move ahead.
This problem happends some times, Its with the configuration.
Hope this will help you.
cheer,
Vinod V
**Reward, if found helpful

Is it Possible to import an IDoc type from R/3 into APO system

Hi Gurus ,
Could you please guide if we can import an IDoc type from R/3 system to APO system ?? If yes , can you please give the guidelines / step - by - step procedure for this.
Thanks in advance ,
Roseline

hi
yes u can export an idoc from r/3 to a legacy system.
the brief outline is as follows:
1. set up an rfc connection. it has to be 'T' type in t-code sm59
configure the saprfc.ini file if on windows based os. if on unix based os configure rfcexec.c to have the login details of apo system.
2.set up logical systems( at least 1 each for r/3 and apo) using T-code SALE.
3.assign clients to the logical sytems using T-code SALE..
4.create ports using tcode we20.
5. create idoc segments using we30 and release.
6. create idoc type using we31.
7. create message type using we81.
8. assign message to idoc using we82.
9.build a customer model using tcode bd64.
10. create an outbound process code usint tcode we41.
it will help if you specify your idoc that you want to use- for vendor, customer and material there are predefined distributions and idocs.
Thanks.

Importing RFC from R/3 3.1i PI 7.0

Hi,
The scenario is picking a file from third party FTP sever and posting an Idoc into SAP R/3 3.1i using PI 7.0. In between we call an RFC from R/3 3.1i from PI 7.0 for converting values. The problem here is, where we tried to import RFC from R/3 3.1i into PI 7.0, its is not allowing to import.It says unauthorized access, even though i had permissions to do that.
1:) Is this a compatible issue?
2:) Can we import RFC from 3.1i into Pi 7.0? Then why i am not able to?
3:) Is there any other way to use that function module in mapping?

Hello
1:) Is this a compatible issue?
- yes
2:) Can we import RFC from 3.1i into Pi 7.0? Then why i am not able to?
- No, this is not supported. The import of RFCs and IDocs is supported from SAP Release 4.0 and higher.
3:) Is there any other way to use that function module in mapping?
- If the RFC is not too complex, just created the objects in the ESR. Or import from a system which is > 4.0.
Check the KBA #1535964 How to import an IDoc/RFC into the ESR, for further details.
Regards
Mark

Inbound IDOC error (Name MARA is not in the namespace for generated BW Metaobjects)

Hi everybody,
we are currently having some issues with importing idocs into our ERP DEV System and i cannot figure out what the problem could be.
I am trying to import an IDOC Type ARTMAS (5) but i keep getting the following error "Name MARA is not in the namespace for generated BW Metaobjects"
The system is a ERP only system with no BI content activated at all.
I don´t find any more errors nor any dumps or SLG1 entries related to this issue.
Did someone already experienced that kind of problem, or do some of you maybe have an idea where to have a deeper look.
thanks & best regards
Peter
EDIT:
Running on ERP 6.0 EHP 7 SPS 4

Hi Ganesh,
I guess there is something wrong with the data in the ODS.
Check this post:
Re: error 18 in the update!
Bye
Dinesh

File to IDOC - Error Inbound -56

Hi,
I am doing file to Idoc. (CREMAS01).. My scenario in
RWB is successful. But in R/3 it is shwoing IDOC
error :"EDI: Partner profile inbound not available".
I created Partner Profile in R/3(logical name of BS-
sender file). Still is shwoing Error.
Regards,
Mukharji
Message was edited by: Mukharji T

Hi Mukharji,
I hereunder give you the step by step procedure for File to IDOC scenario. Cross check whether you have done all these:-
SLD
1) Create a Product/Software Component
2) Technical System pointing to R/3 system
3) Business System for the above technical system
In the Repository
1) Import the Software component created in the sld
2) Create a namespace,
3) import the idoc and then create sender data type/message type etc and mapping
4) Mapping Rules is depends on the requirement
In the Directory
1) Create a Scenario /import the business system
2) Create Receiver/Interface determination
3) Create communication channels for sender and receiver
4) Sender Agreeement and Receiver Agreement.
Then the file adapter configuration is depend on the input file format.
Also you need to have Logical destionation created in the XI , and the IDX1 entry
In R/3 Port, Partner profiles etc should be created
Have a look into this document~
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
While doing an File -> XI -> IDoc scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you will need a sender agreement for the file.
4. In this configuration note that you will also need a receiver agreement for the IDOC.
For any File -> XI -> IDoc scenario ref:
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
Hope this helps you.
Regards.
Praveen

Problem with import of IDOC fromSAP 3.1i to PI 7.0

Hi ,
I have an IDOC as ZXYZ.ORDERS01 in SAP R/3 3.1i System, I am unable to import the IDOC in PI7.0
Let me know the process to import that idoc.
( I am Doing IDOC to File and file to IDOC Scenario )
Regards,
Edited by: TomShey on Sep 22, 2010 6:27 PM

Hi,
We also had same problem of unable to import IDOC structures automatically from SAP 3.1I to XI/PI, as the support of this feature as mentioned by SAP starts from version >= 4.0.
Please find the prerequisite as mentioned in help.sap.com
Prerequisites
The SAP system from which you want to import the RFCs or IDocs must contain function modules for calling metadata. You can import RFCs and IDocs from SAP Release 4.0 and higher. The table below gives an overview of the required support packages:
(http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm)
So as per my experience, I could identify three options after indepth investigation.
1. Recreate the IDOC structures in another SAP system which is of latest version >= 4.0 may be IDES, and then import the structure in IR for further developments. This is the option we are using for our developments now.
2. Get WSDL of the IDOC structure by creating manually the structure using XML Enterprise edition using the complete syntax or xpath and import as external definitions and use it in mapping.
3. Re-create the IDOC structure in XI system itself and try to use it.
Let me know if this helped you.
Regards,
Bindu

RFC Lookup error :No RFC authorization for function module

Hi All,
I have created RFC in the PI system and enabled it as remote. I am working on PI7.1
I have imported RFC into Repository.But when i am trying to execute RFC lookup function in the graphical mapping I am getting No RFC authorization for function module error.
Unhandled RFC exception: <rfc:Z_MAIL_LOOKUP.Exception xmlns:rfc="urn:sap-com:document:sap:rfc:functions"><Name>RFC_ERROR_SYSTEM_FAILURE</Name><Text>No RFC authorization for function module Z_MAIL_LOOKUP.</Text><Message><ID>RFC_ERROR_SYSTEM_FAILURE</ID><Number>341</Number></Message><Attributes><V1>RFC_NO_AUTHORITY</V1></Attributes></rfc:Z_MAIL_LOOKUP.Exception> com.sap.aii.mapping.api.StreamTransformationException: Unhandled RFC exception: <rfc:Z_MAIL_LOOKUP.Exception xmlns:rfc="urn:sap-com:document:sap:rfc:functions"><Name>RFC_ERROR_SYSTEM_FAILURE</Name><Text>No RFC authorization for function module Z_MAIL_LOOKUP.</Text><Message><ID>RFC_ERROR_SYSTEM_FAILURE</ID><Number>341</Number></Message><Attributes><V1>RFC_NO_AUTHORITY</V1></Attributes></rfc:Z_MAIL_LOOKUP.Exception> at com.sap.aii.mappingtool.flib7.RfcLookup.cacheMore(RfcLookup.java:95) at com.sap.aii.mappingtool.tf7.rt.AMultiResIterator$MultiOutIterator.gotoNextContext(AMultiResIterator.java:95) at com.sap.aii.mappingtool.tf7.AMappingProgram.processNode(AMappingProgram.java:315) at com.sap.aii.mappingtool.tf7.AMappingProgram.processNode(AMappingProgram.java:406) at com.sap.aii.mappingtool.tf7.AMappingProgram.start(AMappingProgram.java:496) at com.sap.aii.mappingtool.tf7.Transformer.start(Transformer.java:133) at com.sap.aii.mappingtool.tf7.AMappingProgram.transform(AMappingProgram.java:626) at com.sap.aii.ibrep.server.mapping.exec.ExecuteXiMappingCommand.transformInternal(ExecuteXiMappingCommand.java:197) at com.sap.aii.ibrep.server.mapping.exec.ExecuteXiMappingCommand.execute(ExecuteXiMappingCommand.java:94) at com.sap.aii.ib.server.mapping.exec.CommandManager.execute(CommandManager.java:43) at com.sap.aii.ibrep.server.mapping.ServerMapService.execute(ServerMapService.java:40) at com.sap.aii.ibrep.server.mapping.MapServiceBean.execute(MapServiceBean.java:40) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy1005_10002.execute(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351) at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62) at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37) at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304) Runtime exception when processing target-field mapping /ns0:MT_FileDummy/File; root message: Unhandled RFC exception: <rfc:Z_MAIL_LOOKUP.Exception xmlns:rfc="urn:sap-com:document:sap:rfc:functions"><Name>RFC_ERROR_SYSTEM_FAILURE</Name><Text>No RFC authorization for function module Z_MAIL_LOOKUP.</Text><Message><ID>RFC_ERROR_SYSTEM_FAILURE</ID><Number>341</Number></Message><Attributes><V1>RFC_NO_AUTHORITY</V1></Attributes></rfc:Z_MAIL_LOOKUP.Exception>
13:42:37 End of test
Edited by: Rams on Apr 17, 2009 1:43 PM

Hi! Rams,
I think the issue is related to Authentification Issue..Even though u did correctly please check once the below
1) Check any Typo Erros are there while configuring or giving names in Lookups.
2) please check Authorizations like ID and PWD and Sufficient Roles
3) Also please check did u given paramters correctly while doing RFC look up I mean paramers , Binding parameters and RFC channel name and adapter type or Simple type it must be an adapter
4) In ID part while configuring Interface determinaition you need to give your RFC look Up name there also..Hence check whether u given or not if yes correctly or not
5) Also remember one thing if your scenario is correct mostly you can know the result in mapping itself it seems while testing Message mapping and Interface mappings give your RFC look up paramters in the parameters tab present in TEST tab and later in Document tab give Input...and execute it works if it doesn;t works and if there is an issue with RFC you can get there only..ok
Also go through the below document::
[https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20befc9a-aa72-2b10-ae9b-b0988791d457]
I hope this will give u brief idea...
Also check with basis while taking SAP_ALL authorization so that first u ill came to know whether issue is related to authentification or RFC module itself remote enabled and also do SXI_CACHE also ocne to refresh ESR and ID objects..
Regards::
Amar Srinivas Eli

Problem in Importing RFC from ECQ to XIQ

Hi.....
I have a problem in importing the RFC from ECC Quality Server to PI Quality Server.......
When I fill the fields like
Application Server......
System Number.....
UserName
Password.....
I am getting a screen Problem.....in which error information is given....
One of the error is UserName(XXXX) cannot have access to aii.sap......
Please help me.....
Thanks,
Sudheer

Hi Sudheer,
Kindly check the user having all authorizations which you are try to importing the RFC's from ECQ to XIQ, check with your basis team and try to provide the required authorizations for that particular user.
Then you can able to import RFC's and do the design by activating the objects.
Regards
Venkat Rao .G

Import RFC/IDOC error

Similar Messages

Maybe you are looking for