SLD doesnu00B4t refresh de Logical System

Hi All,
I work on enviroment that had never had an IDOC scenario, because this the Technical System in SLD doesn´t have a Logical System.
So, now the company needs a IDOC scenario, and I created one correct logical system in the BD54 (R3 Receiver), after this I updated the Logical system of the Client in Technical System (SLD).
However, When I check the Business system linked with this Technical System as I said above, the logical system name isn´t updated as I did.
I tried to create other clients in TS to see if the BS refresh, but the Logical system still not showing up in BS.
Am I missing something ?
The BS needs to have a Logical system name and thus I can update the BS in Integration Builder (configuration)
Thanks in Advance.
Diego Crespo
Edited by: Consultores Procwork on May 13, 2009 4:42 PM

Hi
-->While creating technical system as WEB AS ABAP in your SLD you need to maintain the details of your R/3 system like DB Host name,Installation number,Client etc.....While creating TS you no need to maintain any LS.
-->While creating the Business System as WEB AS ABAP along with your name to BS it will ask the LS name and you ned to select your required TS(ie WEB AS ABAP TS).
-->The LS name which you maintained in your SLD must and should created in your R/3 system in BD54 and that LS name should be assigned to client using t-code SCC4.
-->If the LS name which you assigned to your BS is not reflecting in your ID means,
FROM->MENU->Clear SLD.
-->Select your BS and click on button compare with SLD
Thanks

