Solution Manager interface

Hi,
Can anyone give me assistance in the following requirement:
When a call is created in solution manager (v4), I need to transfer the data through XI to an external help desk and visa versa.
Where do I start?
Thanks,
Leanne

There does not seem to be any Pre delivered SOL MAN content on the Service market place.
That means you willhave to write some RFC's or Abap proxies on SOL MAN.
The call centre application will probably have to expose a web service for you to consume. If not you will have to do it with some sort of file (FTP) mechanism.
It still will be a bt of work to get this done.
Rod

Similar Messages

  • Solution Manager Interface with Tools Outside SAP

    Does anyone have information on Solution Manager's abilities to interface with tools outside of SAP?  I am interested in interfacing Solution Manager with legacy systems and main frame systems (e.g. Informatica).  I am especially concerned with Root Cause Analysis, Exception Analysis, and Error Reporting in Solution Manager regarding non-SAP systems.  Also, if Solution Manager is able to interface with these systems, can it access details from outside SAP (e.g. data from legacy systems)?

    Hi,
    The solution manager can be interface with the ARIS.We did in our project this interface.
    The Business process flow was defined in ARIS & synchronize with the solman & once configuration is done then we reverse synchronize the same to update the ARIS,so you can interface with legacy also.
    Regards,
    Raj.

  • Solution Manager Interfacing with Remedy

    How do we interface Remedy (Ticketing tool ) to Solution Manager and is it mandate to enable Solution Manager Service Desk  for an effective ChaRM implementation or  can we use the existing Remedy tool interfaced directly to Sol Man.

    Some Discussion about Remedy And Solution Manager,
    Solution Manager - Service Desk + Remedy Integration
    And Yes BMC Remedy can be integrated with solution Manager, so please Contact Remedy to guide you on this one.
    Regards
    Shailesh Mamidwar

  • XML Interface in Solution Manager

    Hi All,
    In Solution Documentation presentation, there are slides that give details on importing documentation from external sources like(Excel) into Solution Manager documentation. Has anyone done this task and what is the interface used to export to standard SAP XML format from EXCEL and import files from XML format into soution documentation (SOLAR01)?
    Details from slides are:
    Using a XML interface business process documentation of external sources like MS Excel, Lotus Notes can be efficiently imported in SAP Solution Manager
    Data transfer process flow:
    Detailed steps
    1. Develop a data extractor program to convert MS Excel to XML document
    - Create a program to extract content from data source. The extractor has to use the  xml schema definitions provided by SAP 
    - Extract the data from the data source into XML format
    Benefit
    Quick and efficient method to transfer external documentation into SAP Solution Manager
    Detailed steps
    Use SAP Solution Manager interface to import XML documentation
    - Import the data into SAP Solution Manager within SAP Solution Manager
    - Verify the imported documentation
    Thanks and regards,
    Nischal

    Hello,
    You can find links to many interesting documents and also some troubleshooting guides at https://wiki.sdn.sap.com/wiki/display/SM/Maintenance+Optimizer
    Best regards,
    Miguel Ariñ

  • 1)    Is there North Bound Interface / API from SAP Solution Manager available for 3rd party integration?       i. The list of the modules that are being managed by SAP Solution Manager(s)      ii. The performance metrics of those modules/components at th

    1)
    Is there North Bound Interface / API from SAP Solution Manager available for 3rd party integration?
    i. The list of the modules that are being managed by SAP Solution Manager(s)
    ii. The performance metrics of those modules/components at the high level
    iii. The information about Early Watch Alerts (or situations to watch for)
    2)
    Is there a full SNMP interface for getting the above information from SAP Solution Manager?
    3)
    Is that understanding that SAP has SNMP support for forwarding alerts to a 3rd party system, correct?
    4)
    Does SAP has both free and licensed? If yes then what are the advantages of licensed over the open/free version?

    Mugunthan
    Yes we have applied 11i.AZ.H.2. I am getting several errors still that we trying to resolve
    One of them is
    ===========>>>
    Uploading snapshot to central instance failed, with 3 different messages
    Error: An invalid status '-1' was passed to fnd_concurrent.set_completion_status. The valid statuses are: 'NORMAL', 'WARNING', 'ERROR'FND     at oracle.apps.az.r12.util.XmlTransmorpher.<init>(XmlTransmorpher.java:301)
         at oracle.apps.az.r12.extractor.cpserver.APIExtractor.insertGenericSelectionSet(APIExtractor.java:231)
    please assist.
    regards
    girish

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

  • Working on Solution Manager

    Hi Gurus,
    in our project we are having to work through solution Manager. I am new to the solution Manager environment.
    a) Is there any link that helps us understand the basics of working on solution manager.
    b) Also, i understand we need to give the transaction codes that we work on in solution manager. (But in HCM as we work in the IMG the transaction code is always seen as SPRO for most of the configuration)
    c) How do we set the T Codes for entire configuration?
    We have the sub modules
    a) Personnel Administration (Recruitment Included)
    b) Organisation Management
    c) Time Management
    d) Payroll
    e) Personnel Development (PMS- OSA)
    f) Training and event Management
    g) ESS and MSS
    Awaiting your reply and Thanks in advance
    Regards
    RR

    The SAP Solution Manager application management solution facilitates technical support for distributed systems u2013 with functionality that covers all key aspects of solution deployment, operation, and continuous improvement. A centralized, robust application management and administration solution, SAP Solution Manager combines tools, content, and direct access to SAP to increase the reliability of solutions and lower total cost of ownership.
    With SAP Solution Manager, you can be sure your entire SAP solution environment is performing at its maximum potential. The toolset addresses your entire IT environment, supporting SAP and non-SAP software and covering current and forthcoming SAP solutions. And, as a customer of SAP, you have full access to the core SAP Solution Manager for no extra charge.
    SAP Solution Manager targets both technical and business aspects of your solutions, focusing strongly on core business processes. It supports the connection between business processes and the underlying IT infrastructure. As a result, it eases communication between your IT department and your lines of business. And it ensures that you derive the maximum benefits from your IT investments.
    SAP Solution Manager features and functions include:
    SAP Business Suite implementation and upgrades u2013 SAP Solution Manager provides content that accelerates implementation. Configuration information and a process-driven approach to implementation speed the blueprint, configuration, and final preparation phases. SAP Solution Manager enables efficient project administration and centralized control of cross-component implementations.
    Change control management u2013 SAP Solution Manager controls all software and configuration changes of the IT solution. This includes the approval process for change requests, the deployment of changes, and later analysis of changes. This ensures quality of the solution and enables traceability of all changes.
    Testing u2013 SAP Solution Manager speeds test preparation and execution. It provides a single point of access to the complete system landscape and enables centralized storage of testing material and test results to support cross-component tests.
    IT and application support u2013 The service desk included in SAP Solution Manager helps you manage incidents more efficiently and eases the settlement of support costs. Centralized handling of support messages makes the support organization more efficient.
    Root cause analysis u2013 The diagnostics functions in SAP Solution Manager allow identification, analysis, and resolution of problems, even in heterogeneous environments. This helps to isolate general performance bottlenecks, to isolate exceptional situations, to record the activity of single users or processes, and to identify changes to the productive landscape. As a result, problem resolution is accelerated and business availability increased.
    Solution monitoring u2013 SAP Solution Manager performs centralized, real-time monitoring of systems, business processes, and interfaces, which reduces administration effort. It can even monitor intersystem dependencies. Proactive monitoring helps you avoid critical situations, while automatic notifications enable fast response to issues.
    Service-level management and reporting u2013 SAP Solution Manager allows easy definition of service levels and provides automated reporting. Service reporting covers all systems in the solution landscape and provides a consolidated report containing the information you need to make strategic IT decisions.
    Service processing u2013 SAP Solution Manager makes appropriate service recommendations and delivers SAP support services. These include SAP Safeguarding, which helps you manage technical risk; SAP Solution Management Optimization, which helps you get the most from your SAP solutions; and SAP Empowering, which helps you manage your solutions.
    Administration u2013 Administration tasks are mainly executed locally on the involved systems, but can be accessed and triggered from a central administration console. The administration work center in SAP Solution Manager offers a central entry point and unified access to all SAP technology.
    The concept is very user friendly and can be easily worked on.  Thank you friend for your response.
    i used solar 2 and was able to work further.
    Regards
    RR

  • JSPM error while updating solution Manager

    Hi All,
      I am getting following error in JSPM while updating SP14 solution manager to SP17 .
    Jan 10, 2010 1:03:35 AM [Info]: Dialog type InfoText with dialog name step displays dialog text <html>Could not obtain MBean server connection with host: hostname, p4Port: 50000 and username: J2EE_ADMIN.
    com.sap.engine.services.jmx.exception.JmxConnectorException: Unable to connect to connector server.
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interface
    s.cross.DestinationException: cannot establish connection with any of the available instances
            Nested exceptions are:
            com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: x.x.x.x and port: 50000
    com.sap.engine.interfaces.cross.DestinationException: cannot establish connection with any of the available instances
            Nested exceptions are:
            com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: x.x.x.x and port: 50000
    Anyidea how I can fix it ?
    Thanks,
    Suman

    Hi Suman,
    Usually the p4port should be 5<xx>04 where xx is the instance number. But the error says p4port is 50000.
    Login to Visual Admin and check the p4provider service under dispatcher node. If the port is 50000 then change it to 50004.
    Then try again.
    Cheers.....,
    Raghu

  • Error with install Solution manager on step: check DDIC password.

    Iu2019m installing  SAP Solution Manager 7.0. ABAP and JAVA instance. OC SLES 10.2. БД Oracle 10.2, update 10.2.0.4. At step 28 out error:
    Test logon to SAP System UST failed.
    SOLUTION: Make sure that the system is started, that the user DDIC exists and that the password of user DDIC is correct.
    Error of sapinst_dev.6.log
    WARNING[E] 2010-07-01 11:30:00.166 [iaxxrfcimp.cpp:433]
               CAbRfcImpl::openRfcConn
    FRF-00007  Unable to open RFC connection.
    TRACE      2010-07-01 11:30:00.167 [iaxxrfcimp.cpp:434]
               CAbRfcImpl::openRfcConn
    Failed to open RFC connection
    TRACE      2010-07-01 11:30:00.167 [iaxxrfcimp.cpp:436]
               CAbRfcImpl::openRfcConn
    DB-Error -          0
    Error of  /usr/sap/UST/DVEBMGS03/work/dev_rfc.trc
    u2026.
    ERROR file opened at 20100701 124301 YEKST, SAP-REL 700,0,48 RFC-VER 3 815142 MT-SL
    T:1115703616 ======> CPIC-CALL: 'SAP_CMNOREGTP'
    LOCATION    CPIC (TCP/IP) on local host
    ERROR       partner '10.10.8.240:3303' not reached
    I have tried to change password DDIC at 19920706. Error could not be fixed.  In the SAP GUI can connect SAP *. When Iu2019m trying to connect DDIC out  DB-Error u2013 0.

    suse102:/usr/sap/UST/DVEBMGS03/work # cat dev_rfc.trc
    ERROR file opened at 20060102 052456 YEKT, SAP-REL 700,0,48 RFC-VER 3 815142 MT-SL
    T:1115703616 ======> CPIC-CALL: 'SAP_CMNOREGTP'
    LOCATION    CPIC (TCP/IP) on local host
    ERROR       partner '10.10.8.240:3303' not reached
    TIME        Mon Jan  2 05:24:56 2006
    RELEASE     700
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -10
    MODULE      nixxi.cpp
    LINE        2764
    DETAIL      NiPConnect2
    SYSTEM CALL connect
    ERRNO       111
    ERRNO TEXT  Connection refused
    COUNTER     2
    T:1115703616 ======> Connect to SAP gateway failed
    Connect_PM  TPNAME=IGS.UST, GWHOST=suse102, GWSERV=3303
    LOCATION    CPIC (TCP/IP) on local host
    ERROR       partner '10.10.8.240:3303' not reached
    TIME        Mon Jan  2 05:24:56 2006
    RELEASE     700
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -10
    MODULE      nixxi.cpp
    LINE        2764
    DETAIL      NiPConnect2
    SYSTEM CALL connect
    ERRNO       111
    ERRNO TEXT  Connection refused
    COUNTER     4
    ERROR file opened at 20100706 142541 YEKST, SAP-REL 700,0,48 RFC-VER 3 815142 MT-SL
    T:1115703616 ======> CPIC-CALL: 'SAP_CMNOREGTP'
    LOCATION    CPIC (TCP/IP) on local host
    ERROR       service '/tmp/.sapstream40300' in use
    TIME        Tue Jul  6 14:25:41 2010
    RELEASE     700
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -4
    MODULE      nixxi.cpp
    LINE        3148
    DETAIL      NiIBindSocket: could not delete file '/tmp/.sapstream40300'
                for hdl 2
    SYSTEM CALL unlink
    ERRNO       1
    ERRNO TEXT  Operation not permitted
    COUNTER     4
    T:1115703616 ======> Connect to SAP gateway failed
    Connect_PM  TPNAME=IGS.UST, GWHOST=suse102, GWSERV=3303
    LOCATION    CPIC (TCP/IP) on local host
    ERROR       partner '10.10.8.240:3303' not reached
    TIME        Tue Jul  6 14:25:41 2010
    RELEASE     700
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -10
    MODULE      nixxi.cpp
    LINE        2764
    DETAIL      NiPConnect2
    SYSTEM CALL connect
    ERRNO       111
    ERRNO TEXT  Connection refused
    COUNTER     6

  • Home Hub 3.0B Management interface unresponsive.

    This month (2 weeks ago) I upgraded to Infinity 2 and got a new Home Hub 3.0 Type B.
    I was able to get it all working as I wanted to - home network using 172.16.0.1/23 (because of conflicts with vpning into work which already routes 192.168./16 and 10./8)
    However, often, very often, trying to access the Hub web interface on 172.16.0.1 or via bthomehub.home simply fails to respond. Regardless of the browser, or me using telnet to simulate a HTTP call.
    #host bthomehub.home 172.16.0.1
    Using domain server:
    Name: 172.16.0.1
    Address: 172.16.0.1#53
    Aliases:
    bthomehub.home has address 172.16.0.1
    # telnet 172.16.0.1 80
    Trying 172.16.0.1...
    Connected to 172.16.0.1.
    Escape character is '^]'.
    GET /
    And it just hangs.
    Even though the web management interface is unresponsive, the internet seems to work ok, though wifi is sporadic.
    Rebooting the hub doesn't seem to help.  I read some reports of badly fitted heatsinks on these Type B's - so could mine be over heating and causing this lock up?  If I leave it and try again in a few hours it may work again.  Yesterday the internet connection dropped twice and when I was able to login to the web interface, the Event log showed that the hub had spontaneously rebooted itself.
    Do I have a bad home hub?

    Hi pgregg,
    Have you tried a full reset of the hub yet? Not just a reboot?
    Chris
    BT Mod Team.
    If you like a post, or want to say thanks for a helpful answer, please click on the Ratings star on the left-hand side of the post.
    If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

  • SOLUTION MANAGER 4.0 SR2 - SP12 deployment issue

    Dear all,
    in our Solution Manager system we're moving our SP stack level from 10 to 12.
    We could successfully deploy via JSPM all the needed components except sap.com/CAF 12, here's the relevant part of the JSPM log:
    Jul 23, 2007 8:57:44 AM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Jul 23, 2007 8:59:37 AM  Info: Begin of log messages of the target system:
    07/07/23 08:57:44 -  ***********************************************************
    07/07/23 08:57:47 -  Start updating EAR file...
    07/07/23 08:57:47 -  start-up mode is lazy
    07/07/23 08:57:47 -  EAR file updated successfully for 63ms.
    07/07/23 08:57:47 -  Start updating...
    07/07/23 08:57:47 -  EAR file uploaded to server for 47ms.
    07/07/23 08:59:37 -  ERROR: Not updated. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Cannot deploy application sap.com/caf~km.proxies..
                         Reason: Webservices common deployment exception! The reason is: Error occured, trying to update ws clients for application sap.com/caf~km.proxies. . Additional info: ; nested exception is:
                              java.lang.Exception: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment exception! The reason is: Error occured, trying to update ws clients for application sap.com/caf~km.proxies. . Additional info:
                              at com.sap.engine.services.webservices.server.deploy.wsclient.update.WSClientsUpdateProcessor.updateWSClients(WSClientsUpdateProcessor.java:162)
                              at com.sap.engine.services.webservices.server.deploy.wsclient.update.WSClientsUpdateProcessor.updateWSClients(WSClientsUpdateProcessor.java:118)
                              at com.sap.engine.services.webservices.server.deploy.wsclient.update.WSClientsUpdateProcessor.updateWSClients(WSClientsUpdateProcessor.java:104)
                              at com.sap.engine.services.webservices.server.deploy.wsclient.update.WSClientsUpdateProcessor.updateWSClients(WSClientsUpdateProcessor.java:77)
                              at com.sap.engine.services.webservices.server.deploy.wsclient.update.WSClientsUpdateManager.makeUpdate(WSClientsUpdateManager.java:53)
                              at com.sap.engine.services.webservices.server.deploy.WSDeployer.makeUpdate(WSDeployer.java:275)
                              at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:400)
                              at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
                              at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:669)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
                              at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                              at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                              at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    I've found an interesting, Note 956443 - In NW04s deploy of Java WS with security fails, but here they speak about SP6 and we're already at 10, moving to 12... so I'm not sure.
    Any advice will be greatly appreciated.
    Franco.

    Deal all,
    thanks for all the suggestion.
    Even though we tried all the advices we received the solution came from Note 941595 - Download J2SE 1.4.2 for the x64 : we switched to JDK version 1.4.2_15 and sap.com/CAF was deployed just smoothly as all the other SPs.
    Again thank you !
    Franco.

  • Solution Manager 7.1 SP11  Functionality

    Dear SAP specialists;
    Our company is currently using Solution Manager for the following purposes:
    Solution Manager 7.0 - to be decommisioned soon
    Document repository for SAP systems.
    Solution Manager 7.1 SP6
    SAP Banking Services and SAP BW Upgrade Projects documentation.
    Business Process Monitoring (BPMon) or Banking End-of-day (EOD) jobs, PI/XI interface queues, tRFC queues, Banking Services PCO/ PPO/CpD worklists, DBA Backup monitoring.
    SAP Data Volume Management (DVM) for production systems.
    Technical SAP system monitoring.
    Non-SAP Technical system monitoring.
    Intake Request Tool (custom-developed tool to log the request tickets through froms in SAP Portal).
    SAP Maintenance (MOPZ).
    SAP Early Watch Alert / SAP Ad-Hoc Reporting.
    Root Cause Analysis.
    Change Request Management (ChaRM) - *Under Development*.
    We are planning to get Solution Manager 7.1 SP11 soon and I am wondering about the following:
    Is there a comprehesive source of functional and technical information (presentations, white papers, guides, overviews) about Solution Manager SP11?
    How much does the SP11 upgrade changes the Solution Manager usage for purposes listed above?
    As of SP10 there is a new experimental MAI Alert functionality for Business Process Monitoring and Technical Monitoring. It is limited and does not support most of BPMon tools we use. This includes Application log Monitors, Notification BADI's, Monitoring Objects Lists, BW storage and reporting, monitoring templates and migration of current solutions)    
    How does CO Wily Introscope work with Solution Manager SP11?

    Hi Viacheslav,
    Here is the location for the info you are asking; Changes and New Features in SAP Solution Manager 7.1 SP11 - SAP Solution Manager - SAP Library
    Regards,
    Vivek

  • Solution Manager Installation Fails at step Run ABAP Reports

    I'm trying to install Solution Manager 4.0 on Windows 2003 using SQL 2005.  The installation fails at the Run ABAP Reports step: Executing ABAP report RADDBDIF
    I have logged in manually and run the RADDBDIF job in SE38 but I receive the same error message.  My SAPTRANHOST is properly defined and so are the shares.  Can anyone help? Thank!
    Here's the sapinst_dev.log:
    Calling function module: INST_RFC_GET_INTERFACE
    INFO       2008-10-21 14:00:34.842 [iaxxrfcimp.cpp:1065]
               CAbRfcImpl::performFunctionCall
    Function call was successful.
    TRACE      2008-10-21 14:00:34.842 [iaxxrfcimp.cpp:1066]
               CAbRfcImpl::performFunctionCall
    Function module call succesful: INST_RFC_GET_INTERFACE
    INFO       2008-10-21 14:00:34.842 [iaxxrfcimp.cpp:924]
               CAbRfcImpl::getRfcInterfaceSAP
    Function interface generated successfully.
    INFO       2008-10-21 14:00:34.842 [iaxxrfcimp.cpp:926]
               CAbRfcImpl::getRfcInterfaceSAP
    Technical properties of function set successfully.
    INFO       2008-10-21 14:00:34.842 [iaxxrfcfls.cpp:107]
               CRfcFuncRep::insFuncIf
    Information for application function INST_EXECUTE_REPORT copied to local repository.
    TRACE      2008-10-21 14:00:34.842 [iaxxrfcfls.cpp:108]
               CRfcFuncRep::insFuncIf
    Function interface entered into repository for INST_EXECUTE_REPORT
    INFO       2008-10-21 14:00:34.842 [iaxxrfcimp.cpp:622]
               CAbRfcImpl::setFunction
    Function module INST_EXECUTE_REPORT set successfully.
    TRACE      2008-10-21 14:00:34.842
    2008-10-21 14:00:34.842 JSCo.setFunction() done: true
    TRACE      2008-10-21 14:00:34.842
    2008-10-21 14:00:34.842 JSCo.setParameter(PARA, [])
    TRACE      2008-10-21 14:00:34.842
    2008-10-21 14:00:34.842 JSCo.setParameter() done: true
    TRACE      2008-10-21 14:00:34.842
    2008-10-21 14:00:34.842 JSCo.setParameter(PROGRAM, RADDBDIF)
    TRACE      2008-10-21 14:00:34.842
    2008-10-21 14:00:34.842 JSCo.setParameter() done: true
    TRACE      2008-10-21 14:00:34.842
    2008-10-21 14:00:34.842 JSCo.execute()
    INFO       2008-10-21 14:00:34.842 [iaxxrfcimp.cpp:1032]
               CAbRfcImpl::callFunction
    Executing function call INST_EXECUTE_REPORT.
    TRACE      2008-10-21 14:00:34.842 [iaxxrfcimp.cpp:1056]
               CAbRfcImpl::performFunctionCall
    Calling function module: INST_EXECUTE_REPORT
    ERROR      2008-10-21 14:00:35.045 [iaxxrfcimp.cpp:1089]
               CAbRfcImpl::performFunctionCall
    FRF-00025  Unable to call function. Error message: Exception condition "WRITE_FAILED" raised. .
    TRACE      2008-10-21 14:00:35.045 [iaxxrfcimp.cpp:1090]
               CAbRfcImpl::performFunctionCall
    RFC failure or system exception raised
    TRACE      2008-10-21 14:00:35.045 [iaxxrfcimp.cpp:1091]
               CAbRfcImpl::performFunctionCall
    Exception condition "WRITE_FAILED" raised.
    INFO       2008-10-21 14:00:35.045 [iaxxbjsco.cpp:561]
               CIaJSCo::disconnect_nothrow(000:DDIC:EN:nath02:00::SOL:)
    RFC connection closed.
    TRACE      2008-10-21 14:00:35.45 [iaxxejsbas.hpp:408]
               handleException<ERfcExcept>()
    Converting exception into JS Exception ERfcException.
    TRACE      2008-10-21 14:00:35.045
    Function setMessageIdOfExceptionMessage: modlib.jslib.caughtException
    ERROR      2008-10-21 14:00:35.045
               CJSlibModule::writeError_impl()
    MUT-03025  Caught ERfcExcept in Modulecall: Exception condition "WRITE_FAILED" raised..
    TRACE      2008-10-21 14:00:35.45 [iaxxejsbas.hpp:483]
               EJS_Base::dispatchFunctionCall()
    JS Callback has thrown unknown exception. Rethrowing.
    ERROR      2008-10-21 14:00:35.45 [sixxcstepexecute.cpp:951]
    FCO-00011  The step runRADDBDIF with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_ABAP_Reports|ind|ind|ind|ind|2|0|runRADDBDIF was executed with status ERROR ( Last error reported by the step :Caught ERfcExcept in Modulecall: Exception condition "WRITE_FAILED" raised..).
    TRACE      2008-10-21 14:00:35.61 [iaxxgenimp.cpp:752]
                CGuiEngineImp::showMessageBox
    <html> <head> </head> <body> <p> An error occurred while processing service SAP Solution Manager 4.0 Support Release 4 > SAP Systems > MS SQL Server > Central System > Central System( Last error reported by the step :Caught ERfcExcept in Modulecall: Exception condition "WRITE_FAILED" raised..). You may now </p> <ul> <li> choose <i>Retry</i> to repeat the current step. </li> <li> choose <i>View Log</i> to get more information about the error. </li> <li> stop the task and continue with it later. </li> </ul> <p> Log files are written to C:\Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS. </p> </body></html>
    TRACE      2008-10-21 14:00:35.61 [iaxxgenimp.cpp:1255]
               CGuiEngineImp::acceptAnswerForBlockingRequest
    Waiting for an answer from GUI

    Hello Amélie,
    Check the file systems if you're not ran out of disk space.
    Second, check the database if you've enough storage space left.
    Hope it helps.
    Cheers,
    Satish.

  • System Monitoring Setup in Solution Manager

    Hello Experts,
    We are going to implement and configure Solution Manager - System monitoring setup for pre testing purpose
    Currenly we have installed below SAP Systems
    1.Solution Manager Server
    2.ECC server (Without Ides) - Abap
    3.CRM Server (Without Ides) -Abap + Java
    We need to setup below tasks in Solution Manager
    1.Early watch alert
    2.System Monitoring
    3.Central System Administration
    4.Business Process Monitoring
    5.Service Level reporting
    1.Is it possible to setup the solution manager -above mentioned tasks without Ides system ?
    Could you please someone give input reg this.
    Thanks
    Thirumal
    Edited by: Thiru Thirumal on Aug 6, 2008 4:56 AM
    Edited by: Thiru Thirumal on Aug 6, 2008 4:57 AM

    Hi,
    Q. Is it possible to setup the solution manager -above mentioned tasks without Ides system ?
    A. Yes.
    Check with links for
    1.Early watch alert
    This process helps you to identify potential problems early, avoid bottlenecks, and monitor the performance of your ABAP and JAVA systems and your most important business processes, regularly, automatically and effectively. The data collection infrastructure comprises the ABAP Service Data Control Center and the JAVA function module Data Provider. The SAP EarlyWatch Alert in the SAP Solution Manager is a service provided by SAP.
    To be able to use it, you have:
    maintained the non-ABAP systems correctly in the system landscape maintenance (transaction SMSY)
    RFC u2013 Connections between: and an RFC u2013 Connections established.
    your satellite systems and the SAP Solution Manager system
    SAP Solution Manager and the SAP Service Marketplace
    Solution Manager system and Solution Manager Diagnostics
    Cf: Solution Manager IMG (transaction SPRO).
    checked the availability of the tools required for the SAP Service sessions (add-on ST-A/PI), with the report RTCCTOOL.
    activated Alert Monitoring and set-up the Automatic Session Manager (ASM) in the Service Data Control Center (SDCCN) of your satellite systems, for all SAP satellite systems and the central SAP Solution Manager of your solution
    set-up your systems in a solution landscape in the SAP Solution Manager
    configured Solution Manager Diagnostics
    2.System Monitoring
    The system monitoring in the SAP Solution Manager is, as described above, like a system-wide central CCMS. It can also contain the central CCMS (CEN) of satellite systems. These CENs can then monitor other components.
    The graphical display in the SAP Solution Manager gives you access to the alerts of all systems in a solution. You can go to the local or central CCMS of the satellite systems.
    The system proposes the most important alerts in the CCMS monitor collection, according to SAP experience, and their alert thresholds, for each system in the solution, in the system monitoring Session. You can activate or deactivate these alerts. The connection between the local CCMS and the SAP Solution Manager allows you to maintain the alert thresholds directly in the SAP Solution Manager, overwriting the values in the local CCMS.
    3.Central System Administration
    You activate the customizing for business processes in your solution, in the Business Process MONITORING session in the SAP Solution Manager. A monitoring tree element (MTE), or a monitor collection, u201EBPMu201C of several monitoring objects, is created in the local or central (CEN) CCMS of the satellite system.
    The data is collected for the monitoring types of the business process monitoring in contrast to system monitoring, as follows:
    ● The system collects performance (dialog transactions), posting cancellations (V1 and V2) and u201EOther CCMSu201C and interface data, in the local CCMS of the satellite systems.
    ● The system collects background processing, application list, application monitors, delivery lists, and document size data, in the central SAP Solution Manager CCMS.
    The SAP Solution Manager system copies the data from the local CCMS.
    The graphical display in the SAP Solution Manager simplifies access to the alerts for the business processes, business process steps or the interfaces between the systems in a solution. You can go to the local CCMS of the satellite systems.
    The connection between the local CCMS and the SAP Solution Manager allows you to maintain the alert thresholds directly in the SAP Solution Manager. These overwrite the values in the local CCMS.
    4.Business Process Monitoring
    The system and business process monitoring (including interface monitoring) in the SAP Solution Manager, both use the Computing Center Management System (CCMS) (transaction RZ20) architecture. This means that system alerts which occur in the local CCMS, are passed to the SAP Solution Manager via RFC connections between the SAP Solution Manager and the satellites. The system shows these alerts in a graphic or in Sessions. You can also handle the alerts centrally, without having to go to the local CCMS of the satellite systems.
    You can see the alerts from several systems in a solution landscape in the SAP Solution Manager, in a graphical overview, in contrast to the local CCMS of the SAP Solution Manager satellite systems. This is the view of a central CCMS (CEN). You can also monitor non-SAP systems in a central CCMS (CEN) of a satellite system
    5.Service Level reporting
    http://service.sap.com/solutionmanager for all solman tasks as given below.
    http://www.asap.net.cn/homepage_en/Solution%20Manager%20EN.pdf
    http://help.sap.com/saphelp_sm32/helpdata/en/1b/f02c41ab78f66fe10000000a1550b0/content.htm
    http://help.sap.com/saphelp_sm32/helpdata/en/9f/1f46570f8a4a268b3154e0e0f07280/content.htm
    Regards,
    Srini Nookala

  • How can we monitor IDOCS of managed system from Solution manager .

    Hello
    Please tell me the steps clearly involved in monitoring IDOC's..
    I have created BPM RFC till now ..
    Thanku..
    Dev

    Hi
    you need to configure interface monitoring
    config guide
    https://websmp104.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000258142008E
    usage scenario
    /people/johannes.fleig/blog/2008/05/25/new-business-process-monitoring-functionalities-in-sap-solution-manager-150-ale-idoc-monitoring
    Hope it solved ur prb completely
    Regards
    Prakhar

Maybe you are looking for