Regarding copying support message

We are using Solution Manager System from maintaining support desk
messages.
In our Solution Manager System using two client i.e. client 100 & 200
for maintaining different division support deak message.
Now, as per requirement we want to close one client & maintain all
messages in one client. But the problem is required all old support
desk messages in one client.
Therefore, pls. suggest how it is possible to copy all the support desk
message from one client to another for viewing purpose.
With Best Regards
Bipin Singh

Hello,
Deactivate Earlier message and activate the one suggested, check if you are using correct application area.
In the case of an error message, processing cannot be continued until user input has been corrected. You can also group the messages according to user classes by saving the messages as different versions.
After having saved the message categories as different versions, you can assign a version to certain users. This results in the same message appearing as an error message for one user, but as warning for another.
regards,
Prashant Rathore.

Similar Messages

Error 513 while creating a support message (related to roles/profiles)

Hello everyone,
my user is getting the generous error 513 while sending a support message either on the SAP GUI or Workcenter. I am trying to implement a profile for a key user, who can display, reply and create simple messages without putting in technical data.
I gave him the following roles:
SAP_SMWORK_INCIDENT_MAN
SAP_SUPPCF_CREATE
SAP_SUPPCF_ADMIN
SAP_SUPPDESK_DISPLAY
SAP_SUPPDESK_CREATE
SAP_SV_FDB_NOTIF_BC_CREATE
and a generous role with the missing parts:
ZSAP_SMWC
When I tried sending a message with the GUI I used SU53 to find out which rights are missing and added them to ZSAP_SMWC. Now I got all of them and the SU53 replies that there are no more missing rights.
Thing is: When I add the profile SAPALL to my user, it works just fine. This is leading me to a problem i can't solve._
I also have to say that I accidently deleted some flags inside of sap_suppcf_create without copying it. Is there a way to restore SAP standard settings?
Thanks in advance,
Hendrik

I just seen the following SAP Knowledge Base Article related to ST 400 SP24:
[1522809 - Solution Manager: Because of error 513, no message was created in Support Desk System|www.service.sap.com/sap/support/notes/1522809 ]
Regards, Ruediger

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

Support Message creation in Satellite System should trigger ZLFN not SLFN

Hi Experts!
I guess (hope) this is a rather simple question but I just can not find the right section in SPRO.
We made a lot of customizing regarding Change Requests and Change Documents (made copies of SDCR and SDMJ). The Support Message (SLFN) has been left unchanged (except copy rules to create ZDCR instead of SDCR)
Soon it might be necessary to change SLFN regarding (adding more Partner Functions and such) so I would like to make a copy to ZLFN and have Solution Manager create ZLFN instead of SLFN when a Support Message is created in satellite system.
Could anyone please tell where to make this setting? Just can not find the right section in customizing!
Thanks a lot.
/cheers

Hi Christian,
Thanks for updating your post.
Could you please confirm the following:
The Transaction Type used in Support Messages created from SolMan is diferent from the Transaction Type used when a message is composed from Satellite Systems ?
Can you please list any additional details missed out in that thread.
Warm regards,
Srini

Support message and change requests only for production system

Hi guys,
I would like to connect the solman helpesk with CHARM ( CHARM is still running ).
In CHARM I have to create a CR only for production system. ( don't know why - but works as designed).
In SAP helpdesk I can create support messages for every kind of system type but if I want to connect both (HD and CR) , the source system (ibase component) of the issue will copied to the CR and runs in error because of the rule (only p-system) of CHARM.
Of course I can change the ibase to production system manually in SDCR but it seems a very error-prone method.
Now my question: is it possible to change the ibase component due to the creation of CR by copy rule or something like this?
Kind regards
Rayko

Hi Rayko,
We do not have this option.
Once in ChaRM, we assume that the changes will always correct an issue in the PROD system.
I would recommend to open the tickets directly with the PROD system IBase, once the issue is also happening there.
Best Regards,
Fernando

Customize Application Component Structure for Support Messages Workcenter

Is it possible to customize the application component structure for creation of support messages via Incident Workcenter (meaning adding own entries to the structure)?
Cheers,
Andy

Hi Andy Rohr
Its always possible. We did our Custom application for Service desk Using Work Centers. We have copied existing SLFN content to ZLFN done changes as per the requirement.
Could you please clarify where exactly your having the issue?
Regards
Bhasakr

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

Create support message in satellite system

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

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

ERROR when Trying to create support message in satellite system

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

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

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

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

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

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

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

In Mail when deleting a file i get this response 68615.emlx" couldn't be copied to "Messages

in Mail when deleting a file i get this response 68615.emlx” couldn’t be copied to “Messages
Donnie
<Edited By Host>

HT2500 Error when deleting email: Apple Support Communities

Service Desk Determination. In the support message Sold to party &

Dear Friends,
Sold to Party , IBASE & Component are not fetching the support message created from Satellite system BI.
I have configured the Service Desk for satellite system ECC 6.0. Now I have configured it to BI, but Sold to party & IBASE & Component are not fetching in the support desk message.
Following things done for adding satellite system BI to Solman.
1) IBase creation for BI is done.
2) SMSY configiration also done for BI
3) BP no created in Solman, mapped identification also.
What else i need to check.
Can anybody tell me which roles I need to assign the BI end users for raising the message. Is this issue related to roles
Regards
PK

Hi,
There are several predefined roles for Support Desk, containing specific authorizations.
Rolle
SAP_SUPPDESK_ADMIN Administrator role for Support Desk. Comprises
authorizations to configure Support Desk
SAP_SUPPDESK_PROCESS Role for processing Support notifications. Comprises all the
authorizations for notification processing and using the Solution Database
SAP_SUPPDESK_DISPLAY General display role, no authorization to create or change
notifications
SAP_SUPPDESK_CREATE Role to create Support notifications. This role must be
assigned to both users who will create notifications in the
SAP Solution Manager and to users who will create
notifications from the satellite systems in the SAP Solution
Manager.
Regards,
Deepanshu

Regarding copying support message

Similar Messages

Maybe you are looking for