Query status of support message to define a schedule condition

Hi Experts!
I have read a lot of documentation and done a lot of custumizing about this topic but this one is driving me nuts for days now.
I am trying to query a certain status of a support message to use it for scheduling an (mail)action.
The deal is I am able to query every status of a support message except the values "Sent automatically to SAP" (E0011) and "Escalated" (E0009).
[See picture|http://i31.tinypic.com/nq6afn.jpg]
Somehow those two status are not user status but something else.
Even the document is in status "Sent to SAP" (E0004) AND "Sent to SAP automatically" (E0011) an action will not be scheduled if the schedule condition is set to "user_status = E0011" or "user_status = E0011 AND user_status = E0004"
I have been also playing around with container element AUTO_STATUS (reference TJ30 | ESTAT or datatype CRM_J_STATUS or datatype CRMT_STATUS)
No success yet.
Anyone got a solution for this one?
Is it possible to retrieve those status without custom developement?
Thanks in advance
Christian Kaunzner
PS: I already know the email configuration guides which are available for Service Desk / VARs
@Mrs. Popp: thanks for setting back all those test messages to customer action!!

Hi Prakhar,
my final goal is to trigger a mail when status is "E0002" (in process) AND "E0011" ("aut. forwarding to SAP" is active).
For testing porpuses I am using E0009 and a (non-automatic) action which should be available via toolbar.
I already tried many conditions including:
&CRM Service Process.User Status& = E0009SLFC0001
&CRM Service Process.User Status& = E0009SLFC0001 AND &CRM Service Process.User Status& = E0002SLFC0001
&CRM Service Process.User Status& [*] E0009SLFC0001
&CRM Service Process.User Status& [*] E0009++++++++
Non of these are working.
When using:
&CRM Service Process.User Status& [*] E0002SLFC0001
or
&CRM Service Process.User Status& = E0002SLFC0001
the action is available. So the syntax of the schedule condition is correct. Just for some reason E0009 and E0011 are not handled the same way other status are.
Basically this is the way it should work and it is working for all status E0001, E0002, E0003, .... except E0009 and E0011.
In your system could you please try to schedule an action using E0009 only?
Thanks in advance
Edited by: Christian Kaunzner on Jul 27, 2009 11:04 AM

Similar Messages

Status Profile and User Status for Support Message

Hi All,
We need to customize Status Profile and User Status Specifc to customer requriments.
we need the following Status for Support Message:
Open
Accepted
Rejected
Fixed
Retest
Closed
Note:
1] Only the Message creator should be able Set staus Open and Closed
2] Message Processor should only set status Accepted, Rejected, Fixed and Retest
I have created the Status Profile in BS02.
Can some one help me the steps or guide how to implement the above logic and restrict the status access between Message Creator and Message Processor
Thanks!
Regards,
Pradeep L

> 1] Do i have to create different Auth.key for Message processor and Message creator and then assing them in BS02 to Status Profile?
       Anand: Diffrent authorization key for different statues......not for message processor and creator
> 2] Now how do i assign this Auth.Key to the Auth Object B_USERSTAT?
       Anand: Using Tcode PFCG, this can be done.... Consult Basis.....
>     do i have to create a new Zrole and assign or is there any other way.
       Anand: Yes u need to create a Z role and include that authorization objects in that z role....
       so u might have to create 2 Zroles and then assign them to the persons concerned....
Inspire ppl by rewarding
Regards,
Anand...

Define aditional status of support messages

