Create support message

Dear sir,
we are facing problem while creating support message in solution manger and satellite systems.we have done all the basic settings in SPRO and activated EWA.
in the satellite system.it is working fine.But while creating support message we are getting the following error message ERROR IN LOCAL MESSAGE SYSTEM
MESSAGE 009999000014 NOT COMPLETE. in solution manager and satellite system.
we have refer the following notes 824640,838063.please suggest me.
Regards,
Venkat

Hello Venkat,
If you are in SOLMAN 4.0 SP9 for solving the problem in SOLMAN apply note
1011376.
Which message number did you get in the satellite? please check that the user used in the RFC connection SM_..._BACK in SOLMAN system has roles
SAP_SUPPDESK_CREATE
SAP_SV_FDB_NOTIF_BC_ADMIN
In PFCG make sure that both roles has Authorization and User tabs in green status.
Hope this helps,
Dolores

Similar Messages

  • SOLMAN EHP1 - anyone can create support message in Satellite System's Help?

    Hi,
    I just curios that why everyone can create support message in satellite system-> help -> create support message?
    I tested with restricted profile user and without role SAP_SUPPDESK_CREATE, NO BP created but he still manage to create support message???? Any idea??
    Also, same goes to any user can process ticket in SOLMAN with no BP-Employee role and SAP_SUPPDESK_* roles assigned.
    Your kind input is very much appreciated.
    Thanks,
    Nicholas Chang

    Hi Nicholas
    If you are using a "Named" user instead of the Trusted Relationship in the RFC maintained in BCOS_CUST for entry OSS_MSG then this is quite possible. In this case the "Named" user will be used to call the interface to create message and the calling user ie the end user creating the ticket will only be used as "Reporter" of the message.
    The user entered in the RFC details probably has the authorization to create Support desk messages.
    Regards
    Amit

  • Create support message in satellite system

    Hi,
    What are the pre-requisites to configure  creating support message in satellite system.
    Thanks
    Rajesh

    Hi,
    Follow this blog u can set up ur service desk
    mainly it comprises of roles table entry and rfc destination in satellite systems
    /people/bruyneel.guillaume/blog/2008/05/02/service-desk-implementation-guide-part-i
    /people/bruyneel.guillaume/blog/2008/06/13/service-desk-implementation-guide-part-ii
    hope it solves ur problem
    Regards
    Prakhar

  • ERROR when Trying to create support message in satellite system

    Hi
    I have a wired problem.
    My user's are opening support message in the solman through the ECC system.
    But when a user is open a support message with the component FI he get the following message:
    "Error in Local Message System: Component FI does not exist: Check your entry Message was Not Created"
    I'm working with ECC6 and SOLAMN 4.
    Why I can't generate support message with the component "FI" ?
    Please advice
    Best regards
    Lior Grinberg

    Hi
    SAP Component is FIN Financials not FI that is why I thnk u r getting an error.
    Normal process is
    Whenever your user will post any message from any Transactions of FI module in ECC they goto help->create support message
    This will automatically fill the SAP Component
    Secondly if they are posting from initial logon screen they can choose the value by pressing F4 in SAP component field
    Hope it solves ur problem
    Regards
    Prakhar

  • Service desk error creating support message "help- create support message"

    Hi
    I'm customizing SM 7.0 SP Stack 15 service desk scenario. I'm in a VAR SAP, so It's a mandatory scenario.
    I've done all basic settings from General Settings, Connection to SAP, Online Documentation, ...,
    Business Partners, iBase, Basic BC-Sets for Configuration, Number Ranges. After them , for Scenario-Specific Settings-> Service Desk->Service Provider I've done all these steps. At SAP System Solution Manager, I've created solutions at dswp transaction and EW Alert are centralized these steps works. Transaction notif_create works and iBase are well mantained.
    The problem is when I try create a support message from satellite SAP system. I logged With a SAP user which is BP, key user and has authorizations in a satellite system and I choose help->create support message, so a pop-up appears and I fill the fields, and I press button (Save/Send). An error appears:
    Error in Local Message System: Access via 'NULL' object reference not possible. Message was Not Created
    In order solve the error I review:
    - The satellite SAP system is at the iBase installed components.
    - I've Assign Number Range for ABA notifications at SLF1 transaction.
    - I've Checked number range for Service Desk Message at SLFN transaction.
    - I've configured ABA Message transaction DNO_CUST01, transaction DNO_CUST04
    - (satellite system) Transaction sm30, table BCOS_CUST:
       Appl.            +       Dest.                                  +                     +
       OSS_MSG   W     SM_SMGCLNT010_BACK    CUST620          1.0
       TST_CUS                                                        0120009939
       RFC SM_SMGCLNT010_BACK works, SM recollects EW Alert from this satellite system
    - (satellite system) I logged with a SAP user with these roles:
      SAP_SUPPDESK_CREATE
      SAP_BC_CUS_CUSTOMIZER  according SAP NOTE 834534
      SAP_BC_CUS_ADMIN       according SAP NOTE 834534
      SAP_SV_FDB_NOTIF_BC_CREATE
      SAP_SV_FDB_NOTIF_BC_ADMIN
      All these roles are mantained.
    - I've review SAP Notes 834534, 864195, 621927(I haven't applied this SAP Note because it's older)
    Please could you help me?
    Thanks and Regards
    Raul

    Hi,
    When I try create a SAP message via help->create suuport message, I get the same error so I run help->create support message in a satellite system so I run help->create support message in Solution Manager
    system. Also, a dump is generated in Solution Manager when I try create support message or from satellite or from solution manager.
    ========================================================================
    Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED
    Date and Time          10.07.2008 10:17:26
    Short text
        Access via 'NULL' object reference not possible.
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "CL_BOR_SERVICE_PPF============CP" had to be
         terminated because it has
        come across a statement that unfortunately cannot be executed.
    Error analysis
        You attempted to use a 'NULL' object reference (points to 'nothing')
        access a component (variable: " ").
        An object reference must point to an object (an instance of a class)
        before it can be used to access components.
        Either the reference was never set or it was set to 'NULL' using the
        CLEAR statement.
    How to correct the error
        If the error occures in a non-modified SAP program, you may be able to
        find an interim solution in an SAP Note.
        If you have access to SAP Notes, carry out a search with the following
        keywords:
        "OBJECTS_OBJREF_NOT_ASSIGNED" " "
        "CL_BOR_SERVICE_PPF============CP" or "CL_BOR_SERVICE_PPF============CM004"
        "PROFILE_CONTAINS_PARTNERDEP"
        If you cannot solve the problem yourself and want to send an error
        notification to SAP, include the following information:
    Information on where terminated
        Termination occurred in the ABAP program "CL_BOR_SERVICE_PPF============CP" -
         in "PROFILE_CONTAINS_PARTNERDEP".
        The main program was "SAPMSSY1 ".
        In the source code you have the termination point in line 41
        of the (Include) program "CL_BOR_SERVICE_PPF============CM004".
    =========================================================================
    Thanks and Regards
    Raul

  • How to restrict usage of "Create Support Message" action in Help menu

    Dear Experts,
    hoping someone can help me to find a solution to this:
    in our company we are building a business process so that not everyone should be able to open a new support message under maintenance cycle, but only "Power Users" - we call them BPE for Business Process Experts.
    All the rest business comunity should filter their inquiries thru BPE's, and if BPE decides that Support Message is required, then (s)he will use the Create Support Message function under Help main menu.
    Is there any way in SAP to restrict usage of "Create Support Message" function to only a group of people (BPE) by security or other means, so that it's invisible (or not executable) by other people ?
    Thank you in advance
    Elena

    Hi,
    You can restrict the creation of support message thru the Auth Obj CRM_ORD_PR.
    Thnx,
    Waseem.

  • Error 513 while creating support message help menu in Solman system.

    Hi Expert
    I am trying to create support message though help in the Solman system. But i am getting an "error 513 message has not created in the Solution manager system".
    - maintained the BCOS_CUST table with RFC - NONE
    - have SAP ALL authorisation
    - using the transaction type SLFN for support message.
    - Check the Action profile for SLF1 and found OK.
    - Also refered some notes in the sap and implemented but still i am getting the same error.
    Please advice.
    Regards
    Kumar.

    HI
    Do u have BP existing for ur id in solman
    Use BP_GEN to create bp for ur user id
    otherwise using BP tcode and check if the identification tab is carrying details for solman system with curent client and userid
    Hope it solv ur prb
    Regards
    Prakhar

  • Add new field in the Create Support Message Popup Screen

    Hi Experts,
    I need to create Project Code Field in the standard popup screen Create Support Message
    Suggest me any Badi or FM or Bapi or Enhancement to create a new field and update the field value to the Support Message created.
    Please let me know if this is possible or not?
    Thank You,
    Sowjanya Sreekrishna

    Dear Abhijit
    Even after doing PGI, there are some fields which are in editable mode in delivery.  For example, in VL02N, if you select "Goto --> Header --> Shipment, you can see fields like Bill of Lading are in editable mode.
    If you specify what your requirement is, then probably, a better option can be given.
    Thanks
    G. Lakshmipathi

  • Wrong number range in ECC Message creation in "Create Support message " tab

    Dear All,
    While creating the support message in any R3 server (ECC,BW etc.) system by clicking
    help->create support message option in main menu tab.
    The message number sequence changes from existing to new saequence.
    The initial sequence is 9999011940 but the current sequence generated
    by system is 1549. We had updated our R3 system with SAP_APPL component
    stack to 17. This changed sequence is happening after patch upgrade.
    Thanks in advance.
    Regds
    Ravi Kant Arya
    +91 9818880902

    Hi Ravi,
    Did you also patch your SOLMAN system ?
    I believe this is controlled by number range object CRM_SERVIC  in your solution manager. Check OSS note 903528 (particularily the section around the resetting of the number range object)
    Regards.
    Ruchit.

  • Create Support Message via ESS

    Hi,
    I have come up with one new requirement to create support message from ESS.
    I have found one BSP application DSWP_CREATE_MSG for same and attached
    It in portal. Now the problem is, when message is created SOLD-TO-PARTY, Reported By
    Are not getting populated, even Ibase is not getting populated.
    I have mapped user with BP also.
    When same user creates support message from R/3 its works all fine.
    Please help me in this matter..
    Edited by: SHREE WADEKAR on May 29, 2009 3:19 PM

    Hi SHREE WADEKAR,
    Did you find solution for this issue?
    We encounter the same issue.
    Can you please share the solution?
    Thanks in Advance.
    Regards
    Sanjai

  • Create Support Message via Help - Limitation for certain people

    Hi,
    i try to configure my SolMan, so that only a couple of person can create a support message with Help -> Create Support Message.
    I look for a role, but can't find anything to solve this issue. Does anyone now what I have to customize, that only people I allow can create a support message in that way?
    Thanks in advance
    Michael

    Thanks for your replies, but this doesn't solve my problem
    1) When I don't create a business partner for those people, they can create messages, but then then the filed "message processor" would be empty in SolMan
    2) which role do you mean? I tested with a test-user without any role - he can create support messages as well...
    regards
    Michael

  • How to create Support Message in Solaman

    Dear All,
    I know how to create message in satellite system and configuration required for that but now my requirement is to create message in solman only and then further process the same as usual. How can I do that.
    NOTIF_CREATE is the transaction code for that but it ask for lot of details to create ticket. Can I create ticket form Help--->Create Support Message? Do I need to maintain table BCOS_CUST in solaman? What else configuration is needed to be done?
    Regards,
    Nikhil

    Hi Nikhil,
    There can be many reasons for 513 error.
    Please check the following steps in you systems:
    Check the number range assignment for SLF1 in transaction dno_cust01.
    Check for ur authorization of SAP_SUPPDESK_CREATE to create the messages.
    Go to transaction DNO_CUST04. Select the field NO_USER_CHECK, and check the "filed value". should be X
    Confirm Ur entries in Service Desk destinations in the Solution Manager System. OSS_MSG must exist
    Regards,
    Sunny

  • Help-Create Support Message In SAP

    Hi,
         When iam creating a new message from Help-Create Support Message it is throwing the error message as 513. Can anyone help me in the mentioned issue.
    Regards,
    Mirza Kaleemulla Baig.

    Hi Mirza,
    Please check the following:
    - Check that the users used to create the support desk message has the
    following authorizations.                                                                               
    SAP_SUPPDESK_CREATE   
    - Can you please attach the contents for the table BCOS_CUST in both the
    solution manager system and one of your satellite systems.   
    This table must show this entry at least:
    OSS_MSG     W     NONE     CUST620     1.0    
    - Check also note 1011376   
    Hope this helps,
    Dolores

  • Create Support Message from external system

    HI experts,
    I would like to change the Create Support Message screen(Menu->Help->Create Support Message) and add three fields namely: Category, Subject and Solution Number because currently these fields are not populated in the Service desk if I create message in this way unlike in using NOTIF_CREATE tcode where there are selection fields for these.
    Also, I'm creating the support message from an external SAP system and the messsage is sent to the Solution Manager system. The NOTIF_CREATE tcode does not exist in the external system as well as the whole package DSWP.
    Please let me know you rthoughts on this.
    Thanks
    Eric

    Hi guys,
    Thanks for your answers... But is it possible to call transaction NOTIF_CREATE from an external system?
    I have done something already so that those 3 fields will be automatically populated for a message sent from an external system.
    I changed the screen and called FM BAPI_NOTIFICATION_CREATE(a remote enabled FM which is the one being used by transaction NOTIF_CREATE to create a message) inside FM BCOS_SEND_MSG.
    I populated the category, subject and solution in the FM export parameters as well as the solution number in the sap data table. I put a destination also..
    This FM calls another FM DNO_OW_CREATE_NOTIFICATION which is the one being used from the external system but do not cater the functionality to send the 3 fields that we need.
    As you will notice, there are lots of standard objects that I've changed. =)
    My problem now is that the system data sent is the same with the system data if you create the message using NOTIF_CREATE. Some system that were sent when a message is sent from an external system is missing but at least the sap system and client ID is sent. There is no external reference number also. But hopefullly, the users will accept it. Can't find any other solution to this.
    Thanks,
    Eric

  • With SP16-17 we can't create support message from satellite system anymore

    hello,
    We have implemented the support package 16 and 17 SAPKITL427 in solution manager last week-end and since then all satellite systems can not create support message anymore.
    The process is perfectly working in solman itself and we don't think we have thus a process customizing issue here but who knows...
    The key user creates the message with the help -> create support message
    and when he saves it (clicking the mailbox button) he gets the following error
    Error in Local Message System: Function not available Message was Not
    Created
    In fact the error Message is BCOS088
    We debugged the function BCOS_CREATE_MSG and we found out that the function
    DNO_OW_CREATE_NOTIFICATION is returning error code 1.
    We checked out RFC connection and it looks ok
    There is no dumps in ST22, no error in SLG1 in both system...a nightmare
    The notification SLF1 is created in solman but the status field of the notification is empty and it looks that the record is somehow corrupted because you can't modify it with dnotifwl.
    Due to the fact that the notification is not correctly created the support message is also not created.
    SAP and our solman consultant are working on it since 2 days but don't have a clue.  Maybe some program where no regenerated correctly ?
    If you would have any idea in which direction to look, i would greatly appreciate
    thanks a lot
    best regards Xavier

    hi Rohit,
    on the satellit I have the following versions
    SAP_BASIS     700     0012     SAPKB70012     SAP Basis Component
    SAP_ABA     700     0012     SAPKA70012     Cross-Application Component
    PI_BASIS     2005_1_700     0012     SAPKIPYJ7C     PI_BASIS 2005_1_700
    ST-PI     2005_1_700     0006     SAPKITLQI6     SAP Solution Tools Plug-In
    SAP_BW     700     0013     SAPKW70013     SAP NetWeaver BI 7.0
    SAP_AP     700     0009     SAPKNA7009     SAP Application Platform
    SAP_HR     600     0018     SAPKE60018     Human Resources
    SAP_APPL     600     0010     SAPKH60010     Logistics and Accounting
    EA-IPPE     400     0010     SAPKGPID10     SAP iPPE
    EA-APPL     600     0010     SAPKGPAD10     SAP Enterprise Extension PLM, SCM, Financials
    EA-DFPS     600     0010     SAPKGPDD10     SAP Enterprise Extension Defense Forces & Public Security
    EA-HR     600     0018     SAPKGPHD18     SAP Enterprise Extension HR
    EA-FINSERV     600     0010     SAPKGPFD10     SAP Enterprise Extension Financial Services
    FINBASIS     600     0010     SAPK-60010INFINBASIS     Fin. Basis
    EA-PS     600     0010     SAPKGPPD10     SAP Enterprise Extension Public Services
    EA-RETAIL     600     0010     SAPKGPRD10     SAP Enterprise Extension Retail
    EA-GLTRADE     600     0010     SAPKGPGD10     SAP Enterprise Extension Global Trade
    IS-PS-CA     600     0010     SAPK-60010INISPSCA     IS-PUBLIC SECTOR CONTRACT ACCOUNTING
    IS-OIL     600     0010     SAPK-60010INISOIL     IS-OIL
    IS-M     600     0010     SAPK-60010INISM     SAP MEDIA
    IS-H     600     0010     SAPK-60010INISH     SAP Healthcare
    IS-CWM     600     0010     SAPK-60010INISCWM     Industry Solution Catch Weight Management
    INSURANCE     600     0010     SAPK-60010ININSURANC     SAP Insurance
    FI-CAX     600     0010     SAPK-60010INFICAX     FI-CA Extended
    FI-CA     600     0010     SAPK-60010INFICA     FI-CA
    ERECRUIT     600     0010     SAPK-60010INERECRUIT     E-Recruiting
    ECC-DIMP     600     0010     SAPK-60010INECCDIMP     DIMP
    IS-UT     600     0010     SAPK-60010INISUT     SAP Utilities/Telecommunication
    SEM-BW     600     0010     SAPKGS6010     SEM-BW: Strategic Enterprise Management
    LSOFE     600     0010     SAPK-60010INLSOFE     SAP Learning Solution Front-End
    ST-A/PI     01K_ECC600     0000          -     Application Servicetools for ECC 600
    APICON     1470000000     0000          -     APICON GmbH, Interface Add ON
    thank you Xavier

