Product Definitions in Solution Manager 4.0

Hello,
This is a question about the 'Product Definitions' displayed using transaction SMSY in Solman 4.0.  When I click on product 'SAP ECC', I'm shown 2 product versions, SAP ECC 5.0 and SAP ECC 6.0. When I double click on SAP ECC5.0, I get to see a lot of form tabs, for exmaple, Frontend GUIs, SAP Best Practices, SAP ECC Server and so on.   But when I double click on SAP ECC 6.0, I do not get to see the form tab I'm looking for and that is 'SAP Best Practices'.  Can anyone please tell me where to find this for ECC6?   I've tried searching for this but couldn't find anything relevant ....
We have Solution Manager 4.0 on stack 6.
Thanks,
Renuka.
Renuka.

HI,
what version of ECC are you using?
Thanks,

Similar Messages

  • Error - Update Product Data in Solution Manager

    Hello,
    We are currently downloading the Enhancement Package 4 in SOLMAN via Maintenance Optimizer, however, after choosing the Technical Usages in step 2.1, it shows an error in step 2.2 (Select OS/DB Dependent Files):
    Error : Update Product Data in Solution Manager
    Has anyone encountered the same problem? Would it be fine to continue on the next step after selecting the files which you need for your operating system-database combination.
    Any information is highly appreciated. Thank you.

    Hi Jaypee,
    Check guide How-To Install EHP4- A practical guide. Solution of this problem is documented there. you can download it from http://service.sap.com/erp-ehp
    Extract from this guide for this problem:
    Make sure that you update the product data in SAP Solution Manager. This is described in SAP Note 1277035 which is referenced from the collective SAP Note 1122966. If you do not update the product data, you might get an error message after the stack calculation. The message text explains the problem in more detail.
    Thanks
    Sunny

  • Production SLD in solution manager

    Hi,
    I have small doubt regarding SLD (System Landscape Directory) in Solution Manager.
    We have an Production SLD in Solution Manager dual stack system, and our Production System (Portals, BI, ERP, PI) was configured to Production SLD in Solution Manger.
    We are planning to apply patches for our live production Solution Manager System, I know that SLD will stop while doing the Patches on Solution Manager and this will make our production systems stop working.
    Therefore I need to know the correct way around this to allow us to patches for our Solution Manager system.
    Thanks and Regards
    Pavan Morishetty.

    Joshi,
    Thanks for your quick reply.
    But in our company we don't want to change our Production SLD from Solman system to any other System (eg. PI, Portal).
    If you any other suggestion please update me for applying the patches in Solman System.
    Thanks and Regards
    Pavan

  • How to remove Production System from Solution manager.

    Hi All,
    We have Three system landscape and solution manager installed.
    All the system are managed by Solution manager.
    here we are looking to remove the Production System from Solution manager.
    as in case if is there any problem in solution manager then we are not dependent on it.
    things will work directly on Production system.
    Could you please let us know the procedure to remove the system from solution manager.
    Please let us know if is there any document provided by SAP.

    Hi,
    Have you implemented charm,ccms monitoring or any other functionalities?
    if yes,.Delete the sytem from tms domain. and TR route needs to be adjusted, if you are using ccms, remove the agent details from RZ21 also.
    Does your production system data coming from SLD?
    if yes, Delete the entry from SLD
    if both the answer is no.
    1.delete  RFC from SOLMAN to the production systems.
    2. delete the production system using SMT2 transaction.
    3. Remove system rom SMSY from SOLMAN.
    Thanks,
    Jansi

  • Configure microsoft products in Sap solution manager

    Hello,
    can any one tell me how to configure different microsoft products in sap solman.
    As well as configure powerpoint desk in SOLMAN.
    Thanks in advance.
    Regards,
    Ramkrishna

    ramkrishna borhade wrote:
    how to configure different microsoft products in sap solman.
    As well as configure powerpoint desk in SOLMAN.
    Ellaborate your requirement!! What do you mean by configure???
    Feel free to revert back.
    -=-Ragu

  • RFC Connection Problem between Production Server & Solution Manager

    Hi,
    I want to make a RFC Connection between Production Server & Solution Manager.
    But when go through Tcode- SM59 and click on Remote Logon from Production to connect Solution Manager it showing me a  Client/Userid/Password window and when i connect go through Solution Manger to Production Server it connects normally. I already done the same process in both the clients, as i already mentioned Logon details in the Logon/Security tab but why it is showing me Client/Userid/Password pad when i am login through Production to SolMan?
    +Tell me where the actual problem is! In my Solution Manager end or in my Production Server end +
    I want to access Solution Manager from Production Server on just clicking once on Remote Logon from Tcode- SM59.
    Thank you.
    Edited by: varun@pcl on Jul 31, 2010 4:40 PM

    Hi
    Mention which Client u login and valid username and password from both PROD Server and Solman .
    https://websmp201.sap-ag.de/support under Solman manager .
    https://websmp201.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000633637&
    Regards

  • Intergaration Solution Manager with Peregrine's ServiceCenter 6.0

    Hi,
    We are planning to integrate Peregrine's ServiceCenter 6.0 (HP product) with SAP Solution manager service desk and change request management.
    Our idea of integration is that we will integrate the Peregrine's ServiceCenter 6.0 with Solution Manager where Solman will manage the service desk for any incident ticket raise by Peregrineu2019s Service center, application, transport request and etc.
    u2022     I would like to know whether anyone has integrated Peregrineu2019s service center with Solution manager before? What is your advice?
    u2022     Any suggestion on the process?
    u2022     It this process can be carry out?
    Thanks!!

    Hello MeiYen Cheng ,
    SAP Solution Manager can be integrated with a Third Party Service Desk tool.
    As of Release 4.0, SAP Solution Manager includes an open interface for exchanging messages with help desk systems from other providers. The purpose of the open interface is to act as a central access point for reporters and support employees. It allows you to integrate the SAP Solution Manager service desk into existing help desk systems. Messages are exchanged via Web services for simple, flexible, and platform-independent operations.
    I have attached a PDF file here which explains the scenario.
    For more information on SAP Solution Manager service desk please refer to the SAP Help Portal (help.sap.com -> SAP Solutions -> SAP Solution Manager -> SAP Solution Manager [current release] [Choose language] -> Service Desk).
    Regards
    Amit

  • Own Forum for Solution Manager

    We are implementing the Change Request Manager part of the SAP Solution Manager, and are still navigating on the high seas.
    So I had a look at the SDN if I can find some useful tips.
    I found contributions in Web AS general, CRM, Netweaver Platform, Other SDN Questions, ...
    Business Process Management (BPM) should be the right one, but it seems to be too generic for this complex and by its own nature difficult to isolate product.
    So I suggest an own forum for the SAP Solution Manager, easy to be found by everybody, where all problems can be concentrated.
    Thanks for your kind attention!

    Hi Craig & Hi Mark,
    Until the Solution Manager Forum is up and running, I have a small question that I'm hoping you can help me with.  I am currently evaluating Solution Manager as more than just a "technical communication channel" between client and SAP.
    I would define my work tasks as being functional, and see a wonderful opportunity to use SolMan as the name of the product advertises: a solution manager (integration of the roadmap, IMG, business blueprint, project management, monitoring, help-desk, etc.).  Where I work, this would translate into integration of the functional and technical personnel.
    I've heard from a previous presentation that the 3.1 version had certain issues.  I was wondering if the ramp-up 4.0 of December would have "smoothed" out these issues.
    I was reading in the forum all I could find on SolMan, and came across this thread which seems to indicate that SolMan is still primarily a "technical communication channel".
    Re: ASAP roadmaps in Solution Manager 3.1
    Can I get input for the 4.0 ramp-up?

  • Create a Support Message in Production system showing up in Solution Manage

    Has anyone setup the link between creating a support message (under help) in a production system (like ECC) and SAP's Solution Manager.
    I understand that it uses BADI SBCOS001 with the interface method PREPARE_FEEDBACK_BO, but when I try to run it, it tells me that Customizing for feedback functionality missing. What functionality is missing? And how to I correct this? And how do I ensure it shows in SAP Solution Manager under a solution or project?
    Thanks
    Paul

    Hi Paul
    The only way is to use the IMG. I have just completed this via the IMG info. BUT, it is not that simple.
    Make sure your RFC's are trusted and that you have SAP ALL during config.
    I hope this will help:
    Setup Service Desk
    Steps to follow while configuring support desk.
    1) Implement the note 903587 .
    2) Create all the relevant RFC objects in the satellite system and add the appropriate logical components using transaction SMSY.
    3) Check all the objects in the table BCOS_CUST using transaction SM30.
    Appl : OSS_MSG
    + :W
    DEST :BACK RFC NAME (for solution manager system keep this field as 'NONE')
    + :CUST 620
    + :1.0.
    *4) Check whether the BC sets are activated or not using the transaction SCPR20.If the BC sets are not activated then implement the note 898614.The steps to activate the BC sets are described below
    4.1) Activate SOLMAN40_SDESK_BASICFUNC_000 BC Set.
    4.2) Activate this in expert mode with option u201COverwrite everythingu201D.
    4.3) Activation of the following components has to be done by replicating the previous steps
    3.1) SOLMAN40_SDESK_TPI_ACT_AST_001
    3.2) SOLMAN40_SDESK_ACTIONLOG_001
    3.3) SOLMAN40_SDESK_ACT_ADVCLOSE_001
    3.4) SOLMAN40_SDESK_TEXTTYPES_001
    *Depends upon the number of inactive BC set objects that we have after the upgrade.
    4.4) if the actions mentioned in 4.3 are not listed while executing the transaction SCPR20, then implement the note 898614.In the source client 000 of the solution manager system create a transport request using transaction SE09, unpack the file 'PIECELIST_SERVICE_DESK_INIT.ZIP' from the attachment of the note. Copy the contents of the file 'PIECELIST_SERVICE_DESK_INITIAL.TXT' to the transport request. And activate the actions. Use transaction SCC1 to import the transport request to the solution manager client. If any short dump occurs during the activation, implement the note 939116.
    5) Check whether the number range is set correctly. If not set the number ranges of basic notification (ABA) and the support desk message (Service transaction SLFN).To be able to use the same number ranges for both message types, the internal number range for basic notification (ABA) must correspond to the external number range for the support desk message.
    Number ranges for ABA notifications
    5.1) create an internal and external number range using transaction DNO_NOTIF.
    5.2) assign number range intervals to groups internal and external.
    5.3) SLF1 is the internal number range group
    5.4) SLF2 and SLF3 is the external number range interval
    5.5) Use transaction DNO_CUST01 to assign message categories to the number range.
    5.51) Go to transaction DNO_CUST01
    5.52) From the GOTO menu select the menu item DETAILS
    5.53) Now you can assign the number range of basis notification (ABA) into the notification type.
    The number range for ABA notification is 12 characters in length and to make it compatible with the CRM service transaction insert 2 ZEROES at the beginning.
    Number ranges for Support Desk notification
    5.54) Use transaction CRMC_NR_RA_SERVICE, and define the internal and external number ranges. Intervals must correspond to the intervals of the basic notifications (ABA notification).
    5.6) Then assign both the external and internal numbering
    5.61) Go to SPRO and then to SAP Solution Manager
    5.62) Then select General Settings and then select Transaction types
    5.63) Select the transaction type SLFN and then select the menu item DETAILS from the GOTO menu.
    5.64) In the Transaction Numbering block, assign the internal and external number range. The Number Range object should be CRM_SERVIC.
    5.7) To view the priorities use transaction DNO_CUST01 and select the notification type as SLF1 and then select priorities from the left pane of the screen. The priorities of the first four cannot be deleted, but new priorities can be added.
    6) Check the Action profiles for ABA Notifications (Action profiles are used for synchronization of ABA notification with the CRM Service transaction).
    6.1) To check the action profiles use the transaction SPPFCADM and select the application type DNO_NOTIF then select u2018DEFINE ACTION PROFILE AND ACTIONSu2019.
    6.2) Select the item u2018SLFN0001_STANDARD_DNOu2019 and then from the menu GOTO, select the menu item DETAILS.
    7) The Action profile u2018SLFN0001_STANDARD_DNOu2019 has to be assigned to the message category SLF1 (ABA notifications) using the transaction DNO_CUST01.
    8) The action profile for the support desk message can be set to u2018SLFN0001_ADVANCEDu2019.
    8.1) From SPRO select SAP Solution Manager then Scenario Specific Settings.
    8.2) Select the item Service Desk and then to general settings.
    8.3) Execute the category u2018Define Transaction Typesu2019.
    8.4) Select the transaction type as SLFN
    8.5) From the GOTO menu select the menu item u2018DETAILSu2019 and assign the action profile as SLFN0001_ADVANCED .
    9) Activate the partner/ Organization
    9.1) Go to CRM->MASTER DATA->BUSINESS PARTNER->INTEGRATION BUSINESS PARTNER ORGANIZATION MANAGEMENT->SET UP INTEGRATION WITH ORGANIZATIONAL MANAGEMENT.
    9.2)Find the entries starting with HRALX
    HRALX-HRAC WITH VALUE 'X'.
    HRALX-OBPON WITH VALUE 'ON'.
    HRALX-PBPON u2018ONu2019.
    HRALX-MSGRE u2013 u20180u2019.
    9.3) If entries are not found create it.
    10) Generate Business partner screens
    10.1) Go to transaction BUSP.
    10.2) Execute the report with the following parameters
    CLIENT - Client in which business partners should be created (solution manager client)
    APPLICATION OBJECT-
    SCREEN - *
    Generate all/ selected screens - All screens.
    delete sub screen containers -
    11) implement SAP note 450640.
    11.1) Go to transaction SA38 and select the report CRM_MKTBP_ZCACL_UPDATE_30.
    11.2) Execute it with test mode box unchecked.
    If a new relationship is to be created then steps 12 and 13 has to be followed
    12) To create a relationship category
    12.1) Go to transaction BUBA
    12.2) Select the entry CRMH00: Undefined relationship
    12.3) click on copy
    12.4) Rename CRMH00 to ZCRMH00.
    12.5) CREATE A RELATIONSHIP CATEGORY.
    IN GENERAL DATA FILL LIKE ' FROM BP1 : HAS THE ACTIVITY GROUP '.
    ' FROM BP2 : IS A PART OF ATTUNE
    13) Add the relationship category to the support team partner function
    13.1)Use SPRO
    IMG GUIDE->SAP SOLUTION MANAGER->SCENARIO SPECIFIC SETTINGS->
    -> SERVICE DESK->PARTNER DETERMINATION PROCEDURE->DEFINE PARTNER FUNCTION.
    13.2) FIND THE PARTNER FUNCTION SLFN0003 (SUPPORT TEAM).
    13.3) In the field relation ship category, Select the newly created relationship category and save.
    14) Steps 12 and 13 should be repeated for various business partner types like sold-to-party, message processors if new relationship is to be created for the respective business partner types.
    15) Create a new access sequence for the support team determination
    15.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
    SAP Solution Manager -> Configuration ->
    -> Scenario Specific Settings ->Service Desk -> Partner Determination Procedure ->
    ->Define Access Sequence
    15.2) Click on New Entries
    15.3) Define a new access sequence with sequence name as u2018Z001u2019 and description u2018NEW BP RELATIONSHIP ACTIVITY GROUPu2019
    15.4) Create an new Individual Access with the following value:
    u2022 Batch Seq: 10
    u2022 Dialog Seq : 10
    u2022 Source : Business Partner Relationship.
    u2022 Detail on the source:
    u2022 Partner Function : Reported By (CRM)
    u2022 Mapping/restrictions
    u2022 Flag Mapping/definition for partner being Searched
    u2022 Partner Function in Source: Support Team (CRM).
    Save it.
    This Access Sequence will give us the Partner which has the relationship assigned
    to the Support Team in the Reported By partner data.
    16) Adapt the partner determination schema/Function
    16.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
    SAP Solution Manager -> Scenario Specific Settings ->Service Desk ->
    -> Partner Determination Procedure -> Define Partner Determination Procedure.
    16.2) The two options to adapt partner determination schema are
    16.21) Adapt the standard Procedure (SLFN0001) or to create a new one by copying the standard one.
    16.22) select the line starting with SLFN0001 or the newly created procedure.
    16.23) Double Click on Partner Function in Procedure.
    16.24) Select the Partner Function "Support Team", and click Details.
    16.25) in the detail view only change the Partner Determination/access Sequence to
    the one we've just created. Save your entry.
    17) Create a root organizational model.
    17.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration-> Scenario Specific Settings ->Service Desk -> Organizational Model ->Create a Root Unit for Your Organizational Structure.
    17.2) creating an organizational unit by entering the data in the BASIC DATA tab.
    17.3) enter the organizational unit, the description and save it.
    18) Create the support team organization
    18.1) go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Scenario Specific Settings ->Service Desk -> Create Organizational Objects in the Organizational Structure. Or use transaction (PPOMA_CRM).
    19) Create the business Partners.
    19. 1) Key users- End user (Business Partner General) ,Address should be specified.
    19.2) go to the transaction BP.
    19.3) create a new Person, Select the role: Business Partner (Gen).
    For Identification of the key user
    19.31) click on the identification tab
    19.32) enter a line in the identification number formatted as follows
    IDTYPE : CRM001.
    Identification number : <SID><INSTALL NUMBERS><CLIENT><USERNAME>
    eg: USER NAME : USER1.
    CLIENT : 100.
    SID : ER1.
    INSTALL NUMBER : 123456789.
    IDENTIFICATION NUMBER : ER1 123456789 100 USER1.
    20) Message Processors- Support Team members .
    20.1) they should be created first as the users in the corresponding client of the solution manager.
    20.2) As business partners they will have the role 'EMPLOYEE'.
    20.3) Go to transaction BP .
    20.4) Create New Person with the role employee.
    20.5) In the Identification tab you should enter the user name in the employee data/User Name.
    eg: username: proc1
    enter proc1 in the field User name.
    21) Organizational Business Partner- Organizational BPS have the same country in there main address tab. They should be created through the organizational model. Business partner corresponding to the root organization have the role 'SOLD TO PARTY'.
    22) Assign the business partners (Message Processors) to the previously created support team.
    22.1) Go to transaction PPOMA_CRM.
    22.2) Select the support team 1.
    22.3) Click on create
    22.4) select position
    22.5) call it 'MPROC_T1/Message Processors for team 1
    22.6) Replicate it for the other support teams.
    22.7) Select the position MPROC_T1/Message Processors for team1 and click assign,
    choose owner/Business Partner find and select the business partner
    22.8) Validate and Save it.
    22.9) If the assignment of business partner is not possible then implement the note 1008656
    Or 997009
    23) Create the iBase component
    23.1) IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings -> Standard Configuration of Basic Settings -> Solution Manager -> iBase -> Initially Create and Assign the Component Systems as iBase Components.
    23.2) or use the transaction IB51 to create the installed base.
    23.3) it is also possible to create the SOLUTION_MANAGER, select the solution and go to menu Edit -> Initial Data Transfer for iBase.
    24)Assign Business Partners to iBase Components
    IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings
    -> SAP Solution Manager System ->ServiceDesk-> iBase -> Assign Business Partners to iBase Components.
    *--optional--
    If you want to be able to assign the System Administrator: Go to the IMG: SAP Solution Manager Implementation Guide -> Customer Relationship Management -> Basic Function -> Partner Processing -> Define Partner Determination Procedure.
    Select the entry "00000032 Installed Base/IBase" and double click on Partner Functions in Procedure.
    Then copy the Entry "Contact Person (CRM)" to a new entry with the partner Function "System Administrator (CRM)" , save it.
    Go back to transaction IB52, select a component, and Goto -> Partner, you should be able
    now to assign the partner Function "System Administrator".
    25) Assign the SAP Standard Role to the user. Message Creator should have the role : SAP_SUPPDESK_PROCESS.
    26)Define the transaction variant for the message processors
    Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration -> Scenario Specific Settings ->Service Desk -> General Settings -> Specify User Selection Variant.
    Here we will create variants for the central message processing transaction CRM_DNO_MONITOR.so that the user will have direct access to there dedicated message.
    27) Go to transaction PFCG
    27.1) Enter the role name as Z_MSG_PROCESSORS and choose single role.
    27.2) Give a description Message Processor role and save it.
    27.3) Go to the menu tab and choose add report
    27.4) select the report type : ABAP Report
    27.5) And in the report enter the report name as 'CRM_DNO_SERVICE_MONITOR'.
    27.6) Enter the previously created variant.
    27.7) flag the skip initial screen box.
    27.8) flag the SAPGUI for windows.
    27.9) Create a new transaction with tcode starting with Y or Z.
    27.10)Display this transaction and check the values at the bottom of the screen
    in the subscreen Default Values, you should have the following parameters:
    u2022 D_SREPOVARI-REPORT = CRM_DNO_SERVICE_MONITOR
    u2022 D_SREPOVARI-VARIANT = MY_TEAM_MSG
    u2022 D_SREPOVARI-NOSELSCRN = X
    And also all the user should have the correct role.

  • Solution Manager does not get service definitions from SAP in self diagnosi

    Hi,
    In our production solution manager transaction solution_manager, self diagnosis we are getting a warning message on our development solution manager. 
    Solution Manager XXX does not get service definitions from SAP.
    The production Solution Manager is the master in SDCCN for the test Solution Manager.  In the test Solution Manager, the scheduled task REFRESH SERVICE DEFINITIONS has task System ID of O01.  It is pointed to RFC destination SDCC_OSS, not the production Solution Manager system.
    It gives the same warning if I point the task to the production Solution Manager system.
    Has anyone seen this before?  Any ideas?
    Best regards,
    Russ

    Hi,
      i guess have you activated SDCCN from your solution manager system too?
    if not please activate. since that setup helps solman retrive the service definitions used in SDCCN from SAP (SAPOSS).so this ultimately allows you to set solution manager system as Master, so all the satellite system get the service definition from solman and do not need a direct SAPOSS connection.
    and Please check this Note 1143775 - SAP service content update
    the wiki for trouble shoot ["EarlyWatch Alert is Red Flagged - how to resolve" |http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=228262728]
    please check.
    Thanks,
    Jansi

  • Create New Service Session at Solution Manager = Product System missing

    We have installed SAP EHP 1 for SAP Solution Manager 7.0 last year but not really use it.
    We have setup in the system landscape:
    Server (ecc6sbx)
    Databases (MCD)
    Product System (MCD) => SAP ERP
    Assigned them to logical component (eg ZECC6DEV)
    RFC destination for MCD was generated
    SDCCN Administration at solutions manager display MCD with SDCCN status in green color.
    At the satellite system MCD, SDCCN Maintenance job was created and scheduled. Initial single run was also done.
    There were no issue. Connection to SDCC_OSS was fine.
    Back to the SOLUTION_MANAGER transaction, we created a new solution ECC ERP - Development.
    In the Solution Landscape => Solution Settings, we have assigned the Logical Component into the System Group.
    However when we expand the tree, and click on the Servers folder it did not display anything.
    Click on the Product Systems also did not display anything.
    We have another Solution Manager which display information on those Servers and Product Systems folder for satellite system.
    Going back to the Solution Manager for the Solution ECC ERP - Development, I tried to Create New Service Session for EarlyWatch Alert. When  I click on the Create button, I could only see SAP EarlyWatch Alert for Solutions, there is no SAP EarlyWatch Alert for the Reference Object MCD (<installation number). I could not create a session for MCD.
    Does anyone have ideas what I am missing here? I am trying to attached a document which have print screen for reference while creating this message, but there is no such function here.
    Adding to link to the document file contain print screen
    [Wihtout System and EarlyWatch Selectable.doc|http://www.easy-share.com/1915633524/Wihtout System and EarlyWatch Selectable.doc]
    [With System and EarlyWatch.doc|http://www.easy-share.com/1915633514/With System and EarlyWatch.doc]
    Edited by: Steven Foo on May 24, 2011 8:00 AM
    Edited by: Steven Foo on May 24, 2011 8:18 AM

    Anyway, in the solution manger  how to we setup earlywatch alert for the SM SID host itself (source system)?
    I have the information on the below from our solution manger
    The data for this session is overdue. Data has not yet been transferred from the associated satellite system.
    Go to the Service Data Control Center (transaction SDCCN) in the satellite system and check why the data has not been sent.
    Typical sources of errors are:
    The RFC connection for the SAP Solution Manager system is not working.
    The 'Task Processor' background job, which collects the session data, has been changed.
    Problems arose while data was being collected (see the detail log for the task that collects the session data).
    A periodic 'SDCC Maintenance Package' task has not been scheduled to check whether your SAP Solution Manager system requests session data.
    I tried to go SDCCN on the solution manager itself and look at the Maintenance Service Definitions:
    I get the information:
    No suitable RFC Destination found in SDCCN settings.
    When I click ok I get the following
    No RFC destionation to source system of service definitions available
    Delete Service Definitions (radio button selected).
    I did not continue and cancel it as I did not want to delete anything.
    I check the Task Processor background job is running at SM host itself.
    I managed to get the Maintenance Package job running. However it failed with the following
    Error refreshing service definitions from destination SM_SSMCLNT001_BACK
    Source and target system may not be identical SSM
    The source and target system is the same ==> SSM, will this be an issue?

  • Solution manager configuration for EHP4 install (Product Version Problem)

    Hi guys!
    I'm new on SAP and SDN is a help all days and this time i really need some help from you guys!
    Im installing EHP 4 and need the XML Stack file, so i go to the solution manager to generating them. But after configuring the logical components, make the associations, etc. on create maintenence transaction, the product version dropdownlist is empty...
    It is configured but it dont appears... Anyone had this problem before and could give me some help!
    I will appreciate that!
    My regards,

    Hi,
    In SMSY, the system should have product version as SAP ERP 6.0.
    Next the logical component created for ECC Server should also reflect this version.
    The solution you create in DWSP should include this logical component via the Solution Landscape definition. Here again the logical component should show the product version.
    If all above are in place, the MOPZ for the respective solution should have the product version list populated.
    Regards,
    Srikishan

  • Solution Manager Install on Windows/MSSQL-Dev/QA/Production R/3 on AIX-UNIX

    Hello,
    We are about to install Solution Manager Install on Windows/MSSQL.  Our current R/3 4.7 Enterprise environments (Dev/QA/Production) are installed on AIX-UNIX servers running Oracle 9i. 
    Is installing Solution Manager on a windows environment compatible with our R/3 servers in relationship to our transportation management system existing in a UNIX environment?  i.e. can Solution Manager on windows control transports across our UNIX landscape?
    If so, could someone point me in the direction of documentation/notes on this?
    Thanks,
    Laurie

    You will have to load the Unicode kernel and here is the link to OSS where you can get get the download of SOLMAN for AS/400
    https://websmp110.sap-ag.de/solutionmanager , then choose this one:   ZIP 51033506_7 NW 7.0 SR3 UC-Kernel 7.00 OS/400  Info  550479 24.04.2008 .
    The install manuals are out there as well.

  • Service Definition Refresh in solution manager 4.0 continues infinitely

    Hello,
    I am trying to refresh service definitions through SDCCN in Solution Manager 4.0 but it is continuing infinitely. The status shows that the task is Active.It seems like getting hanged. Task log says only single line :
    " Refresh of service definitions started from destinition SDCC_OSS"
    I have checked my SDCC_OSS and SAPOSS RFC connections. Both seems to be working fine. Can anyone tell me the reason behind this?
    Regards,
    Yashodhan

    Hi Udo,
    Thanx for the reply. Yes I have already checked the authorization by using menu item Utilities->Test-> Authorization test.
    However there is some modifications to this problem now. Yesterday night i left the service definition task running and now in the morning when i am looking at the session log,some "reimport includes" are happening since last night and its more than 12 hrs now  but still the job is running. Below are the first and the last few lines of the log with time stamp:
    *******************LOG*********************************
    16.05.2006 18:32:05 Refresh of Service definitions started  from destinition SDCC_OSS
    16.05.2006 18:42:28 Update of reimport includes started
    17.05.2006 08:18:52 Reimport include successfully generated /1CAGTF/IF_LOGFUNC_000045DB_ORA_TABLESPACE_HISTORY_MONT
    17.05.2006 08:39:42 Reimport include successfully generated /1CAGTF/IF_LOGFUNC_000045DB_ORA_TABLESPACE_HISTORY_WEEK
    ************************LOG****************************
    I don't think this is normal behaviour. How much time does it normally takes?
    Regards,
    Yashodhan

  • Export DVD for product CRM/SOLMAN Upgrade Solution Manager 7.1

    Hello Experts,
    It is my first time doing an upgrade and I have a problem, the SOLMANUP tool gives me: "Enter at least the mount point containing "Export DVD for product CRM/SOLMAN"", I downloaded from SMP the 12 parts of the SAP Solution M. 7.1 Upgr.Export (51039400), I got now 1 .exe file and 11 .RAR files and when I put the path, the SOLMANUP doesnt recognize as a valid mount point, any advices?
    Regards,
    Paul

    Hi Paul,
    Have you already checked note 1577909?
    Note: 1462137 - Add. info. about Upgrading to SAP Solution Manager 7.1
    Please enter mount points for the DVDs required for the upgrade.
    Enter at least the mount point containing "Export DVD for product
    CRM/SOLMAN"
    Please check if the requested Data Carrier is mounted on any of the mount points:
           Path                                     Description
          +                                        +             +
         1 /usr/sap/SMP/SOLMANUP/51042010
         2 /usr/sap/SMP/SOLMANUP/51040039
         3 /usr/sap/SMP/SOLMANUP/51040119
         4 /usr/sap/SMP/SOLMANUP/51040868_2/DVD_OS_
         5 /usr/sap/SMP/SOLMANUP/upgrade_export_dvd
         6 /usr/sap/SMP/SOLMANUP/upgrade_export_dvd
    You will have to download all the archives and then extract them. Please go through the
    SAP Note 886535 for these kind of archives. Once everything is archived
    and extracted, provide the path.
    Thanks
    Regards
    Vikram

Maybe you are looking for