SWCV still contains IDocs/RFCs from an SAP system

Hi
I have imported Idoc to a SWCV. Now am trying to create one more namespace under it. When I try to create another namespace, it automatically selects the check button Import of Idoc and RFC interfaces from SAP systems permitted. If I select not permitted and try to create namespace it gives me this message
Unable to save object XYZ , 1.0 of ABC
Indicator cannot be undone since the software component version still contains IDocs/RFCs from an SAP system 
Delete the objects first.
Is it possible for me to create another namespace under a SWCV, to which I have already imported Idoc, by selecting the option " Not permitted ". I want to create another namespace and I don't want to select that option as I have already imported Idoc

Hi,
You no need to touch that check box, you can still create the namespace under software component.
Just double click lick on software component, goto edit mode and click on + symbol to insert namespace and save then activate.
Note:- As you have already imported the RFC and IDoc under your software component(not namspace as you mentioned), you keep that check box import of RFC and IDocs permitted. Dont try to uncheck that.
thanks,
madhu

Similar Messages

  • How we can import an IDOC structure from one SAP system to another

    Hi Gurus,
    How we can import an IDOC structure from one SAP system to another? If we're using ALE, how can we do that? Please can someone give me the process and necessary t codes.
    Any response will be awarded!
    Thanks a lot.
    Samson

    hi!
    Define the logical system names in both the systems.
    Logical system names :SAP001
    SAP002
    SAP001 FOR 001 CLIENT
    SAP002 FOR 002 CLIENT
    These two logical system definitions should be present in both the systems.
    Assign the logical systems to the client. (in both the systems)
    Assign SAP001 to 001 CLIENT
    Assign SAP002 to 002 CLIENT
    you can See these in transaction SALE.
    After this define the rfc DESTINATION IN sm59. (in both the systems)
    In 001 client create the RFC destination name SAP002
    In the tab log on security, give the user name and password and client of the 002 client and save it.
    Similarly do the reverse in the 002 Client.
    In 001 client create the port.(Transaction WE21)
    Specify the RFC destination name as SAP002.
    Now you can define the ports, (both the systems)
    Create the partner profile for partner(ie gve logical system name of partner) , so give as SAP002.
    partner profile in both the systems.
    Now create the distribution model in BD64 and goto edit>model view>distribute.
    The same model view will be visible n distributed to the partner system also..which in this case is sap002.
    U may trigger the idoc from we19 and chk its status in we05.
    Please let me know if you need further info on this.

  • How we can import an IDOC structure from one SAP system to another w/o ALE

    Hi Gurus,
    How we can import an IDOC structure from one SAP system to another? we're not able to use ALE tech, these two sap systems are isolated.
    Any response will be awarded!
    Thanks a lot.
    Samson

    hi,
    1.One is by change pointer concept i.e by executing the RBDMIDOC.We can generate the idoc and automatically to the inbound System.
    2.By executable program also like bd10 and bd11.
    Regards,
    SHIVA(reward if helpful).

  • Move IDOC Configuration from one sap system to other sap system

    Hi All,
    I have a scenario where in we need to move the SAP Configuration including Port,partner funtions details etc to other Sap system .As per my knowledge we have some SAP Standard tables which stores all the SAP Config data .So my thought is that if we move those table entries from sorce sap system to target sap system the task will be completed however i dont know which table entries i need to move.Kindly suggest.
    Venu

    Many of these IDoc settings are not asking for transport requests, since they are considered master data (table class A). They are to be done directly in each system, because the are often linked to information that is or might be specific, like master data, logical system names, path names, etc...
    Please also search for previous discussions, you are probably not the first one encountering this issue.
    Thomas

  • Call a remote RFC from one sap system to to other sap system

    Hi experts,
    I'd like to know how to connect two sap systems via RFC. The two systems are in the same network and I'd like to know how to set up the SM59 in order to create the destination to the RFC.
    Any help in configuring the SM59 to stablish the communication?
    thanks a lot.

    <b>You can do that from t-code SM59 or SALE</b>
    This step is to create the Logical system for the remote system.
    A logical system allows SAP internal functions to interface with external systems, either an SAP system or a non-SAP system. We also need to have a logical system name for the SAP system,.
    SALE is the transaction.
    Expand the Sending and receiving Systems and then the Logical systems click on define logical system.
    You will receive the informational message, “The table is cross-client.” Click the green check icon to continue.
    Now click on the New Entries.
    The Screen appears like this here you will be giving the LS name and the description of that.
    After u click on the save button a window will be displayed like the bellow asking for the Request ID. Here we can create our own  or we can use the existing one.
    After that we see the message blow as DATA SAVED.
    Now the step is to Link the LS to the client.
    Click on the Assign Client to LS .
    The Screen as below will be appearing. 
    Double click on the client on which u r going to work and there specify the SAP LS(IDS47800) and you also need to specify the City and Std Currency and the client role as Test for the drop down box.
    Register the RFC server module with the
    SAP gateway
    The RFC (Remote Function Call) destination is a logical name used to define the
    Characteristics of a communication link to a remote system (in our case, LS for the remote system) on which a function needs to be executed. In ALE, the RFC specifies information required to log on to the remote SAP system to which an IDoc is being sent.
    To register the RFC Sever Module as the RFC destination:
    SAP transaction code: SM59 – Type /nsm59 on the SAP input window and press the
    Enter key.
    Expand the TCP/IP connections directory.
    Give some name to the RFC Destination (ALESERVER), Connection type as T. and fill the Description field.
    In technical settings give the program name as you desired.
    Click on save
    regards,
    srinivas
    <b>*reward for useful answers*</b>
    Message was edited by:
            XI_Novice
    Message was edited by:
            XI_Novice

  • ALE: Sending IDOC inbound from non-SAP system

    Hi
    How does one need to setup the SAP system to accept data from an external non-SAP system. Should one setup some sort of conection to trigger an import to SAP?

    Hi,
    On the SAP side you need to create a partner profile in T.code: WE20 of type LS. And add the message type, idoc type in the inbound parameters section of it.
    And you must also specify the partner number you created here, on the IDoc control record.
    This link from SAP help, will provide some addition data.
    <a href="http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6524507d11d18ee90000e8366fc2/frameset.htm">http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6524507d11d18ee90000e8366fc2/frameset.htm</a>
    Hope this helps.
    Regards,
    Sumant.

  • Callig RFC from Non SAP System

    Hi,
    I would like to know how can I call a RFC enabled Function Module from a non SAP system, I know of Webservices, SAP API, SAP jco etc but to download all this connectors (SAP jco Sap .net etc) you require SAP service ID logon, i do not have it, with reference to Web services i cannot use it since the client is not interested ...
    1) in short i do not have SAP service user id ... what are the other options for calling  SAP RFC using an application say java even if i can use any middleware to connect the java apllication and sap rfc it is fine.
    2) The SAP services is 4.7 and they do not use EP, Netweaver Developent Studio etc ... simple plain SAP System ... also what setting has to be done at the server side ...
    regards
    Santosh

    Check this link . Might solve your problem.
    http://www.sapnet.ru/viewtopic.php?t=832

  • CRM_Order_maintain not wortking from other SAP system

    Hi ,
    we need to change the msg partner for a support desk msg from webdynpro application.for that we are creating a custom RFC function module, Contains the below coding ,
    CRM_ORDER_MAINTAIN
    CRM_ORDER_SAVE
    BAPI_TRANSACTION_COMMIT
    It is successfully changing the business partner ( msg processor ) in the support desk msg . But if we call this function module from webdynpro it is not creating as such.
    what could be the reason .
    ____________ we checked the following
    1. we called the RFC from other SAP system . it is not working .
    2. we debugged that RFC from R/3 , we found the difference. For the below functional module is not returning any events from R/3 . whereas if we run the FM from solution manager it is exporting events .
    CRM_EVENT_PASS_INFO_EXE_OW

    Hi,
    Did you solve this issue?? if you do? how you do it?
    thanks in advanced.

  • Receiving IDocs from non-SAP system ...

    Hello guys,
    I have problem with implementing IDoc-XI-IDoc scenario. The sender system is a subsystem (non-SAP system) sending IDocs but XI is not able to receive them. I thing the IDoc metadata can not be found.
    Logical system name of the sender is IF6020DEV. I registered the system in SLD. In Integration Directory I imported the Bussines System IF6020DEV to my scenario and I created communication channel of type Sender IDoc Adapter in it.
    In IDX2 I created new port called IF6020DEV and I copied needed metadata into the port. But it doesn't work. Probably I don't do it right because I'm beginner with SAP XI.
    Could you give me any advice how to configure XI for receiving IDocs from non-SAP system?
    Thank you in advance!
    Regards
    Zbynek

    Thank you very much. The issue described in refered discussion is almost same issue what I'm solving. Unfortunetally the described solution dosn't work for me.
    The sender system still returns following error. I know you probably won't understand it because you don't know the subsystem, but maybe you could get some idea what is wrong.
    05/29/09 16:09:19.482 idoup2 Logon...
    05/29/09 16:09:19.482 idoup2 RfcOpenEx (TRACE=1 CLIENT=110 USER=xxxxxx LANG=D LCHECK=1 GWHOST=xxxxxx GWSERV=3361 ASHOST=xxxxxxx SYSNR=61 PASSWD=<password>)
    05/29/09 16:09:19.529 idoup2 Logon RfcOpenEx result=1
    05/29/09 16:09:19.607 idoup2 Call to (IDOC_INBOUND_ASYNCHRONOUS) failed (3)
    05/29/09 16:09:19.607 idoup2 Handle=1
    05/29/09 16:09:19.607 idoup2 key............:
    05/29/09 16:09:19.607 idoup2 status.........:
    05/29/09 16:09:19.607 idoup2 message........:IDoc-Adapter Eingang: Der Absenderport ist initial
    05/29/09 16:09:19.607 idoup2 internal status:
    05/29/09 16:09:19.607 idoup2 idoc_upload failed with rc=(3), try(2)
    05/29/09 16:09:20.607 idoup2 key............:IDoc-Adapter Eingang: Der Absend
    05/29/09 16:09:20.607 idoup2 status.........:EXCEPTION SYSTEM_FAILURE RAISED
    05/29/09 16:09:20.607 idoup2 message........:IDoc-Adapter Eingang: Der Absenderport ist initial
    05/29/09 16:09:20.607 idoup2 internal status:
    05/29/09 16:09:20.607 idoup2 idoc_upload failed with rc=(18), try(1)
    05/29/09 16:09:21.607 idoup2 Logoff...

  • Sending IDoc from Non-SAP system to XI

    Dear all,
       We have a non sap system which needs to send IDoc to XI, Please could you answer my following four questions
    1. What should be the values for the following fields in the IDoc control record
    e.g. RCVPRN = <logical system name of XI>
    SNDPOR
    SNDPRT
    SNDPRN
    RCVPRT
    RCVPOR
    2. How does XI decide which port(idx1) to be used when it receives an idoc
    3. The third party system is a non sap one, so it does not have a client no, so I would assume, I need to use another SAP system as a meta data provider, in that case, how would i tell XI to use that port when it receives IDocs from the non-SAP system ?
    4. In what step does XI use the logical system name of the Business system(in SLD)?
    Thanks in advance
    cheers
    danus
    Edited by: Chidambaram Danus on Jan 25, 2008 2:21 PM

    Hi
    there is bit wrong interpretation of the statement
    If the sender system is a non-SAP system, the sender service is identified from the logical system name of the sender port.
    If the sender system is nonSAP it indicates taht the data is coming to XI from non sap systems such as file, database, webservice etc. to XI and from XI it will pass to sap as IDOC inbound.
    For this you need to create the logical system in SAP (receiver) and pass on that value to IDOC header.
    You could maintain it in the Business service used for Sender system (nonSAP). here it will be available in the tabs ---> History.
    note : IDOC is the concept of data container in SAP, you will not be able to have the IDOCs in non sap systems...
    Thanks
    Swarup
    Edited by: Swarup Sawant on Jan 25, 2008 2:54 PM

  • 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

  • Call rfc sender adapter from non-sap systems

    Hi,
    is ist possible to connect to an rfc sender adapter from non-sap systems? I want to use the the RFC-Connector from http://rfcconnector.com, but in the client connect options there is no way to specify the program id.
    Best regards,
    Daniel

    hi,
    you don't need to use RFC type T (with program ID) - you can use whole connection string - just like in the example:
    http://www.rfcconnector.com/documentation/examples/client/#functioncall
    so just specify: host system number etc.
    it should work like that - but let me know as I don't know this RFC connector
    Regards,
    Michal Krawczyk

  • Problem in Fetching data using RFC FM from NON SAP system

    Hi All,
    Need help from experts on data transfer using RFC from a non SAP system/database. I have creasted the destination in sm59.
    I have created a function module too which has an import parameter as a query and export parameter as an internal table.
    No when i test run this function module it returns some entries. But when I call this FM in a program it throws a dump 'rfc_external_abort' .  Here is what the call to FM looks like in my program. Please guide me on this.
    Thanks in advance,
    Saket.
    DATA : lv_query TYPE string,
           it_gddbdata TYPE ZC9_TAB_SOLMAN_XI_RFC.
    lv_query = 'SELECT *  FROM GDDB.VW_GDDB_PERSONS WHERE LASTNAME = ''''A'''''.
    CALL FUNCTION 'Z_C9_SOLMAN_XI_GDDBCON'
    DESTINATION  'D39'
      EXPORTING
        in_sql_query       = lv_query
    IMPORTING
       ET_GDDB_DATA       = it_gddbdata

    Hi,
    your question..
    DATA : lv_query TYPE string,
    it_gddbdata TYPE ZC9_TAB_SOLMAN_XI_RFC.
    lv_query = 'SELECT * FROM GDDB.VW_GDDB_PERSONS WHERE LASTNAME = ''''A'''''.
    CALL FUNCTION 'Z_C9_SOLMAN_XI_GDDBCON'
    DESTINATION 'D39'
    EXPORTING
    in_sql_query = lv_query
    IMPORTING
    ET_GDDB_DATA = it_gddbdata
    you are telling that you are fetching the data  from non sap system  using RFC function module.. how it is possible..you canot fetch the data from non SAP system using RFC FM alone.. you have to use the concept BAPI.. it will work..
    I hope this will help  you..
    Regards,
    Kiran

  • Launch a RFC in a SAP system from Redwood CPS

    Hi,
    How can I launch a rfc in a SAP system from Redwood ?
    Ex : in SE37, the function DATE_GET_WEEK, with a date (DD.MM.YYYY) as input parameter returns the corresponding week (YYYYWW)
    Regards.

    Hi,
    SAP CPS uses an RFC to communicate with a target SAP system via the XBP interface so that Jobs can be executed.  The CPS executable only knows of the calls that are appropriate to that interface or function modules created when CPS transports are loaded.  If there was an RFC type interface that exposed your function to an external executable then of course CPS could execute the executable.
    Regards,
    Simon

  • No Idocs arrived from the source system.

    Dear All,
    Please read this issue carefully.
    Error Message is that
    "No Idocs arrived from the source system."
    In the Details Tab:
    Trasnfer( IDOCS &TRFC):Missing Messages or warinings.
    Request IDOC:Application Documnet posted from BW side and it is green..There is a request BW IDOC number  sent to R3.
    Where as an InfoIdocs 1:Sent not arrived :Data passes to the Port is ok.
    Here i can see there is one idoc frm  OLTP R3 side ansd no incomming idoc for BW side
    I went to r3 side bd87 and found that idoc is posted well with status 53.
    This is happing in Bw for each iinfopcakage is running?

    Hi,
    go through this link...
    [https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=noidocsarrivedfromsource+system&adv=false&sortby=cm_rnd_rankvalue]
    System.-> Check RFC connection and clear/process stuck IDOCs.
    Idocs Missing or No Idocs arrived from source
    For this check the TRFC que(SM58).If any Idocs r strucked up there execute them manually.checkin sm58 transactions, you can check the status of your Idocs using BD87 in R/3. Idocs may not be processed because of load on system. You can process them manually from context menu.
    And go to BD87 to process the idoc's ..
    check which idoc has to process...select the idoc and click process ..Then It will push the data into the data targtes,
    Hope it will help you;
    regards,
    NR

