Solution Manager NOTIF_CREATE

Hyee all,
I am trying to customize SAP SOLUTION MANAGER for creating support message (CRM_NOTIF_CREATE), but it gives an error "Defective call up of API's for the installed base".
Could anyone please help me out in this case.
Thanks in advance,
Palak.

hi anybody can help me for badi implementation assign mail (notif_change) badi definition (DNO_EVENT_SAVE)
E-mail Notification on changes.
I need all data declaration for that.
Problem in Func Module
CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
  EXPORTING
    DOCUMENT_DATA                    = DOC_DATA
  DOCUMENT_TYPE                    = 'RAW'
  PUT_IN_OUTBOX                    = ' '
  COMMIT_WORK                      = ' '
IMPORTING
   SENT_TO_ALL                      = SENT_TO_ALL
    NEW_OBJECT_ID                    = OBJECT_ID
  TABLES
  OBJECT_HEADER                    =
    OBJECT_CONTENT                   = INT_OBJ_CONT
  CONTENTS_HEX                     =
  OBJECT_PARA                      =
  OBJECT_PARB                      =
    RECEIVERS                        = INT_RECV
EXCEPTIONS
   TOO_MANY_RECEIVERS               = 1
   DOCUMENT_NOT_SENT                = 2
   DOCUMENT_TYPE_NOT_EXIST          = 3
   OPERATION_NO_AUTHORIZATION       = 4
   PARAMETER_ERROR                  = 5
   X_ERROR                          = 6
   ENQUEUE_ERROR                    = 7
   OTHERS                           = 8
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
I am not getting object_id.
Please help

