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).

Similar Messages

  • 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...

  • 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.

  • 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 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

  • Creating a Business system in the SLD

    I am receiving an error message when trying to create a business system in the SLD. The error is "The selected client has an associated logical system nae that is already  used for another business system. Select a different client."
    Here is my issue. The business system that I am creating is for our R/3 4.6C production system. I currently have a business system for our R/3 4.6C quality system. Our prodution and quality R/3 systems do have the same logical system name and client number. This is because we recreate our qaulity R/3 system from our production system.
    So, the question is, How do I create a business system in the SLD for my production R/3 system when the logical system name is used assoicated with and business system.
    I should add that all my R/3 systems have been created as technical systems without any problems.
    Thanks,
    Jim

    It is recommended to have all ALE names unique.
    If it is not possible the following workaround can be used.
    Create one system in SLD (business system/technical system) which contains the ALE name. Proposal: The production system
    Create the other systems(dev/QA) without the ALE name
    During configuration the production system will be configured as usual.
    For Dev/QA systems: Define in the receiver agreement the header mapping and use The Receiver service to reference the production system. Because you reference the production system the ALE name of the production system will be used to fill the idoc.

  • Exporting technical/business systems from one SLD to another

    Hi Experts,
    Currently we have dev/qa SLD and production SLD.  I currently have access to create/modify technical and business systems in dev/qa SLD but when I try to export these technical/business systems the link to export is disabled.  Is there a different security role that I need in order to be able to export the techincal and business systems that have been created in the dev/qa SLD?  I need to export these systems and import them into the production SLD.
    Are there any impacts/differences between exporting/importing and creating the systems manually?  For example if I cannot export the systems would it be ok if I created them again in the production SLD?
    Thank you

    YOu need the authorization for login in SLD as admin
    Follow this link for compete details:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9e76e511-0d01-0010-5c9d-9f768d644808
    Are there any impacts/differences between exporting/importing and creating the systems manually? For example if I cannot export the systems would it be ok if I created them again in the production SLD?
    No differeence...it's just increase the work you have to do in SLD...but the important thing here is when you move the tranports of the SLD BS from DEV to Production you have to maintin the same name as you have maintained in the trnsport targets in the DEV......your ID tranport to Production is dependedn on what is the BS name you are mentinog of production in the transports targets.

  • 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

  • Error while reading access data (URL, user,password) for the Adapter Engine

    Hi,
    Any idea on below message? I am doing file to file scenario and got the below tarce from sxmb_moni.
    <?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="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
      <SAP:P1>af.pi1.piserver1</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>no_messaging_url_found: Unable to find URL for Adapter Engine af.pi1.piserver1</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while reading access data (URL, user, password) for the Adapter Engine af.pi1.piserver1</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Thanks
    Balaji

    It looks like the adapter engine is not able to register him self on SLD, you have to check in the SLD the "Exchange Infrastructure" domain, you have to verify restarting the J2EE the adapter engine update the entries in the SLD related to the specific XI Domain.
    Launch Visual Administrator >> Server >> Services >> SAP AF CPA Cache
    Enter the appropriate values for:
    SLD.selfregistration.hostname (Use fully qualified hostname)
    SLD.selfregistration.httpPort
    SLD.selfregistration.httpsPort
    Sandro

  • Error while reading access data (URL, user, password) for the Adapter Engin

    Hi all,
    I encountered a red flag in sxmb_moni and when I click on the flag, I get the following message:
    Error while reading access data (URL, user, password) for the Adapter Engine
    Is there any way I can resolve this? thanks all
    Regards,
    IX

    Possible reason is Adapter engine is not registered on SLD. Check in SLD.
    You can also try restarting J2EE adapter engine and update SLD entries specific to XI domain.
    Lauch Visual admin go to Server > services > SAP AF CPA Cache
    Enter the appropriate values for:
    SLD.selfregistration.hostname (Use fully qualified hostname)
    SLD.selfregistration.httpPort
    SLD.selfregistration.httpsPort
    Finally, if all the above seem to be correct check the userID / pwd for user ID : PI*.

  • Error: Encountered premature EOF while reading Version (Grid Control)

    Hi all,
    i´am trying to configure a server in my Grid Control, but when i click "Target", select my host, and click in "Configure", the Grid show me that error:
    Error: "Encountered premature EOF while reading Version"
    Please, someone can help me?
    Regards,
    Francisco Conejeros

    whats the oms,agent version and platform
    does installation was sucessfull ?

  • Transport Error while transporting ID TR (Target Business System not found)

    Hi Gurus,
    We are facing a issue with transports while transporting a ID transport to Prod from QA.(We are using CTS+)
    Its our first transport to PROD and we have checked the configuration for BC Application Server in Administration ->Content Maintenance and all looks good .
    Our SLD is looks as below
    We have shared SLD for Dev and QA and it looks as below
    Dev's BS has target business system of QA BS
    And in Prod Sld looks like as below
    QA's BS has target business system of Prod BS
    When we transport from Dev To QA transport works fine but when we transport from QA to Prod its gives below error and in error its points that target for  Dev business system is not found in Target SLD.
    We thought we should try to point Dev BS ====>>Prod BS may be that might work work but its also giving error same error.
    Below mentioned is the Error
    class java.rmi.RemoteException:
    ClientServerException exception:Import failed because of business system transfer of object Service   BS_ACN_MDH_DEV:Obligatory transport target for business system BS_ACN_MDH_DEV not found in System Landscape Directory
    com.sap.aii.ib.core.transport.api.TransportCsException: Import failed because of business systemtransfer of object Service   BS_ACN_MDH_DEV: Obligatory transport target for business system BS_ACN_MDH_DEV not found in System Landscape Directory
    #at com.sap.aii.ibdir.server.transport.impl.postprocessing.TransportPostprocessor.postprocessTransport(TransportPostprocessor.java:741)
    #at com.sap.aii.ibdir.server.transport.impl.postprocessing.DirImportPostprocessor.postprocess30Import(DirImportPostprocessor.java:62)
    #at com.sap.aii.ibdir.server.transport.impl.postprocessing.InternalPostprocessingService.postprocess(InternalPostprocessingService.java:205)
    #at com.sap.aii.ibdir.server.transport.impl.postprocessing.PostprocessingService.doPostprocessing(PostprocessingService.java:171)
    #at com.sap.aii.ibdir.server.pvcadapt.XIDirPropagationProvider.transportFinished(XIDirPropagationProvider.java:90)
    #at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcImport(PvcTransport.java:107)
    #atcom.sap.aii.ibdir.server.transport.impl.pvc.DirPvcTransport.pvcImport(DirPvcTransport.java:74)
    #atcom.sap.aii.ibdir.server.transport.impl.service.InternalDirTransportServiceImpl.pvcImport(InternalDirTransportServiceImpl.java:142)
    #at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:721)
    #at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importXiStream(InternalTransportServiceImpl.java:500)
    #at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importXiStream(TransportServiceImpl.java:265)
    #at com.sap.aii.ib.server.transport.impl.hmi.CmsHmiMethods.process(CmsHmiMethods.java:306)
    #at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
    #atcom.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
    #at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
    #at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl1_0.process(HmisLocalLocalObjectImpl1_0.java:144)
    #at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
    #at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211)
    #at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70)
    #at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
    Can you guys please help out in resolving this error.
    Thanks in Advance.

    Hi,
    I assume you have two SLDs(SLD1 - for Dev and QA , SLD2 - for Prod) and PI 7.0 or XI 3.0.
    In this case the ideal solution would be to
    1. set up a SLD bridge between your Dev/QA SLD and Prod SLD. The bridge basically forwards all the Technical system SLD info to Prod. SLD.
    2. Import Dev business systems information into Prod.
    3. Then create transport target,
    Make sure that you have created Business Groups for Dev/QA/Prod properly
    Edited by: Nageshwar Reddy on Mar 17, 2009 8:29 AM

Maybe you are looking for