Maybe you are looking for

  • Mega Sky 580 no channels

    Hi Installed Mega Sky 580 and Presto program nicely but I cant receive any channels. The program doesnt find any channel, not even if I am outside with my laptop. Does the Mega Sky need an external roof antenna to work????? Tommy

  • Text Resolution

    Hi, I'm new to Final Cut Express, moving up from iMovie. I have one major issue that is common to both iMovie and Final Cut, so I'm thinking I must be doing something wrong. When I create a nice title or other text with Live Type, it looks excellent,

  • Timecapsule and iMac Early 2008 - Problems with Airport Utility

    I have bought a new iMac and a TimeCapsule. With *Leopard 10.5.5* i have some problems to change the configuration. The Assistant will not work. The changed settings will not send to theTime Capsule (Ethernet or and Wireless). The airport signal is _

  • Random Loss of art work.

    My iPod 5th Gen is often loosing artwork for the odd few albums. I have it set to show artwork in my preferences and all my artwork is in my iTunes still. I have 3 times totally removed artwork by selecting "do not display album artwork", in my iPod

  • Merge columns in an ALV Table

    Hi colleagues, is it possible to merge two or more columns in ALV Table (like ColSpan in the Matrix-Layout) to write a text over more than one column? I haven't found any solution for it until now. Best regards Stefan