Is Logical System required for Solution Manager to work?

Hi all
We will be upgrading to SAP ERP in the near future and will have to use Solution Manager.
We only have one company code and no business areas in our configuration. So that, we do not need ALE, consequently, we have not defined/used a logical system.
Do we now need to define a logical system and assign our client to it, in order to use Solution Manager?
tia
Manuel

Hi Manuel,
in logical components the term "Logical System" is used to discribe the combination of system and client in an ABAP system. This does not mean you have to define logical systems in ALE customizing. That is not required as far as I know.
Regards
Andreas

Similar Messages

  • System refresh for solution manager

    Hi All,
    Do you think its possible to do a system refresh for solution manager?
    Even though we do, wont there be a lot of inconsistencies between satellite system and with new solution manager?
    Ideally i need do system refresh of X solution manager to Y solution manager
    Thanks
    Gopal

    Hi,
    How about the consistency between your two X and Y systems. Are they in single TMS. Requests properly transported from X to Y? If its positive, then go ahead you can make System Refresh..
    Feel free to revert back.
    --Ragu

  • Fields required for Solution Manager

    Hi,
    Can anybody knows solution manager message start time and end time fields in any datasource.
    I required these fields.
    Thanks and Regards,
    SGK.

    Hi Manuel,
    in logical components the term "Logical System" is used to discribe the combination of system and client in an ABAP system. This does not mean you have to define logical systems in ALE customizing. That is not required as far as I know.
    Regards
    Andreas

  • Basic Strategy / Best Practices for System Monitoring with Solution Manager

    I am very new to SAP and the Basis group at my company. I will be working on a project to identify the best practices of System and Service level monitoring using Solution Manager. I have read a good amount about SAP Solution Manager and the concept of monitoring but need to begin mapping out a monitoring strategy.
    We currently utilize the RZ20 transaction and basic CCMS monitors such as watching for update errors, availability, short dumps, etc.. What else should be monitored in order to proactively find possible issues. Are there any best practices you all have found when implimenting Monitoring for new solutions added to the SAP landscape.... what are common things we would want to monitor over say ERP, CRM, SRM, etc?
    Thanks in advance for any comments or suggestions!

    Hi Mike,
    Did you try the following link ?
    If not, it may be useful to some extent:
    http://service.sap.com/bestpractices
    ---> Cross-Industry Packages ---> Best Practices for Solution Management
    You have quite a few documents there - those on BPM may also cover Solution Monitoring aspects.
    Best regards,
    Srini
    Edited by: Srinivasan Radhakrishnan on Jul 7, 2008 7:02 PM

  • Requirements for lead management system in sap sd

    hii
    can we maintain lead management system in sap sd module..what are the requirements for lead management system.

    no

  • "You are running an operating system that Lightroom no longer supports. Refer to the system requirements for a full list of supported platforms." Whats the solution?

    Error "You are running an operating system that Lightroom no longer supports. Refer to the system requirements for a full list of supported platforms." Whats the solution?

    again, you need to upgrade your os or use lr5, System requirements

  • System Monitoring in Solution Manager 4.0

    Hi all,
    I want to set up system monitoring for landscape BW, ECC and SCM systems using Solution Manager 4.0 and am new to Sol Man.
    So could anyone please help me with the steps.
    Thanks in advance,
    Sandeep.

    Sandeep,
    Trust me, there is no one resource that you can refer to and complete this system monitoring project. I recently configured this a couple of days ago. I can tell you that I haven't completed it yet. I have only completed the configuring the 'System Monitoring' part of it. I am yet to define monitors so that, I can monitor what I want of the satellite systems. So far, it took me about 4 days. Let me point out the basic steps you need to follow. Beyond that, please refer to the links I paste below:
    Steps to configure 'System Monitoring' in Solution Manager:
    1. Follow the 'Solution Manager Preparation' found under SPRO --> Solution Manager --> Read Me.
    2. Make sure you have the latest ST-ICO and ST-SER installed in your Solution Manager (Note: 892412).
    3. Make sure the Solution Manager has the latest support packages applied.
    4. Prepare the 'Satellite Systems' as per note 455356:
         a. Create the role 'SAP_BC_CSMREG' (if it doesn't exist) with the following authorization objects
              --> S_CCM_RECV (with the objects and values mentioned in the above note)
              --> S_RFC (with the objects and values mentioned in the above note)
              --> S_RZL_ADM (with the objects and values mentioned in the above note)
              --> S_CUS_CMP (with the objects and values mentioned in the above note)
         b. Create a 'communication' user CSMREG (if it doesn't exist) and assign the profile S_CSMREG
    5. Create the user CSMREG in Solution Manager using RZ21 transaction
              -->RZ21 --> Technical Infrastructure --> Configure Central System --> Create CSMREG user (Provide the required password and confirm).
    6. An agent needs to be registered in all the satellite systems that collects the monitor statistics and pass on to the Solution Manager. Before registering the agent in the satellite system, a 'CSMCONF' file has to be generated in the Solution Manager and store it in a central location which, will be used by the CCMS agent while registration. This CSMCONF file holds the communication details for the agent to talk to the Solution Manager. To create CSMCONF file, proceed as follows:
              --> RZ21 --> Technical Infrastructure --> Configure Central System --> Create Start CSMCONF for Agents
              --> Store the file in a central location that can be accessed by the satellite system/s.
    7. In the satellite system, copy the file 'CSMCONF' to the working directory of SAPCCM4X (F:\usr\sap\PD1\SYS\DVEBMGS01\log\sapccm4x - for example. If the 'sapccm4x' folder does not exist, create one).
    8. Copy the downloaded 'SAPCCM4X.exe' file to the kernel directory on the satellite system.
    9. Execute "sapccm4x -R pf=<path of the instance profile>". This should ask for the 'CSMREG' password and the admin user password on the solution manager system. Please input the same and confirm other questions. Upon confirmation, the CCMS agent should be registered in the satellite system.
    10.Make sure you establish the trusted RFC connection on the Solution Manager to the satellite system you would want to monitor. This you can do from 'SMSY' transaction.
    11.After successfully creating the RFC connections, and assigning the system to a logical component, please go to transaction, 'SOLUTION_MANAGER'. You can see the monitored system in the System Overview.
    Below are the reference links:
    Weblogs Related to Solution Manager
    Hope this helps. Award with relevant points if my response is helpful.
    Thank you.

  • ERROR while CREATING RFC FOR SOLUTION MANAGER DIAGNOSTICS

    Dear all,
    Hi,
    I am configuring solution manager 7.0.
    In SPRO>basic setting >operation>solution manager diagnostics > create RFC for solution manager diagnostics i am getting this error
    program WEBADMIN not registerred.
    can any one tell me how to register this program in sap gateway.
    best regards
    azeem

    Hi Azeem,
    Just before creating the rfc connection do this step.
    Set-Up Solution Manager Connection to Solution Manager Diagn
    Use
    Check the connection to function Solution Manager Diagnostics.
    Default Settings
    The function Solution Manager Diagnostics is installed on the Java instance of the Solution Manager system by default.
    Activities
    If the default values are correct, save the settings.
    To run the Solution Manager Diagnostics in another system, enter the required data and save.
    Also check that your java is active.
    Regards
    Ashok

  • Wily Introscope Version for Solution Manager 7 SPS 17

    Hi
    We have a solution manager 4 (now 7) running on an ABAP stack only, this was recently upgraded from Solution Manager 3.2 which was installed 3 years ago as ABAP stack only, this server was never powerful enough to have the Java stack added and the project did not require it.
    I am now looking to migrate this ABAP Solution Manager 7 to a new server, using ABAP & JAVA so I can make use of Solution Managaer tools like Diagnostics, RCA, WILY etc.
    On a sandpit copy I have migrated the ABAP instance to a more powerful server and added the Java Instance from the Solution Manager 4 Installation Master, so I now have a dual stack SM 4, I have patched this to SP17.
    I am looking to install Wily Introscope for monitoring, I have read Note 797147 - Wily Introscope Installation for SAP Customers, where it says you should always use the latest version of Wily, which is 8.0.2, but looking at the note, the downloads for Introscope Enterprise Manager and Introscope Workstation are from SAP SOLUTION MANAGER 7.0 EHP 1, but I am not running Solution Manager on EHP1, I am on SP Stack 17.
    Looking in the SWDC there are downloads in  SAP SOLUTION MANAGER 7.0 -> Entry by Component -> Solution Manager JAVA Stack -> WILY INTROSCOPE ENTPR MGR 8
    Is this what I should be using for my SP Stack 17, or should I use the EHP1 version?
    Also, setting up the Solution Manager Diagnostics, is there a setup PDF for Solution Manager 7 SP17 ? I cannot find a setup guide for this release, most are for EHP1, I would rather not have to implement EHP1 as part of this migration !
    Thanks for any help.
    Paul.

    Hi Bhudev
    Thanks for the reply, I presumed it was the Wily introscope 8 without the EHP1 I required.
    As for installation guide, I have think you have misunderstood my question, I already have the wily installation guide from the note location, I wanted to know if there is any Solution Manager Diagnostics setup guides for SP17 ?
    When I use transaction SOLMAN_WORKCENNTER --> System Monitoring --> Solution Manager Diagnostics --> Diagnostics System --> Diagnostics Setup --> Setup Wizard
    the first 2 (of 23) setups are failing :
    SSO The value of profile parameter login/accept_sso2_ticket could not be checked
    BI Cannot invoke CCMSBISETUP on host localhost
    Warning :
    User(BI) Role SAP_BI_E2E does not exist
    Then it says :
    To complete the Diagnostics Setup, you should perform the following operations as documented in Diagnostics Setup Guide
    I cannot find this Diagnostics Setup Guide for SP17 ?
    The installation guides are mainly for EHP1, media library under sap-ag.de/diagnostics does not show this setup guide, Master Installation guide does not mention it, so was wondering if anyone could point me in the right direction for this guide ?
    Thanks,
    Paul.

  • No EarlyWatch Alert for Solution Manager task in SDCCN

    Hello All,
    We have configured SAP Solution Manager and managed system to generate EWA report.
    In Solman, we have created the system, logical system and solution. We have activated the managed system in Setup EarlyWatch Alert in Solman.
    In Managed system, we have activated SDCCN, assigned BACK RFC, created Maintenance package and refresh sessions.
    However, after completing the Maintenance package task there is no EarlyWatch Alert for Solution Manager task created in managed system. We have reviewed the task logs and found no errors.
    In Solman, when we create EWA for today's date the status is showing with an Hour glass stating that "Wait for session data: SAP EarlyWatch Alert and session number"
    Kindly assist us in fixing this issue
    Thanks in advance
    Regards,
    Satish

    Hi
    the task "early watch alert for solution manager" created automatically when did you perform the task "refreh session" or "Maintenance Package"
    please create the  relevant task, via : SDCCN -> Task -> Create ->Request session data ->Periodic -> Earlywatch Alert -> Continue.
    'Schedule' the start date of the first session  and - Task -- create Click on 'Refresh sessions' - Press 'Enter' - Select 'Now', to schedule the job 'immediately. once you create the relevant tasks you go by,  in the Menu -  Goto -> start - to activate the Earlywatch alert session Now, you can check the finished EWA task in 'done' tab.
    Login to Solution Manager, goto trx. DSWP --> Select your solution, Solution Monitoring - Earlywatch alert -  Click on Earlywatch alert --> start service processing --> Press 'OK' to start the background job - click 'Refresh'
    Now, you can see the 'Early watch alert' in the green colour .
    more further refer here [EWA guide|http://forums.sdn.sap.com/servlet/JiveServlet/download/156-1701991-9166329-1518/EWA_Activation.pdf]
    jansi

  • Same logical system name for two productive systems - BW, PI issues

    Dear all,
    we have a productive system which serves two companies (different company codes). This system is connected both to BW and PI for both companies.
    There is a requirement that these two companies must use their own system, so the whole landscape (dev,qa,prd) will be copied to different systems (different server with different system id).
    As a result of the above procedure we wll have two different productive systems, as required, but we wll have the same logical system name for the two productive systems, which must be both connect to bw and PI.
    However as far as I know:
    - we cannot connect systems with same logical system name to BW,PI
    - we cannot convert logical system name of the one of the two productive systems as they are productive and so this is not supported.
    How can we overcome the problem?
    Please advice.

    > However as far as I know:
    > - we cannot connect systems with same logical system name to BW,PI
    > - we cannot convert logical system name of the one of the two productive systems as they are productive and so this is not supported.
    Right.
    > How can we overcome the problem?
    Since you split up systems (or plan to) I highly recommend booking an SLO service (http://service.sap.com/slo). Those people have to the tools and the knowlege to help you. I would not do this on my own.
    Markus

  • How to create System component in solution manager

    Dear Experts,
    How to Add a new (Custom) system component in solution manager which is used for service desk and also how to replicate the same component while creating  support message (i.e., in F4-help for component filed).
    Thanks in Advance.
    Thanks and Regards,
    *bold* Thirukumaran. R *bold*

    check this blog:
    /people/dolores.correa/blog/2007/10/06/service-desk-solution-database
    basically it is at:
    IMG under SAP Solution Manager -> Configuration ->  Scenario-Specific settings -> Service Desk -> Solution Database
    Nesimi

  • No logical system maintained for party entitled to dispose

    Dear Experts,
    "Party Entitled to Dispose"   field is empty and not editable in the node -
    > "Map Storage Locations from ERP System to EWM" in Interface.
    Here, I am getting the error message "No logical system maintained for party entitled to dispose" .
    I am suspecting, because of the above issue, I am getting another message "Party entitled to dispose SH01 is not allowed in warehouse number INCH"   while creating Outbound Delivery in EWM directly.
    Kindly help me understand how to get rid of this message to proceed further.
    Regards,
    Shetty

    Hi Shashidhar ,
    Kindly guide as how you managed to solve error "
    " No logical system maintained for party entitled to dispose XXX "
    Thanks in advance for your kind cooperation.
    Jinoy

  • BI content for  Solution Manager 4.0

    Hi Experts,
    I want to install BI content for  Solution Manager 4.0 but i don't know what kind of BI content i need and where can i get some information about this.
    if somebody knows somthing , please , let me know.
    Thank you.

    There isn't a lot of standard content for Solution Manager. It's mostly alerts, server, module, database and overall system information for the environments connected to that Solution Manager instance. The standard DataSources are:
    0SM_DSWPBI_BPM                   BPM Data (Alert Data)
    0SM_DSWPBI_DB390               
    0SM_DSWPBI_DB400                DB400 Data
    0SM_DSWPBI_DBADA               Adabas Data
    0SM_DSWPBI_DBDB2               DB2 Data
    0SM_DSWPBI_DBINF                Informix Data
    0SM_DSWPBI_DBMSS              SQL Server Data
    0SM_DSWPBI_DBORA              Oracle Data
    0SM_DSWPBI_MODUL              Module Data
    0SM_DSWPBI_PERF                 Performance Data
    0SM_DSWPBI_SERVER            Server Data
    0SM_DSWPBI_SYSDATA          System Details Data
    0SM_DSWPBI_SYSTEM            System Data
    There are several InfoCubes, one for each DataSource in the standard content. These InfoCubes are then unioned in a standard content MultiProvider.

  • Process for applying for Solution Manager Key?

    I have to install a NW2004s system in a AIX Machine.
    I understand that i need a solution manager key for installation. We dont have solution Manager installed in our Landscape. But i came to know that i can request for a solution manager key from SAP
    Please let me know the website, process for applying for Solution Manager key

    Balaji,
    This is interesting, SAP is pushing customers to have solution Manager installed with features like Solution Manager Key, Maintainance Optimizer etc. It will get difficult for customers who do not have solution Manager running on their site.
    You will have to create support message under the component XX-SER-SMKEY and request for solution manager key, provide them all the details of your system.
    Cheers,
    Nisch

Maybe you are looking for