Deletion of logical system

hi friends ,
i created a logical system long back and i have sent idocs succesfully  from crm system to Tibco System , recently i have deleted this logical system and i created a new logical system , now the problem is if i trigger an idoc , two idocs are getting generated one with previous logical system and another with new logical system , but the previous logical system is not visible in SALE OR BD54 can u please suggest me how it is getting trigered or i need to delete it at some other tcode please suggest
please help me it is very urgent
with Regards
abaper

hi dilip ,
thanks for your reply ,
actually i deleted the old logical system because it is assigned to a client , and added a new one with out assigning to the client and i have changed in we20 also , and its working fine but the thing is that it triggering two idocs one for the new logical system with status 03 and with 0ld  with status 29 or 37 with standard message type CRM_XIF_PARTNER_SAVE AND WITH OLD LOGICAL SYSTEM  so please suggest me how can i restrict the older one , and i am unable to know where the system is picking the older logical system even thought i have deleted in SALE
PLEASE REVERT ME YOUR SUGGESTIONS
THANKS,
SRINIVAS

Similar Messages

  • Client Delete and Logical System and CUA

    I'm getting ready to do some client clean up in prep for an upgrade from ECC 5 to ECC 6 soon.
    Currently we have a 3 system landscape: DV1 QA1 PR1
    Clients on these systems are as follows: (not including 000, 001, 066)
    PR1:100 - the production client
    QA1:100 - Integration Master - not used except for RFC connections for Solution Manager
    QA1:110 - Cycle 1 testing - not used
    QA1:120 - Cycle 2 testing - not used
    QA1:200 - Old training master client - not used
    QA1:201 - Old training client - not used
    QA1:710 - no longer being used for testing
    QA1:720 - client used for system and integration testing
    DV1:100 - Configuration - not used
    DV1:110 - ABAP development
    DV1:120 - Configuration
    DV1:700 - Template for test - not used
    DV1:710 - Test with prod data
    Most have a logical system defined for the client.
    I am going to delete those I've underlined above as they are no longer used.
    Some of these are setup in the CUA system.
    All are showing up in Solution Manager SMSY system landscape.
    My plan is to backup the system database first! 
    Then:
    1) Delete the client(s) (SCC5) one by one
    2) Remove the client from CUA (SCUA)
    3) Remove the logical name (SALE)
    What I am unsure about is the order of the process.  Should the CUA and ALE modifications come before actually deleting the client?
    Does this sound like a reasonable plan to clean up our client landscape?
    Thanks in advance for your suggestions and help.
    Laurie McGinley

    Dear Laurie,
    Order should be like below:
    1) Remove the client from CUA (SCUA)
    2) Delete the client(s) (SCC5) one by one
    3) Remove the logical name (SALE)
    More over you should delete these clients from Solution Manager also inorder not to have error message when you go to solution Manager for doing anything on that system.
    Please revert back for any queries.
    Regards
    Shailesh Mamidwar

  • How to delete a Logical system?

    Hi all,
    I was trying to execute the Demo examples provided as part of SAP XI. Before executing, I am trying to configure the settings, but I created some Logical Systems which didn't configured well.
    So, I want to delete them in order the reconfigure every thing from begening. But I am uable to delete the Old Logical Sustems completely. I am still seeing them in my Integration Builder(Configuration).
    Please let me know is there any way to delete them.
    Thanks,
    Nagarjuna.

    Hi
    How to delete them from Directory?
    I see them under Scenarios(tab) and when i try to delete tem it says that "They will not be deleted and will be available in Objects(tab)".
    Please help me in this.
    Thanks,
    Nagarjuna.

  • Deleting Logical system from BD54

    Hi ,
    I have created 2 logical systems in BD54. now I want to delete that logical systems. When I am trying to delete that logical systems..i am getting the msg " Logical Systems <Logical System Name> must not be deleted".
    Whats the problem nd how to delete it.

    Hi Vijay,
    Goto-BD54--> Click on the Position -->provide you logical system name..Then press enter
    Select logical system which you want to delete----> press Minus symbol in the application tool bar --> enter.
    Thanks,
    Nelson

  • BD54 not allowing to delete logical system

    Hi,
    We did system refersh from Prod to Quality and further we found that while starting BDLS it was not allowing to do so. We got message like <Target> logical system already existing . Further checks revealed that in BD54 that our quality system's logical client entry was already there which would normally come after running BDLS post DB refresh activity for System refresh). Because of this issue we are unable to dlete the quality entry in BD54 and to further start our BDLS acitivty.
    Please to confirm us as we are stuck.
    Thanks & Regards,
    Ashish Robinson
    SAP BASIS Support

    Hi ,
    Thanks all. I resolved my issue.
    Solution:
    1) Removed quality system RFC "STQCLNT002" from SM59 just to b sure nothing was blocking
    2) Also entry of STQCLNT002 needs to be removed  from BD97.
    3) Further if you try to use ENTER when you try to delete entry inBD54 of quality it won't allow ,how many time you may try pressing enter to get away with the warning message. So solution here is to further double clieck on that warning message (in BD54) and see where its blocking . It will show you some method where its blocking .
    4) To locate the method use txn BD64 and scan through the entires to get to the affected link (here it was STQCLNT002).
    5) Be careful, do not delete the entry of STQCLNT002 itseld but actually the corresponding leaves of the methos needs only to be removed to over come the blocking in BD54 (where we wanted to remove the entry of STQCLNT002).
    6) Now goto BD54 and and you can easily remove entry of STQCLNT002.
    7)Now BDLS would easily start.
    Regards,
    Ashish Robinson
    Please grant me point if you find the answer useful. It surely did work for me absolutely fine.

  • Deleting Logical System

    Hi all,
    I created a logical system , now i want to delete it. But while deleting it , it is asking to enter the description for the logical systems which i have not created.
    Can anybody tell me how to delete my own logical system without entering the description other logical systems.
    Thanks,
    Praveena.

    Hi Praveena,
    It is strange, as how could they were able to create the logical system without the descriptions, May be they have maintained it directly in the table TBDLS so other option with you is write a simple ABAP code to delete entry from TBDLS table with the KEY = <your logical system name>
    Reward points if useful.
    Regards,
    Atish

  • How do you identify the Logical system in start routine of a transformation

    My scenario is this.  I have five r3 systems that I am extracting from.   In the start routine of the transformation from the r3 data source to my data store I  am going to delete data and I need to know the source system id.    How do I identify the logical system or source system id in the transformation.  Is there a system field that contains this information.    I do not want to hard code the source system id in the routine.

    hi
    have a lool at tables rsreqdone and rsbkrequest with a join you should be able to determine the source.
    regards
    Boujema
    How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).
    Edited by: Boujema Bouhazama on May 9, 2008 12:04 AM

  • Logical systems in production with CUA

    Hi,
    We have recently implemented CUA and are rolling out ECC 6.0.  We created the logical systems for development, QA, and production in the development system and transported them to QA and production. 
    The solution manager system is the CUA master. 
    We normally only have production logical systems defined in production and would like to remove the development, QA, and solution manager systems.  If we attempt to delete these definitions in production in SALE, it complains that the logical system is still used in distrubution model CUA, although solution manager, not production, is the CUA master.
    If we are using CUA, do we have to have all logical systems defined in all client systems?
    TIA,
    Russ

    Hi Pradeep,
    I don't think that's quite it.  SM1 is the master.  I'm in the production system (PE1) trying to delete the development system (DB1).  I am not trying to delete SM1.  I'm getting the following message.
    Logical system DB1CLNT300 must not be deleted
    Message no. B1199
    Diagnosis
    The logical system DB1CLNT300 is still used in distribution model CUA (client 800).
    System Response
    The deletion cannot be carried out.
    Procedure
    Confirm that the logical system DB1CLNT300 is really no longer used. Delete it first from distribution model CUA (client 800), then delete it here.
    Thanks and best regards,
    Russ

  • 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

  • XI testing for two SAP R/3 systems with same system id/logical system

    Hi
    We are currently in the process of upgrading our R/3 4.7 to ECC 6.0 and plan to maintain dual landscape for DEV & QA (4.7 & ECC 6.0) for a period  for testing and maintaining existing applications for fixes etc. The second DEV & QA (upgraded to ECC 6.0) are copy of respective systems and these systems are created automatically under technical systems in SLD by auto update (RZ70).
    The question is, can we use the same XI system for testing inbound/outbound interfaces for both the systems i.e 4.7 & ECC 6.0 at the same time.  I am aware of the fact that XI Technical/Business sytems dependent on unique logical systems, so we cannot create new business system for the upgraded DEV-II ECC 6.0 system. 
    For your information, we have two slds (one for XID/XIQ and second one for XIP).
    What are the options without disturbing & maintaining the current XI system set up?
    1) Can we change current Business systems e.g DEV010 to use new technical system i.e DEV-II ECC 6.0 for testing for a period and switch it back to DEV-I 4.7 technical system?
    2) or change logitical system name of DEV-II ECC 6.0 and create new business sytem in SLD without interfering the existing setup and modify/create interfaces to use this new business system?
    3) Do we need to refresh cache from time to time in XI ?
    4) Any other implications
    We will be upgrading XI to PI 7.1 after ECC 6. 0 Upgrade.
    Any views on this would be highly appreciated.
    Regards
    Chandu

    Hi
    Technical System was created in the SLD automatically after RZ70 configuration in the new DEV-II system. We then modified Business System to use the new Technical system and carried out following steps:
    1)     Original Idoc metadata was deleted from XID
    2)     The port definition  was deleted
    3)     A new port definition was created for new system
    4)     The metadata for each idoc type used was re-created in IDX2 , using METADATA -> CREATE
    5)     This brought in all known versions of the idoc segments, including the 7.1 version.
    I have already checked the guides suggested for our upgrade and we are thinking of going ahead with fresh installation and migrating the interfaces.
    Regards
    Chandu

  • Logical  system name to be updated while client copy--URGENT HELP REQUIRED

    Hello All,
       I have a  query regarding the "Logical System name" updation during Client copy.
      When we make a client copy(SRM Masters) for the Production system(SRM),the Old Logical system name for backend(which is attached to the SRM masters) gets copied to the new Client (Copy) which needs to be updated.
      There is  a  std transaction BDLS through whcih w e can change the current Logical system name to  a  new one but this  seems to work fine for System copy but not for Client copy.
      So when i make  a client copy of  SRM masters  for Production system,is there  any other std  way wherein i can change the "Logical system name " for the  backend or  do i have  to write a  CUSTOM program wherein entries  for  the Backend Logical system name in tables like CRMMLSGUID will  be updated  with  the new  Logical system name?
       Any help on this is  appreciated.
    Thanks & Regards,
    Disha.

    Disha,
    Yes, I did it twice and it worked fine.
    The R/3 GUID is sent by the OLTP system (R/3) in R/3 message header.
    SRM checks this GUID in CRMMLSGUID table.
    If is not the same one, then replication process fails.
    The only solution I found was to delete this entry. It is automatically recreated with the new GUID with the next replication, with FM CRMT_OLTP_LOGSYS1, called in BAPI_CRM_SAVE.
    Look at OSS note 588701 & 765018 for deletion of CRMMLSGUID.
    The issue is exactly ours: around system/client copy.
    In an CRM environment, this is more critical, because we make a huge use of the middleware. But in our case, and especially after system/client copies, we can go, even if SAP does not guaranty anything, because we don't care about "old" replicated data (I don't care about old BDOCs, that should even be deleted after processing).
    We have to take some risks sometimes...
    Rgds
    Christophe

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

  • PLEASE HELP ME TO FIND THE SOLUTION REGARDING "LOGICAL SYSTEM CHANGED"

    HAI EVERYBODY,
    PLEASE HELP ME TO FIND THE SOLUTION REGARDING "LOGICAL SYSTEM CHANGED" during the material master replication by using middleware parameters.
    step1 : i have taken SRM client 810 and named it as CHINNISRM
    step2 : i  have taken r3 client 810 and named it as CHINNIR3
    step3: During material master replication i maintained tables like crmconsum,crmrfcpar,crmparoltp in   r3   and smofparsfa in srm client and filtered the objects and loaded the objects through r3ac3,r3ac1,r3as.
    step4 : And later i have checked in r3 queues to activate the objects,but i have seen a message like  "LOGICAL SYSTEM CHANGED:SEE 588701".according to the oss instructions i have checked in CRMPRLS table in se16 in R3 .there i found out there is one logical client  named with T90CLNT810.
    oss :588701
    Solution
    There are different cases in which different forms of processing are
    required or where several options exist:
    - The logical system name of an R/3 Backend client was changed in
    current operation. In this case, the data hangs in the outbound
    queues of the R/3 Backend system as specified under point 1 of
    the symptom. In this case, the logical system name must be
    changed back to the original value. Then the outbound queues
    can be reactivated. If no data was transferred to the EBP/CRM
    server before the change, also a correctioin of the check table
    is possible.
    - The same logical system name was used again in a new client of
    an R/3 Backend system that was linked to the EBP/CRM server. In
    this case, the data is in the inbound queue of the EBP/CRM
    server with the exception GUID_FOR_LOGSYS_CHANGED. In this
    case, the queue entries which have status SYSFAIL must be rejected, however, not the entire queues. If the new client of  the R/3 Backend system you have linked has exactly the same
    data as the old client and if it is meant to replace the old
    client (that is, this was deactivated), also a correction of
    the check tables is possible. In this case, the inbound queues
    can be reactivated after the correction.
    oss:765018
    1. If the situation in your system corresponds to the situation described
    under "Reason and Prerequisites" and if symptom 1 occurs, you can
    delete the table entry from table CRMPRLS table (there is just one
    entry). Since there is no maintenance dialog for this table and you
    cannot maintain it using transaction SE16, you must use a report to
    delete it. This report is attached to this note as correction
    instructions.
    Create the report ZZ_DELETE_CRMPRLS in your system and copy the source
    code from the correction instructions. You cannot implement this
    source code using transaction SNOTE.
    You can use the report in every plug-in or plug-in basis system, even
    if it is not specified in the validity section.
    After you have run the report, you can trigger existing queues again
    in transaction SMQ1.
    2. If the situation in your system corresponds to the situation described
    under "Reason and prerequisite" and if symptom 2 occurs, you can
    delete the entry from table CRMMLSGUID (there is just one entry).
    Since there is no maintenance entry for this table and you cannot
    maintain it using transaction SE16, you must use a report to delete
    it. This report is attached to this note as correction instructions.
    If they do not yet exist, add the following messages to message class SMOF in your logon language:
    Message Message short text
    303 User &1 is not allowed to change table &2.
    304 User &1 IS not allowed to display table &2.
    305 Logical system &1 was not found in table &2.
    306 System error! The current client was not
    found in table T000.
    Create the report ZZ_DELETE_CRMMLSGUID in your system and copy the
    source code from the correction instructions. You cannot implement
    this source code using transaction SNOTE.
    You can use the report for every release of the CRM system, even if it
    is not specified in the validity section. The only exceptions are CRM
    releases with Support Package versions that are too low such as CRM
    Release 3.0 with Support Package 12.
    After you have run the report, you can trigger existing queues again
    in transaction SMQ1 of the R/3 back-end system or transaction SMQ2 of
    the CRM system.
    so what should i do to do the replication.please suggest me .untill and unless i solve my problem i cant move to the further activity.i hope you people can solve my problem.thanks in advance.
    thanks and best regards,
    n.chakradhar

    Hi chakradhar,
    Did you find a solution to your issue? We are facing a similar issue and looking to figure out how this can be resolved.
    BR// 420

  • 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

  • Local logical system is not defined-Maintenance Optimizer Config

    Hi,
    When I try to configure Maintenance Optimizer in SAP Solution Manager 7, it gives me an error saying "Local logical system is not defined"
    But I have created a Logical client using SCC4.
    And the other thing is for this created client, does not have any users on this client, If I run,
    SQL> select bname, UFKLAG from sapsr3.usr02 where mandt='400';
    Answer is "no rows selected"
    So I cannot even login in to my new client as well. I tried with SAP/PASS no use. I tried to re-set sap by deleteing it nothing helped.
    my login/no_automatic_user_sapstar parameter also have 0 (But this is in Red, I dont know why its like that)
    Please help me to rectify both these issues. Issue with Maintenance Optimizer and loggin in to the new client.
    Thank you!

    First of all, 'Logical System' and 'Logical Client' are two different things.
    For Client Problem:
    You did create a client in SCC4.
    1. did you create a logical system via BD54 and then did you assign that logical system to this newly created client ?
    2. did you perform a local client copy to put data into this new client from an old or from a standard client like 000 ?
    If you didn't perform above two things, then please do. Only then, you will be able to see some data in this client and will be able to to select statements, And, obviously the SAP*/PASS login (login/no_automatic_user_sapstar should be 0 after reactivation of profile and restart of the instance)
    For MOpz issue:
    Could you please search in sap marketplace for any particular note specific to MOpz ?