Hello every body
Is there a way to define aditional status besides the standar (new, in pocess, cutommet action, etc?

Dear Marcelo
Yes you can do the same
goto spro->solution manager->scenario specific->service desk->status profile
got change status profile
Choose SLFN0001 and copy it to Z smthng...then you can create ur own zstatus
Secondly after ur zstatus profile is completed
spro->solution manager->scenario specific->service desk->defin action profile->assign action profile to busines transaction type
Choose SLFN stnd for service desk double click it.
So assign here ur zstatus profile to ur SLFN transaction type.
Also can check this guide
https://websmp202.sap-ag.de/~sapdownload/011000358700001197002005E/Addtional_Information.pdf
Regards
Prakhar

Support Message Status should default to Incident in Solution Manager

Hi Friends
Need your Help!!
I need to change the Priority settings set for the support message in Solution Manager , If a user logs a support message in the ECC system (production) with any priority (low, medium, high, very high etc.) it should default to Incident in Solution manager.
From there the client wants to classify the Priority as per his requirement in Solution Manager.
The current settings are like below
For a Low Priority it is defaulting to Incident
For a Medium Priority it is defaulting to 1: Bug P1-2
For a High priority it is defaulting to 2: Bug P3-4
For a Very High Priority it is defaulting to 3: Bug P5-10
Really appreciate your help, many thanks.
Kind Regards,
Vattikonda.

Hi
thank you for response.
It is the clients requirement to default the priority status to Incident if a support message is created from a managed system (ECC).
for e.g,
An user creates a support message in ECC production client giving the relevant input and he selects the priority as High, this created message should default to Incident in solution manager.
please see how the current settings are from my earlier at the bottom..
Kind Regards,
Sandeep.

Service Desk: How do i Reply back to a support message?

I am in the process of configuring the servcie desk.
I am using Solution manager 4.0 sp13.
I am recieving the messages in the Service desk, and the suport team members are able to get their respective messges based on the PFAC responsibility rules.
How do the support team members reply back to the message creater about the completion of the work,?
Or
put it another way, how does a mesage creater in a satellite system know the status of his message?
Lalchand.R

Hi Lalchand,
An action can be defined in configuration (SPRO) for sending mail notification to message creators whenever the message gets a particular status.
You can copy the standard action ' Email message to creator' under the SLFN action profile and change the conditions for automatic trigger.
Regards,
Kathir

Sold-to party rol doesn't fit new support message

Hi,
I'm configuring Solution Manager SP17, I work at VAR SAP so I've to manage many customer numbers. Some scenarios are running.
I've a customer with three SAP systems, these SAP systems have been defined at smsy transaction in Sol. Man. VAR successfully. So these systems exists at ib52 transaction too.
From satellite SAP (customer site):
   1.- system->system->status Installation number is 0020225238
   2.- at service.sap.com for this customer this is the installation number that appears for this SAP system.
At Solution Manager VAR SAP(VAR site):
   1.- smsy->systems at the header data tab this installation number appears 0020225238
   2.- ib52 for this SAP system I've defined this system with one entry to the correct client:
              BWP 0020225238 100
   3.- I've filled for this SAP System and the other two SAP systems for this customer partner so I select BPW SAP system->goto->partner.The business partner with function sold-to party has these roles: business partner and sold-to party. At the identification tab it has 3 entries(one per SAP system):
    BWP 0020225238 100 SANTI
If I execute steps to create a support message:
1.- from satellite SAP system(customer site) help->create support message I create and send successfully the support message
2.- from Solution Manager VAR SAP(VAR site) crm_dno_monitor transaction I open the support message just created and :
           - sold-to party field is empty.
(this field is filled successfully to the other two SAP systems for this customer)
          - at transaction data buttton->SAP Attributes tab the installation number that appears is 0120009939 and not 0020225238.
Please could you help me?
Thanks and Regards.
Raul

Hi Sreedhar,
Thanks for your reply.
As I typed at my first description. The role sold-to party is working. This customer has three SAP systems: R/3 development, R/3 productive, BW productive. So when the customer sends a SAP message from his SAP satellite system to our SAP VAR solution manager, the sold-to party rol works only to R/3 development, R/3 productive but doesn't work to BW productive(Netweaver 04).
I've chequed that:
- ib52 transaction the SAP satellite system BW productive has the same installation number that you can view If you logon at the SAP satellite system BW productive->system->status. The client is correct too.
- bp transaction the sold-to party Business Partner has three lines( one per SAP system).
Please could you help me?
Thanks and Regards.
Raul

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"

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.

Fields missing in Support Message from CRMD_ORDER

Hi All,
when we create a Support Message from transaction notif_create, there some fields like
component, project and solution
but when we create the same support message from transaction crmd_order, i could not find those fields.
Please suggest
Regards,
Pradeep L

Hi Prakhar,
Is there any work around where we can configure such these fields would be visible in the transaction CRMD_ORDER.
The issue we are facing is:
Standard Transaction Type: SLFN is being used for another project in the same system
Now i have created another Transaction Type: ZSLF with customized status, action and date profile.
Now we cannot use notif_create as it will pick up SLFN and we cannot change it to ZSLF as the other project is using it
Please suggest
Regards,
Pradeep L

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 .

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

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

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

Howto Close support message in Solution Manager

Hello,
Iu2019m installing and setting up the Service Desk on my Solution Monitoring system.
Iu2019m able now to create a support message in my satellite system with menu action u201CHelp  Create Support Messageu201D. The message is put in the queue and could be edited in the tr-Solution_Manager under the Item u201CService Desk  Messagesu201D. When I open a message Iu2019m able to change the status of the message form u201CNewu201D to u201C in progressu201D etc. but the item u201CConfirmedu201D is always gray!
Could anyone explain to me how I or the end user could confirm thesupport message?
I couldnu2019t find a detailed description about the process flow only a global one.
Thanks for the information.
Kind regards,
Richard Meijn

Hi Meijn,
Already solved? If no, check the following customizing.
In SPRO, SAP Solution Manager -> Scenario-Specific Settings -> Service Desk -> Service Desk -> Status Profile -> Change Status Profile for User Status, then choose status profile "SLFN0001" or your customized profile.
"Lowest status no." and "Highest status no." shows which status it can be changed to.
For example, in the following case, you can not change the status from NEW to Confirmed. Also, you can not change it from WIP to NEW. In such cases, target status which you can not change to will be shown as gray in status list.
Status Text low high
10   NEW 10 20
20...WIP    20 40
30...
40   Confirmed 40 40
I hope this could help...
Kobayashi

Query status of support message to define a schedule condition

Similar Messages

Maybe you are looking for