SLD Again :-)

CIM_ERR_FAILED: SAP_BusinessSystem.CreationClassName="SAP_BusinessSystem",Name="CXD" referenced by association SAP_BusinessSystemExchangeServer.Antecedent=ref"SAP_BusinessSystem.CreationClassName=\"SAP_BusinessSystem\",Name=\"CXD_BS_D\"",Dependent=ref"SAP_BusinessSystem.CreationClassName=\"SAP_BusinessSystem\",Name=\"CXD\"" does not exist.
SAP_BusinessSystemExchangeServer.Antecedent=ref"SAP_BusinessSystem.CreationClassName=\"SAP_BusinessSystem\",Name=\"CXD_BS_D\"",Dependent=ref"SAP_BusinessSystem.CreationClassName=\"SAP_BusinessSystem\",Name=\"CXD\""
The above error is what I received whenI imported my business systems onto the new SLD... Does anyone know what exactly it is or means?

hi,
this means you need to go along with SAP suggestions
and have only one SLD
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Similar Messages

  • PI7.0: SLD - Technical System of type "Exchange Infrastructure"

    Hi Guys,
    The adapter engine was empty in the integration directory and as part of it i followed the steps in the sap note - 764176 Error in XI due to inconsistency in the sld. I did the following steps
    1. Switch to "Home" in the "Technical Landscape" view, and select the
    "Exchange Infrastructure" technical system type there. Select all
    domains and XI components for the host and delete these by selecting
    them and pressing 'Remove'.
    2. Restart the J2EE server. After you restart the server, the XI
    components log on to the SLD again and create a new entity of class
    "XI Integration Server".
    3. To register the directory and repository again, you must also log on
    to the two tools.
    I have restarted the j2ee server and looged into the IR and ID but they are not automatically registered in the central sld.
    central sld is on solmanger box.  How to register IR, ID, RWB and central adapter engine under the technical systems of type exchange infrastructure ?
    any help would be really appreciated
    Thanks,
    Raj

    Hi Reddy,
    i faced the same problem few days back...
    check this link
    /people/venugopalarao.immadisetty/blog/2007/03/15/adapter-engine-cannot-be-found-in-integration-directory
    and also cross-check the post installation steps.
    In my case the Business system for XI was created of type web as java... but it should be of type web as abap.
    Sachin

  • SLD Communication: LD_ERROR and RWB not connected to SLD

    Hi all,
    I have installed SR2 on MS SQL Server 2005
    I have run the template installer and also rectified the errored out steps
    All RFC destnation are created propely and thr connection checked
    I have three queries
    1) In SLDCHECK the error i get is
             Calling function LCR_LIST_BUSINESS_SYSTEMS
              Retrieving data from the SLD server...
              Function call returned exception code     4
              => Check whether the SLD is running!
    2)In SXI_CHACHE cache is obsolete and there is LD_ERROR
    3)In RWB the component monitoring and other stuff when i try to open give and error
           Communication from SLD failed:500 Internal server Error
    I went throught note 764176
    and did the following
    1. In the SLD editing interface, choose "Administration" -> "Content Maintenance". Select "XI Integration Server" from the drop-down menu, and navigate to the associations of the integration server. Select the "XI Integration Server Logical Identity" association and delete the association by choosing 'Remove'.
    2. Switch to "Home" in the "Technical Landscape" view, and select the "Exchange Infrastructure" technical system type there. Select all domains and XI components for the host and delete these by selecting them and pressing 'Remove'.
    3. Restart the J2EE server. After you restart the server, the XI components log on to the SLD again and create a new entity of class "XI Integration Server".
    But after restart none were registered .. i also tried logging into Rep and Dir but these were not registered
    in "Technical Landscape" ->"Exchange Infrastructure"
    Rgds
    aditya

    I have three queries
    1) In SLDCHECK the error i get is
    Calling function LCR_LIST_BUSINESS_SYSTEMS
    Retrieving data from the SLD server...
    Function call returned exception code 4
    => Check whether the SLD is running!
    2)In SXI_CHACHE cache is obsolete and there is LD_ERROR
    3)In RWB the component monitoring and other stuff when i try to open give and error
    Communication from SLD failed:500 Internal server Error
    Firstly are you installing the PI7.0?
    1) In SLDCHECK the error i get is
    Calling function LCR_LIST_BUSINESS_SYSTEMS
    Retrieving data from the SLD server...
    Function call returned exception code 4
    => Check whether the SLD is running!
    check the SLDAPICUST is pointing to correct SLD,
    check RFC destinations LCR*, SAPSLDAPI (check this names in the Intallation document once) are created and working fine.
    Also make sure your SLD is up and running.....
    You need to cross check the JCO connections created.....
    2)In SXI_CHACHE cache is obsolete and there is LD_ERROR
    check RFC destination integreation_directory_HMI is created and working fine.....

  • Error , while running the Template Installer

    Hi Experts,
    I am getting the following error when running the Template Installer in NWA.
    When i trying to save the domain information in CMS , i am getting the following error.
    Unexpected error; inform your system administrator: <Localization failed: ResourceBundle='com.sap.cms.util.exception.CMSExceptionMessages', ID='SLD name-server configuration error', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key SLD name-server configuration error.
    I have seen following  solution in the forums.
    In the SLD->Technical Landscape-> Technical System Type, select "System Landscape Directory" ensure that the SLD server you use has the 'Name Server' check box selected and right CIM Server URL is mentioned.
    But i haven't find this navigation for (Technical Landscape)in my SLD again in that choosing the"System Landscape Directory" . Please let me know the correct path to fix this problem.
    I have logged in to sld
    http://<server>:<port>/sld
    Under the "Home" -> Link having Landscape -> Technical System and Landscapes.
    I have tried in both (Technical Systems and Landscapes)the places , i have nt find the "System Landscape Directory". to see the "Name Server" check box to select.
    Please give the right path to select the respective check box
    Please give the solution . It is urgent.
    Regards
    Vijay

    Hi
    When you use the template installer, the users
    NWDI Administration User
    NWDI CMS Administration User
    NWDI Development User
    are automatically created and they are required. Also the steps to allocate the users to groups are automatically performed
    Check the following help doc for more info
    http://help.sap.com/saphelp_nw2004s/helpdata/en/44/60dc1943c2311ce10000000a155369/frameset.htm
    Perhaps you might try creating the groups manually as described
    Regards
    krishna

  • Error in Saving Domain in CMS

    Hi Experts,
    When i trying to save the domain information in CMS , i am getting the following error.
    Unexpected error; inform your system administrator: <Localization failed: ResourceBundle='com.sap.cms.util.exception.CMSExceptionMessages', ID='SLD name-server configuration error', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key SLD name-server configuration error.
    For this error i have searched in the forms , But some of the people has given the reply that, following need to be implemented for rectify the problem.
    In the SLD->Technical Landscape-> Technical System Type, select "System Landscape Directory" ensure that the SLD server you use has the 'Name Server' check box selected and right CIM Server URL is mentioned.
    But i haven't find this navigation for (Technical Landscape)in my SLD again in that choosing the"System Landscape Directory" . Please let me know the correct path to fix this problem.
    I have logged in to sld
    http://<server>:<port>/sld
    Under the "Home" -> Link  having Landscape -> Technical System and Landscapes.
    I have tried in both (Technical Systems and Landscapes)the places , i have nt find the "System Landscape Directory".  to see the "Name Server" check box to select.
    Please give the right path to select the respective check box.
    Regards
    Vijay

    HI
    Thanks for the reply,
    I searched lot. But i have not able to find the right link for creating the System Land Scape. Canu please forward the link or document which explains step by step process.
    If u have any documents to be forwarded. Please forwarded to following id: vijay00_m at yahoo
    Because of the mail id is not allowed in this form i have give "" as at.
    Regards
    Vijay

  • Not able to import business system in Integration Directory

    Dear all,
    Currently i involved in XI system copy. As per the standard documetn i have finsihed the initial activites like EXPORT and import of abap and java files is succedded.
    Now in the post instalaltion activites.
    I have changed the exchange profile parameter
    SLD connection.
    And other post installation activites succesfully.
    But I am not able to import the business system in Integration director. It throws an error by mentioning.
    *Access to object list of type business system using the internalEOA service business system accessor failed *
    Here we are maintaing a central SLD and hence i created the service users with specific roles.
    SLDcheck is working fine and it dispalying the businees system as well.
    I confirmed that the user and password are same in XI and SLD system,
    But in SLD I am not able to see the domain under web as Exchagne Infrastructure alonng with the componets. I have tried to registerd the same using the note 761476 but in vain. After the changes i restarted the machin and checked the domain status in SLD technical system under exchagne Inffrastructure its not working.
    Is this the problem or am i missing out somewhere?
    FYI: The users are not locked.
    Kindly suggest me and it will be greatful if i get immediate reply.
    Thanks and regards
    Vijay kumar G

    Hi Vijay,
    It looks like the problem is with the SLD.
    Did you delete the SAP ABAP and Java technical system and business systems and recreate them in the central SLD? If this was the case, then you may not be able to import them into your integration directory anymore, as the GUID of the new technical systems and business systems are not the same with the previous one.
    Why not tried to recopy the SLD again, and this time do not change the technical and business systems. If the reregistration of these systems are not avoidable, then you will have to open up the copied IR for configuration.
    Regards,
    Lim...

  • Message Interface not found during Receiver determination

    Hi Folks,
    While doing Receiver determination i found this error
    “Problem Loading Schema Description: Message interface does not exist in any software components installed on this business system”
    i checked it in SLD also for Product assigned to Particular Business System. Even i tried with creating a new one and assigning the product and software component to it.
    When i imported the Business system from SLD, i m not able to see any inbound and outbound interface for particular business system.
    But it is working for another scenario where inbound interfaces are used.
    plz help me out
    Sachin

    Sachin,
    ><i>DEV and QA is having diff. SLD so i created the SWC and products in SLD again.</i>
    You should export the SWCV from your Old SLD and import in into your new SLD.
    and then import the same in Integration Respository.
    When you try to export SWCV from SLD, you will get a .CIM file which you need to save in your local desktop and then import this in the new environment.
    More in this article,
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9e76e511-0d01-0010-5c9d-9f768d644808
    Regards
    Bhavesh

  • Adapter engine missing in the comm channal configuration

    Hi Experts,
    I am creating a File-IDOC scenario. While doing the configuration for the sender communication channel for file adpter the integration server is missing in the adapter engine drop down.
    But when i checked for other adapter type like Idoc and Http adapter, the Integration channel is available in the adapter engine drop down(only for these two apater type only, for other adapters also i am not getting the integration server).
    Can anyone help me regarding this, how to resolve this problem.
    Any SAPnotes or blogs for that.
    Help will be apprediated and rewarded as well.
    Thanks
    Manisha

    hi manisha,
    check the previous reply....the blog is nice
    and also check the note 764176
    check below
    1. Open the "Content Maintenance" view under "Administration" in the SLD editing interface. (in 7.10: the view "CIM Instances".) Select "XI Integration Server" from the drop-down menu and navigate to the associations of the integration server. Select the "XI Integration Server Logical Identity" association and delete the association by pressing the 'Remove' button.
    2. Switch to "Home" in the "Technical Landscape" view, and select the "Exchange Infrastructure" technical system type there. (as of 7.10: "Process Integration".) Select all domains and XI components for the host and delete these by selecting them and pressing 'Remove'.
    3. Start the J2EE server. After you restart the server, the XI components log on to the SLD again and create a new entity of the "XI Integration Server" class.
    4. To register the directory and repository again, you must also log on to the two tools.
    5. Under 'Technical Landscape' in the SLD, select the "Exchange Infrastructure" technical system type. (as of 7.10: "Process Integration") and check whether all XI components (Adapter Engine, Integration Directory, Integration Repository, Integration Server and Runtime Workbench/RWB) are logged on correctly. The Adapter Engine component may be missing. In this case, start the registration of the Adapter Engine as described in Note 1031321, step 2.
    6. Change again to the administration interface --> Content Maintenance (7.10: "CIM Instances") to the associations of the XI integration server.
                  Create a new association by pressing the 'New Association' button, select the "XI Sub-System viewed Application System" associations type here, and, in the next step, choose the BC system for the Integration Server. Save the association by selecting 'Associate'.
                  Create a new association by pressing the 'New Association' button, select the "XI Integration Server Logical Identity" association type here, and, in the next step, choose the business system for the Integration Server. Save the association by selecting 'Associate'.
    7. Under 'Technical Landscape' in the SLD, select the "Exchange Infrastructure" technical system type. (7.10: "Process Integration") and check whether the association to the application system is displayed there (in column "Application System", the business system on which the integration server runs should be displayed).
    8. To make the changed associations known in the directory, the SLD temporary storage must be deleted in the directory. To do this, log on to the Integration Directory and select the 'Environment --> Delete temporary storage areas for SLD data' menu option.
    reward  points if helpfull
    regards
    kummari
    Edited by: kummari on Jul 10, 2008 8:42 AM

  • XI - IDoc - MDMP

    Hello!
    How can XI send IDocs to a SAP 4.6 MDMP system which needs to receive several Asian languages?
    When I change the SM59 settings on XI according to SAP Note 613389 I can send Asian characters to these systems and they are correctly displayed there.
    However, the problem is that it only works for one language at a time, e.g if I put in logon language ZH it only works for IDocs with Chinese characters and if I put JA it only works for Japanese.
    I was thinking I might be able to create several SM59 destinations with different logon languages and then pick the correct one according to the language flag in the IDoc. But it is not possible to reference different communication channels (pointing to different SM59) for the same business system.
    And I also cannot create a new business system for each language because I cannot use same logical system and client in the SLD again.
    Regards, Tanja

    Hi Tanja,
    I do not know if this works, but it may be worth a try:
    Create a new business service as receiver and create an IDoc channel for it.
    In the receiver agreement add a header mapping for the receiver service, where you put the original business system.
    Regards
    Stefan

  • Problem create jco connection in webdynpro application run time

    Hi There,
    I created webdynpro application using rfc model.
    After deploy the project , i created two jco connection
    for data & meta data this is work o.k (test with no errors). the sld is o.k.
    We are using application server (Single Server) for data
    & message server for meta data (Load Balance).
    During run time there is an error message:
    Error stacktrace:
    com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type com.ness.crm.customerlasttwo01pckg.model.types.Datab could not be loaded: com.sap.dictionary.runtime.DdException:
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:205)
         at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init(AttributeInfo.java:471)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:771)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:756)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
         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.progmodel.controller.Component.getCustomControllerInternal(Component.java:433)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:371)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:400)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:138)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:746)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
         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.progmodel.view.ViewManager.getView(ViewManager.java:540)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
         at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:41)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:134)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:374)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
         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.doGet(DispatcherServlet.java:48)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Caused by: com.sap.dictionary.runtime.DdException:
         at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:225)
         at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:180)
         at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:78)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:64)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:39)
         at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
         at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:234)
         ... 44 more
    <u>Can some one help me with this matter?</u>
    Best regards Nir Shohat.

    Hi Nir,
    We also had same problem but no we won't. Check ur config on SLD again and the try to the test connection from the http://localhost:4444/webdynpro ( WAS 6.4 )server.
    If this connection is OK then deploy some small application n see.
    Is ur's JCo connection working for J2ee application?
    Arnigs

  • Adapter Engine Issue in RWB

    Hi,
    I am getting a error in the RWB:
    Self-Test Status: HTTP request failed. Error code: "500". Error message: "Internal Server Error [http://host:port/AdapterFramework/rtc]"
    I have a mail channel setup that is running on this Adapter Engine. I am able to monitor the channel on this Adapter Engine and the channel is collecting mails from the POP3 mailbox and delivering the message to the Integration server. However I am getting the error above.
    Please can you assist to get this matter resolved.
    Many Thanks
    Regards
    Willie Hugo

    Hi,
    This problem is still persisting. I have however not mentioned that we are running PI 7.10 and therefore there is no Visual Administrator only NWA. This was a new install. I have changed all the Host Names to use fully qualified domain names. This is the exchange profile and sxmb_adm, RZ70, sldapicust and in the RFC's user on the ABAP side. Also I have checked out the destinations on NWA and changed the Host Names the to fully qualified domain namesand also the SLD Data Supplier Configuration. I also changed the FQ D names on the JCO RFC Destinations. All well so far.
    I however still has the same error on the Adapter Engine in the RWB. What I have notice though is where the error is displayed in the RWB then the Host Name is not FQ. Where can I correct this?
    Also I have noticed when going into SXI_Cache > Goto > Adapter Engine Cache then there is no cache for the Adapter Engine.
    I have changed the host name of the integration server on the SLD to FQ D names as well.
    I think that I need to delete all the entries for this tech+business system and all the assosiations to it from the SLD and then re-register the whole PI to the SLD again, but is not sure how to do that again.
    Please can any one assist.
    Regards
    Willie

  • Support Package pre-requistis accross different landscapes

    I am struggling with which landscape but be patched before another since adding PI 711 into the mix.
    I am supporting ECC6 EHP4 with NW701, BI 70 at Netweaver 70, Solution Manager 70 Ehp1 and now PI 71 ehp1.
    I have been told PI must lead all other landscapes support package level but with it being at a later version of Netweaver than all other landscapes it is a far comparison or does it already lead them?
    My immediate need is to begin planning for a support package project on the ECC6 EHP4 landscape in the fall.  Since this landscape was last patch, about one year ago we add the PI landscape.
    It is a pretty safe bet I will be struggling with this same question in about 6 months when I start looking at a BI support package project.
    Any help that could be provided on this would be most appriciated.
    Bill

    I think we need to understand more why you feel certain systems need to be patched first or in a certain order
    - from what you say there must be technical concerns across more than one product area
    Perhaps it could be that --->
    Generally systems that interact with one another should be on the same BASIS level and SP stack - the general rule of thumb
    Products such as SLD definately have to be on systems with equivalent or higher BASIS version and SP stack than systems
    they interact with because the content created for a Netweaver 700 SLD
    may not be able to cope data supplier information from a Netweaver EHP1 system (this also raise other concerns regarding
    exporting data between SLDs - again equivalency - or higher for target system is recommended, sometimes with SLD lower BASIS version source systems may have limited export options as well)
    Products such a Solution Manager also as a rule of thumb have to be on equivalent or higher BASIS version or SP levels
    than the systems they interact with
    But PI also may have similiar concerns because they manage communication between systems e.g business systems
    However lets take say Payroll in ECC without any ESS or Legacy Systems, ALE
    - totally standalone payroll system - the only rules that apply there are that it works, has the latest fixes and required legal changes and follows a recommended stack - no BASIS equivalency level between other systems may exist in order for payroll to carry out its purpose
    Does this help clarify further ?
    Best wishes
    Stuart

  • Adapters not showing in Adapter monitorin

    Dear Collegues,
                   we have upgraded from SP14 to Sp17 for our XI.
    Unfortunately, we were unable to view the adapters provided by SAP in Runtime work bench.
    PATh
    RWB:->Component Monitoring->Adapter Monitoring->List of Adapters .
    Can anyone help out of this issue.
    Regards
    Chandra SHekar
    T-Systems India Limited.

    Hi Chandra,
    This may be because of inconsistencies in SLD. Please check OSS note 764176 for this. it has listed out a number of possible solutions for this issue. I have pasted them below. However I would recommend reading the entire OSS notes.
    Solution steps:
    1. In the SLD editing interface, choose "Administration" -> "Content Maintenance". Select "XI Integration Server" from the drop-down menu, and navigate to the associations of the integration server. Select the "XI Integration Server Logical Identity" association and delete the association by choosing 'Remove'.
    2. Switch to "Home" in the "Technical Landscape" view, and select the "Exchange Infrastructure" technical system type there. Select all domains and XI components for the host and delete these by selecting them and pressing 'Remove'.
    3. Restart the J2EE server. After you restart the server, the XI components log on to the SLD again and create a new entity of class "XI Integration Server".
    4. To register the directory and repository again, you must also log on to the two tools.
    5. In the "Technical Landscape" --> Technical System Type "Exchange Infrastructure" view, check whether all XI components are logged on correctly (Adapter Engine, Integration Directory, Integration Repository, Integration Server and Runtime Workbench/RWB). The Adapter Engine components may be missing. If so, stop and restart in the J2EE Visual Admin --> Server --> Services, and deploy application sap.com/com.sap.aii.af.cpa.app.
    6. Change again to the administration interface --> content maintenance for the associations of the XI Integration Server.
                   Create a new association by pressing the 'New Association' button, select the "XI Sub-System viewed Application System" association type here, and in the next step choose the BC system for the Integration Server. Save the association by choosing 'Associate'.
                   Create a new association by pressing the 'New Association' button, select the "XI Integration Server Logical Identity" association type here, and in the next step choose the business system for the Integration Server. Save the association by choosing 'Associate'.
    7. In the "Technical Landscape" --> Technical System Type "Exchange Infrastructure" view, check whether the assignment to the application system is also displayed there (the business system in which the Integration Server is running should appear in the "Application System" column for the Integration Server).
    8. To make the changed associations known in the directory, the SLD temporary storage must be deleted in the directory. To do this, log on to the Integration Directory and choose 'Environment --> Delete temporary storage areas for SLD data'.
    regards.
    Ruchit

  • Do i need a new SWCV and a business system

    Hi Friends
    Do i need a new SWCV and Business suystem for every scenario .
    Let us say i created one file to iDOC scenario with the same sender and same target system
    and now for the same Sender and Reciever i want to create one more scenario which is again a file to idoc
    So for this do i have to do all the stuff in SLD again.
    Thanks

    No you need not create a new technical and business system. You can use the existing technical and business system defined for the same source and target system. You just need to go to the "Objects" tab in ID and add the business system to your scenario.
    As far as technical and business sytem info:
    SLD is based on the CIM model ( Common Information model)
    this model clasiifies the system in terms of SWC, Product, TS, BS to list down....
    TS--> Technical details of the system likeserver name, IP etc....it mostly identifies the system with it's technically ( this gives option to change the TS in future suupose you change the server or its configuration etc)
    BS---> represents the BS usuage identity suppose youa re using the SAP r/3 clnt 100 is sued for develoment activity 200 for QA here the R/3 palys the TS system and 100 200 plays int he Business system....for that particular business wht'a the role of this system......
    Do award points if you feel your query is answered.
    Thanx
    Ravijeet

  • Adapters not found!

    Hi,
    I couldnt able to see any adapters other than JPR.our basis guy imported BASIS package ,I could see Basis component in IR.we did CPA Cache full refresh but still we didnt see any adapters in RWB ->Adapter monitoring.
    he imported Basis pkg that he downloaded from service market place.
    or does it need to be export BASIS SWCV in SLD and import that into IR as .tpz?
    or either of them is fine?
    thank you,
    babu

    hi
    May this will be useful to u.
    notes:
    764176
    804124
    SXI_CACHE
    Solution
    In the Runtime Workbench in the Component Monitoring (hierarchy display),
    check whether all expected components are listed completely.
    The integration server is usually missing in the case of inconsistencies caused by the upgrade.
    Under 'Technical Landscape' in the SLD, select the "Exchange Infrastructure" technical system type.
    Check whether all XI components of the same XI domain are assigned and whether there are several XI domains for the server.
    There may be two domains with similar names, one with a fully-qualified host name and one with a short host name.
    This is an inconsistency.
    Often, the integration server and another XI component
    (directory, repository, or adapter engine) are not assigned to the same domain either.
    You can solve the inconsistencies as follows:
    1. In the SLD editing interface, choose "Administration" -> "Content Maintenance".
    Select "XI Integration Server" from the drop-down menu, and navigate to the associations of the integration server.
    Select the "XI Integration Server Logical Identity" association and delete the association by choosing 'Remove'.
    2. Switch to "Home" in the "Technical Landscape" view, and select the "Exchange Infrastructure" technical system type there.
    Select all domains and XI components for the host and delete these by selecting them and pressing 'Remove'.
    3. Restart the J2EE server.
    After you restart the server, the XI components log on to the SLD again and create a new entity of class "XI Integration Server".
    4. To register the directory and repository again, you must also log on to the two tools.
    5. In the "Technical Landscape" --> Technical System Type "Exchange Infrastructure" view, check whether all XI components are logged on correctly (Adapter Engine, Integration Directory, Integration Repository, Integration Server and Runtime Workbench/RWB).
    The Adapter Engine components may be missing.
    If so, stop and restart in the J2EE Visual Admin --> Server --> Services, and deploy application sap.com/com.sap.aii.af.cpa.app.
    6. Change again to the administration interface --> content maintenance for the associations of the XI Integration Server.
    Create a new association by pressing the 'New Association' button, select the "XI Sub-System viewed Application System" association type here, and in the next step choose the BC system for the Integration Server.
    Save the association by choosing 'Associate'.
    Create a new association by pressing the 'New Association' button, select the "XI Integration Server Logical Identity" association type here, and in the next step choose the business system for the Integration Server.
    Save the association by choosing 'Associate'.
    7. In the "Technical Landscape" --> Technical System Type "Exchange Infrastructure" view, check whether the assignment to the application system is also displayed there (the business system in which the Integration Server is running should appear in the "Application System" column for the Integration Server).
    8. To make the changed associations known in the directory, the SLD temporary storage must be deleted in the directory.
    To do this, log on to the Integration Directory and choose 'Environment --> Delete temporary storage areas for SLD data'

Maybe you are looking for