Maybe you are looking for

  • IOS 6 and iTunes 10.7 WiFi Sync issues

    WiFi sync works for a day or two then from the device is just keeps saying Looking for Mario Michela's iMac...  I restart iMac, reboot iPhone and or iPad. connect via usb cable, uncheck WiFi Sync (apply), recheck WiFi Sync. It will work again for 2 o

  • Crystal reports on a server without C drive

    Hey all I want to know whether I can run an application built in .Net ; having crystal reports as reporting tool, on a server which does not have C: drive only E: Drive. I ran into the issue of specified path cannot found when try to run on server. I

  • Routing based on destination IP and traffic type

    Is it possible to route traffic based on the destination IP and the type of traffic? ASA5512 Software 9.2.1 We have an ASA 5512 that is used as a VPN termination point. Our employees connect from one of our customer sites to this VPN point. The custo

  • Broken links on the web page :(

    Hi Guys I have been chasing this for a few weeks now & no one seems very interested in the issues with the web site On this web page http://www.palm.com/au/support/treo680/downloads/680mr_win.html Their is a link Download: Treo680_2_12_ROW_desktopupd

  • Automatic restart of SAP J2EE Engine

    Dear Experts, We have a 2004s server. Once in a while the server automatically restarts. When i checked the J2EE Engine tab in NWDS, the SDM, dispatcher and server0 all have a flag called automatic restart and it is set to YES. How do i set them to N