Support Desk issue

Hi all,
I have configured service desk. But there is one problem. Consider a scenario - user A creates support message 111 from satellite system and say user B is part of assigned support team for message 111.
Now if I login to the solution manager with user id A and try to execute report "reported by me" , it does not show any output. But if I try same thing with user id B and execute report "reported by me", output is shown which includes support message 111.
I have assigned role SAP_SUPPDESK_DISPLAY to user A
I am trying for last 5 days. Help will be appreciated. I'll reward points for correct answer.
Thanks in advance
Edited by: Meghan Kambli on Jun 3, 2008 4:51 PM

Hey Anand,
Thanks a lot for suggestion. It helped and finally solved the problem.
I forgot to assign Employee role. Your solution was to the point.
Thanks to you, Mr Patrick. Those notes were really helpful. Points awarded to both of you. Netherland gonna win EURO'08
-Regards
Meghan

Similar Messages

  • Priority issue in Support Desk in Solutionsolution Manager

    Hi Guru's
        When we create the support Desk Message in solMan or thru any Satellite system, the email will trigger to the Concerned person, But in the Support Desk mail the priority is not appearing,we are using the solution Manager 4.0 ( Upgraded).can Any Guru's Help me out.
      Regards
    Charan

    Check if the below linnk can help you....
    Mail to Support Team During the creation of  Support Message
    It makes anote of a BADI and may be further configuration to this BADI can reach you to the requirment. I personally have not worked on this but would be great if it works out for you.
    All the best
    Br,
    Sri
    Award points for helpful answers

  • Error 513, no message was created in support desk system BCOS005

    Hi All,
    After completing the ITSM config on Solution Manager 7.1, I am stuck with the following error when creating message from any of the satellite system, or from SM itself.
    "Because of error 513, no message was created in support desk system"
    Message no. BCOS005
    Error logs from SLG1:
    "No message created from SAP message 00xxxxxx 000xxxxx 2013 due to missing IBase"
    Transaction: SOLMAN_INCIDENT_UPD
    Program:AI_CRM_IM_UPDATE_FROM_SAP
    I have already checked various threads and suggested notes including 1522809 / 1741109, but unable to fix the issue.
    RFC's between both the systems are working fine. The entry for BCOS_CUST on SM is maintained as
    OSS_MSG   W    NONE    CUST   6.2    1.0
    The number range for SLF1 is maintained as 01 in TCode DNO_CUST01
    I suspect this to be related to IBASE or Number range, but seem to have the correct values maintained as mentioned in above notes. Would appreciate your valuable inputs on this.
    Thanks,
    Varun

    Hi Vivek,
    Tried updating the parameter, but no luck
    "Because of error 513, no message was created in support desk system"
    Message no. BCOS005
    Should be something to do with BCOS, can't figure out though.
    Any further thoughts?
    Regards,
    Varun

  • Error 513, no message was created in Support Desk System

    After implementing QAS in sp's 15, when the user wants to create a message from QAS solution manager, get the following error "Because of error 513, no message was created in Support Desk System"
    has been revised rfc connections and have no problem because when the user is done with NetWeaver - works perfect basis.
    Nor is it because of permissions users have the same roles that were assigned in the other systems DEV and PRD, and when they have no problems sending messages.
    I have reviewed the table BCOS_CUST "and is fine. As in other systems.
    I am grateful if someone can help me.
    Regards

    Dear Leonor,
    This forum is related to Public Sector Funds Management (budget) issues.
    I believe the best for you is to open this thread in the Basis forum. There you will find the experts to help you.
    Best Regards,
    Vanessa.

  • Support desk configuration from portal

    Hi all
    is anybody configured sending message from support desk in portal to solution manager ?
    i followed this link
    http://help.sap.com/saphelp_nw04s/helpdata/en/84/91bfddb6c33246a6eae4d483749635/frameset.htm
    i am getting 102 jco exeption error but i havent created any jco connection between potal and solution manager .
    anybody knows here how the data was transmitted from portal to solution manager.
    if possible can somebody points me to some configuration document to do so
    Regards,
    Vijay.
    ps: i had successfully configured support desk scenerio for all the satellite system with abap stacks.

    HI
    thanks for your reply
    i had already done that correction specified by you
    The actual problem is with the firewall and after unblocking the firewall now i could able to test my system succesfully in portal landscape but still i could not able to send message from portal to solution manager as it is taking too long time and hanging at the end of transaction.
    what could be the reason
    any idea?
    regards,
    Vijay.
    ps: i could able to send the message from portal to solution manager .i have still some issues with BP configuration.
    Edited by: vijayakumar kanniah mohan on Oct 16, 2008 1:27 PM

  • Support desk queries on solution manager

    Hi All
    I have few queries on solution manager support desk functionality.
    1.Is this the only way to create support desk message HELP-CREATE support desk Message from each individual system??
    2.In our scenario,when we are creating the message we would like to assign component( it should be project specific component,not SAP specific component)...How to acieve this??
    3.We have a requirement where the message has lot of status and fields and depending on the message processor I would like to control which status or field user should be able to view and work on...how to achieve this??
    4.Need the way to send a message to the processor,as soon as his name appear as message processor.
    5.I want to track all the persons involved in the message processing,how can I do this??
    6.I want to use a different transaction type not the standard SLFN,so what configurations are needed??When I create a message it should automatically take properties of transaction type of newly created one??

    Hello Dolores,
    first of all thanks for that answer. I read it in the germany documentation help.
    Here an extract:
    +Anlegen von Support-Meldungen über NOTIF_CREATE
    Mit der Transaktion NOTIF_CREATE können Benutzer, die in Satellitensystemen arbeiten, Meldungen anlegen und an den SAP Solution Manager versenden.
    Vorgehensweise
    Starten Sie Transaktion NOTIF_CREATE.
    Geben Sie folgende Werte im Dialogfenster Anlegen einer Support Meldung ein:
    Priorität
    System/IBase-Komponente
    Kurz- und Langtext
    Um Anlagen anzuhängen, wählen Sie Registerkarte Anlagen.
    Sichern Sie Ihre Eingaben.
    Ergebnis
    Sie haben eine Support-Meldung angelegt.+
    Yesterday I search the internet for a note, but I didn't find one. So I'am happy now.
    But now the next problem occurs. My next issue is about the SLD. The system cannot get the data from the satellites. I'am not sure, but I think our SLD isn't perfectly configuried. Do you have an "How To" or something like that?
    regards
    marc

  • Support Desk Message Creation in SOLUTION MANAGER  through  External Emails

    Hello Experts,
                        I am a ABAP Developer , as mentioned in subject, my part is to Create support desk message in solution manager,through external Emails like outlook Express . To do this task i  am in need of more information about some  componenets which are used in solution manager support desk Message.
          My Doubts are,
    1) What is the use of Ibasecomponent in Message Creation?
    2) What if the ibasecomponent is mentioned as a defaut value ' 24 ' ( i.e is the ibasecomponent for solution manager - support desk ) ?
    3) To track the system from which the message is created , is ibase required or the SAP component will give those information?
         If anyone has already worked with this subject, please give me some suggestions ASAP.
    Thanks in Advance,
    Mohana

    Hello Mohana,
    Let see if I can explain this well:
    1) What is the use of Ibasecomponent in Message Creation?
    When you define a Solution in the SOLMAN, you need to update your Ibase
    Edit->Initial Data transfer for Ibase
    This create a tree structure in the ibase IB52, as you can see in the attachment.
    You get a componet number for SID-Client
    You can configure the SOLMAN in a way that when a message arrives from
    <System ID> <Installation Number> <Client> <User Name>
    this is what solman knows from a message comming from a satellite, them you
    know directly from which component/ibase the message has been received.
    This is important data, the component/ibase, for reporting issue, for assigning this component to a sold-to-party (being in IB52, left tree, select a system and go to Goto->Partner  you can assign a Sold-to party BP there for example)
    2) What if the ibasecomponent is mentioned as a defaut value ' 24 '
    By default the SOLMAN system has a Intalled base 01 already created for being used and maintained "automatically":
    being in dswp, solution : Edit->Initial Data transfer for Ibase
    If not you msut maintain the ibase manually from IB52, this is also possible.
    The Ibase 01 is a prconfigured iBase for being used for the SOLMAN application.
    Tink that the SOLMAN system is built up a CRM system, so the IBase is CRM matter. SOLMAN is only using some CRM applications to build the Service Desk scenario for example.
    I3) To track the system from which the message is created , is ibase required or the SAP component will give those information?
    Ibase is required
    Hope this helps,
    Dolores

  • BI : Diagnostic and support desk tool

    Hello
    I'm currently using BI7.0 SP9 and the support desk tool version 0.370.
    I have a current red light that i'm not able to solve :
    URLs Prefixes Customized on Both J2EE and ABAP Side
    and the  long text is :
    The URL for ABAP customizing table RSPOR_T_PORTAL: http://cod..airliquide.com:50100 is not compatible with the URL for URL with which you call the WebAS Java: http://cod:50100
    and it told me to apply OSS note 596698 as well as note 654326 for details
    The problem is not solved on this note.
    I would like to know how to chanfe the URL in the abap part whan i call the java part to use the long name and included the domain on it ???
    regards
    François

    Hello
    closed
    we have to use http://hostname.domainName:5XX00 instead of http://hostname:5XX00 to avoid such issue
    François

  • Problems with the correct Customizing of the Support Desk Rule 13200137

    Hallo All,
    I have an issue with the rule 13200137. If I create the responsibility and assign a user, the Support Desk works well. The partner processing get the user of the created rule and fills the field "SupportDesk", with the assigned user. I tried to create a organisation with the SAP Standard and assign it in tab "Responsibility", after that the rule doesn't work. The "Support Desk"-field stays clear, also the field "Message Processor". I do all the steps like in the different "HowTo's", but it doesn't work. Does anybody have an idea?
    Solution Manager 4.0.
    Best regards
    Marc

    Hello All,
    the assignment between the field "Support Desk" and the organisation-modell works now. But the field "Message Processor" stays clear.
    Here the steps I have done:
    1 Create BP as employee and assign the user-id of a system user (In that case my user-id)
    2. In the change view of the organisation-modell I did assign the created BP of step 1. to to a organisation-unit. For the test scenario i used the SAP standard-units for "Service Desk".
    3. Modify the rule 13200137 for SAP-Components
    4. Assign the organisation-unit to the rule.
    Has anybody an idea what is wrong? Why stays the field "Messages Processor" clear?
    Best regards
    Marc

  • Error in deployed compoents when running diagnostics & support desk tool

    when I run netweaver Business Explorer diagnostics & support desk tool
    I got error in "deployed components".
    the message says:
    "The SCA 'BI-BASE-S' (7.00 SPS 9, patch level #0) is a invalid combination of version/support package with your WebAS ABAP system (7.00 19)"
    the solution says
    "Ensure that both your WebAS Java and your WebAS ABAP have a valid combination of version and support package stack level. Please note that beginning from BI SP 11, the versioning scheme of BI ABAP SPs has changed"
    then I was referred to note 1013369 and 1163789. then which SCA file SPS/patch do I need for ABAP SPS19?
    what do I need to do? and how do I do this? my basis guy need advice.
    George

    Hello George,
    To correct this issue ensure that both your WebAS Java and your WebAS ABAP have a valid combination of version and support package stack level.
    Also you can check the note  1013369 -  SAP NetWeaver 7.0 BI - intermediate Support Packages
    and check the compatibility table.
    I hope that this can help you.
    Kind regards
    Diego Ferrary

  • Several support desk messages using BADI_DET_PROC_TYPE_FROM_DNO

    Hello,
    We're trying to realize creation of several support desk messages ZLF1 and ZLF2 based on the SAP system from wich messages were sent. For example, from SS1 system it's necessary to create support notification ZLF1 and corresponding service desk transaction ZLFN; from SS2 system it's necessary to create ZLF2 and YLFN.
    We'd like to implement BADI_DET_PROC_TYPE_FROM_DNO for this case. Could anybody help us with the implementation?
    Regards,
    Arkadiy Terzi

    Hi Jansi,
    Thank you for the answer.
    We made necessary settings in SPRO->SAP Solution Manager -> Service Desk -> Multi Transaction Type Handling.
    And created BADI implementation ZBADI_DET_PROC_TYPE_FROM_DNO. But it seems that the system doesn't take into account this implementation.
    Could you provide more detailed information or any SAP notes about the issue?
    Thanks,
    Arkadiy

  • Unable to raise Message from Sattelite System to support Desk

    Hi Experts,
    I am facing issue when i try to raise the message from sattelite system to support desk in solution manager 7.0.For this Below Checks i ahve already performed please suggest i am missing something.
    1.RFC in Back Format.
    2.addtional RFC authorization to RFC user in solmon system.
    3.Sattelite systems entry Maintained in solmon in SMSY and loical clients.
    4. No Range Maintained for both internal as well as external.
    5.Support Pack level looks fine
    Thanks in Advance
    Suveer

    I have come across this issue. The system was giving the same error message as you got.(error 513 ). But actual problem turned out to be authorization..!!(took some time for debugging that)
    Look at the user which <solman>_back RFC uses when logging in from satellite system. Now login to Solution manager and check the authorization of that user. Does it have the following roles assigned..
    SAP_SUPPDESK_CREATE
    SAP_SV_FDB_NOTIF_BC_ADMIN
    If NO, generate these roles (if not done) and assign them to this user.
    Do let me know if it helps...
    Regards,
    Anish

  • Email PDF smart form Support Desk

    Hi SDN,
    I'm working on support desk - solution manager, and i need to send the solution of the support message by email to the final user.
    There is an standard action (SLF1 -SMSD_SERVICE_ORDER_DNO_OUTPUT)  that sends the solution in pdf format by email, but we couldn't set the receivers online.
    So, I'm using an "z" action that executes an smart form, and i would like to send the smart form in pdf format by the internet.
    I'd like to use fm SO_DYNP_OBJECT_SEND, because the user must fill the receivers on-line
    So far i have de OTF, and i know that i can make a conversion to pdf format, but i've the following problem
    - the pdf in attach is empty, it may be because of the format, or may be i'm not using correctly this function.
    Thanks in advance,
    Maria João Rocha
          call function 'CONVERT_OTF'
            exporting
               format                = 'PDF'
            importing
              bin_filesize          = w_pdf_size
            tables
              otf                   = es_job_output_info-otfdata[]
              lines                 = t_pdf[]
            exceptions
              err_max_linewidth     = 1
              err_format            = 2
              err_conv_not_possible = 3
              err_bad_otf           = 4
              others                = 5.
    * header
          wa_head-objnam = 'EMAIL'.
          wa_head-objdes = ls_output_options-tdtitle.
          wa_head-objnam = ls_output_options-tdtitle.
          wa_head-objla = sy-langu.
          wa_head-objsns = 'O'.
          wa_head-file_ext = 'TXT'.
          append wa_head to t_head.
          wa_packing_list-transf_bin = 'X'.
          wa_packing_list-head_start = 1.
          wa_packing_list-head_num = 0.
          wa_packing_list-body_start = 1.
          wa_packing_list-objtp = 'RAW'.
    *      wa_packing_list-objtp = 'EXT'.
          wa_packing_list-objdes = ls_output_options-tdtitle.
          wa_packing_list-objla = sy-langu.
          wa_packing_list-objlen = w_pdf_size.
          wa_packing_list-file_ext = 'PDF'.
          append wa_packing_list to t_packing_list.
    *---------- enviar o mail
          call function 'SO_DYNP_OBJECT_SEND'
            exporting
    *            object_hd_change           = ls_output_options-tdtitle
              object_type                = 'RAW'
    *            originator_type            = 'B'
    *            originator                 = sy-uname
    outbox_flag      = 'S'
            tables
    *            objcont                    = t_text
    *            receivers                  = t_receivers
              packing_list               = t_packing_list
              att_cont                   = t_cont
              att_head                   = t_head
            exceptions
              active_user_not_exist      = 1
              communication_failure      = 2
              component_not_available    = 3
              folder_not_exist           = 4
              folder_no_authorization    = 5
              forwarder_not_exist        = 6
              note_not_exist             = 7
              object_not_exist           = 8
              object_not_sent            = 9
              object_no_authorization    = 10
              object_type_not_exist      = 11
              operation_no_authorization = 12
              owner_not_exist            = 13
              parameter_error            = 14
              substitute_not_active      = 15
              substitute_not_defined     = 16
              system_failure             = 17
              too_much_receivers         = 18
              user_not_exist             = 19
              x_error                    = 20
              others                     = 21.
        endif.

    Thanks for your reply.
    I'm working on it, and I’ve seen the SCOT documentation, so I've change my strategy.
    Right now I'm using some of the methods of the BOR.
    I think I've to code because I want a popup to introduce the list of the receivers and the mail body, and of course I want to attach a smart form on pdf format.
    But I can’t send the mail because of the error: Erro interno: SO_OBJECT_MIME_GET Exceção: 2
    Can you help me on this? What I’m doing wrong? What document class I need to use on the “AttachmentType”?
    Thanks in advance.
    Best regards,
    Maria João Rocha
    FUNCTION Z_MAIL_DIALOGO.
    *"*"Interface local:
    *"  IMPORTING
    *"     REFERENCE(TITULO) TYPE  SOOD1-OBJDES OPTIONAL
    *"     REFERENCE(FILE_SIZE) TYPE  SOOD1-OBJLEN OPTIONAL
    *"  TABLES
    *"      OTF TYPE  TSFOTF OPTIONAL
    *"      PDF STRUCTURE  TLINE OPTIONAL
    *"      CONTEXT TYPE  SOLI_TAB OPTIONAL
    * Makros für Zugriff aufs BOR
    include <cntn01>.
    *parameters: dialog like sonv-flag.
    data: dialog like sonv-flag.
    * Datendeklaration
    data: message type swc_object.
    data: recipient type swc_object.
    data: recip_tab type swc_object occurs 1 with header line.
    data: objkey like swotobjid-objkey.
    data: content like soli-line occurs 0 with header line.
    data: title(80).
    data: persnumber like adcp-persnumber.
    data: sent_to_all like sonv-flag,
          object_list like sosndinf occurs 1 with header line.
    data: t_otf type standard table of ITCOO.
    data: itab like soli occurs 0.
    * Deklaration eines Containers
    swc_container container.
    * Message-Objekt anlegen
    * * Neues Message-Objekt generieren
    swc_create_object message 'Message' space.
    swc_clear_container container.
    if dialog = space.
    * * Create w/o dialog
      concatenate 'Mensagem Support Desk' sy-datum sy-uzeit into title
               separated by '/'.
      swc_set_element container 'DOCUMENTTITLE' title.
      swc_set_element container 'DOCUMENTNAME' 'Support Desk'.
    *  swc_set_element container 'DOCUMENTTYPE' 'INT'.
    *  swc_set_element container 'DOCUMENTTYPE' 'SCR'.
      swc_set_element container 'DOCUMENTTYPE' 'OTF'.
      swc_set_element container 'NO_DIALOG' 'X'.
    else.
    * * Create with dialog
      swc_set_element container 'NO_DIALOG' ' '.
    endif.
    swc_call_method message 'Create' container.
    perform error_handling(rssobcitest11).
    * Create attachment (RAW document from internal table)
    SWC_CLEAR_CONTAINER CONTAINER.
    *att_bor_obj-objtype = 'MESSAGE'.
    *swc_set_element container 'ATTACHMENT' pdf.
    *swc_set_element container 'ATTACHMENT' otf.
    swc_set_element container 'ATTACHMENT' context.
    swc_set_element container 'ATTACHMENTTITLE' 'Anexo'.
    swc_set_element container 'AttachmentType' 'OTF'.
    *swc_set_element container 'DocumentSize' 0.
    swc_set_element container 'DocumentSize' file_size.
    *swc_set_table container 'DocumentContent' itab.
    SWC_CALL_METHOD MESSAGE 'Attach' CONTAINER.
    PERFORM ERROR_HANDLING(RSSOBCITEST11).
    *SWC_CLEAR_CONTAINER CONTAINER.
    *SWC_SET_ELEMENT CONTAINER 'EditorSettings' 'D'.
    *SWC_SET_ELEMENT CONTAINER 'STARTING_AT_X' '5'.
    *SWC_SET_ELEMENT CONTAINER 'STARTING_AT_Y' '5'.
    *SWC_SET_ELEMENT CONTAINER 'EnableApplObjAttachments' 'X'.
    *SWC_CALL_METHOD MESSAGE 'EditRecipientList' CONTAINER.
    *PERFORM ERROR_HANDLING(RSSOBCITEST11).
    * Einen Empfänger (interner Benutzer) automatisch hinzufügen
    * Recipient-Objekt anlegen
    swc_clear_container container.
    swc_create_object recipient 'Recipient' space.
    swc_set_element container 'AddressString' sy-uname.
    swc_set_element container 'TypeId' 'B'.
    swc_call_method recipient 'CreateAddress' container.
    perform error_handling(rssobcitest11).
    * Kopie des Recipient-Objekts anfügen
    swc_clear_container container.
    swc_set_element container 'NewRecipient' recipient.
    swc_call_method message 'AddCopyOfRecipient' container.
    perform error_handling(rssobcitest11).
    * Outbox-Flag setzen
    swc_clear_container container.
    swc_set_element container 'OutboxFlag' 'X'.
    swc_call_method message 'SetOutboxFlag' container.
    perform error_handling(rssobcitest11).
    * Empfängerliste editieren
    swc_clear_container container.
    swc_call_method message 'EditRecipientList' container.
    perform error_handling(rssobcitest11).
    swc_get_table container 'RecipientsInfo' object_list.
    if sy-subrc = 8.
    * Kopiertes Message-Objekt versenden
      swc_clear_container container.
      swc_call_method message 'Submit' container.
      perform error_handling(rssobcitest11).
      swc_get_table container 'RecipientsInfo' object_list.
    endif.
    swc_get_element container 'SentToAll' sent_to_all.
    * Kopiertes Message-Objekt sichern
    swc_clear_container container.
    swc_call_method message 'Save' container.
    perform error_handling(rssobcitest11).
    * Protokollausgabe:
    * Key des Message-Objekts ermitteln
    *SWC_GET_OBJECT_KEY MESSAGE OBJKEY.
    *WRITE: / 'Key des Messageobjekts', OBJKEY.
    * Protokollausgabe:
    perform write_recipient_info(rssobcitest11) tables object_list
                                                using  sent_to_all.
    * Freigeben der Referenzen
    * MESSAGE-Objekt
    swc_free_object message.
    * RECIPIENT-Objekt
    swc_free_object recipient.
    commit work.
    ENDFUNCTION.

  • Error while creating change request via solman support desk message

    I have configured CHARM and my change req. is working for urgent correction, I have tested the entire workflow.
    however when i try to create a new change req. via support desk message --> create a change request open
    I get following error
    An action was terminated due to an exceptional situation.
    Message no. SOCM_ACTION_LOG 090
    Diagnosis
    An exception has been triggered in PPF action processing.
    System Response
    Action processing has been terminated. The status of the transaction is still incorrect.
    Procedure
    You cannot execute the action until the cause of the error has been removed.
    The error messages will be kept until the transaction is next checked for subsequent analysis.
    Procedure for System Administration
    If necessary, analyze other messages in the application log for the incorrect transaction. To analyze the termination, you can activate the breakpoints in the checkpoint group socm_exception.
    Additional Information:
    Exception CX_SOCM_PRECONDITION_VIOLATED occurred (program:
    CL_HF_HELPER==================CP, include:
    CL_HF_HELPER==================CM00A, line: 29).
    pls help

    Hi Yunus,
    Your probably have changed the transaction type SLFN to a the customer namespace Z or Y. If this is the case you MUST also "Define Mapping Rules for Copy Control".
    Goto SPRO -> SAP Solution Manager -> Scenario-Specific Settings -> Change Management -> Change Request Management -> Extended Configuration -> Change Transaction -> Change Transaction Types -> Copy Control for Change Request Management ->  Define Mapping Rules for Copy Control.
    Once at this point in the IMG make a copy of SLFN -> ZLFN. This will resolve your problem.
    Kind regards,
    Latief

  • Set sap Component mandatory while creating the support desk message

    Hi,
       When create the support desk message from any application sysytem, the sap component get selected automatically but when we create the suppport desk message from the Easy Access the component wiil be blank, so some user create the support message without giving the component. So we want to make the component as mandatory while createing the support desk message from application system and also  set mandatory  when we create support message in solman.can anybody help me in setting component mandatory.
      Regards
      charan

    Dear Charan,
    The logic of setting the SAP Component mandatory is explained in the note 640532.
    Kindly use the note to resolve the purpose.
    Hope this solution helps.
    Regards
    Amit

Maybe you are looking for