Similar Messages

  • How to customize  solman_workcreate  screen in solution manager

    Hi all,
    i have a requirement as below.
    i need to change  solman_workcreate service in solution manager.
    1)i need to replace new message link under incident management with notif_create (tcode screen).
    2)provide search link to search solution database
    can you please tell me
    1)how to find out the standard application used by solman_workcreate service ?
    2)can we replace new message link with Notif_create tcode?
    3)how to call search solution database functionality(is there any standard application or TCODE available)?
    Regards,
    VANI

    Hi
    What is the error you are getting when you are adding the tcode.
    Have you checked the role of the system.....if not then
    in solar01 goto sap menu
    Business blueprint->sytem role...choose the appropriate system role
    In addition have you generate the Project IMG in the satellites system using solar_project_admin tcode  under system landscape tab
    check this guide
    https://websmp210.sap-ag.de/~sapdownload/011000358700002006042008E/HowTo_Impl_Bus_Proc.pdf
    Let me know further if this doesnt solve ur prb
    Regards
    Prakhar

  • 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

  • Solution Manager - Error Message DSWP349 -  No IBASE Components Exist ...

    The subject error DSWP349 occurs when using transaction Notif_Create for a new Service Desk Message. 
    The error message points to the use of IB52/IB53 which has already been correctly (as far as I can tell) used to set up the IBASE components.
    The error message also point to Note 824640 which I have checking out and also points to Note 1059271 from SAP Service Marketplace.
    I am going to try and apply some of those notes' recommendations but as they do not seem directly relevant, am looking for any other suggestions in the meantime; for example, if anyone has an printout example of how the IBASE and its lovely components should look in IB52/IB53 that would be most appreciated !     
    Last point.  Maybe part of the problem is that our SAP Solution Manager only links to one other internal SAP system and is not 'connected' to SAP AG (as it is an external system - this for security reasons), however we do have, for example, some external RFCs entered as part of the configuration.
    Thanks all.

    Hi
    The issue is now resolved, this is how I did it.
    1) Removed entries from BCOS_CUST from client 000 for OSS_MSG which was pointing to the RFC name
    Then got another error:
    No RFC connection to the central lock information management system.
    The project lock functionality is active in the local system, but there is no RFC connection to the Solution Manager system.
    2a) Ran the report in SA38 TMW_CONTROL_PROJECT_LOCK with selection for Deactivate the "project lock functionality".
    2) Filled the "Deactivate Project Lock" field with "X" then clicked EXECUTE.
    Problem got Solved.
    Thanks
    Ashish

  • How to start the Solution Manager Implementation

    Hi Gurus , I am in Solution manager implemnetation project , and i wanted built the exsisted landscape into Solman  so any one can help me out in this like where to and how to start.

    Hi Gurus, i wanted to implement these concepts
    Configuring Solution Manager
    Configuring Solution Manager
    1)      Solution Monitoring
    a       SAP EarlyWatch Alert
    a1      Setting-Up EarlyWatch Alerts    Y
    a2      Manually Executing Downloads    Y
    a3      Create Report and Display Session Details       Y
    a4      Save, Retrieve and Archive EarlyWatch Alert     Y
    b       Service Level Reporting
    b1      Service Level Reporting Change Mode     Y
    b2      Maintain General Settings       Y
    b3      Specify Systems and Contents for Service Level Report   Y
    b4      Select Business Processes for the Service Level Report  Y
    b5      Select Business Processes from the Business Process Monitoring  Y
    b6      Process Service Level Report Data Manually      Y
    b7      Create Service Level Report     Y
    b8      Create, Save and Archive Service Level Report Manually  Y
    b9      Process Service Level Report Session    Y
    b10     Send E-Mail Automatically       Y
    b11     KPI Calculation Y
    2       Configuring Alert Monitor
           Central System Administration (Part of ALERT Monitor)
    c2.1    MTE Classes and Attribute Groups        Y
    c2.2    Methods Y
    c2.3    Operating the Alert Monitor     Y
    c2.4    Actions in the Alert Monitoring Tree    Y
    c2.5    Selecting Nodes in the Alert Monitoring Tree    Y
    c2.6    Elements of the Alert Monitor   Y
    c2.7    General Properties of Monitoring Tree Elements  Y
    c2.8    Properties of Monitoring Objects and Attributes Y
    c2.9    Customizing the Alert Monitor   Y
    c2.10
    Changing Properties in the Alert Monitoring Tree
           Y
    c2.11
    Changing Properties in Customizing Transaction RZ21
           Y
    c2.12
    Triggering a Heartbeat Alert if No Values Are Reported
           Y
    c2.13
    Changing the Frequency of Method Execution
           Y
    c2.14   Defining, Releasing, and Transporting Methods
           Y
    c2.15
    Assigning Methods to MTE Classes or Individual MTEs
           Y
    c2.16   Assigning Methods to MTE Classes or Individual MTEs     Y
    c2.17
    Editing Monitors and Monitor Sets
           Y
    c2.18
    Creating and Editing Monitor Sets
           Y
    c2.19   Transporting Monitor Sets and Monitor Definitions       Y
    c2.20   Copying, Renaming, and Deleting Monitors        Y
    c2.21   Creating and Changing Monitors  Y
    c2.22   Rule Node: Rule Description and Use     Y
    c2.23   Defining Monitors with the DEFINE_R3_SYSTEMS/GET_MTE_BY_CLASS Ru        Y
    c2.24   Defining Monitors with the Rule GET_MTE_BY_CLASS_AND_OPTIONS    Y
    c2.25   Defining Monitors with the Rule GET_MTE_BY_CLASS_AS_VIRTUAL     Y
    c2.26   Copying a Monitoring Properties Variant Y
    c2.27   Create Monitoring Properties Variant    Y
    c2.28   Change Monitoring Properties Variant    Y
    c2.29   Activating a Monitoring Properties Variant      Y
    c2.30   SAP-DEFAULT     Y
    c2.31   Creating a New SAP-DEFAULT Variant      Y
    c2.32   Monitoring Multiple Systems     Y
    c2.33   Monitoring Multiple Systems: Defining RFC Connections   Y
    c2.34   Monitoring SAP R/3 3.x Systems  Y
    c2.35   Creating the CSMREG User        Y
    c2.36   Monitoring Multiple Systems with an Identical System ID Y
    c2.37   System Groups in the Alert Monitor      Y
    c2.38   Deactivating and Reactivating Monitoring Tree Elements  Y
    c2.39   Deleting and Restoring Nodes in the Alert Monitoring Tree       Y
    c2.40   Display Options of the Alert Monitor    Y
    c2.41   Saving and Resetting the Layout of a Monitor    Y
    c2.42   Extending the Shared Memory Area        Y
    c2.43   Setting Up a Central Data Cache         Y
    c2.44   Configuring the Caches of the Monitoring Architecture   Y
    c2.45   Working with All-Clears (Green Alerts)  Y
    c2.46   Displaying the History of the Threshold Values of Performance No        Y
    c2.47   Availability Monitoring with CCMSPING   Y
    c2.48   Installing Availability Agent CCMSPING  Y
    c2.49   Changing the Monitoring Frequency and Timeouts of CCMSPING      Y
    c2.50   Adding Systems to the Availability Monitoring Manually  Y
    c2.51   Finding and Correcting Errors with CCMSPING     Y
    c2.52   Configuring Availability Monitoring     Y
    c2.53   Creating and Changing Monitoring Rules  Y
    c2.54   Changing Monitoring Setting of Servers and Groups       Y
    c2.55   Using Multiple CCMSPING Agents  Y
    c2.56   Creating and Changing a Monitoring Pause        Y
    c2.57   Monitoring System Groups with CCMSPING  Y
    c2.58   Availability and Performance Overview Monitor   Y
    c2.59   Monitoring Log Files with CCMS Agents   Y
    c2.60   Structure of the Log File Template of the Log File Agent        Y
    c2.61   Example Log File Templates      Y
    c2.62   Logfile Monitoring Monitor      Y
    c2.63   Monitoring Selected Processes with SAPOSCOL     Y
    c2.64   Monitoring Response Times of Transactions or Clients    Y
    c2.65   Monitoring Database Tables with the Alert Monitor       Y
    c2.66   Self-Monitoring of the Alert Monitor    Y
    c2.67   Selected Alert Monitor Methods  Y
    c2.68   Forwarding Alerts to Alert Management (ALM)     Y
    c2.69   Interpreting a Text Attribute as File Name/URL and Display Content      Y
    c2.70   Displaying a Subtree as ALV Grid Control        Y
    c2.71   Defining an Automatic Alert Notification        Y
    c2.72   Auto-Reaction Method: Execute Operating System Command  Y
    c2.73   Setting Up Central Auto-Reaction Methods        Y
    c2.74   Installing CCM4X        Y
    c2.75   Activation in the background,if the Host restarts       Y
    c2.76   Creating RFC Connection Y
    c2.77   Copying File from Solution manager to agents    Y
    c2.78   Copying version for SAPCCM4X    Y
    c3      Central User Administartion(CUA)
    c3.01   Create manaintain landscape     Y
    c3.02   Creating RFC    Y
    c3.03   Create Logical clinets in SM1   Y
    c3.04   Field distribution parameters   Y
    c3.05   Transfering users from child system     Y
    2       Service Desk
    a       Set-Up Message Creation in Web Browser  Y
    b       Create support messages with NOTIF_CREATE       Y
    c       Process Messages in Service Desk        Y
    d       Search for Solutions to Support Messages        Y
    e       Copy Support Message into Solution Database     Y
    f       Forward Support Message to SAP  Y
    g       WebClient Interaction Center    Y
    h       Create Messages with Interaction Center WebClient       Y
    i       Process Messages in the Interaction Center WebClient    Y
    j       Service Desk for IT Service Providers   Y
    k       Using an External Service Desk  Y
    l       Connect an External Service Desk        Y
    m       Service Desk Customizing Error Analysis Y
    it's very high prioriety
    Cheers

  • BI Content - Solution Manager (Notifications)

    Hi,
    I´ve checked the Solution Manger content at BI Content and I ended up not knowing the right Infocube (the description is not available) to activate/use to check information generated by transaction NOTIF_CREATE in Solution Manager where we use to controls project issues.
    Does anyone knows if there´s an Infocube that this kind of information can be analyzed ?
    Thanks in advance.
    Fábio
    List of available Infocubes that can be activated:
    0SM_OBPM 0SM_OBPM
    0SM_BPM 0SM_BPM
    0SMD_CA01 0SMD_CA01
    0SMD_CA02 0SMD_CA02
    0SMD_EA1D 0SMD_EA1D
    0SMD_EA1H 0SMD_EA1H
    0SMD_EA2D 0SMD_EA2D
    0SMD_EA2H 0SMD_EA2H
    0SMD_EA3D 0SMD_EA3D
    0SMD_EA3H 0SMD_EA3H
    0SMD_EA4D 0SMD_EA4D
    0SMD_EA4H 0SMD_EA4H
    0SMD_EA5D 0SMD_EA5D
    0SMD_EA5H 0SMD_EA5H
    0SMD_EA_H 0SMD_EA_H
    0SMD_PE2D 0SMD_PE2D
    0SMD_PE2H 0SMD_PE2H
    0SMD_PERH 0SMD_PERH
    0SMD_PI2D 0SMD_PI2D
    0SMD_PI2H 0SMD_PI2H
    0SMD_SB1S 0SMD_SB1S
    0SMD_ME1H 0SMD_ME1H
    0SMD_ME2H 0SMD_ME2H
    0SMD_ME3H 0SMD_ME3H
    0SMD_ME4H 0SMD_ME4H
    0SMD_ME5H 0SMD_ME5H
    0SMD_MPCA 0SMD_MPCA
    0SMD_MPEH 0SMD_MPEH
    0SMD_MPIH 0SMD_MPIH

    Hi Fabio,
    I'm using 0CRM_SRV_PROCESS_H as datasource and 0CSRV_C01 as data target.
    This is a kind of CRM dataflow, because data generated by tr-cd NOTIF_CREATE can be able to treat as CRM data.
    Regards,
    Kobayashi

  • Solution Manager  - Things to be learned

    Hi Gurus
    could any one help me in letting me know the following details.
    i)  I need to know the T codes which a good SolMan Consultant should be
        familiar of working with.
    ii) I heard that , its better to learn Basis along with Solution Manager.If that is the
       case ,could any one list out the T codes.
    In brief i need to know the areas which a good SolMan cosultant must be familiar with.
    Points will be rewarded for appropriate answers.
    Thanks in advance.

    Hi Raju,
    Normally SolMan Tcodes that will be used by the end-users is like
    Solar01 - functional consultants use to create blueprint structure
    Solar02 - functional consultants use to do configurations in the satellite systems Stwb_work - Test Managers use to create test plans & packages and to assign to testers
    Stwb_2 - testers to perform testing
    notif_create - the message creator can create the service desk message from the solman system
    Even though the above are used by different end users, SolMan consultant should be familiar with these transactions to help the end users in using them effectively.
    (ii) Normally all administrative configurations of the SolMan system need to be done from SolMan's SPRO
    (iii) Apart from that setting up the system landscape can be done by BASIS consultants using SMSY transaction
    (iv) Creating the project and landscape for the project can be done using SOLAR_PROJECT_ADMIN transaction
    (v) Lot of BASIS related activities like monitoring, EWA, etc can be done using SOLUTION_OPERATION transaction
    (vi) SOLAR_EVAL transaction helps in generating lot of reports.
    (vii) In the RMMAIN transaction you can get lot of accelerators(templates for various project deliverables).
    (vi) These are basic transactions. Apart from that for Service Desk Management, Change Request Management and all we have certain other transactions and activities.
    best regds,
    Alagammai.

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

  • Define Service Desk Destination in the Solution Manager System (Dump creen)

    hi,
    in SPRO when i click on Define Service Desk Destination in the Solution Manager System
    i got dump screen with the error below 
    any help?
    Runtime Errors         SAPSQL_EMPTY_TABNAME
    Except.                CX_SY_DYNAMIC_OSQL_SYNTAX
    Date and Time          13.07.2008 14:05:57
    Short text
        A dynamically specified FROM clause has an unexpected format.
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "SAPLSHI2" had to be terminated because it has
        come across a statement that unfortunately cannot be executed.
    Error analysis
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SYNTAX', was not
         caught in
        procedure "STREE_READ_NODE_GENER" "(FUNCTION)", nor was it propagated by a
         RAISING clause.
        Since the caller of the procedure could not have anticipated that the
        exception would occur, the current program is terminated.
        The reason for the exception is:
        The running ABAP program attempted to execute an Open SQL statement in
        which a FROM clause was specified dynamically in the field "TABLE_NAME". In
         this
        FROM clause, either a table name after a join operator is missing, or an
         alias name after the key name "AS". The field "TABLE_NAME" could be empty as
        well.
    regards

    Hi,
    I am facing the same problem. What is SP15 ?
    Is there any SAP Note that can be applied to correct this ?
    Thanks.

  • Implementing the Enterprise Support in Solution Manager

    Hi Experts,
    Can anybody tell me what are the pre requisites to implement Enterprise support in solution manager?
    Also let me know what are steps involved in implementing the enterprise support.
    Thanks in Advance
    Hari

    Hello Hari,
    In order to implement Enterprise Support your organization should registered as a Value Added Reseller(VAR) with SAP. You can get all the required documentation under https://websmp104.sap-ag.de/solutionmanager --> Information for VARs, ASPs and AHPs which is in the left hand side of the page. However, you need to have a S-user ID of the VAR.
    The following are the steps need to perform in implementing the Enterprise Support firmly known as Service Desk for VARs.
    1. SAP Solution Manager basic settings (IMG)
      a) Initial Configuration Part I
      b) Maintain Profile Parameters
      c) Maintain Logical Systems
      d) Maintain SAP Customer Numbers
      e) Initial Configuration Part II
         1) Activate BC Set
             a) Activate Service Desk BC Set
             b) Activate Issue Monitoring BC set
             c) Set-up Maintainance optimizer
             d) Change online Documentation Settings
             e) Activate Solution Manager Services
             f) Activate integration with change request Managemnt
             g) Define service desk connection in Solution Manager
       2)Get components for SAP Service Market place
            a) Get SAP Components
       3) Get Service Desk Screen Profile
           a)generate Business Partener Screen
       4)Copy By price list
           a)activate Service Desk BC Set
           b)Activate Issue Monitoring BC set
           c)Set-up Maintainance optimizer
          f) Business Add-In for RFC Connections with several SAP customers
          g) Business Add-In for RFC Connection of Several SAP Cust. no.
          h) Set-Up SAP Support Connection for Customers
          i) Assign S-user for SAP Support Portal functionality
          j) Schedule Background Jobs
          k) Set-Up System Landscape
          l) Create Key Users
          m) Create Message Processor
    2. Multiple SAP Customer Numbers
          a) Business Add-In for RFC Connections with several SAP customer numbers
          b) Set-Up SAP Support Connection for Customers
    3. Data transfer from SAP
          a) Data Transfer from SAP
    4. Create u201COrganizationu201D Business Partner
    5. Service Provider function (IMG)
          a) Business Add-In for RFC Connections with several SAP customer numbers
          b) Business Add-In for Text Authorization Check
          c) Activate BC Set for Service Provider
          d) Activate Text Types
          e) Adjust Service Desk Roles for Service Provider Menu
    6. Service Provider: Value-Added Reseller (VAR)
          a) Business Add-In to Process Actions (Post-Processing Framework)
         b) Activate BC Sets for Configuration
         c) Create Hierarchy and Product Category
         d) Set-Up Subcategories
         e) Create Business Partner as Person Automatically
         f) Set-Up Automatic Confirmation of Messages
        g) Maintain Business Partner Call Times
        h) Set-Up Incident Management Work Center
    7. Work Center (Web UI)
        a) Activate Solution Manager Services
        b) Assign Work Center Roles to Users
    Hope it helps.
    Regards,
    Satish.

  • Install Solution Manager in RedHat Enterprise 6 with Oracle 11

    Hello ,
    In the marketplace-PAM,  RedHat Enterprise 6 is not listed as approved for EHP1 Solution Manager 7.0 64 bit (unicode) with Oracle.
    Does anyone have any information on this subject?
    Has anyone installed the Solution Manager 7.0/Oracle with RedHat Enterprise 6?
    tks

    Yes, you are correct. Apart from PAM, following Note confirms this. RHEL 6 is not supported yet for Oracle, is in planning stage.
    Note 1565179 - SAP software and Oracle Linux
    Thanks

  • System landcape in large enterprise with solution manager

    Dear Guru,
    Do you have any ideas of how to set up Solution Manager in a big national enterprise?  Let's suppose
    a big company has a headquarter and serveral branches.
    Every branch has its ERP, BW, etc,  do you think it is better to set up respective Solution Manager system
    for each branch or just create a powerful one centrally in the headquarter. Of course the latter means
    less management but more authorization seperation related actions.
    Is there any recommendation for this situation? Your opinion and insight is highly appreciated.
    Thanks
    Ray

    Dear Gugu,
    I know Solution Manager support some scenarios for multiple customer .e.g VAR in service desk.
    But is it possible for hide solution or project infomation, especially content of respective business blueprint
    to different customers?
    I mean we want to use one single Solution Manager for multiple customers, but customers do not want their
    owned document and business process information shared with other customers.
    e.g.  one customer log on to SOLMAN, then he could view project or solution information of other customer,
    furthermore, he could also build up his business blueprint referring to other customer's  business blueprint.
    Is it possible to segregate this infomation?
    Thanks a lot.
    Ray

  • Logical systems while implementing charm in solution manager

    Hello Everybody,
    I just wanted to know how many logical systems we need while implementing charm in solution manager 7.0. I have 3 clients in development , 3 clients in Quality and 1 client in production.
    Thank you,
    vikram.

    Hi Vikram,
    Yes, i1n ChaRM we always work with logical systems, I mean clients.
    The standard is:
    DEV -> QAS -> PRD
    However, you can also use:
    - Minimum
    DEV -> PRD
    - Target groups
    DEV -> QAS -> PRD
             - > TST
    DEV -> QA1 -> QA2 -> PRD
    DEV -> QA1 -> PR1
             -> QA2 -> PR2
    There are a lot of combination possible.
    BR
    Fernando

  • XI 3.0 and BW 3.5 system type/logical component in Solution Manager

    We are in the process of performing an upgrade for ERP 2004, XI 3.0 and BW 3.5. Initially this is being done in the sandpits. All systems are configured and connected our Solution Manager to download the packages.
    We are unable to determine what type of system the XI 3.0 and BW 3.5 should be configured under. For example, previously we had an issue where ERP was configured as ECC 5.0 rather than ERP 2004. This was causing an issue in MOPZ where the upgrade option wasn't visible in a maintenance transaction. The same issue is now happening for XI and BW.
    Please advise on the system type (logical component to use) for XI 3.0 and BW 3.5 in Solution Manager as SAP have made it very confusing. Currently both are under type Netweaver 04.
    Regards,
    -Rohan

    Hi
    I believe that SAP hasn't upgrade option for BW 3.5, Check link:
    https://service.sap.com/solman-mopz
    Upgrade
    a "straight" upgrade for SAP Business Suite (upgrade from SAP ERP 2004 to SAP ERP 6.0, for example) is not supported by Maintenance Optimizer
    Upgrade with an Installation of an Enhancement Package is supported for SAP ERP, SAP SCM, SAP SRM and SAP CRM
    Regards
    William Neira

  • Using HR data in R/3 to create business partners in Solution Manager

    Is it OK for me to setup Solution Manager to automatically download HR data from R/3 to create the Business Partners (employee role) in Solution Manager?
    We have setup SAP CRM 4.0 to automatically download the HR data and create Business Partners (employee role) in CRM.  Since Solution Manager has the CRM component in it, I assume we can do it as well in Solution Manager.
    Regards,
    Mel Calucin
    Bentley Systems

    We did it, i don't see the problem...

Maybe you are looking for