Similar Messages

  • SLD question: When is Logical system mandatory?

    Hi Experts,
          When we create a business system we get a dialog for entering logical system. My question is, for what business system, logical system in mandatory? Is it for ABAP? or third party? or Java?
    What is the real significance of a logical system?
    Thanks
    Gopal

    Hi,
    When your Business System you create is going to be a Web AS ABAP and you are going to use this with the IDOC adapter , then the Assignment of the Logical System Name with the Client is mandatory.
    Otherwise, when you are adding a clinet to a technical system, the Logical System Name is optional.
    Regards,
    Bhavesh

  • XI 3 File to IDoc scenario - Still referencing Old Logical system

    Hi
    Dont know if you can help. I have a file to idoc scenario  using XI 3 to R/3 4.6c system.
    I had the interface working from a third party system XMLHUB to SAP R/3. The Logical system name for the XMLHUB was XMLHUB01 in the SLD which I have set up as a partner profile in R/3. I have recently changed the logical system name to XMLHUBDEV01 in the SLD and created that logical system in R/3 and changed the partner profile to XMLHUBDEV01.
    Unfortunately in the sender information of the IDoc the partner number is still XMLHUB01 and not XMLHUBDEV01. I don't understand where this partner is sent from to get into the control record of the IDoc.
    I have cleared the SLD cache in both the Repository and the directory. Is there somewhere else I should be looking? Any help would be appreciated.
    Regards
    Daniel

    hi daniel...
    this thread wud answer ur query....
    Re: IDOC Payload
    regards..
    vishal

  • Clarification on Logical System naming

    I have a Web AS ABAP Technical system ES1 with a client 100 assigned as a Logical system ES1CLNT100.
    I also have a Business system BS_ES1 running on this with a Logical System name ES1CLNT100 i.e. the same as the technical system (this is a test system and no I did not set this up myself).
    I assume that I need to change the logical system ID of the business system to something different, say BSES1. Is that correct?
    If I use that BS_ES1 business system as the receiving system for IDocs, do I need to enter the logical system name in SALE for the receiving system that receives the IDocs?
    Kind Regards,
    Tony.

    Were you allowed to create 2 Business Systems in the SLD with the same logical System Name? That is strange?
    Even though maybe you can do this at the SLD, when you try to import it into the ID, you will be unable to activate the Business System in ID.
    There can be one and only one business system in the ID that uses one Logical System Name.
    Regards
    Bhavesh

  • Logical system name in business system (SLD)

    Hi,
    While creating business system in SLD what should give for the logical system name?
    Should the logical system name exists in ABAP stack or the new one?
    Thanks.

    Hi,
    If you are creating the BS for SAP R/3 in SLD means we have to give the LS name which we had in SAP R/3( goto SALE and take the LS from there)
    Goto Assign LS-----take the client which you are using for SAP R/3 and take the LS name assigned to that Client
    Regards
    Seshagiri

  • An SLD system has not been assigned to logical system TEC101

    Hello all
    We are trying to send an message RFC or IDOC from our SRM (5.0) system to the XI (7.0). But we allways get the error
    "An SLD system has not been assigned to logical system TEC101". In the SLD the system is visible, sldcheck works.
    Does anyone know this problem and can give me a hint how to fix this problem?
    Thanks a lot
    Stefan

    Hi Stefan,
    Is there a technical & Business System for SRM5.0 in SLD? If entry exists then confirm if the logical system name mentioned in Business System is TEC101.
    If entry does not exist in SLD for SRM, then in SRM run t-code
    1) SLDAPICUST .. Enter relevant details
    2) RZ70 : Give XI Server details , activate and then Execute.
    Once you do that you can see entry for SRM in SLD.
    After that try running the schenario again.
    Regards,
    Sumit

  • Logical System Conversion after system refresh failed

    Hello,
    Logical System Conversion after system refresh couldn't complete as the printer was locked. This job was run in the background. In SM37, the  job log of RBDLSMAP shows as job finished, but it took only 40 seconds. Now I see that the logical system got changed(Converted) in the client settings scc4 but I know that this client being a production client and would run for couple of hours. Here is the job log information.
    02/18/2009 16:09:33 Job started                                                                     00           516          S
    02/18/2009 16:09:33 Step 001 started (program RBDLSMAP, variant &0000000000000, user ID ABCD)      00           550          S
    02/18/2009 16:09:33 Output device PRN1 is locked in the SAP system                                  PO           349          I
    02/18/2009 16:10:19 Job finished                                                                    00           517          S
    When try to rerun bdls again, it shows that it is already available and it says "The new logical system name is already assigned to the current client".
    Any suggestions on this?
    Thanks,
    Mahesh

    Hi ,
    Rerun the BDLS again as this took very little time.
    When you try to run again it popsup message saying it already exists just delete that and again put the Logical system name and run it will run that time.
    May be while scheduling the job you gave for spool I am not sure why is it looking for Printer which is locked.
    Thanks.

  • Logical System not appearing in SLD

    Hello Friends,
    Logical System of SAP R/3 system is not appearing in SLD. The logical system is available in backend ABAP System. I have even run the RZ70 data collection programs as well. However, I am not able to populate the logical system names in SLD.
    I have put the same logical system names in the client tab of the technical system but in vain. The logical system field is non-editable and I believe it is always non-editable unless some technical system is not assigned to it.
    The logical system name is also not available in ID (if it is not in SLD then it won't be in ID as well).
    [The SLDCHECK is throwing exception 4. what to do for this? May be the data is not transfered because of this? Even though I have maintained proper password in SLDAPICUST!!!]
    Request your kind adivse on what can be done. Where can I lookout for possible errors.
    Thanks & Regards,
    Anand Patil

    Hi
    On SLD - > Technical System -> Client -> Logical System Name , generally It is Editable entity .
    If in Your Case , You can not change it, chech with ut basis Guy , for roles and authorisation against your Username ,
    Check the Same SLD Roles with some PI Service  User.
    Regards
    Prabhat Sharma.

  • Logical System Name in SLD

    Hi All,
    I was going through the guide
    https://websmp105.sap-ag.de/~sapdownload/011000358700001410142005E/Configure.pdf
    for the configuration of IDOCS. In this document, they have asked to verify the name of Logical System in SLD. In SLD I cant find an entry for the field Logical SYSTEM(for my client xxx in R/3). Now I do not want to delete the existing bussiness system but edit it to contain the Logical System Name in it.
    Pls help me out.
    Thanks & Regards,
    Jai Shankar.

    Hi
    - Go to Technical System in the SLD.
    - Select the system you want to check
    - Select the client number you want to check
    Here you will find the Logical System Name

  • Logical system name in SLD for the R3 buss. system is not open for input.??

    Dear all,
    We are upgrading to PI 7.1  and have a problem in a scenarie  where PI is sending IDOC to R3.
    The problem is probably related to the fact that it is not possible to write a logical system  name in SLD for the R3 system. I can not read the logical system name for the R3 system into the Directory (adapter specific identifier), *because the logical system for  the R3 bussines system is not an input file??*. How can i enter the logcal system name so i avoid following error:
      <?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>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_RCV_SERV</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Receiver service cannot be converted into an ALE logical system</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Regards Ugur

    There are two ways....
    Option 1 : Go to the BS of ur R3 system in Integration Direction. Go to edit mode mode and select Properties -> Adapter Specific attributes - > enter the LS name and save...
    Option2 : You can use it from the mapping.... U either hard code/use from source the EDIDC40 section of ur mapping and the in ur IDOC receiver config select the option user
    Option ! is the best soln...All the IDOC to that R3 system will go the specified LS...
    regards,
    Arvind R

  • SLD: Adjust / Add logical system name for Business System [XI 3.0]

    Hi,
    In the <b>System Landscape Directory</b>, is it possible to adjust the logical system name of an already created business system?
    I found in the content maintenance in Subset="All Classes", Class=SAP_BCClient" --> <MY_BUSINESSSYSTEM_ENTRY> the only possibility to add information on the logical system name of a business system.
    Unfortunately, the information provided in the BCClient Entry is not forwarded to the Business System Entry for my Business System in the Business Landscape View of the SLD...
    Is there another possibility to add the logical system name to an exisiting business system?
    Regards
    Kristian

    In a third party business system, it is not possible to add a logical system, but you can delete the business system and recreate it with the same name without problems.
    After assigning a new logical system to a business system, you have to go to the integration directory and reload the logical system for the business system. Therefore open the Business System in change mode and maintain the Logical System with menu service -> Adapterspecific Identifiers.
    Regards
    Stefan

  • Logical system missing in PI SLD

    Hi,
    The problem I facing currently during transport of SAP business system from Dev to Quality system, logical system  is missing in the Adapter Specific parameters.
    The actual problem I have seen in the SLD, the logical system is a blank and even after I pushed from RZ70.
    Can you please suggest me how could i retrieve the Logical system in the SLD by automatically.
    Thanks in advance.
    Best Regards,
    Sateesh

    Hi Sateesh,
    Please check the following links for similar issue , if it helps:
    Logical system of PI in SLD
    Logical system name in SLD for the R3 buss. system is not open for input.??
    Logical System Name Not appearing in the Business System
    Also, you can enter the Logical Name in the SLD, for the related TS / BS.
    Regards,
    Azhar

  • SLD - Logical System Management

    Hi,
    We are implementing XI and we have the problem with SLD logical system management. The problem is that we use the same Logical system name (Ex. PRDclnt350) for all the systems to avoid running lengthy BDLS process when we hook our R3 systems to their respective BW systems.
    Can you please suggest how we take care of this in XI -SLD landscape as it requires unique logical system names for each Business System when maintaining in SLD.
    Can we have multiple SLDs and will it take care of the issue. If so can we take one of them as the master SLD and the rest as slave SLDs. What would be the best practices for synchronizing them. Any help in this regard is greatly appreciated.
    Thanks and regards..
    Haritha

    Hi All,
    We opened an OSS note with SAP regarding this. Please see the question we asked and the response we got from them regarding the SLD maintenance:
    Hi,
    We are on BW 3.5 and SAP ERP 5.0. We are implementing XI now. So we
    need to configure SLD and register our Business systems. The problem is
    we have the concept of using the same logical system for all our SAP
    systems, say WRPCLNT750, when we are hooking our systems to their
    respective BW systems. And in SLD, we have problem becuase of this, as
    it recommends to have unique logical system name for each Business
    System being registered.
    We want to mention some points in here about our landscape and some of
    the recommendations we got from SAP regarding this. Ours is a very big
    warehouse system and in order to avoid the lengthy "BDLS" runs, SAP
    recommended using the same Logical System name for all the SAP systems.
    Hence we are using the same logical system name for our systems.
    So now coming to our problem, can you please tell us what would be the
    best practice that needs to be followed now for SLD Business System
    registration. How can we overcome the hurdle of NOT having a unique
    logical system name for our systems in central System Landscape
    Directory.
    Please let us know the solution as early as possible.
    Thanks and regards..
    Haritha.
    The Response:
    Hello Haritha
    I have found some pass cases with the same question that you have,
    however, the replies from developer are as below.
    Logical systems cannot be duplicated within the SLD, that means one
    Business System per Logical System name, both need to be unique, the SLDis working a designed here.
    I would suggest you rename one of the copies of the productive system
    to solve this.
    My apology that I couldn't provide you a better answer for this.
    Thanks & Best Regards
    Andy Lam
    Active Global Support - SolMan & Technology
    Kindly, please let me know your suggestions.
    Thanks and regards..
    Haritha.

  • SLD Logical System Name Changes not taking effect in IDOC

    All -
    I've had to change a logical system name in the SLD, everything appears to be okay but new Idocs are still posting with the old LS name - any suggestions as to where to look for the old name would be most appreciated.
    Thanks!

    Hi Dennis,
    After changing the logical system name in SLD have you done "Compare with  SLD" from Service --> "Adapter-Specific Identifiers" for Business system in Integration Directory?
    - Pinkle

  • ATTRIBUTE_INV_SND_SERV (partner number different of SLD logical system)

    Hi,
    I'm implementing an interface with XI 3.0. In my scenario, I've created one IDOC communication channel. and i try to send some data from file (File --> XI --> IDOC R/3)
    I am using a XSL mapping to build an Idoc-XML from this input file and I'm filling the sender and receiver partner name (different of the default logical system of SLD)
    In a first test, the Idoc adapter changed the partners name by the default ALE name of SLD, then when Idoc couldn't be processed in R/3 system because EDI partner was not customized. We would like to use the logical system of our mapping instead of the logical system froM SLD.
    Then, I've applied next changes:
    - I've checked "Apply Control Record Value from Payload"
    - I've changed the Header mapping, indicating:
            Sender service as XPath = ..../SNDPRN
         receiver service as XPath = .... /RCVPRN
    - The schema as ALE#LS
    But althought these modifications, we are having this error in the monitoring (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>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to convert sender service to an ALE logical system</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
      Please, i would really appreciate if anybody of you can help me to fix this problem.
    Thanks in advance,
    Gerardo

    Hi michal,
        I've reviewed your weblog and it's very helpful as verifications guide.
        We've imported the Business system from the SLD, but we don't want to use its logical name. We would like to use the logical name of our XSL mappings.
        We've also checked the receiver agreements in SXI_CACHE, and both seems to be ok:
    ReceiverService     /.../IDOC/EDI_DC40/RCVPRN
    SenderService     /.../IDOC/EDI_DC40/SNDPRN
        And as last step, we've applied oss note 791181, but i have still the same error message ATTRIBUTE_INV_SND_SERV.
       Anyway, thanks a lot for you help. Please, if you have any more idea, please, i would really appreciate your help.
    Regards,
    Ger

Maybe you are looking for

  • Running disk utility resulted in an error... what should I do next?

    My MacBook Pro wasn't booting up today. I was getting the spinning wheel and after a minute or so it would restart, and it just continued to restart like that. Looking through the forums, I found some steps to take including starting in safe mode whi

  • What is this virus and how to get rid of it

    My laptop has had this strange system malfunction ever since I opened a bad video link. (And I know it's not an iMac, but I read that this would be a better forum for my problem, and I hope the system is the same.) I'm not sure when this started happ

  • Problem in migration of sybase triggers

    Hi, I am using version mwb 1.3.1 version. sybase 11.5, oracle 8.1.7 I came across the following problem Assume in sybase, you have database DB1, table TAB1 and trigger TRIG1. The code in trigger TRIG1 refers to a table TAB2 which is another database

  • LR5 Watermarks presets saved but linked png signature file lost...

    hello, I work recording the lightroom settings/presets in library folder rather than in the os user settings. I switched from PC (7) to Mac (Mavericks) and I could open my catalogs on mac keeping the majority of my settings and preferences. Except fo

  • Sony NEX 7 - when will Aperture support RAW formats?

    Just got my Sony NEX 7, but the RAW files are unsupported. The camera has been around for a while, so when will Aperture provide an update?