"Port 'A000000001' of type ALE does not exist"

Hi Guys,
I am getting the following error message when I am trying to activate the Source System in RSA1. This connection is self connection to BW system.
"Port 'A000000001' of type ALE does not exist"
When I go and try to create the port in WE21 for the port "A000000001". I am getting the following error message.
Choose another name! Name Range reserved.
As far as I know that the source system is pointing to 'A000000001" port which I could not find in WE21. So how do i point this particular port to this system. Is there any way where I can go ahead and change the table entries.
Waiting for your suggestions.
Regards
Pooja

Thanks for update.
I am the one responsible for al.
I went to we21 under TRFC type a port XXXXXXXXX9 alreday exists pointing to the logical client rfc.
I tried to create a new port entry with A0000000001 but no sucess.
I tried to edit the 1st entry but the port filed comes disabled.
Please assist in this regard.
Thanks
Pooja

Similar Messages

  • Type com.sap.xss.ser.xssmenu.model.types.P_Pernr does not exist

    Hi there,
    same Thread I post in "Portal Developement". Now I try my luck in ths category...
    we implement ESS (ERP2004 with WebDynpros) in our testsystem, but we got an error and don´t know what to do...
    System Landscape:
    - mySAP Enterprise Portal 6.0 SP17
    - Java Application Server (excluding from HR)
    - mySAP ERP2004 HR-System
    The Connections from the portal runs to the Java-App-Server, not direct to the HR-System (HR-System has no Java Installation and our Customer don´t want a installation, because it could be a bad performance)
    We implement the Jco´s and fill out the usermapping. If we want to call the firstpage of the new ESS-Role we get this error.
    Can anyone help us? Do we need some installations?
    Best regards
    Christian
    Error
    500 Internal Server Error
    Web Dynpro Container/SAP J2EE Engine/6.40
    Failed to process request. Please contact your system administrator.
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
    com.sap.dictionary.runtime.DdException: Type com.sap.xss.ser.xssmenu.model.types.P_Pernr does not exist
    at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
    at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:586)
    at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:286)
    at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:95)
    at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
    ... 54 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; InfoPath.1; .NET CLR 2.0.50727)
    Version
    DOM version
    Client Type msie6
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, Build ID: 6.4015.00.0000.20051123162612.0000 (release=630_VAL_REL, buildtime=2005-12-14:21:51:22[UTC], changelist=377533, host=PWDFM026)
    J2EE Engine No information available
    Java VM Classic VM, version:1.4.2, vendor: IBM Corporation
    Operating system AIX, version: 5.2, architecture: ppc64
    Other
    Session Locale de
    Time of Failure Thu Jan 11 16:14:11 GMT+00:00 2007 (Java Time: 1168532051021)
    Web Dynpro Code Generation Infos
    sap.com/pcui_gp~xssutils
    SapDictionaryGenerationCore 6.4018.00.0000.20060530191647.0000 (release=630_REL, buildtime=2006-09-20:21:03:45[UTC], changelist=405154, host=PWDFM027.wdf.sap.corp)
    SapDictionaryGenerationTemplates 6.4018.00.0000.20060530191647.0000 (release=630_REL, buildtime=2006-09-20:21:03:57[UTC], changelist=405154, host=PWDFM027.wdf.sap.corp)
    SapGenerationFrameworkCore 6.4015.00.0000.20050818152155.0000 (release=630_VAL_REL, buildtime=2005-11-24:21:18:08[UTC], changelist=363812, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 6.4018.00.0000.20060823112633.0000 (release=630_REL, buildtime=2006-09-20:21:14:40[UTC], changelist=415262, host=PWDFM027.wdf.sap.corp)
    SapMetamodelCommon 6.4018.00.0000.20060302125746.0000 (release=630_REL, buildtime=2006-09-20:20:56:46[UTC], changelist=392271, host=PWDFM027.wdf.sap.corp)
    SapMetamodelCore 6.4018.00.0000.20060302125746.0000 (release=630_REL, buildtime=2006-09-20:20:56:36[UTC], changelist=392271, host=PWDFM027.wdf.sap.corp)
    SapMetamodelDictionary 6.4018.00.0000.20060302125547.0000 (release=630_REL, buildtime=2006-09-20:21:00:39[UTC], changelist=392265, host=PWDFM027.wdf.sap.corp)
    SapMetamodelWebDynpro 6.4018.00.0000.20060823112248.0000 (release=630_REL, buildtime=2006-09-20:21:09:40[UTC], changelist=415252, host=PWDFM027.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 6.4018.00.0000.20060915154217.0000 (release=630_REL, buildtime=2006-09-20:21:52:30[UTC], changelist=417774, host=PWDFM027)
    SapWebDynproGenerationCore 6.4018.00.0000.20060823112633.0000 (release=630_REL, buildtime=2006-09-20:21:15:10[UTC], changelist=415262, host=PWDFM027.wdf.sap.corp)
    SapWebDynproGenerationTemplates 6.4018.00.0000.20060915154217.0000 (release=630_REL, buildtime=2006-09-20:21:52:30[UTC], changelist=417774, host=PWDFM027)
    sap.com/tcwddispwda
    No information available
    sap.com/pcui_gp~xssfpm
    SapDictionaryGenerationCore 6.4018.00.0000.20060530191647.0000 (release=630_REL, buildtime=2006-09-20:21:03:45[UTC], changelist=405154, host=PWDFM027.wdf.sap.corp)
    SapDictionaryGenerationTemplates 6.4018.00.0000.20060530191647.0000 (release=630_REL, buildtime=2006-09-20:21:03:57[UTC], changelist=405154, host=PWDFM027.wdf.sap.corp)
    SapGenerationFrameworkCore 6.4015.00.0000.20050818152155.0000 (release=630_VAL_REL, buildtime=2005-11-24:21:18:08[UTC], changelist=363812, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 6.4018.00.0000.20060823112633.0000 (release=630_REL, buildtime=2006-09-20:21:14:40[UTC], changelist=415262, host=PWDFM027.wdf.sap.corp)
    SapMetamodelCommon 6.4018.00.0000.20060302125746.0000 (release=630_REL, buildtime=2006-09-20:20:56:46[UTC], changelist=392271, host=PWDFM027.wdf.sap.corp)
    SapMetamodelCore 6.4018.00.0000.20060302125746.0000 (release=630_REL, buildtime=2006-09-20:20:56:36[UTC], changelist=392271, host=PWDFM027.wdf.sap.corp)
    SapMetamodelDictionary 6.4018.00.0000.20060302125547.0000 (release=630_REL, buildtime=2006-09-20:21:00:39[UTC], changelist=392265, host=PWDFM027.wdf.sap.corp)
    SapMetamodelWebDynpro 6.4018.00.0000.20060823112248.0000 (release=630_REL, buildtime=2006-09-20:21:09:40[UTC], changelist=415252, host=PWDFM027.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 6.4018.00.0000.20060915154217.0000 (release=630_REL, buildtime=2006-09-20:21:52:30[UTC], changelist=417774, host=PWDFM027)
    SapWebDynproGenerationCore 6.4018.00.0000.20060823112633.0000 (release=630_REL, buildtime=2006-09-20:21:15:10[UTC], changelist=415262, host=PWDFM027.wdf.sap.corp)
    SapWebDynproGenerationTemplates 6.4018.00.0000.20060915154217.0000 (release=630_REL, buildtime=2006-09-20:21:52:30[UTC], changelist=417774, host=PWDFM027)
    sap.com/tcwdcorecomp
    No information available
    Detailed Error Information
    Detailed Exception Chain
    com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type com.sap.xss.ser.xssmenu.model.types.P_Pernr could not be loaded: com.sap.dictionary.runtime.DdException: Type com.sap.xss.ser.xssmenu.model.types.P_Pernr does not exist
    at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:250)
    at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
    at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:314)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:669)
    at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:233)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:654)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)
    at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:347)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:855)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:158)
    at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:143)
    at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:135)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent$ComponentUsageManager.createBLCComponentUsage(FPMComponent.java:628)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:773)
    at com.sap.xss.ser.xssmenu.vc.header.VcXssMenuHeader.onInit(VcXssMenuHeader.java:196)
    at com.sap.xss.ser.xssmenu.vc.header.wdp.InternalVcXssMenuHeader.onInit(InternalVcXssMenuHeader.java:225)
    at com.sap.xss.ser.xssmenu.vc.header.VcXssMenuHeaderInterface.onInit(VcXssMenuHeaderInterface.java:162)
    at com.sap.xss.ser.xssmenu.vc.header.wdp.InternalVcXssMenuHeaderInterface.onInit(InternalVcXssMenuHeaderInterface.java:144)
    at com.sap.xss.ser.xssmenu.vc.header.wdp.InternalVcXssMenuHeaderInterface$External.onInit(InternalVcXssMenuHeaderInterface.java:220)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:466)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:354)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:179)
    at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:95)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:347)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:370)
    at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:608)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
    at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java: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(Compiled Code))
    at java.security.AccessController.doPrivileged1(Native Method)
    at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))
    Caused by: com.sap.dictionary.runtime.DdException: Type com.sap.xss.ser.xssmenu.model.types.P_Pernr does not exist
    at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
    at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:586)
    at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:286)
    at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:95)
    at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
    at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
    at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
    ... 52 more

    Hi,
    uhm... good question, long time ago...
    Error should be in the JCO-Destinations, where you can choose a targetsystem for each Jco-Destination.
    Since them we installed a java on the abap-system, so we have a doublestack.
    In the Jco Destiantions must be the ABAP-System.
    Application via SAPTicket and MetaData via fix User like DDIC.
    Regards
    Christian

  • Source message Message Type: POR does not exist in software component versi

    HI All,
    I have a .tpz file exported from an SRM 4.0 PI system which i have imported in SRM 7.0 ECC 6.0 PI.
    I have imported the .tpz file through the import through "client" option.
    I am able to open all the objects but i am not able to open the Message mappings.....
    It is throwing the following error:
    Source message Message Type: PurchaseOrderRequest does not exist in software component version xx_xx_PO_PROCESSING, 1.0 of xx.com Check whether software component version xx_xx_PO_PROCESSING, 1.0 of xx.com is in the Enterprise Services Repository. Import this or a newer version if necessary.
    This needs to resolved very urgently...
    Kindly help...
    Thanx in advance..
    Nandan

    Hi,
    I'd say you need to import some other SWCV which has all the IDOC typos you use in your scenario
    probably this is a prerequisite for importing your SWCV
    I don't think this is related to sp level or anything like that
    it's just that SWCV is missing
    Regards,
    Michal Krawczyk

  • Basic type CREMAS03 does not exist

    Hi all.
    We have SRM 7 Classic Scenario with ECC 6.4
    My problem is in scenario MM-SUS. When we try to replicate a vendor data from MM to SUS the idoc MM is processed correctly, but in (SUS) has an error in trx WE05: Basic type CREMAS03 does not exist.
    I review the settings and I can not find the cause.
    any idea about that?
    Regards

    Hi,
    I am not clear with your issue. Why are you checking for idoc status in SUS system?
    IDOC is sent from the ERP system and check what the status of IDOC is in ERP. Next check whats the xml status in PI system and if its successful in PI then check xml in SUS system/. You can check xml status using tcode: sxi_monitor.
    Regards
    Sam

  • Production scheduling profile for production order type 10 does not exist – SAP Message No.10085

    When i tried to make confirmation for Production Order through CO15 transaction , i receive the following error message “ Production scheduling profile for production order type 10 does not exist – SAP Message No.10085 “
    In Work Scheduling view, Production Scheduling Profile is maintained as per OPKP only.
    How to check whether production scheduling profile is maintained for relevant order type 10.
    To do this , i went to OPKP & KOT2_OPA transactions but i don’t know how to check. I guide me through with a screen shot.
    Also, pls explain about  “Order Type 10” and how it is linked with material and order execution.
    Looking for a detailed explanation with screen shots , since i am new to SAP.
    Thanks With Regards,
    Dinesh Kumar V.

    Hello Dinesh,
    Please check the order type dependent parameter in OPL8 here you will get the Substitute Scheduler
    Then go to OPCH and check valid production scheduling profile assign here as per OPKP to your production scheduler for your plant.
    Production order have Order category as 10  Process Order  40 in standard SAP you can check this in OPJH.
    Best Regards,
    R.Brahmankar

  • Set type COMM_PR_UNIT does not exist

    Hi All
    How do i make set types available for assignment to categories if they are not available but are there in comm_settype. Getting errors as follows: Set type COMM_PR_UNIT does not exist.
    Please assist
    Regards,
    Patrick
    Edited by: Patrick Chidarara on Jul 22, 2008 10:14 AM

    Hi Patrick,
    Please see OSS note Note 966072 - Download of material fails - set type COMM_PR_UNIT
    Regards,Nishant

  • Address type XXDEFAULT does not exist

    Hi Gurus,
    i am working on crm 2007 web Ui.
    when i try to create a new corporate account from masterdata>accounts>corporate account, i just provided name and country and click on save.
    Getting following error.
    """ Address type XXDEFAULT does not exist: Address usage XXDEFAULT cannot be created ""
    Any idea why i am getting this suddenly.
    to know the solution, i got componet and view names from the WEB ui screen using F2 technical attributes.put a break point in all of those methods and dubugged, but could not find the solution
    i appriciate your help.
    thanks
    seema

    Hi,
           This may be a R/3 to CRM download configuration issue. See if this thread if it helps.
    [Problem with initial download;
    Regards,
    Arun Prakash

  • Middleware initial load error on funcloc segment type (ADR2) does not exist

    Hello,
    We are doing initial loads of data into a new CRM 7.0 system.
    So far all objects have been done except Functional locations (FUNCLOC).
    During the initial load of the functional locations the various BDOCs all go into error state.
    The error is the same everywhere: segment type adr2 does not exist.
    If we deactivate the adr2 table In transaction R3AC1 and process again, we get the error message for the next table
    (Like:  segment type IFLOTX does not exist) and so on.
    IS there any settings we can do to manage these 'segments' or would there be another wa to solve this?
    Thanks.
    Joram

    Hello,
    Take a look at note 1271465, it does not talk about the ADR2 segment but about segment errors in SMW01 for functional location download. It might be useful. Observe especially the constraint in ERP version number, it might be that your ERP system is out-of-date/incompatible for this scenario.
    Second thing to check, go to SPRO>CRM>Master Data>Installed Base>Replication of technical objects from ERP
    There you'll find a mandatory customizing activity for Functional location download.
    And in the documentation of activity "Replication of Functional locations: Prerequisites and General information" you'll find all the necessairy actions to perform.
    This helped me in setting up funcloc replication in CRM 7.0.
    Hope this helps,
    Kind regards,
    Joost

  • Category for material type MAT_KMAT does not exist for configurable product

    Hi,
    Trying to download Confihurable product from ECC to CRM,for this I am getting the below error.
    "Category for material type MAT_KMAT does not exist"
    For this , i have successfully downloaded the object DNL_CUST_PROD1, but still the  material type MAT_KMAT does not exist under R3PRODSTYP in COMM_Hierarchy transaction.
    kindly let me know how to get the material type MAT_KMAT  under R3PRODSTYP .
    Regards,
    PV

    Hi
    Please go through the below pdf document. This will be useful.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/9076a9a4-923c-2c10-7483-d997a9eae976?quicklink=index&overridelayout=true
    Regards

  • Production scheduling profile for production order type 10 does not exist

    Kindly suggest me how to resolve this error
    Production scheduling profile for production order type 10 does not exist

    Hi Archana,
    Go to material master-work scheduling view and check what is the production scheduling profile maintained for the same materisl -plant combination.
    then go to OPKP and check if production scheduliong profile is maintained for relevent order type 10 in custmizing. If not maintain one and it should resolve the error.

  • DBSIZE.XML with type NODE does not exist

    I am receiving the following message when installing the ERP 2004 IDES ECC5.0 DB instance.
    SO:Windows 2000 Server ADV SP4 DB2 v8.1.9.700.
    The file are not present in CD or DVD or marketplace, exists for all the DB to outside of: DB2 DB4 DB6.
    How I can order to continue?
    [email protected]

    This is what I am trying to do
          newNodeName = (String) regionComboBox.getSelectedItem();
          selectCompanyType = (String) selectCompanyTypeComboBox.getSelectedItem();
            Node getRegionNode = perXmlDoc.getNode("REGION");
            Node setRegionLocation = perXmlDoc.getNode(getRegionNode, newNodeName);
      Node checkCompanyTypeLocation = perXmlDoc.getNode(setRegionLocation,
                  selectCompanyType);
              if (checkCompanyTypeLocation.equals("")) {
                Node setCompanyTypeLocation = perXmlDoc.addNode(setRegionLocation,
                    selectCompanyType);
              else {
                Node setCompanyTypeLocation = perXmlDoc.getNode(setRegionLocation,
                    selectCompanyType);this is part of the xmlDoc
    - <PRESCRIBERS>
    - <COMPANY_TYPES>
    � <RETAIL />
    � <STORE />
    � <CRAIG />
    � </COMPANY_TYPES>
    - <REGION>
    � <TAS />
    � <MELB />
    � </REGION>
    � </PRESCRIBERS>
    Basically what I am after doing is 2 combo boxes 1st is the Region that you can select. then the company type from the 2nd combo it then uses the region node and adds in the company type to the region node and then stores the comapny info ie address and phones etc.
    Once you have placed a company type under the region i can get to that node to add further companies but when I don't have a company type under the region that is where I need to check to see it it is there if not add new company type node.
    I hope I have explaned this right
    Craig

  • Source system restore - Source system does not exist

    Hello friends,
    We have a problem. Now we have a new test system QA2. From BW system source system connection was configured for older test source system QA1.
    We needed to route this source system to new system. I tried with changing RFC of QA1 to QA2 details.
    Now, when i check RSA1 source system Check for QA1, i get this error :
    Port 'A000000103 ' of type 'ALE ' does not exist
    No destination exists to source system QA1
    I can see this source system in RSA1 in BW. However, in WE21 port is not available now.
    Please suggest.
    I do not have to lose transfer rules/PSA tables..etc.
    thanks
    ashish

    I get this when i try to restor connection :
    Source system does not exist
    Message no. RSAR175
    Diagnosis
    You have specified that you want to restore source system QA2. This source system is not known in BI.
    System Response
    The source system is not restored.
    Procedure
    Recreate the source system.
    If the source system should be known to BI, the name of source system QA2 may be incorrect. Rename the source system and try the function again.

  • Transaction Type is 922 does not exist

    Hi,
    While posting FI document I am getting below error message :
    Error: Enter another transaction type (Transaction type 922 does not exist)
    Message no. AA816
    Diagnosis:
    According to your entry or specification, you want to use transaction type 922. However, this transaction type has not been defined.
    Procedure:
    Check the if transaction type 922 is defined in FI-AA Customizing
    Please advise how can I rectify this issue!
    Regards
    VS Rao

    Hi VS Rao
    Seems you used TT.922 in T-cd: OAYT but somehow you deleted  TT.922 afterwards. You can either delete the setting of TT.922 from T-cd: OAYT or simply redefine the TT.922 accordingly if any necessary.
    Best regards
    George

  • WD Java - Type does not exists

    Hi folks,
    we use the RFC Import in WebDynpro JAVA and import a function module of name like /tyed/myFunction where /tyed/ is a namespace.
    when running that application we get an error on a structure which is of name like /tyed/myStructure and in JAVA the namespaces are translated from /tyed/ to __tyed__
    The dump says com.sap.dictionary.runtime.DdException: Type ordmon.types.__Tyed__Atcp_S_Ordmon does not exist
    But these data-types do exist? are there any known problems with namespaces ???? or what could that be.
    kind regards
    oliver

    Hi Oliver,
    The most likely reason for this kind of an error could be the follows
    •     The backend to which to connect at Runtime is not the same as the backend from which you imported the model. This could cause inconsistencies. You need to run with the same backend from where you imported your model or the version of the RFC in the backend used at runtime must be compatible to the one used to import the model.
    •     Data types have changed in the backend, such that the “Type” you imported earlier no longer exists. You need to re-import the model again.
    Regards,
    Arun

  • Source System Activation - IDOC Type does not exist

    I'm doing a new installation of BI7 and when I want to activate the source system on  replicate Metadata Box and select "Only Activate" it comes up with error stating :Basic Type ZSxxxxx does not exist
    When I look in SE16 on table RSBASIDOC I can see the IDOC Type exist on both BW and R/3 Systems
    Any solution?

    Check my reply
    Re: "Basic Type Does Not Exist"

Maybe you are looking for