Adding logical systems in SMSY SPQ(Qas),SPP(prd) and SDP(dev)

Hi,
   we are implementing solman 7.1 sp08.
while configuring Managed system for java side SPQ(quality) is added successfully and also generating the EWA reports. But the SPD(dev) and SPP(prd) are not showing the SID while browsing. Please can any help regarding this issue.
Please find the below attached screen shot.

Hi,
Probably they are associated with a different product/software, and in that case, the system cannot match the 3 systems.
Regards,
MM

Similar Messages

  • Reg: Table name where logical system name will store in R/3 and CRM..

    Hi
    We are trying to replicate the sales order from CRM 5.0 to ECC 6.0. we mainatined publication, site, subscription and rfc connections. When the sales order is created in the CRM the BDOC is getting posted but it is picking up the wrong logical system which we were using earlier. Due to this wrong logical system, out-bound queue is getting generated in CRM but In-bound queue is not getting generated in the ECC.
    Can anybody tell me where (in which table) we need to modify the things for getting the correct logical system.
    Regards

    Hi,
    In CRM:  look for the table CRMMLSGUID. This should have the logical system name of the R/3 that it is connected to CRM and also the GUID. To check if the GUID is correct cross check with GUID from R/3 table CRMPRLS.
    In R/3: look for the table CRMRFCPAR. This will give you all the RFC connections that R3 is connected to. If you want to check whether the CRM RFC value is defined correctly compare it with RFC destination in the Administration Console (smoeac) from CRM.
    If the entries are matching then the systems are connected correctly if not you need to look at the RFC destinations from SM59 transaction.
    Hope this helps.
    Thanks,
    Karuna.

  • Logical system on QAS after remote client copy from PRD to QAS

    I wander after remote client copy from PRD to QAS do I have to change Logical system on QAS. Do I have to run some postprocessing program?
    Thank you in advance

    Hi Branko,
    After the system copy, go to transaction SALE -> Sending and receiving Systems -> Logical systems -> Define Logical System , click New Entries and create a new logical system for your QAS; then go to SALE -> Sending and receiving Systems -> Logical systems -> Assign Client to Logical System, click on the client, click change and assign the new Logical system.
    Other activities, check Jobs, RFC's, etc...
    Regards
    Juan
    Please reward with points if helpful

  • Clarifiation : Adding Systems in SMSY - please help

    HI All,
    We have SAP Application server installed on system1 and Databse installed on system2 for a satellite system
    Now when adding the System in SMSY of solution manager under Landscape components:
    1.created a server with hostname  system1(SAP application server), i added system1's FQDN and ip addres in technical data
    2.created another server with hostname system2(Database), added system2's  FQDN and ip address in technical data
    Now under Database-cretae new database- i added SID ,but which server(system1 or system2) should i add in technical data of this
    rgds
    MAR

    Hi MAR,
    don't worry too much about the database data. It is more or less for documentation reasons only.
    Just look at your landscape as it is: the DB resides on the dbserver, so put server2 here. Later on, when you enter your system data (this is important!) you should have two instances for the system SID: Instance one (AS) on server1, instance two (DB) on server2. When creating the RFC connections, it is obvious that they will point to your application server(1).
    Hope this helps you.
    Regards,
    Dirk

  • 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

  • Logical system in CLEAN_REQREQ_UP and BBP_GET_STATUS

    Hi experts,
    Just a very simple question : do you confirm the logical system we have to put in CLEAN_REQREQ_UP and BBP_GET_STATUS variants are that of SRM?
    Thanks in advance.

    Hi,
    CLEAN_REQREQ_UP:
    It checks whether the backend documents (namely-PR/PO/RES) have been created in the backend systems. Deletes obsolete table entries in SRM as well as updates document numbers in the Shopping Cart. You can't process the SC in SRM until this update is complete.
    BBP_GET_STATUS_2:
    It ensures that the information on the back-end documents is up-to-date. Retrieves the updated information from the Back-end systems (for example PO number after it was converted from a PR)
    since both the reports checks and picks up data from backend system, we need to specify RFC for backend systems only.
    -rgds,
    Ravi

  • Could not determine BW release of logical system 'BWPCLNT100

    after a BI systemcopy (production to development) we get the following
    error when we run load jobs of type "delta load". full loads work fine
    "Could not determine BW release of logical system 'BWPCLNT100'"
    even if i start the deltaload from the R/3 system with transaction RSA3
    with update mode "C" i get the same error . when i use update mode "F"
    it works fine , but that's not the thing we want.
    BWPCLNT100 is the logical system of the productive system .
    we have changed all the logical system setting to BWDCLNT100 using
    transaction BDLS and we have also changed all entries in RSBASIDOC,
    RSISOSMAP, RSOSFIELDMAP,.... .
    we have done several systemcopies in the past , they all worked fine
    and without this error. this is the first copy in BI 7.00 .
    are there any loadmodules which have to be regenerated with the new logical system name?
    thank you for your help and kind regards hannes toefferl

    Hi,
    As you said you are getting error after system copy when you are doing the delta load and full load is working fine for you.
    This mainly happens due to init disturbance in the source system.
    I would suggest you to delete the init and rerun the Init from BW once again.
    This should solve your problem.
    Thanks
    Mayank

  • Create Logical System in R/3 system

    Hi all,
       I am  trying to define logical system for xMII server in R/3 system using SALE transaction. But the logical system for xMII server doesn't already exist. So I have chosen to create one. Seems there is format like <sys_id>'CLNT'<client>.
    1) How to create logical system for xMII server in this format?
    2) How does R/3 know in which host xMII server is running? Do we specify that somewhere? Is there any other configurations for linking xMII host and logical system?
    I am new to xMII and so not aware of the steps. Please help me out.
    Points will be rewarded for helpful answers.
    Regards,
    Harini S

    Harini
    Welcome to xMII.
    Though i nvr used such things from the SAP R/3 system side, i think the logical system name format must be something like <b>SAPSYS<Number></b> for SAP Connection <b>BUSCON<Number></b> for Business Connector. After hving defined the Logical System in R/3 System, u need to configure the <b>SAP Business Connector Interface</b> Action in xMII-based Business Logic Services.
    In additional to this, hope this following links will help u to understand more
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3861e693-0e01-0010-e791-9b44d2693e6c
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/201769e0-3174-2910-e287-baa58d198246
    Wait till there comes other some suggestions/solutions for ur quieries
    Best Regards
    Som

  • Logical System and Logical System Name

    Hi,
       I would like to create the following  and please tell me how do I go about doing this. I am doing this because I am trying to implement both RFC/Idoc to File and File to Idoc/RFC. The basis admin guys are unavailble at the moment so I am on my own at this moment.
    Creating a port(I suppose I need to do this on the R3. What are the steps involved)
    Create a Partner Profile

    Hi Sonia,
    For XI communicating with SAP R/3 through Idocs ALE settings need to be done,
    just go through the following steps and Configure ALE :-
    SAP XI
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (IDX1)
    a) Select create new button
    b) Enter the port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Load Meta Data for IDOC (IDX2) a) Create new
    b) IDOC Message Type
    c) Enter port created in IDX1.
    SAP R/3
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (We21)
    a) First Select Transactional RFC and then click create button
    b) Enter the destination port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Create Partner Profile (WE20)
    a) Create New
    b) Create the Partner no. name as same the logical system name of the destination system.
    c) Select Partner type LS
    d) Enter details for Type: US/USER, Agent, and Lang.
    e) Click on the + button to select the message type.
    f) Select Partner no. and LS which ever create above.
    g) Select Message type
    h) Select Process code related to the Message type.
    I) save.
    In SLD – System Landscape Directory
    TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
    Ts for Third Party (Logical system):-
    BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
    BS for Third Party (Logical system):-Enter the XI logical system name.
    In Transaction SALE
    Define and Assign the logical system name.
    Regards,
    Ashwin M
    Reward If helpful

  • Is it possible to chenage logical system and how after a system is beeing u

    Hello
    I wander is it possible to chenage logical system and how after a system is beeing used for a while and how?

    Hello Tina,
    If the system is NOT a production system transaction BDLS can be used to change the logical system.  This would be necessary after refreshing a dev system from a production system, for example.
    If the system is a production system, I would agree that this is NOT advisable.
    Regards
    Greg Kern

  • Wrong logical system for partner profile

    Dear gurus,
    we have been sending ORDERS Idocs for some time now, using to a logical system called MSC_MM_PRD, a RFC connection called MSC_MM_PRD and a port for Idoc processing called A000000003.
    Now, we would like to send ORDERS Idocs to another logical system. We created that new logical system called MES001, a RFC connection (MES) and a Port for IDoc processing using that RFC destination (A00000004).
    After that we maintained a partner profile for the new logical system MES001 with outbound parameters for ORDERS Idocs. So far, so good.
    But then, I had to create a new message type for purchase orders to use that new connection (called ZEDI) and I guess that is where I made a mistake: I copied the existing message type for the old ALE connection and changed some parameters (like name etc.).
    Now, when I create a new purchase order and add a message of the new type and save the order, I get an error message:
    EDI: Partner profile outbound process code not available
    Message no. E0335
    Diagnosis
    An outbound partner profile could not be found with the following key:
    /MSC_MM_PRD/LS//EF/ZEDI//
    [u2026]
    Procedure
    Please check the outbound partner profiles for the assignment of the process code:
    As you can see, SAP tries to find an outbound partner profile using the old logical system (MSC_MM_PRD) and the new message type (ZEDI) as a key and obviously fails.
    Can anyone please tell me why SAP uses the old logical system and how I can change that?
    Cheers
    Alicia

    Hi,
    problem was, that we had not created a proper distribution model for the message type (BD64). After we did that, it worked fine.
    Cheers
    Alicia

  • No Logical System Entry in Business System

    When I will send an IDOC from XI to a target R/3 system, I am getting an error "Unable to convert the sender service to an ALE logical system "
    I checked the threads and the problem seems to be, that there is no Logical System recognised by the Business System.
    I'll checked the logical System in the Technical System in SLD, and it is there.
    I checked SALE, and the entry is in the systems.
    But when I go to the Integration Directory and check System-->Adapter Specific Informations, I see an empty entry for "Logical System". The field stays un-editable and when I hit the "Sync with SLD" button, nothing happens.
    Any idea, how to either enter the logical system or make it recognise the SLD entry?
    Thanks for any hints, points will surely be awarded

    Hi,
    Have you looked int XI FAQ by Michal?
    /people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
    Have a look into the weblog
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    which addresses your problem.
    Regards,
    Jai Shankar

  • Run CLEAN_REQREQ_UP withou logical system

    Dear Experts,
    1) I created some POs from the SOCO.
    2) I deleted the POs and the SC items didn't come back to the SOCO.
    3) I run the CLEAN_REQREQ_UP report with a logical sysem and nothing happened.
    4) I run the CLEAN_REQREQ_UP report without a logical sysem and the SC items came back to the SOCO.
    Do you see some problem to run this report without a logical system?
    We work with SRM 5 and extended classic scenario.
    Best Regards,
    Eyal Weinreb
    HP

    Hi Jay.
    We have the same issue in this moment between our SRM 7.0 EHP 1 y the back-end system SAP ERP ECC 6.0.
    Is the only solution running the report CLEAN_REQREQ_UP without "logical system" ?.
    Regards,
    Martín.

  • Problem Unable to convert the sender service to an ALE logical system

    Hi to All..
    I'm facing a problem in one scenario File to Idoc .. I got this problem
    "Unable to convert the sender service to an ALE logical system" in pipeline Call Adapter.
    I check this blog but the problem persist . /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    Also I have another scenario in other Software Component Version SCW  and the Idoc works correctly..
    I wonder if I miss something
    this the trace
      <Trace level="1" type="T">----
    </Trace>
    - <Trace level="1" type="B" name="CL_IDX_IDOC_SERVICE-ENTER_PLSRV">
      <Trace level="1" type="T">Pipeline Service ID: PLSRV_CALL_ADAPTER</Trace>
      <Trace level="1" type="T">Get Information from IS-Header Objekt</Trace>
      <Trace level="1" type="T">Get Information from SD-IDoc-Endpoint</Trace>
      <Trace level="1" type="T">Sender and Receiver after Header-Mapping</Trace>
      <Trace level="1" type="T">Sender service Sys_XXX</Trace>
      <Trace level="1" type="T">Receiver service Sys_EDV_XXX</Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    Edited by: Luis Ortiz on Jan 25, 2010 3:37 PM

    Hi,
    in order to use only one logical system (PI's) in we20 in ECC and not as many as you have sender systems
    Regards,
    Michal Krawczyk

  • Party/Receiver determination/agreement with logical system

    Hi all
    I have gone thru various messages in the forum dealing more or less with the issue, but haven't really found an answer to my problem yet.
    XML orders from a Web shop are sent to XI, which I am mapping to an IDoc of type ORDERS.ORDERS05 to be sent to the SAP R/3 backend system. The partner profile in the backend system is defined as a logical system because (a) even though the Web shop is for a closed user group of known customers, I could not possible create a partner profile of type KU for every of them, and (b) I need to do some special stuff for IDocs of this order process which is triggered by a separate process code.
    My plan in XI configuration was to create a new scenario and setting up either two parties or one party and a service without party (with a business service). I have tried both ways, but I am not getting it to work. The main reason for that is because of "Unable to convert sender service xxx to an ALE logical system". The "standard logical system" is used in another scenario already, and because of the special processing in the backend, I would like to keep it separate by a logical system defined for this process only anyway.
    Posts with party definitions and logical system problems exist already, but I haven't really found a applicable answer. Can something be done in the header mapping (which I am not so familiar with yet) to get one or the other way to work, or is there another "good" way completely to handle this?
    I am a little bit lost right now, and would appreciate your feedback. Thanks,
    Daniel

    Hi Michal
    Thanks for your feedback. I have implemented the scenario anew based on your input, and other information that I've found. I've got a working solution after playing around with the settings for a while, and is as following now:
    R/3:
    System id: D01
    Client: 200
    WE20: Partner Type LS
    ...Partner no.: XI_ABC
    ...Parter type: LS
    ...Inbound message type: ORDERS
    SLD - Technical system:
    Technical system type: Third-Party
    Name: XI_ABC on xy01sys01cs
    ...Installed products: SAP R/3 ENTERPRISE, 47X200
    ...Business systems: XI_ABC
    SLD - Business system:
    Business system type: Third-Party
    Name: XI_ABC
    ...Related integration server: XD1
    Integration Directory:
    Scenario: CSC_ABC_ORDER
    ...Party: PP_ABC_SYSTEM
    ......Business service: BS_All_Data
    ......Communication channel: CC_S_File_ABC_Order
    ......Adapter type: File
    ...Party: PP_SAPSYS_ABC
    ......Business system: XI_ABC
    ......Adapter-specific identifiers: Logical system XI_ABC
    ......Communication channel: CC_R_IDoc_To_SAP
    ......Adapter type: IDoc
    ......RFC destination: D01_200
    ......Port: SAPD01
    ......NO Apply Control Record Values from Payload
    ......NO Identifiers
    ...Service without Party:
    ......Business system: XI_ABC
    ......Adapter-specific identifiers: Logical system XI_ABC
    ...Receiver Agreement
    ......Sender party: PP_ABC_SYSTEM
    ......Service: BS_All_Data
    ......Receiver: PP_SAPSYS_ABC
    ......Service: XI_ABC
    ......Interface: ORDERS.ORDERS05
    ......Receiver communication channel: CC_R_IDoc_To_SAP
    ......Sender service constant: XI_ABC
    ......Receiver party constant: <space>
    Once again, thanks for your input.
    Regards,
    Daniel

Maybe you are looking for