Maybe you are looking for

  • Error while installing HFM 9.3.1 Client on windows 7.

    Hello, I am trying to install and configure HFM 9.3.1 client on windows 7 x64 machine, but getting following two errors while configuring with shared service, in random manner. 1. An Unknown CSS error occurred. Please check that information entered i

  • Cost Component Structure (OKTZ) Issue - Max number of cost fields reached

    Hello. I'm having this issue in OKTZ when adding new cost component in an exisiting cost component structure. it says "maximum number of cost fields reached (40)". not sure what to do with this. please see screenshot http://img39.imageshack.us/img39/

  • Trouble connecting Apple TV to Sony TV (KV-24FV10)

    I am having some problems connecting my new Apple TV to my Sony TV (model: KV-24FV10). I used cables that previously was connected to my DVD but when I use them on the ATV the picture is black and white. I plugged the cables in so RED=RED, WHITE=BLUE

  • TV Episodes Appearing Under Movies

    Ever since I upgraded to Snow Leopard, TV episodes I've ripped from DVDs I own that I add to iTunes have been appearing in the movies category of Front Row. It is driving me bananas, because I have a lot of media in my library, and I enjoyed accessin

  • Can we develop cells or push buttons with increaseing number  auotmatically

    hi all    I am customizing a sinario which contains different number of  flats in different appartments. Sianrio is to customize Flat nos. as a blocks.  So if we give no.of Flats in an Appartment, can we get blocks with numbering with increase order.