The Business-System  from SLD canu00B4t read

Hello,
during export from an configuration object folloging exception occure:
"The Business-System  from SLD can´t read"
It seams all OK ...
Thanks in advance,
Frank

Did you change the name of the Business System in the past? Then you need to keep the old Business System name in the SLD, as during exporting and importing of configuration objects the history of the objects is checked as well.
Regards
Stefan

Similar Messages

  • Error when reading the ID of the business system from the SLD

    Hi,
    I am working on a scenario JDBC - XI - BW (ABAP Proxies). I configured all the steps required to connect XI & BW systems. The SLDCHECK transaction is all green. I was able to connect to SLD from BW using SXMB_IFR tcode too. I was able to look at all the XI Repository interfaces from SPROXY tcode in BW. Created a new ABAP proxy (class interface and method) for the message interface in XI from BW (SPROXY Tcode). Created all required config in XI Directory. Got the message from JDBC adapter, mapping done successfully, and the message failed in the CALL Adapter Step.
    The error is "Error when reading the ID of the business system from the SLD for system BWS and client 100."
    What could have gone wrong. Thanks in advance.
    Srini

    Hi,
    :::::::One Should Have the Following Roles AS A XI Developer With Out Admin Rights ::::::
    1) SAP_XI_Developer_ABAP +
    2) SAP_XI_Developer_J2EE  +
    3) SAP_XI_MONITOR_ABAP   +
    4) SAP_XI_MONITOR_J2EE    +
    5) SAP_SLD_ADMINISTRATOR +
    6) SAP_XI_BPE_MONITOR_ABAP +
    7) SAP_XI_DEMOAPP
    8) SAP_XI_DISPLAY_USER_ABAP +
    9) SAP_XI_DISPLAY_USER_J2EE +
    Regards
    Sesh

  • Error while deleting the business system in SLD

    HI
    I am trying to delete the business system in SLD and encountering the following error .
    if some one has any idea as to why is this error occuring
    java.lang.NullPointerException at com.sap.sld.wd.businesssystem.BusinessSystem.removeXIIntegrationServer(BusinessSystem.java:497) at com.sap.sld.wd.businesssystem.wdp.InternalBusinessSystem.removeXIIntegrationServer(InternalBusinessSystem.java:474) at com.sap.sld.wd.businesssystem.BusinessSystemMainView.RemoveOk(BusinessSystemMainView.java:450) at com.sap.sld.wd.businesssystem.wdp.InternalBusinessSystemMainView.wdInvokeEventHandler(InternalBusinessSystemMainView.java:477) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.clientserver.event.CustomEventProcessor.handleServerEvent(CustomEventProcessor.java:45) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleServiceEvent(WindowPhaseModel.java:361) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:128) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:330) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processPhaseLoop(WebDynproWindow.java:341) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:152) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:297) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:706) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:660) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:228) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47) 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: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)
    Thanks
    Nikhil

    hi Nikhil,
    Null pointer errors are difficult to correct as is
    If you have imported the BS from some other system make sure the BS has been imported correctly without errors & any Tech systems attached to it exist.
    sachin.

  • How to Remove Business System From SLD

    Hi Experts,
    I Created Business System For Web As ABAP.
    While Removing Business System From SLD Means I am Getting the Following Error.
    java.lang.NullPointerException at com.sap.sld.wd.businesssystem.BusinessSystem.removeXIIntegrationServer(BusinessSystem.java:497) at com.sap.sld.wd.businesssystem.wdp.InternalBusinessSystem.removeXIIntegrationServer(InternalBusinessSystem.java:474) at com.sap.sld.wd.businesssystem.BusinessSystemMainView.RemoveOk(BusinessSystemMainView.java:450) at com.sap.sld.wd.businesssystem.wdp.InternalBusinessSystemMainView.wdInvokeEventHandler(InternalBusinessSystemMainView.java:477) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.clientserver.event.CustomEventProcessor.handleServerEvent(CustomEventProcessor.java:45) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleServiceEvent(WindowPhaseModel.java:362) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:129) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:344) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processPhaseLoop(WebDynproWindow.java:355) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:152) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:298) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:705) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:659) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47) 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: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)
    Please Let me know How to Remove it from SLD.
    Regards
    Khanna

    HI Khanna
    Delete the Business System in your IR and ID, if any interfaces are developed under this BS.
    See if any items in locked state...and also after deleting it...activate it and refresh the cache. this shud help
    If you deleted from everywhere then it should not give that message.
    Try after refresh cache using SXI_CACHE.
    Finally Delete the BS from SLD
    In general , that to be you are facing this type of problem only inthis situation , then you have to refresh SLD cache.
    See the below link
    /people/sravya.talanki2/blog/2005/12/02/sxicache--ripped-off - SXI_CACHE
    XI Runtime cache error: Cache contents are obsolete
    Cache Refresh - SAI_CACHE_REFRESH
    /people/sravya.talanki2/blog/2005/11/03/cache-refresh-errors--new-phenomena
    Cheers..
    Vasu
    <i>** Reward Points if found useful **</i>

  • Error while exporting/transporting the Business system from Dev to Quality

    Hi,
    We are getting the following error whil exporting/trsnporting the Business system from development(SLD) env to quality(SLD) environment. The error is
      404   Not Found
      The requested resource does not exist.
      Details:   Go to main page of this application!
    We have followed the following procedure to export :
    1. opened the business system.
    2. Clicked on export option
    3. tried to download
    then we got the above error message.
    Please provide your precious inputs to resove our problem.
    Thanks
    Ramesh

    Go through the following links for transporting XI objects.
    https://service.sap.com/~sapdownload/011000358700001684302005E/HowToSLDandXI.pdf
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/0fa2c490-0201-0010-61b4-df12869c4753
    ere's a good link for what you are looking.
    Re: Transport design and configuration objects
    Here are some blogs.
    /people/sravya.talanki2/blog/2005/11/02/overview-of-transition-from-dev-to-qa-in-xi
    /people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation
    Pls reward if useful

  • Business system from SLD not visible in Integration Directory

    Hi,
    As on the project I do not have access to the SLD, another team created new business systems there. However, when I try in the Integration Builder(Configuration) to assign the newly created systems, I cannot see them on the "Select business systems" page.
    What do you think might be the cause of that? (the SLD and the XI systems are fully customized and have been used successfully until now)
    Thanks in advance,
    George

    Hi,
    In Integration directory -> Environment(Menu) ->
    Click on Clear SLD Data cache and try again.
    If you are unable to get even after doing above step check whether cache is up to date or do full cache refresh. This will solve your problem.
    Regards,
    Sakthi

  • Error while reading ID of own business system from the SLD for system

    Dear all,
    We running on a SAP PI 7.1 enhancement pack 1.I know that there some threads about this subject, but unfortunately all suggestions found so far didn't solve my problem:
    - SLDCHECK reports no errors
    - SLAPICUST: pointing to the SLD
    - SXI_CACHE with full refresh: no result.
    Does anyone have a clue for me?
    Kind regards,
    John.

    I hope you are facing this prolem with one particular Business System.. Since you have checked all the points and still facing this issue then try below options..
    1. First try to clear full SLD cache and then test.
    2. If cache doesn't solve the issue then delete the Business System from SLD and Integration Directory first then re-create the BS in SLD and "Clear SLD Data Cache" from "Environment" menu in Integration Directory and then import the Business System and test your scenario.

  • How to make an entry in transport tab of business system in SLD

    Hi gurus,
    In PI, in SLD we maintain Business systems. In this business sytem if we go to have a detail look there is a Transport tab.
    What is this used for and how to make an entry here.
    I'm a basis person and i'm configuring XI for the first time. Kindly help.
    Regards,
    Priya

    1. Yes , you have to maintain target business system for the EACH BS in PROD system.
    2. Normally we do have 2 different sld one is explictly for production system. another one is for dev and QA system. Once u done creating all the systems needed for the project. we will copy all business from the dev server to production server. So production server will have all BS from Dev and  BS of production server.
    3. i am not sure about this. i dont have particular docuemnts . normally we assign target business system in transport tab. and in Intergration Directory we will export the business system from DEV and and import the business system in production system.
    Regards,
    Balaji
    Edited by: Balaji Pichaimuthu on May 19, 2010 9:06 AM

  • Interface getting failed after changing the Business system to that service

    Hello All,
    Our Env... is XI 3.0 and this is related to produciton env.
    Based on our client requirment to change the business system from client 871 to 100 for  one of the R3 system which is reciever type(rfc).
    After doing all the necessary changes , that particular service is getting failed and in the CC monitoring for that service I can see the log as "RFC_ERROR_LOGIN_FAILURE" mandate 871 (earlier client) does not exist in  the system.
    The steps which I have followed to change the Business system.
    1>I loged into the SLD of PRD system and clicked on businsess landscape .then i have clicked on the specified system to be changed (RY1 ) and then clicked on change mode and selected the required client (100) and saved the settings.
    2>I have logged into ID(Integration Directory) and selected the service (RY1) which need to be changed .Under service -->Adaper specific -->compare sld configurations and then clicked on apply changes.
    3>Now selected that communication channel of service (RY1) RFCRecieverR3 and changed the client 871 to 100 and the password of user XIRFCUSER ...
    Then i saved the changes and after that i have activated that interface.
    After that when i logged into CC monitoring and viewed that service channels and see the following errors:
    Receiver channel 'RFCReceiverR3' for party '', service 'RY1'
    Error can not instantiate RfcPool caused by:
    com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Mandante 871 não existente no sistema (selecionar mandante existente)
    Can any one help me out of this situation , and i need to fix this ASAP as this is production system.
    Awaiting for your reply.
    Best Regards
    Rakesh Reddy

    Hello Nisar
    Thanks for the update,
    Let me say few points  about this particular problem:
    1>The interface "XX" from XI sends data to two systems( R3 -->RP1 & RY1), some thing like branched (same data is passed to both the reciever systems).
    And the second RY1 is copy of First system RP1 (Production sys) which is used for data loading purpose and every week there will be a refresh from First sys (RP1) to Second(RY1).
    2>Now the first sys(RP1) is recieving the data successfully from XI , and the second one (RY1) is getting failed .And this started after changing the Business system 871 to 100 .
    3>As mentioned by you , I have checked all the points mentioned
        i)In SM59 for XI (ABAP part) two rfc's are maintained (LCRSAPRFC & SAPSLDAPI) and the test connection is also fine...But I did not find these two connections in reciever systems(RP1 & RY1 too).
       ii)In reciever system RY1 ,when i went to RZ70 , i did not noticed any special settings and SLD Bridge :Gateway Information is not maitained over there .and the same thing in other reciever system(RP1) , with this can we confirm that there is nothing wrong in RZ70 settings.
       iii)In SLDAPICUST at recievers end for both systems nothing is mantained , where as in XI system all the details are maintained(Host name,port, user & password).
    I have translated the error log into english from the CC monitoring for this interface which is in portuguese language .
    It says that:
    RFC_ERROR_LOGON_FAILURE: 871 Mandante not in the system (select principal existing)
    Kindly advise me what to do ..for fixing this problem(this is pretty urgent and it is production env...)..
    If any information required , I can provide that.
    Best Regards
    Rakesh Reddy

  • SAP XI 3.0 - Error while reading the ID of own business system from the SLD

    Error while reading the ID of own business system from the SLD for system Quality (QOC) and Client 100. 
    I get this error in the SXMN_MONI.  The business process is that the Interface to send master schedule and finished inventory from the legacy system to SAP to create planned orders in SAP for all Plants.
    I could able to get "SUCCESSFULLY PROCESSED" in development and production.  But only in Quality I getting this error.  Could anyone help me to fix this issue.
    thanks...

    Probably, its due to incorrect RFC Adapter properties in config.
    Go to Integration COnfiguration. Double Click on the Business System for your R/3 system. On the right hand screen, Click  on Service-->Adapter Specific Parameters.
    Check whether the Logical System Name comes up as SAP<SID> and whether R/3 system ID and Client are appropriate.
    If these values are inappropriate, make changes to the corresponding Technical System defined in the SLD. After you have made the necessary corrections, come back to Integration COnfiguration, Double click on Business SYstem for R/3. Switch to Edit Mode. Click on Service-> Adapter Specific Parameters and then click on the Icon between Apply and Cancel buttons, inorder to compare with SLD and make those values reflect in config. Then click on Apply and Save the Business System.
    After this, you can retry sending the message.
    Rgds
    R Chandrasekhar

  • Error while reading the ID of own business system from the SLD for system

    Hello,
    I try to send master material data from a 4.7 system via XI 3.0 to an autoID Infrastructure system 2.1. All Communication Channels, Receiver Agreements, Receiver and Interface Agreements are configured. The IDOC gets propper into the XI, Inbound Message is "green". Now, I get the following message:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">SLD_NO_OWN_BS</SAP:Code>
      <SAP:P1>ZTA</SAP:P1>
      <SAP:P2>013</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while reading the ID of own business system from the SLD for system ZTA and client 013</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Can anybody help me?

    Probably, its due to incorrect RFC Adapter properties in config.
    Go to Integration COnfiguration. Double Click on the Business System for your R/3 system. On the right hand screen, Click  on Service-->Adapter Specific Parameters.
    Check whether the Logical System Name comes up as SAP<SID> and whether R/3 system ID and Client are appropriate.
    If these values are inappropriate, make changes to the corresponding Technical System defined in the SLD. After you have made the necessary corrections, come back to Integration COnfiguration, Double click on Business SYstem for R/3. Switch to Edit Mode. Click on Service-> Adapter Specific Parameters and then click on the Icon between Apply and Cancel buttons, inorder to compare with SLD and make those values reflect in config. Then click on Apply and Save the Business System.
    After this, you can retry sending the message.
    Rgds
    R Chandrasekhar

  • Error while reading ID of own business system from the SLD

    HI guys when trying to send Idoc from my R/3 system to SUS i am getting the following error in XI
    <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">SLD_NO_OWN_BS</SAP:Code>
      <SAP:P1>DSM</SAP:P1>
      <SAP:P2>900</SAP:P2>
      <SAP:Stack>Error while reading ID of own business system from the SLD for system DSM and client 900</SAP:Stack>
    I checked in sxmb_adm on both the ends on Xi as well as on my SUS server in Xi the role is the Integration server and on the SUS it is Application server also checked SLDAPICUST which is configured rite. Plz help me to come out of the problem.
    Regards,
    Anand

    Hi Anand,
      check the two thing's in XI.
    1. First created technical system in XI to identify your XI server (Web as ABAP and Web AS Java)
    2. Create the business system based on above technical system and select the role of business system is Integration server.
      URL : http://<hostname>:<ICM Port>/sap/xi/engine?type=entry.
    3. Create the technical system based on your SAP R/3 system.
    4. Create the business system based on your SAP R/3 system.
    here you need to select role of business system : Application system.
      related integration server is : <XI System SID has to come>
    and try to refresh the initical cache once ...
    http://<hostname>:<j2ee stack port>/CPACache/refresh?mode=full
    after all the things post what is the problem you are faceing.
    Regards,
    Venu.

  • Error while reading ID of own business system from the SLD for system D18

    Dear guru's,
    I have almost completed a file2proxy scenario but I'm stuk on the following.
    When sending a message the outbound adapter says:
    <b>Error while reading ID of own business system from the SLD for system D18 and client 200</b>
    What's the problem? I'm using a HTTP connection in the comm. channel. In this http connection a user with SAP_ALL is defined.
    Any suggestions?
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">SLD_NO_OWN_BS</SAP:Code>
      <SAP:P1>D18</SAP:P1>
      <SAP:P2>200</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while reading ID of own business system from the SLD for system D18 and client 200</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>

    Login to system D18 and client 200 and check the TC SLDCHECK and also as per my pervious message check the entries in the SLDAPICUST, it should point to the Server on which SLD is present usually XI server https.
    Actually what happens in this error is when you are done with the configuration part in the ID, you are trying to eceute the scenario File to proxy, when it comes to identify the receiver system which is D18 clnt 200, it goes to SLD to check it and SLD is trying to ping to the machine D18 this connection is set from the TC SLDAPICUST on the machine D18.
    here the problem is that either the D18 is not able to ping to the SLD and also try refreshing the SLD cache.
    Hope you problem is fixed

  • Error while reading ID of own business system from the SLD for system DPI

    Hi All,
    My sceanrio is Proxy to JDBC. and its B2B. am sending the data from BI system and based on the country field from the source, table is decided and value is updated in the table.
    In RWB->Component Monitoring->Adapter Engine->Test Message, I have given the Sender component,Receiver Party,Receiver component,Interface,Interface Namespace,userid and password,Quality of Service and pasted the payload.
    Now I am getting the error :Error While Sending Message: Error stack from response: Error while reading ID of own business system from the SLD for system DPI and client 001 Internal error in Landscape Directory
    Please help me out.
    Thanks
    Kiruthi
    Edited by: kiruthiga balusamy on Nov 24, 2009 4:02 PM

    Hi,
    Check transaction SLDAPICUST for correct SLD configuration.
    http://help.sap.com/saphelp_nw70/helpdata/EN/0b/8512417301ee6fe10000000a1550b0/content.htm
    ~Sanv...

  • SLD Error in IE:Error while reading ID of own business system from the SLD

    Dear Champs,
    Scenario : JDBC to Proxy(APO system)
    We are getting below error in MONI UAT Box. All other interface are working fine but we are facing issue for a particular Bussiness System also logical system are maintained properly.the same interface is working fine in other UAT box.
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">SLD_NO_OWN_BS</SAP:Code>
      <SAP:P1>R/3 Sys ID</SAP:P1>
      <SAP:P2>"Client"</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while reading ID of own business system from the SLD for system "R/3 Sys ID"and client "Clnt no"</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
    Regards,
    Manikandan

    Hi Mani,
    Solution 1:
    Check if the techncal system has associated Business system. I think there is something wrong in your SLD configuration and try to correct it.
    Solution 2:
    Create a Business system in the ID, and create the communication channel do the respective changes in ID ( I.e Receiver agreement, Receiver determination & Interface).

Maybe you are looking for