Report support message activity

Hi,
I am looking for a report to trace activities of a support message, but can't figure out how to find one. I want to select a support message and see its log (date - user - modification etc). Could you recommend me a report, pls?
Best regards,
Ádá

Hello,
I am not sure if it is what you are looking for, but in a support message editing screen, if you go to Extras -> Change Documents, you can see who changed the message since its creation.
I hope this information helps.
Best regards,
Miguel Ariñ

Similar Messages

  • Creating support message field reported by doesn't fill

    Hi colleagues,
    When I create a support message field reported by doesn't fill automatically.
    I think that I've completed all required steps in order these fields were filled automatically. Fields sold-to party and support team are filled automatically, they work ok.
    The steps that I've checked:
    - The support message is created successfully from satellite message(SID=DES_01). The user which creates this message is zprueba5 exists with profiles: SAP_ALL, SAP_NEW at the satellite system.
    -In the solution manager system(SID=SMG), transaction ib52 for the satellite system is filled with partners: employee responsible, sold-to party and system administrator.
    - In the solution manager system(SID=SMG), zprueba5 exists with profiles: SAP_ALL, SAP_NEW.
    - Transaction bp, zprueba5 user contains BP roles: Business Partner, Employee, Bill-To Party, Financial Services and at the tab "Identification":
    External BP Number: SMG 010 ZPRUEBA5
    ID Type     Description                         Identification number
    CRM001    External System Identifier   DES_01 0020281686 100 ZPRUEBA5
    CRM001    External System Identifier   SMG 0020276689 010 ZPRUEBA5
    So, In the solution manager system(SID=SMG), crm_dno_monitor transaction when I open the support message just created from satellite system, I have an error because reported by field isn't filled.
    Please could you help me?
    Thanks and Regards
    Raul Aguilar

    Hi Nikhil,
    At this message I'm going to reply your last two replies.
    1.- You typed me "In ib52 select both the system simultaneously and then go to->parner and assign proper bp no for the respective partner function. You need to do it for every system may be users are same.
    I hope you have maintained proper access sequence i.e. via ibase."
    For each SAP System that I've defined at SAP Solution Manager, at ib52 transaction I've defined the three roles that IMG activity documentation types:
            Assign business partners with the following functions to the new iBase component systems:
                Administrator
                Key User
                Sold-to Party
    SAP Solution Manager Implementation Guide->SAP Solution Manager(SP 17)->Configuration->Basic Settings->Standard Configuration of Basic Settings->Solution Manager->iBase->Assign Business Partners to iBase Components ->transaction Change iBase (IB52), enter in field Installed Base '1' and I select the SAP System->Goto -> Partner
          Function                                        Partner      
        00000014  Employee Responsible     298
        00000001  Sold-To Party                  295
        SLFN0001 System Administrator      295
    2.- You typed me  "Select you partner determination procedure and double click on "User interface setting" here select appropriate partner functions and assign all of them in ibase as I said in above reply.
    You must not be getting reported by partner function. Take out System administrator. Motivate by assigning points."
    My Partner Determ. Proc. is SLFN0001, so I double click on User interface setting like you explained me, adn now appears:
    Header Screen:
    Sequence and Functions for (main) Partner Displayed
    Partner Function1 00000001  Sold-To Party (CRM)
    Partner Function2 SLFN0002 Reported by (CRM)
    Partner Function3 SLFN0003 Support Team (CRM)
    Partner Function4 SLFN0004 Message Processor (CRM)
    But now I don't understand if at ib52 transaction I've to add any role or if from "User interface setting" I've to delete any Partner Function. Could you detail me when you type "You must not be getting reported by partner function. Take out System administrator", please?
    Regards,
    Raul .

  • Support Message from satelite system: Reported By field blank only from BI

    Hi,
    I have configured the Incident Management for solman 7.1 with SP12. I am using the transaction type ZMIN that is a copy of SMIN.
    In our landscape are two satelite systems: BI and ECC
    When I create a message from managed/satellite system via HELP>Create Support Message, it comes to Solman the field "Reported By" is not filled automatically if I created the message from BI. The Creation from ECC works fine: the field "Reported By" is filled automatically.
    The system data is fetched up correctly and it includes the system info, component code and all details. Even the Support Team Determination with BRF+ is working fine.
    Not successful actions to solve the problem:
    - I tried some access sequences in Partner Determination for "Reported By":
         - Preceeding Document -> Reporter -> Current User
         - User
    - Checked IB52
    - Checked DNO_CUST04
         No_User_CHECK; No Existence Check for User; field value:X
    - Checked BP (Generated with BP_GEN):
         identification in BP seems correct (I added created/expiry date manually)
    - Checked BCOS_CUST.
    - Checked Read RFC.
    Has someone an idea what the problem could be?
    Thank You for your effort in advance,
    Beda

    Hi,
    1) Under identification tab in external BP no. put details as
    <Server short name>space<client>space<search term
    (which you have maintained in address tab or employee no.
    of that user in satellite system)>
    2) In ID type put CRM001
    3) Under identification put details as <Server short
    name>space<installation no.>space<client>space<search
    term (which you have maintained in address tab or
    employee no. of that user in satellite system)>
    4)Go to trns. BP>select BP role as "Employee"> Indentification tab--> Maintain user name same as user id of employee in satellite system or serch term you maintained while creating BP.
    Try this. Reward the points for useful answer.
    Regards,
    Niks

  • Service desk-Support Messages-"Reported by" not getting updated

    Hi gurus,
    In a support message when we create message from satellite system. System is not captuing automatically the "Reported by" field.(BP number of the creator).
    Can you pl guide me, is there any missing setting to capture this "Reported By" field.
    Thanks in advance.

    Hello,
    Execute tcode SPPFCADM.....
    There you have to select DNO_NOTIF Application.... scrolll down to get this application.....
    Now after selecting that application, click on "Define action profile and actions" tab.....
    Now you will get 2 actions profiles there....
    Select action profile SLFN0001_STANDARD_DNO...
    This action profile has two actions....
    Select action SLFN0001_STANDARD_DNO_CRM....
    In this Settings method call tab, select Change Processing parameter, there add....
    Element/Name/Short Description as --> PARTNER_FCT_CREATOR
    Structure--> CRMD_PARTNER
    Field--> PARTNER_FCT
    Under initial value tab enter SLFN0002. Save your settings and check it by creating new message.
    Regards,
    Nikhil

  • Sold-To Party and Reported missing when doing Help - Create Support Message

    Sorry, I know this has been asked multiple times, but I'm missing something in the responses.  The responses I am finding either don't seem to apply to my situation, or aren't detailed enough to explain what I'm supposed to be doing.
    Solution Manager 7.0 EhP1 SAPKITL435.
    If we try to do a "Help - Create Support Message" from within our production Solution Manager system, the "Reported by" field is correct, but the Sold-To Party is blank.
    If we try to do a "Help - Create Support Message" from within our non-production Solution Manager system, both the "Reported by" and  Sold-To Party fields are blank.
    If we try to do a Help - Create Support Message" from another SAP system whose RFC is pointing to our non-production Solution Manager system, both the "Reported by" and  Sold-To Party fields are blank.
    I've looked at IB52, as well as the SPRO activities under "Partner Determination Procedure."  I think a big part of my problem is that they just don'e make sense to me yet, because I can't figure out what I should be changing.
    For example, IB52 looks to me like it only applies if you want to assign something to the same person all the time.  Am I missing something there, or is that an answer to a different question?
    I also can't figure out if I need to create something new in "Define Access Sequences," or modify something existing, and, if I modify, to what?
    Does anyone know where I could find specific instructions for setting this up?

    Hi Brenda,
    Regargind this issue, please check if Sold-To party is maintained for
    your system with IB52 in your solman system as the steps below:
    SOLUTION MANAGER system
    ->IB52
    ->select the system on left hand side
    ->click on 'goto' on top menu
    ->Select 'partner'
    ->Now maintain Sold-To party
    Also check below note:
    1165357    Sold-to-Party is not assigned to Service Desk messa
    As you said ou already assigned then i would request you to please check if you have assigned at the system level or not. Somtimes people define at top of the tree and also at system level. Please assign at system level and delete all other. Most of the times this is the issue Sold-to-party doesnt fill automatically.
    For reported by field:
    Please check the note: 824640: Customizing missing for Service Desk in Solution
    read this note carefull and this will help you fixing the reported by issue.
    Please, make sure you have applied the following corrections:
    1439191 Incident Create: Message Reporter or Processor is not saved
    1486132 Incident Create: Enhance search help of Reporter field
    1497700 Work center: Message details not updated after refresh
    After this if you still having issue you need to provide more details but i think this will fix the issue.
    Thanks
    Regards
    Vikram

  • Report for Support Message,  Change Request and Change in one overview?

    Is there a report that shows the relation between the support message, change request and the change in one overview? I am already aware of the Change Management Reporting via SOLAR_EVAL, but this does not show the whole document flow in one overview.
    The incident message processors want to have a quick overview of the status of the changes that are created on the basis of the support message.
    If there is no report, could you point me in the right direction... Do I have to create a query or are you using BW for service desk/charm reporting?

    Hi
    chk te sap note
    [Note 1466131 - ChaRM Reporting: Performance of data update|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1466131]
    jansi

  • Different Transactions or Reports to find Support Messages.

    Hi,
    What are the different transactions available in SAP Solution Manager 4.0 SR1 system thorugh which we can get the support desk message listing depending on our requirements.
    e.g.
    support message list as per the module
    support message list as per the error message
    support message created by an users
    support message solved by user
    etc...
    right now i am using crm_dno_monitor transactions to monitor & update the support message status.
    Thanks,
    Avinash

    under CRM_DNO_MONITOR you can create a filter and save it as a variant, which can then be stored in a transaction. These transactions can in turn be assigned to roles.
    You can create variants using the Selection Monitor (CRM_DNO_MONITOR).
    Define the criteria in the Transaction Monitor, such as where priority = 1 and subject = system issue.
    Then choose from the menu: Goto > Variants > Save as variant
    Give it a name and click Save,
    Go to Transaction SE93:
    • Create a new transaction code
    • Select the transaction with parameters (parameter transaction)
    • Specify the transaction field, enter "Start_Report" and set "Skip entry screen"
    • For GUI support, select all options
    • Specify the following parameters:
    • D_SREPOVARI-REPORT = CRM_DNO_SERVICE_MONITOR
    • D_SREPOVARI-VARIANT = Name of the previously created variant
    • D_SREPOVARI-NOSELSCRN = "X"

  • Default value for Sold to Party and Reported By with Support Message

    I have customized the service desk scenario and went through the entire service desk implementation guide part I blog that talks about the partner setup.
    When I create a support message through the service desk scenario (under help) in the satellite system it does default the sold-to-party and the reported by person in the resulting document.
    When I create a support message in Solution Manager out of DSWP or SOLAR02 it does as well.
    However when I create the support message out of Solution Manager under help it does NOT default the sold to party and reported by, and I always have to correct that in the document later on.
    Has anyone experienced this before and can tell me why this happened. Obviously has something to do with setting up the partner in Solution Manager, but I do not understand how it can work for the Satellite system but not in Solution Manager itself.
    Thanks
    Paul

    > Has anyone experienced this before and can tell me why this happened. Obviously has something to do with setting up the partner in Solution Manager, but I do not understand how it can work for the Satellite system but not in Solution Manager itself.
    Did you generate BP entries for the SolMan system itself?
    Markus

  • Why is my Subscriber Message activity report empty?

    Hi,
    I trying to see who called and left messages for ceratin individuals before they were deleted. This report would be just what i am looking for except the columnes are all blank. Could it be becasue the user deleted the messages from their inbox or is there a parameter that has to be set. I am runnng CUCXN 7.1(5)ES7.
    Thanks in advance.

    Hi there,
    You are hitting this 7.x bug;
    CSCsr45007 - Subscriber Message Activity report problems
    Description
    Symptom:
    Subscriber Message Activity Report doesn't have data that is expected.  Many fields come up as N/A or blank.
    Conditions:
    This happens any time the report is run.
    Workaround:
    None.
    Further Problem Description:
    This underlying problems were diagnosed after 7.0 shipped and will be addressed in 8.0.  It entails a rewrite of this report.
    First Found in:                          (4)
    1.2(1),2.0,7.0(0.313),7.0(1)
    Status:
    Fixed
    Last Modified:
    May 26,2012
    Fixed in:                          (8)
    8.0(0.215),8.0(0.207),8.0(0.205),8.0(0.189)
    8.0(0.178),8.0(0.168),8.0(0.164),8.0(0.160)
    Product:
    Cisco Unity Connection
    Platform:
    Dependent
    Severity:
    4 - minor
    You may want to have a look at the ideas from Jeff in this thread
    https://supportforums.cisco.com/message/1209592#1209592
    Cheers!
    Rob
    "Every fool's got a reason to feelin' sorry for himself" - Springsteen

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

  • 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

  • Support messages not getting displayed in Messages Tab - Solar01/02

    Hi,
    I am having an issue in displaying the support messages under the message tab of Solar01 and Solar02. If I try to create a new message, the notification pops up and also gets saved. But the message does not get displayed under the tab.
    I can find that the message is properly created through transaction monitor.Even if I try to manually assign the support message number in Messages tab it gives an error saying the number does not exist.We are using SOLMAN 4.0 SP 11.
    Please help. Points will be awarded for useful answers.
    Regards,
    J.Prabananth

    Dear Prabanath,
           I am not too sure you will be able to assign numbers to support messages. Run the report CRM_DNO_MONITOR and get the full number from the report and insert the ticket number in issue messages tab and click on save and go back one screen, it will ask you if you want to save, select yes.
       That worked for me. Recently I have strugged to resolve this. We are on Solman 4.0 SP12. Check if you have all necessary permissions for you and do you have any thing in sm21 or st22 by any chance if the issue is related to support pack ?
         Let me know if there are any issues. I might be able to help you.
    N

  • The report of user activity

    The report of user activity
    Can anyone show how the sample report of user activity?
    Is there information that the website opened and how much time was running applications? Is used in an active way of running applications?
    I will be grateful for your help.
    Jerry

    Finding a program of monitoring user activity MAC OS X okazauje be very difficult.
    The program aims to monitor sites visited, but:
    - Can not save passwords
    - It can not sending data to an external server
    I can not find such software
    I found: http://www.net-monitoring-software.com/secure-order.html
    but it turns out that the manufacturer no longer supports MAC platform.
    Help! Is anyone familiar with this type of software?
    Pls. Help me.

  • Report Error Message in BPM Alert?

    Hi,
    I designed a BPM with a transformation step and a send step. For each step I have an exception branch where I want to trigger an alert, when something goes wrong.
    I already configured in TC ALRTCATDEF an alert category (Dynamic Text activated). And I made an container operatinon with folloing control step, where I for example report the message ID.
    But, going through the blogs and threads I didn't find the information, how I can report the exact error message, the error category (and in case of the send step the adapter and the adapter error text) to the alert. How can I get this data to put it into a container variable?
    Can anybody give me some information about that?
    Thanks in advance
    Dominic
    System: PI 7.0 SP15

    You can use the below information for raising an Alert for adapters.
    Specific Error Information from the Adapter Engine:
    Container Element
    ABAP Dictionary Data Type
    Meaning
    SXMS_TO_ADAPTER_TYPE
    CHAR70
    Adapter type
    SXMS_TO_ADAPTER_ERRTXT
    CHAR70
    Error text from the Adapter Engine
    Refer the below link:
    http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm

  • Support message from satellite to SolMan throughout web service

    Hi all,
    Currently we have activated support messages between satellite systems and SM. This functionallity is working fine; users create messages with "help->create customer message". But now we want users to create messages trhoughout web service (bsp). We know that this funcionallity exists, but we don't know neither the way it can be activated nor the way we can access to this service.
    Any idea?
    Thanks in advance.
    Bst Regds,
    Jose Sorli

    Hi Jose,
    For the creation of messages via WEB you can use BSP dswp_create_msg:
    In SICF activate this service
    After call the following url:
    http://server:XXXX/sap/bc/bsp/sap/dswp_create_msg?sap-client=YYY
    server: full hostname server of solman system
    XXXX: HTTP service that you can see in SMICM->Goto->Services
    YYY: Service desk client
    Look in SAP SMP for notes with string dswp_create_msg.
    From note  699087 ( a little old but ok):
    For the application to function, perform the following in the Solution
    Manager system:
        o  Ensure that an HTTP or HTTPS service is running in the Internet
           Communications Manager (transaction SMICM).
        o  Ensure that the services necessary for running BSP applications
           are activated (transaction SICF). These services include:
           -  /default_host/sap/public/bc/ur
           -  /default_host/sap/public/bsp/sap/htmlb
           -  /default_host/sap/public/bsp/sap/public/bc
           -  /default_host/sap/bc/bsp/sap/dswp_create_msg
    The URL necessary to call dswp_create_msg takes the following form:
        o  http://<host>:<port>/sap/bc/bsp/sap/dswp_create_msg?sap-client=
           <client>
    Where <host>, <port> and <client> are the host name, port and client
    respectively of the SAP Web Application Server. For futher information
    on the Internet Communications Manager, please see the SAP Web
    Application Server online documentation.
    Best regards,
    Dolores

Maybe you are looking for